[Kernel-packages] [Bug 1755073] Re: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64
This is a regression caused by CONFIG_VMAP_STACK. The driver uses __pa (phys_to_virt) on a stack address which does not work with virtual mapped stacks. To solve this upstream will require a bit more work, I'm attaching a minimal patch to work-around by using kmalloc for the problematic allocation. ** Patch added: "zip.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755073/+attachment/5090802/+files/zip.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755073 Title: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64 Status in linux package in Ubuntu: Confirmed Bug description: This is a POTENTIAL REGRESSION. This test has passed with 4.13.0-36.40, but not 4.13.0-37.42 The test will stuck with error message in dmesg: ubuntu@starmie-kernel:~$ dmesg [ 470.227210] zram: Added device: zram0 [ 472.262544] zram0: detected capacity change from 0 to 134217728 [ 472.396960] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 475.761947] zram0: detected capacity change from 134217728 to 0 [ 476.796641] zram0: detected capacity change from 0 to 134217728 [ 476.909118] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 480.233817] zram0: detected capacity change from 134217728 to 0 [ 481.239001] zram0: detected capacity change from 0 to 134217728 [ 508.079684] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [mkfs.ext4:2253] [ 508.086994] Modules linked in: lz4 lz4_compress zram nls_iso8859_1 thunderx_edac i2c_thunderx thunderx_zip i2c_smbus shpchp cavium_rng_vf cavium_rng gpio_keys ipmi_ssif uio_pdrv_genirq uio ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd [ 508.087138] CPU: 8 PID: 2253 Comm: mkfs.ext4 Not tainted 4.13.0-37-generic #42-Ubuntu [ 508.087141] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 508.087144] task: 801f57a86900 task.stack: 23ec [ 508.087158] PC is at zip_deflate+0x184/0x2e8 [thunderx_zip] [ 508.087164] LR is at zip_deflate+0x17c/0x2e8 [thunderx_zip] [ 508.087167] pc : [] lr : [] pstate: 20400145 [ 508.087169] sp : 23ec3580 [ 508.087171] x29: 23ec3580 x28: [ 508.087177] x27: 801f57a86900 x26: 0001b104 [ 508.087182] x25: 801f5618c000 x24: 801f6a15bc18 [ 508.087188] x23: 1000 x22: 23ec3688 [ 508.087193] x21: 801f5a2d4880 x20: 801f6a15bc18 [ 508.087199] x19: 23ec3608 x18: [ 508.087204] x17: 0001 x16: [ 508.087209] x15: bd4048db x14: fa13 [ 508.087215] x13: 1000 x12: fa12 [ 508.087220] x11: x10: [ 508.087225] x9 : x8 : [ 508.087230] x7 : x6 : 8000101d6080 [ 508.087236] x5 : 01a69058 x4 : 0008 [ 508.087241] x3 : x2 : [ 508.087246] x1 : 801f6a15be08 x0 : [ 508.087252] Call trace: [ 508.087256] Exception stack(0x23ec3440 to 0x23ec3580) [ 508.087260] 3440: 801f6a15be08 [ 508.087264] 3460: 0008 01a69058 8000101d6080 [ 508.087268] 3480: [ 508.087272] 34a0: fa12 1000 fa13 bd4048db [ 508.087276] 34c0: 0001 23ec3608 [ 508.087280] 34e0: 801f6a15bc18 801f5a2d4880 23ec3688 1000 [ 508.087284] 3500: 801f6a15bc18 801f5618c000 0001b104 801f57a86900 [ 508.087288] 3520: 23ec3580 01a69614 23ec3580 [ 508.087292] 3540: 01a6961c 20400145 801f5a2d4880 23ec3688 [ 508.087297] 3560: 801f6a15bc18 23ec3580 01a6961c [ 508.087304] [] zip_deflate+0x184/0x2e8 [thunderx_zip] [ 508.087311] [] zip_compress+0xd8/0x158 [thunderx_zip] [ 508.087317] [] zip_comp_compress+0x48/0x60 [thunderx_zip] [ 508.087325] [] crypto_comp
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
At the time Colin and I discussed getting thunderbolt-tools into Debian and then eventually into Ubuntu (& of course main via this MIR) bolt's GUI wasn't available yet and bolt was still under some pretty heavy development. >From a client (general purpose laptop or desktop) system perspective it's better to offer something with a GUI, but there are other features that thunderbolt-tools offers that aren't in bolt as well. For example thunderbolt-tools provides some udev rules to assist with starting up thunderbolt networking in the proper situations and recently adopted some features for controlling what happens with the boot time ACL. They are both great solutions that will continue to adopt different features at a different rate. My opinion is that both should be offered in main, but bolt and bolt GUI should probably be the one that gets seeded for Ubuntu desktop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this re
[Kernel-packages] [Bug 1752437] Re: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work
This is the reason why your touchpad doesn't work: [0.948213] amd_gpio AMDI0030:00: Failed to get gpio IRQ: -22 [0.948487] amd_gpio: probe of AMDI0030:00 failed with error -22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux package in Ubuntu: Confirmed Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755839] Re: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I cannot confirm that for my installation: $ sudo apt-get upgrade -f [sudo] password for s: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up linux-image-4.13.0-37-generic (4.13.0-37.42) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-4.13.0-37-generic vmlinuz(/boot/vmlinuz-4.13.0-37-generic ) points to /boot/vmlinuz-4.13.0-37-generic (/boot/vmlinuz-4.13.0-37-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-37-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-37-generic /boot/vmlinuz-4.13.0-37-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-37-generic /boot/vmlinuz-4.13.0-37-generic there it is hanging now for some half an hour -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755839 Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: Ran software update, which hung on DKMS processing for linux kernel upgrade ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1410 F pulseaudio mgann 1799 F pulseaudio Date: Wed Mar 14 10:16:22 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-03-09 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=4214ac83-5fc5-473a-a9ea-0f7b7c7a9291 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD 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/1755839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737890] Re: QCA Rome bluetooth can not wakeup after USB runtime suspended.
Verified on OptiPlex 3060, BT works fine after suspend/resume. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737890 Title: QCA Rome bluetooth can not wakeup after USB runtime suspended. Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: == SRU Justification == [Impact] Some QCA ROME bluetooth devices does not work after runtime suspended. [Fix] Latest mainline does not have this issue. The bisected commit is a0085f2510e8976614ad8f766b209448b385492f "Bluetooth: btusb: driver to enable the usb-wakeup feature". With this commit, the BT device now can wake host controller up. [Test] Cherry-picked the commit into Artful/OEM kernel and the issue is fixed. [Regression Potential] Low. usb-wakeup support shouldn't affect the driver's function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
The fix works as expected, thanks. ** Tags removed: verification-needed verification-needed-artful ** Tags added: verification-done verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in lttng-modules source package in Xenial: In Progress Status in linux source package in Artful: Invalid Status in lttng-modules source package in Artful: Fix Committed Status in linux source package in Bionic: Invalid Status in lttng-modules source package in Bionic: Fix Released Bug description: [Impact] * The 4.13.0-38 artful kernel included a change (backported from 4.15) that modifies the definition of kvm_mmio(). This breaks the lttng-modules-dkms package because it is using the old (<4.15) definition. * lttng-modules-dkms already has a list of kernel version "exceptions" with which it uses the >=4.15 definition. Proposed solution is to add the Ubuntu kernel range 4.13.0-38 up to 4.14.255-255 to that list of exceptions. [Test Case] * Tested by first successfully building lttng-modules-dkms on 4.13.0-37, then reproducing the problem described here on 4.13.0-38, then applying the code-change and confirming that I can successfully build on both 4.13.0-37 and 4.13.0-38 after that. [Regression Potential] * Low-regression potential. Could prevent lttng-modules-dkms from being built for specific kernel versions, but this is unlikely as the change was tested to confirm that it works as expected on 4.13.0-37 and 4.13.0-38 - and should work fine for other Ubuntu kernels as well. The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755762] Re: linux: 4.13.0-38.43 -proposed tracker
The lttng module build issue (bug 1756240) has been solved. So the only concern is the zram smoke test for ThunderX (bug 1758036) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755762 Title: linux: 4.13.0-38.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 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 backports: bug 1755767 (linux-hwe), bug 1755769 (linux-azure-edge), bug 1755771 (linux-gcp), bug 1755773 (linux-azure), bug 1755774 (linux-oem) derivatives: bug 1755765 (linux-raspi2) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755839] Re: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
The hanging issue has been fixed somehow. And I can run update and upgrade. Even reboot is fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755839 Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: Ran software update, which hung on DKMS processing for linux kernel upgrade ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1410 F pulseaudio mgann 1799 F pulseaudio Date: Wed Mar 14 10:16:22 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-03-09 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: ASUSTeK COMPUTER INC. GL703VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=4214ac83-5fc5-473a-a9ea-0f7b7c7a9291 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.13.0-37-generic 4.13.0-37.42 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD 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/1755839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756070] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557]
Issue started after one of the updates. Prior kernel version difficult to pinpoint, since the bug seems to happen only after cold boots, not after a warm boot. WORKAROUND: Start computer, restart after boot process completed. 4.16rc4 didn't show the symptoms, but was unusable since zfs is missing from it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756070 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557] Status in linux package in Ubuntu: Confirmed Bug description: after startup ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm5288 F pulseaudio erik 7152 F pulseaudio /dev/snd/controlC0: gdm5288 F pulseaudio erik 7152 F pulseaudio Date: Wed Mar 14 20:10:57 2018 Failure: oops HibernationDevice: RESUME=UUID=fb731a76-d649-4283-9a48-91fda418f5d4 InstallationDate: Installed on 2018-02-25 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) IwConfig: enp3s0no wireless extensions. lono wireless extensions. enp8s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=269d199c-0dea-47bc-89fb-5388d4361c0e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [Xorg:5557] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U1n dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68X-UD3H-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. 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: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] Re: Wifi-connection constantly disconnecting and then reconnecting
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755073] Re: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755073 Title: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64 Status in linux package in Ubuntu: Confirmed Bug description: This is a POTENTIAL REGRESSION. This test has passed with 4.13.0-36.40, but not 4.13.0-37.42 The test will stuck with error message in dmesg: ubuntu@starmie-kernel:~$ dmesg [ 470.227210] zram: Added device: zram0 [ 472.262544] zram0: detected capacity change from 0 to 134217728 [ 472.396960] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 475.761947] zram0: detected capacity change from 134217728 to 0 [ 476.796641] zram0: detected capacity change from 0 to 134217728 [ 476.909118] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 480.233817] zram0: detected capacity change from 134217728 to 0 [ 481.239001] zram0: detected capacity change from 0 to 134217728 [ 508.079684] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [mkfs.ext4:2253] [ 508.086994] Modules linked in: lz4 lz4_compress zram nls_iso8859_1 thunderx_edac i2c_thunderx thunderx_zip i2c_smbus shpchp cavium_rng_vf cavium_rng gpio_keys ipmi_ssif uio_pdrv_genirq uio ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd [ 508.087138] CPU: 8 PID: 2253 Comm: mkfs.ext4 Not tainted 4.13.0-37-generic #42-Ubuntu [ 508.087141] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 508.087144] task: 801f57a86900 task.stack: 23ec [ 508.087158] PC is at zip_deflate+0x184/0x2e8 [thunderx_zip] [ 508.087164] LR is at zip_deflate+0x17c/0x2e8 [thunderx_zip] [ 508.087167] pc : [] lr : [] pstate: 20400145 [ 508.087169] sp : 23ec3580 [ 508.087171] x29: 23ec3580 x28: [ 508.087177] x27: 801f57a86900 x26: 0001b104 [ 508.087182] x25: 801f5618c000 x24: 801f6a15bc18 [ 508.087188] x23: 1000 x22: 23ec3688 [ 508.087193] x21: 801f5a2d4880 x20: 801f6a15bc18 [ 508.087199] x19: 23ec3608 x18: [ 508.087204] x17: 0001 x16: [ 508.087209] x15: bd4048db x14: fa13 [ 508.087215] x13: 1000 x12: fa12 [ 508.087220] x11: x10: [ 508.087225] x9 : x8 : [ 508.087230] x7 : x6 : 8000101d6080 [ 508.087236] x5 : 01a69058 x4 : 0008 [ 508.087241] x3 : x2 : [ 508.087246] x1 : 801f6a15be08 x0 : [ 508.087252] Call trace: [ 508.087256] Exception stack(0x23ec3440 to 0x23ec3580) [ 508.087260] 3440: 801f6a15be08 [ 508.087264] 3460: 0008 01a69058 8000101d6080 [ 508.087268] 3480: [ 508.087272] 34a0: fa12 1000 fa13 bd4048db [ 508.087276] 34c0: 0001 23ec3608 [ 508.087280] 34e0: 801f6a15bc18 801f5a2d4880 23ec3688 1000 [ 508.087284] 3500: 801f6a15bc18 801f5618c000 0001b104 801f57a86900 [ 508.087288] 3520: 23ec3580 01a69614 23ec3580 [ 508.087292] 3540: 01a6961c 20400145 801f5a2d4880 23ec3688 [ 508.087297] 3560: 801f6a15bc18 23ec3580 01a6961c [ 508.087304] [] zip_deflate+0x184/0x2e8 [thunderx_zip] [ 508.087311] [] zip_compress+0xd8/0x158 [thunderx_zip] [ 508.087317] [] zip_comp_compress+0x48/0x60 [thunderx_zip] [ 508.087325] [] crypto_compress+0x50/0x68 [ 508.087336] [] zcomp_compress+0x48/0x58 [zram] [ 508.087343] [] zram_bvec_rw.isra.18+0x21c/0x660 [zram] [ 508.087350] [] zram_make_request+0x13c/0x360 [zram] [ 508.087356] [] generic_make_request+0xf4/0x290 [ 508.087360] [] submit_bio+0x5c/0x198 [ 508.087367] [] submit_bh_wbc+0x14c/0x1a0 [ 508.087371] [] __block_write_full_page+0x21c/0x3b0 [ 508.087375] [] block_write_f
[Kernel-packages] [Bug 1758017] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1758017 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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-144.193 /trusty-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-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/1755227 Title: linux: 3.13.0-144.193 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 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 backports: bug 1755228 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
Can you find the first v4.16-rc* that fixes this issue? We need to backport the fix to Bionic's 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bug
[Kernel-packages] [Bug 1718293] Re: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel
To sum it up: - the feature is integrated in 18.04 - we have skiboot | 5.10~rc4-1 in 18.04 - it was successfully tested on 18.04 - and the targetmilestone was recently changed from 1710 to 1804 (the title is still 17.10) So if I interpret all this correctly the ticket is correctly marked as Fix Released and an additional ticket doesn't need to be opened, because the target release for Power 9 is 18.04 anyway? Please confirm - thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1718293 Title: [Ubuntu 17.10] POWER9 - Base - Integrate P9 VAS (Virtual Accelerator Switchboard) support in kernel Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This feature request is used to submit kernel changes needed for adding VAS (Virtual Accelerator Switchboard) support. VAS interface allows kernel or user space to communicate with any accelerator (Ex: NX). kernel changes will be to open a window/ channel with accelerator and communicate with copy / paste facility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1718293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658733] Update Released
The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter Status in The Ubuntu-power-systems project: Fix Committed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Trusty: Invalid Status in makedumpfile source package in Trusty: Invalid Status in kexec-tools source package in Xenial: Invalid Status in makedumpfile source package in Xenial: Fix Released Status in kexec-tools source package in Zesty: Invalid Status in makedumpfile source package in Zesty: Invalid Status in kexec-tools source package in Artful: Invalid Status in makedumpfile source package in Artful: Fix Released Status in kexec-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, some interrupts are missed, and dumping the crash will fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix this. [Test Case] Setting up kdump to target a virtio-scsi device on a Power System. [Regression Potential] The parameter could be interpreted differently on a different platform and kdump would fail. However, it has been verified that no other platform uses such parameter. If another parameter would have been incorrectly removed on the patch, kdump could fail on other systems. == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot
This bug was fixed in the package makedumpfile - 1:1.6.1-2ubuntu0.1 --- makedumpfile (1:1.6.1-2ubuntu0.1) artful; urgency=medium * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's only used by ppc64el, it's not required to be conditionally added. (LP: #1658733) * Set crashkernel for ppc64el to load at 128M instead of 32M. That allows larger kernels to boot. (LP: #1728115) -- Thadeu Lima de Souza Cascardo Tue, 07 Nov 2017 12:23:33 + ** Changed in: makedumpfile (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Artful: New Status in makedumpfile source package in Artful: Fix Released Status in linux source package in Bionic: Incomplete Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745636] Re: RT3290 Wireless 802.11n 1T/1R PCIe don't work.
Wondering if this is a regression? Can you try older kernel like v4.4? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745636 Title: RT3290 Wireless 802.11n 1T/1R PCIe don't work. Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hello, I just installed the Ubuntu 17.10 and my wifi doesn't work properly. I can't enable it through the GUI. Sorry about my poor report, I don't have to much detail and English is not primary language. The wifi switch button on the keyboard is always with the red light and I can't change it by pressing. Release: 17.10 $ networkctl status wlo1 results: ● 2: wlo1 Link File: /lib/systemd/network/99-default.link Network File: n/a Type: wlan State: off (unmanaged) Path: pci-:08:00.0 Driver: rt2800pci Vendor: Ralink corp. Model: RT3290 Wireless 802.11n 1T/1R PCIe HW Address: 80:56:f2:cb:11:cf (Hon Hai Precision Ind. Co.,Ltd.) rfkill list all results: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes iwconfig results: wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=off Retry short long limit:2 RTS thr:off Fragment thr:off Power Management:off --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolgan 1243 F pulseaudio /dev/snd/controlC0: wolgan 1243 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=e60841e9-9fed-4e91-bf62-d6029c92982d InstallationDate: Installed on 2018-02-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=72c69e56-63ac-45d7-849c-1455f96f7d8e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.71 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.42 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr088110305E1610100:rvnHewlett-Packard:rn2162:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.version: 088110305E1610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728115] Update Released
The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Artful: New Status in makedumpfile source package in Artful: Fix Released Status in linux source package in Bionic: Incomplete Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter
This bug was fixed in the package makedumpfile - 1:1.6.1-2ubuntu0.1 --- makedumpfile (1:1.6.1-2ubuntu0.1) artful; urgency=medium * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's only used by ppc64el, it's not required to be conditionally added. (LP: #1658733) * Set crashkernel for ppc64el to load at 128M instead of 32M. That allows larger kernels to boot. (LP: #1728115) -- Thadeu Lima de Souza Cascardo Tue, 07 Nov 2017 12:23:33 + ** Changed in: makedumpfile (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter Status in The Ubuntu-power-systems project: Fix Committed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Trusty: Invalid Status in makedumpfile source package in Trusty: Invalid Status in kexec-tools source package in Xenial: Invalid Status in makedumpfile source package in Xenial: Fix Released Status in kexec-tools source package in Zesty: Invalid Status in makedumpfile source package in Zesty: Invalid Status in kexec-tools source package in Artful: Invalid Status in makedumpfile source package in Artful: Fix Released Status in kexec-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, some interrupts are missed, and dumping the crash will fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix this. [Test Case] Setting up kdump to target a virtio-scsi device on a Power System. [Regression Potential] The parameter could be interpreted differently on a different platform and kdump would fail. However, it has been verified that no other platform uses such parameter. If another parameter would have been incorrectly removed on the patch, kdump could fail on other systems. == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount
[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04
Shankey, can you find the first bad -rc* kernel? It's easier to bisect if we can minimize the bisection range first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577140 Title: Wifi Ralink R3290 disabled by default in ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I have my personal laptop and it contains PCI Ralink r3290 wifi adaptor with bluetooth and when i have installed the fresh version of Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is disabled by default and the it doesn’t activates even by pressing the key and when i go the network settings airplane mode is also enabled and when i try to disable airplane mode it switches back on. I dont know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have tried almost every solution and none works in the latest LTS release. Please help I am unable to use internet in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shankey1536 F pulseaudio /dev/snd/controlC1: shankey1536 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 17:02:12 2016 HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6 InstallationDate: Installed on 2016-04-24 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard Compaq 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.39 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.52 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.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Compaq 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758856] [NEW] retpoline hints: primary infrastructure
Public bug reported: Tracking bug for the application of the retpoline hint tracking support. We are having terrible trouble with hints changing on every build. Upstream is moving to hinting those indirections which have been reviewed and are good. This includes direct hinting of PVOPS and the like which are the ones which change all the time as new ones appear and dissappear. Backport the hint support and add our own bespoke checkers against this data. ** Affects: linux (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Description changed: Tracking bug for the application of the retpoline hint tracking support. + + We are having terrible trouble with hints changing on every build. + Upstream is moving to hinting those indirections which have been + reviewed and are good. This includes direct hinting of PVOPS and the + like which are the ones which change all the time as new ones appear and + dissappear. + + Backport the hint support and add our own bespoke checkers against this + data. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758856 Title: retpoline hints: primary infrastructure Status in linux package in Ubuntu: Confirmed Bug description: Tracking bug for the application of the retpoline hint tracking support. We are having terrible trouble with hints changing on every build. Upstream is moving to hinting those indirections which have been reviewed and are good. This includes direct hinting of PVOPS and the like which are the ones which change all the time as new ones appear and dissappear. Backport the hint support and add our own bespoke checkers against this data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090941/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090943/+files/IpAddr.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090942/+files/Dependencies.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090940/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] Re: Wifi-connection constantly disconnecting and then reconnecting
apport information ** Tags added: apport-collected ** Description changed: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled + --- + ApportVersion: 2.20.8-0ubuntu10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lasse 1308 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2018-03-14 (11 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) + IpRoute: + default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp1s0 scope link metric 1000 + 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 + MachineType: HP HP EliteBook Folio 1040 G3 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + Package: network-manager 1.10.4-1ubuntu3 + PackageArchitecture: amd64 + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-12-generic N/A + linux-backports-modules-4.15.0-12-generic N/A + linux-firmware 1.173 + Tags: bionic wayland-session wayland-session + Uname: Linux 4.15.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/15/2016 + dmi.bios.vendor: HP + dmi.bios.version: N83 Ver. 01.05 + dmi.board.name: 80FA + dmi.board.vendor: HP + dmi.board.version: KBC Version 01.38 + dmi.chassis.asset.tag: 5CD6357XVL + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: + dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO + dmi.product.name: HP EliteBook Folio 1040 G3 + dmi.sys.vendor: HP + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.10.4 connected started full enabled enabled enabled enabled enabled ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090939/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdo
[Kernel-packages] [Bug 1758017] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090945/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090947/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090944/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090946/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090953/+files/PciNetwork.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090954/+files/ProcCpuinfoMinimal.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090957/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090956/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090955/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090958/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090961/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] NetDevice.wlp1s0.txt
apport information ** Attachment added: "NetDevice.wlp1s0.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090951/+files/NetDevice.wlp1s0.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] NetDevice.enp0s31f6.txt
apport information ** Attachment added: "NetDevice.enp0s31f6.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090949/+files/NetDevice.enp0s31f6.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090962/+files/nmcli-con.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090950/+files/NetDevice.lo.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] NetDevice.enp0s20f0u3c2.txt
apport information ** Attachment added: "NetDevice.enp0s20f0u3c2.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090948/+files/NetDevice.enp0s20f0u3c2.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090952/+files/NetworkManager.conf.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743091] Re: Xubuntu 17.10 (32 bits)
Sorry I have not tested the new kernel because I fixed the issue on 5th feb 2018 this way: "How I have get out the issue : by restoring the previous Linux Kernel (from the GRUB menu)." Then the Ubuntu auto-update system did some upgrades, and all is working fine since then: uname -a Linux HP-Compaq-6730s 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:35 UTC 2017 i686 i686 i686 GNU/Linux Today I use a more recent kernel and booting is OK too: Linux HP-Compaq-6730s 4.10.0-42-generic #46-Ubuntu SMP Mon Dec 4 14:36:05 UTC 2017 i686 i686 i686 GNU/Linux Perhaps the issue was related to some error on the storage (it's a old 32 GB SSD, that is OK according to the SMART values). I am sorry to have not tested the v4.15 kernel[0], this is because I have access to this computer only every 3 or 6 months. If this is still useful I may do the test in the next 6 months. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743091 Title: Xubuntu 17.10 (32 bits) Status in linux package in Ubuntu: Expired Bug description: Bug ticket opened after I asked this question : https://answers.launchpad.net/ubuntu/+source/linux- meta/+question/663037 $ cat /proc/version_signature Ubuntu 4.13.0-21.24-generic 4.13.13 $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Memory Controller Hub [103c:30e8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30e8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 6.500W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt+ HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 41e1 Capabilities: [90] Subsystem: Device [:] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status:NegoPending- InProgress- Capabilities: [180 v1] Root Complex Link Desc: PortNumber=01 ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed1c000 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB
[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk
Since this update is lingering in -proposed for so long, assuming from #36 context (and earlier #35 notice) that the xenial-proposed version of the package has been used. Also, the package was in -proposed for so long that if there were regressions we would have known by now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu:talclp1: Kdump failed with multipath disk Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in makedumpfile source package in Trusty: Confirmed Status in linux source package in Xenial: New Status in makedumpfile source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in makedumpfile source package in Zesty: Won't Fix Bug description: [Impact] When the target device where to dump the kernel is under a multipath configuration, dumping will fail, possibly leaving the system stuck in the kdump kernel. The fix is to include some scsi device handlers needed for the multipath setup inside the initramfs image that is used by kdump. All modules currently loaded in the system are included. [Test Case] Setting up kdump to target a multipath device using an appropriate storage that requires such scsi_dh modules and triggering a crash will demonstrate that kdump fails. After the fix, it works fine. [Regression Potential] If a bug is introduced, loading kdump might fail, and a crash will not be generated. A worse regression that might be considered is the system is stuck in such a kdump kernel and needs to be rebooted locally (and the crash file is not generated either). But since this is what we are trying to fix, we don't expect other systems to break. This didn't happen on a small (less than 1GiB of RAM) x86 VM, though. Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033 CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_sysrq_trigger+0x78/0xa0 [ 132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110 [ 132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0 [ 132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240 [ 132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110 [ 132.643957] [c000d
[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.6 --- makedumpfile (1:1.5.9-5ubuntu0.6) xenial; urgency=medium * d/kernel-postinst-generate-initrd : Add scsi_dh_* modules if in use so the system can dump a crash when root is on multipath (LP: #1635597) (Closes: 862411) * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's only used by ppc64el, it's not required to be conditionally added. (LP: #1658733) -- Thadeu Lima de Souza Cascardo Tue, 29 Aug 2017 16:56:04 -0300 ** Changed in: makedumpfile (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu:talclp1: Kdump failed with multipath disk Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in makedumpfile source package in Trusty: Confirmed Status in linux source package in Xenial: New Status in makedumpfile source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in makedumpfile source package in Zesty: Won't Fix Bug description: [Impact] When the target device where to dump the kernel is under a multipath configuration, dumping will fail, possibly leaving the system stuck in the kdump kernel. The fix is to include some scsi device handlers needed for the multipath setup inside the initramfs image that is used by kdump. All modules currently loaded in the system are included. [Test Case] Setting up kdump to target a multipath device using an appropriate storage that requires such scsi_dh modules and triggering a crash will demonstrate that kdump fails. After the fix, it works fine. [Regression Potential] If a bug is introduced, loading kdump might fail, and a crash will not be generated. A worse regression that might be considered is the system is stuck in such a kdump kernel and needs to be rebooted locally (and the crash file is not generated either). But since this is what we are trying to fix, we don't expect other systems to break. This didn't happen on a small (less than 1GiB of RAM) x86 VM, though. Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033 CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_
[Kernel-packages] [Bug 1635597] Update Released
The verification of the Stable Release Update for makedumpfile has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu:talclp1: Kdump failed with multipath disk Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in makedumpfile source package in Trusty: Confirmed Status in linux source package in Xenial: New Status in makedumpfile source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in makedumpfile source package in Zesty: Won't Fix Bug description: [Impact] When the target device where to dump the kernel is under a multipath configuration, dumping will fail, possibly leaving the system stuck in the kdump kernel. The fix is to include some scsi device handlers needed for the multipath setup inside the initramfs image that is used by kdump. All modules currently loaded in the system are included. [Test Case] Setting up kdump to target a multipath device using an appropriate storage that requires such scsi_dh modules and triggering a crash will demonstrate that kdump fails. After the fix, it works fine. [Regression Potential] If a bug is introduced, loading kdump might fail, and a crash will not be generated. A worse regression that might be considered is the system is stuck in such a kdump kernel and needs to be rebooted locally (and the crash file is not generated either). But since this is what we are trying to fix, we don't expect other systems to break. This didn't happen on a small (less than 1GiB of RAM) x86 VM, though. Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033 CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_sysrq_trigger+0x78/0xa0 [ 132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110 [ 132.643941] [c000d82e3d50] [c030fc3c] __vfs_wri
[Kernel-packages] [Bug 1758017] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090963/+files/nmcli-dev.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758017] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090959/+files/RfKill.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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.6 --- makedumpfile (1:1.5.9-5ubuntu0.6) xenial; urgency=medium * d/kernel-postinst-generate-initrd : Add scsi_dh_* modules if in use so the system can dump a crash when root is on multipath (LP: #1635597) (Closes: 862411) * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's only used by ppc64el, it's not required to be conditionally added. (LP: #1658733) -- Thadeu Lima de Souza Cascardo Tue, 29 Aug 2017 16:56:04 -0300 ** Changed in: makedumpfile (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04 KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter Status in The Ubuntu-power-systems project: Fix Committed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Trusty: Invalid Status in makedumpfile source package in Trusty: Invalid Status in kexec-tools source package in Xenial: Invalid Status in makedumpfile source package in Xenial: Fix Released Status in kexec-tools source package in Zesty: Invalid Status in makedumpfile source package in Zesty: Invalid Status in kexec-tools source package in Artful: Invalid Status in makedumpfile source package in Artful: Fix Released Status in kexec-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released Bug description: [Impact] On Power Systems, some interrupts are missed, and dumping the crash will fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix this. [Test Case] Setting up kdump to target a virtio-scsi device on a Power System. [Regression Potential] The parameter could be interpreted differently on a different platform and kdump would fail. However, it has been verified that no other platform uses such parameter. If another parameter would have been incorrectly removed on the patch, kdump could fail on other systems. == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-
[Kernel-packages] [Bug 1758017] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1758017/+attachment/5090960/+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/1758017 Title: Wifi-connection constantly disconnecting and then reconnecting Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: On HP Elitebook Folio 1040 G3, the WiFi-connection is going constantly up and down, ever since I migrated from 17.10. System is constantly pushing notifications about disconnects, and then it reconnects. The signal is not very strong here, but I never saw this with Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 12:27:27 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lasse 1308 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-14 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.215 metric 600 MachineType: HP HP EliteBook Folio 1040 G3 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.4-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=8db50b20-626a-49a7-90f2-09b51757c80d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 Tags: bionic wayland-session wayland-session Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2016 dmi.bios.vendor: HP dmi.bios.version: N83 Ver. 01.05 dmi.board.name: 80FA dmi.board.vendor: HP dmi.board.version: KBC Version 01.38 dmi.chassis.asset.tag: 5CD6357XVL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN83Ver.01.05:bd06/15/2016:svnHP:pnHPEliteBookFolio1040G3:pvr:rvnHP:rn80FA:rvrKBCVersion01.38:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP EliteBook Folio 1040 G3 dmi.sys.vendor: HP nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail
Should this bug be switched to verification-failed-xenial in that case? What is the status of this SRU? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Xenial: Fix Committed Bug description: [Impact] When the Bluetooth adapter is not powered on it is not possible to use it in normal way. We used to have a hack to force powering on by using an udev rule but this doe snot work anymore. Luckily the BlueZ has introduced "AutoEnable" option that makes the stack power on adapters by itself. Backporting this to xenial will improve life of the desktop users and will not require them to hack the solution on their own. The fix itself uses the well known solution to this problem that is floating around there for a while. The upload fixes the bug by enabling the 'AutoEnable' option in the bluetoothd config file. [Original Report] . 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 [Test Case] On xenial install from ppa: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez Now reboot the machine. The BT adapter shall be powered on. [Regression Potential] If things go wrong the adapter will not be powered on after the system boots up. Therefore while testing please focus on the adapter state, i.e. powered on or off. [Other Info] This fix is included in the development release, see: http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22 [What to upload] For xenial as in: ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez ) https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743091] Re: Xubuntu 17.10 (32 bits)
Oops, I wrote a mistake: v4.10.0-42 is not more recent than v4.13.0-21 So I decided to take time to test your kernel. For my first time I upgraded the kernel 'manually': v4.15-rc8 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc8/ After booting (and the GRUB menu) I get a reboot before 2 seconds (after GRUB, on the next screen I only see the 2nd text line then the computer reboot). ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743091 Title: Xubuntu 17.10 (32 bits) Status in linux package in Ubuntu: Expired Bug description: Bug ticket opened after I asked this question : https://answers.launchpad.net/ubuntu/+source/linux- meta/+question/663037 $ cat /proc/version_signature Ubuntu 4.13.0-21.24-generic 4.13.13 $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Memory Controller Hub [103c:30e8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30e8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 6.500W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt+ HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 41e1 Capabilities: [90] Subsystem: Device [:] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status:NegoPending- InProgress- Capabilities: [180 v1] Root Complex Link Desc: PortNumber=01 ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed1c000 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: C
[Kernel-packages] [Bug 1757021] Re: ubuntu restarts on resume from hibernate
Will do (soon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757021 Title: ubuntu restarts on resume from hibernate Status in linux package in Ubuntu: Confirmed Bug description: Whenever I sleep the computer, upon waking/opening the lid, it reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm, adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to /etc/default/grub. Nothing seems to help. I believe this started after updating to 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 1809 F pulseaudio /dev/snd/controlC0: eric 1809 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 20:50:52 2018 HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691 InstallationDate: Installed on 2017-05-29 (294 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 7352 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0H9K1J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08: dmi.product.name: Inspiron 7352 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743091] Re: Xubuntu 17.10 (32 bits)
Tag 'kernel-bug-exists-upstream' added. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743091 Title: Xubuntu 17.10 (32 bits) Status in linux package in Ubuntu: Expired Bug description: Bug ticket opened after I asked this question : https://answers.launchpad.net/ubuntu/+source/linux- meta/+question/663037 $ cat /proc/version_signature Ubuntu 4.13.0-21.24-generic 4.13.13 $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Memory Controller Hub [103c:30e8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30e8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 6.500W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt+ HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 41e1 Capabilities: [90] Subsystem: Device [:] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status:NegoPending- InProgress- Capabilities: [180 v1] Root Complex Link Desc: PortNumber=01 ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed1c000 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <256ns, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActi
[Kernel-packages] [Bug 1511019] Re: Ubuntu 15.10 freezes occasionally
Me too on Dell Latitude E5450. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1511019 Title: Ubuntu 15.10 freezes occasionally Status in linux package in Ubuntu: Incomplete Bug description: Lenovo G50-30 WIly 15.10 freezes! More often when I use touchpad, less with a mouse. Always freezes when streaming a video from youtube in the browser or Totem player. Keyboard is inactive after the freeze so nothing helps only reboot. Also happened in 15.04. After several reboots like that it's impossible to switch off the laptop from OS interface - it hangs on and on and I finally have to press switch-off button. WORKAROUND: Use kernel boot parameter: intel_idle.max_cstate=1 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scani 1445 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 28 18:16:52 2015 HibernationDevice: RESUME=UUID=a94e1d4b-d122-47cb-86a9-9090d0b0bda4 InstallationDate: Installed on 2015-10-24 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80G0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8af48aa3-e87a-482f-9e46-6d3ca072423d ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743529] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2018-03-26 06:13 EDT--- Hi, Verified issue with latest ubunu1804 daily build kernel and now not seeing problem with triggering crash with below levels root@whip:~# dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.16-1ubuntu1 ppc64el tools to support fast kexec reboots root@whip:~# dpkg -l | grep makedumpfile ii makedumpfile1:1.6.3-1 ppc64el VMcore extraction tool root@whip:~# uname -a Linux whip 4.15.0-12-generic #13 SMP Thu Mar 22 07:28:54 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux Triggered crash: * root@whip:/etc/default/grub.d# echo c > /proc/sysrq-trigger [ 183.215596] sysrq: SysRq : This sysrq operation is disabled. root@whip:/etc/default/grub.d# echo 1 > /proc/sys/kernel/sysrq root@whip:/etc/default/grub.d# echo c > /proc/sysrq-trigger [ 210.082354] sysrq: SysRq : Trigger a crash [ 210.082396] Unable to handle kernel paging request for data at address 0x [ 210.082518] Faulting instruction address: 0xc07ec4e8 [ 210.082581] Oops: Kernel access of bad area, sig: 11 [#1] [ 210.082646] LE SMP NR_CPUS=2048 NUMA PowerNV [ 210.082713] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) ofpart cmdlinepart vmx_crypto powernv_flash mtd idt_89hpesx crct10dif_vpmsum ipmi_powernv ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio opal_prd ibmpowernv binfmt_misc nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) mlx5_core(OE) nouveau mlxfw(OE) devlink mlx_compat(OE) lpfc ast i2c_algo_bit ttm drm_kms_helper nvmet_fc syscopyarea nvmet cxl sysfillrect sysimgblt nvme_fc fb_sys_fops ahci nvme_fabrics crc32c_vpmsum drm tg3 pnv_php [ 210.083672] libahci scsi_transport_fc [ 210.083722] CPU: 10 PID: 5235 Comm: bash Tainted: G OE 4.15.0-12-generic #13 [ 210.083792] NIP: c07ec4e8 LR: c07ed428 CTR: c07ec4c0 [ 210.083895] REGS: c07fb73279f0 TRAP: 0300 Tainted: G OE (4.15.0-12-generic) [ 210.084027] MSR: 90009033 CR: 2822 XER: 2004 [ 210.084154] CFAR: c07ed424 DAR: DSISR: 4200 SOFTE: 1 [ 210.084154] GPR00: c07ed428 c07fb7327c70 c16eaf00 0063 [ 210.084154] GPR04: c07fdeb7ce18 c07fdeb94368 90009033 000a [ 210.084154] GPR08: 0007 0001 90001003 [ 210.084154] GPR12: c07ec4c0 c3266e00 0f1697af6b08 [ 210.084154] GPR16: 0f167ebce9f0 0f167ec61998 0f167ec619d0 0f167ec98204 [ 210.084154] GPR20: 0001 7fffc5069ac4 [ 210.084154] GPR24: 7fffc5069ac0 0f167ec9afc4 c15e9968 0002 [ 210.084154] GPR28: 0063 0007 c1572a9c c15e9d08 [ 210.085152] NIP [c07ec4e8] sysrq_handle_crash+0x28/0x30 [ 210.085269] LR [c07ed428] __handle_sysrq+0xf8/0x2c0 [ 210.085328] Call Trace: [ 210.085378] [c07fb7327c70] [c07ed408] __handle_sysrq+0xd8/0x2c0 (unreliable) [ 210.085482] [c07fb7327d10] [c07edc34] write_sysrq_trigger+0x64/0x90 [ 210.085584] [c07fb7327d40] [c047de88] proc_reg_write+0x88/0xd0 [ 210.085673] [c07fb7327d70] [c03d11bc] __vfs_write+0x3c/0x70 [ 210.085751] [c07fb7327d90] [c03d1418] vfs_write+0xd8/0x220 [ 210.085824] [c07fb7327de0] [c03d1738] SyS_write+0x68/0x110 [ 210.085941] [c07fb7327e30] [c000b184] system_call+0x58/0x6c [ 210.086030] Instruction dump: [ 210.086067] 4bfff9f1 4bfffe50 3c4c00f0 3842ea40 7c0802a6 6000 3921 3d42001c [ 210.086185] 394a6db0 912a 7c0004ac 3940 <992a> 4e800020 3c4c00f0 3842ea10 [ 210.086293] ---[ end trace 2141bc6e05b3cc02 ]--- [ 211.090273] 211.090393] Sending IPI to other CP[ 373.057331960,5] OPAL: Switch to big-endian OS Us [ 211.12[ 377.207676398,5] OPAL: Switch to little-endian OS 0361] IPI complete [ 213.393057] kexec: Starting switchover sequence. [1.295245] i ntegrity: Unable to open file: / etc/keys/x509_im a.der (-2) [1.295249] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.353447] vio vio: uevent: failed to send synthetic uevent [2.089461] nouveau 0004:04:00.0: unknown chipset (14a1) [2.131257] nouveau 0004:05:00.0: unknown chipset (14a1) [2.131538] nouveau 0035:03:00.0: unknown chipset (14a1) [2.131664] nouveau 0035:04:00.0: unknown chipset (14a1) /dev/s
[Kernel-packages] [Bug 1758869] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1758869 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/1758869 Title: Kernel panic with AWS 4.4.0-1053 Status in linux package in Ubuntu: Incomplete Bug description: This is a POTENTIAL REGRESSION. This issue only occurs on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: 1. Deploy this instance with AWS kernel (4.4.0-1052) 2. Enable -proposed, upgrade it and reboot. Result: * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755762] Re: linux: 4.13.0-38.43 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755762 Title: linux: 4.13.0-38.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 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 backports: bug 1755767 (linux-hwe), bug 1755769 (linux-azure-edge), bug 1755771 (linux-gcp), bug 1755773 (linux-azure), bug 1755774 (linux-oem) derivatives: bug 1755765 (linux-raspi2) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635597] Re: Ubuntu:talclp1: Kdump failed with multipath disk
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16044 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu:talclp1: Kdump failed with multipath disk Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in makedumpfile source package in Trusty: Confirmed Status in linux source package in Xenial: New Status in makedumpfile source package in Xenial: Fix Released Status in linux source package in Zesty: Won't Fix Status in makedumpfile source package in Zesty: Won't Fix Bug description: [Impact] When the target device where to dump the kernel is under a multipath configuration, dumping will fail, possibly leaving the system stuck in the kdump kernel. The fix is to include some scsi device handlers needed for the multipath setup inside the initramfs image that is used by kdump. All modules currently loaded in the system are included. [Test Case] Setting up kdump to target a multipath device using an appropriate storage that requires such scsi_dh modules and triggering a crash will demonstrate that kdump fails. After the fix, it works fine. [Regression Potential] If a bug is introduced, loading kdump might fail, and a crash will not be generated. A worse regression that might be considered is the system is stuck in such a kdump kernel and needs to be rebooted locally (and the crash file is not generated either). But since this is what we are trying to fix, we don't expect other systems to break. This didn't happen on a small (less than 1GiB of RAM) x86 VM, though. Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033 CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_sysrq_trigger+0x78/0xa0 [ 132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110 [ 132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0 [ 132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240 [ 132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110 [ 132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108 [ 132.643961] Instruction dump: [ 132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 3949ba60 [ 132.643972] 39
[Kernel-packages] [Bug 1004597] JournalErrors.txt
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091050/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091049/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091047/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091059/+files/RfKill.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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091052/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091058/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091060/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091051/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091061/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091057/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] AlsaInfo.txt
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091046/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091054/+files/ProcCpuinfoMinimal.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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091048/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091055/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091056/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1004597] Re: Sudden hard reset (reboot) caused by VirtualBox
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dxer 2869 F panel-3-mixer
dxer 2907 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=d46f4be5-bb04-4bd7-97be-5139549e89d3
InstallationDate: Installed on 2013-03-10 (1842 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: FUJITSU LIFEBOOK E752
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic
root=/dev/mapper/ubuntu-root ro crashkernel=384M-:128M
crashkernel=384M-2G:128M,2G-:256M
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-37-generic N/A
linux-backports-modules-4.13.0-37-generic N/A
linux-firmware 1.157.17
Tags: xenial
Uname: Linux 4.13.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/16/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 2.04
dmi.board.name: FJNB252
dmi.board.vendor: FUJITSU
dmi.board.version: M3
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK E752
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion2.04:bd10/16/2012:svnFUJITSU:pnLIFEBOOKE752:pvr10601115935:rvnFUJITSU:rnFJNB252:rvrM3:cvnFUJITSU:ct10:cvrLIFEBOOKE752:
dmi.product.name: LIFEBOOK E752
dmi.product.version: 10601115935
dmi.sys.vendor: FUJITSU
** Tags added: apport-collected xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
U
[Kernel-packages] [Bug 1004597] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1004597/+attachment/5091053/+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/1004597
Title:
Sudden hard reset (reboot) caused by VirtualBox
Status in linux package in Ubuntu:
Confirmed
Bug description:
Starting from today, whenever I (try to) start a virtual machine in
VirtualBox, the host system suddenly reboots without warning, without
even shutting down.
There's certainly some bug in VirtualBox, but if a program, no matter
how buggy or even malicious, can cause the whole operating system to
reboot suddenly, there's by definition some very serious bug in the
operating system itself.
WORKAROUND: Disabling 3D _and_ 2D acceleration in the virtual machine
fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2451 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 28
Simple ctrls : 16
Date: Fri May 25 19:25:15 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic N/A
linux-backports-modules-3.2.0-24-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to precise on 2012-05-17 (8 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
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/1004597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725154] Re: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725154 Title: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: New Status in linux-oem source package in Artful: Invalid Bug description: Issue happens every time we get connected to any WPA network and stay idle for more than 60 seconds. We are working with upstream for a real fix: https://www.spinics.net/lists/linux-wireless/msg167017.html, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1725154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734130] Re: [18.04 FEAT] Add kvm_stat from kernel tree
I believe the best way forward is to postpone this request to 18.10, which will be based on the 4.16 (or later) kernel. Then it will be included in the tools packages, and arrive in 18.04 via -hwe kernel, verbantim. In the meantime, it is quite trivial to get that single script onto systems, by downloading it from kernel.org browsing. There are very little incentives to maintain backports onto v4.15 of all of these recent patches, of which there probably still more to come. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734130 Title: [18.04 FEAT] Add kvm_stat from kernel tree Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Improves RAS characterics of systems running KVM by providing kvm_stat script: https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1734130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751796] Re: zed process consuming 100% cpu
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1751796 Title: zed process consuming 100% cpu Status in linux package in Ubuntu: In Progress Status in zfs-linux package in Ubuntu: Fix Released Bug description: I logged in this morning and found system kind of sluggish. A 'top' showed 'zed' process spinning 100% of a cpu. I didn't feel like worrying about it, so I simply rebooted. System came back up into the same state. Running 'strace -p 2002' shows repeated: ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file descriptor) ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file descriptor) ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file descriptor) ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file descriptor) ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file descriptor) ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file descriptor) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfs-zed 0.7.5-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:34:59 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (949 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
Hello Po-Hsu, or anyone else affected, Accepted lttng-modules into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lttng- modules/2.8.0-1ubuntu1~16.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lttng-modules (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in lttng-modules source package in Xenial: Fix Committed Status in linux source package in Artful: Invalid Status in lttng-modules source package in Artful: Fix Committed Status in linux source package in Bionic: Invalid Status in lttng-modules source package in Bionic: Fix Released Bug description: [Impact] * The 4.13.0-38 artful kernel included a change (backported from 4.15) that modifies the definition of kvm_mmio(). This breaks the lttng-modules-dkms package because it is using the old (<4.15) definition. * lttng-modules-dkms already has a list of kernel version "exceptions" with which it uses the >=4.15 definition. Proposed solution is to add the Ubuntu kernel range 4.13.0-38 up to 4.14.255-255 to that list of exceptions. [Test Case] * Tested by first successfully building lttng-modules-dkms on 4.13.0-37, then reproducing the problem described here on 4.13.0-38, then applying the code-change and confirming that I can successfully build on both 4.13.0-37 and 4.13.0-38 after that. [Regression Potential] * Low-regression potential. Could prevent lttng-modules-dkms from being built for specific kernel versions, but this is unlikely as the change was tested to confirm that it works as expected on 4.13.0-37 and 4.13.0-38 - and should work fine for other Ubuntu kernels as well. The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: ..
[Kernel-packages] [Bug 1745927] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2018-03-26 06:42 EDT--- (In reply to comment #17) > With the proposed installer, the Chelsio card can be seen in the installer. > > ? Primary network interface: ? > ? ? > ? enP1p3s0f4: Chelsio Communications Inc T422-CR Unified Wire Ether ? > ? enP1p3s0f4d1: Chelsio Communications Inc T422-CR Unified Wire Eth ? > ? enP1p3s0f4d2: Chelsio Communications Inc T422-CR Unified Wire Eth ? > ? enP1p3s0f4d3: Chelsio Communications Inc T422-CR Unified Wire Eth ? > > Once the patches are in mainline, this bug can be marked as resolved. > > Thanks, > Harish Issue is not seen anymore with the patches included in mainline Ubuntu 18.04 stream. Hence, Bug can be closed. Thanks, Harish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745927 Title: Driver not found in Ubuntu kernel does not detect interface Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Harish Sriram --Problem Description--- kernel does not detect interface in Ubuntu, driver missing in kernel Contact Information = hasri...@in.ibm.com ---Issue observed--- While installing Ubuntu on a machine with Chelsio card, ubuntu-installer fails to show the interface name - probable cause would be due to missing driver in Ubuntu kernel. Machine Type = Tuleta/Power 8 BML Additional Info- Installer Shell --- BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # ip a 1: lo: mtu 65536 qdisc noop qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enP5p9s0f0: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7c brd ff:ff:ff:ff:ff:ff 3: enP5p9s0f1: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7d brd ff:ff:ff:ff:ff:ff 4: enP5p9s0f2: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7e brd ff:ff:ff:ff:ff:ff 5: enP5p9s0f3: mtu 1500 qdisc mq qlen 1000 link/ether 98:be:94:02:09:7f brd ff:ff:ff:ff:ff:ff ~ # lspci -k :00:00.0 PCI bridge: IBM Device 03dc 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.1 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.2 Ethernet controller: Chelsio Communications Inc Device 4102 Subsystem: IBM Device 03e5 0001:03:00.3 Ethernet controller: Chelsio Communications Inc Device 4102 Subsystem: IBM Device 03e5 0001:03:00.4 Ethernet controller: Chelsio Communications Inc T422-CR Unified Wire Ethernet Controller Subsystem: IBM Device 03e5 0001:03:00.5 SCSI storage controller: Chelsio Communications Inc T422-CR Unified Wire Storage Controller Subsystem: IBM Device 03e5 0001:03:00.6 Fibre Channel: Chelsio Communications Inc T422-CR Unified Wire Storage Controller Subsystem: IBM Device 03e5 0001:03:00.7 Ethernet controller: Chelsio Communications Inc Device Subsystem: IBM Device 03e5 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 02) Subsystem: IBM Device 03ff 0004:00:00.0 PCI bridge: IBM Device 03dc 0004:01:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:02:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:02:03.0 PCI bridge: Integrated Device Technology, Inc. [IDT] PES16T4A/4T4G2 PCI Express Gen2 Switch (rev 02) 0004:03:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:03:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:04:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02) Subsystem: IBM Device 041e 0004:04:00.1 Fibre Channel: QLogic Corp. ISP2532-b
[Kernel-packages] [Bug 1758869] [NEW] Kernel panic with AWS 4.4.0-1053
Public bug reported: This is a POTENTIAL REGRESSION. This issue only occurs on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: 1. Deploy this instance with AWS kernel (4.4.0-1052) 2. Enable -proposed, upgrade it and reboot. Result: * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a POTENTIAL REGRESSION. - This issue only occur on one of AWS testing instance "" + This issue only occur on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: - 1. Deploy this instance with AWS kernel (4.4.0-1052) - 2. Enable -proposed, upgrade it and reboot. + 1. Deploy this instance with AWS kernel (4.4.0-1052) + 2. Enable -proposed, upgrade it and reboot. Result: - * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. + * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) ** Description changed: This is a POTENTIAL REGRESSION. - This issue only occur on one of the AWS testing instance "c3.large" + This issue only occurs on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: 1. Deploy this instance with AWS kernel (4.4.0-1052) 2. Enable -proposed, upgrade it and reboot. Result: * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758869 Title: Kernel panic with AWS 4.4.0-1053 Status in linux package in Ubuntu: New Bug description: This is a POTENTIAL REGRESSION. This issue only occurs on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: 1. Deploy this instance with AWS kernel (4.4.0-1052) 2. Enable -proposed, upgrade it and reboot. Result: * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758869] Re: Kernel panic with AWS 4.4.0-1053
Also affection Trusty + AWS 4.4.0-1015 in proposed, log here: https://pastebin.ubuntu.com/p/6CZdpPnMKw/ ** Summary changed: - Kernel panic with AWS 4.4.0-1053 + Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (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/1758869 Title: Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty) Status in linux package in Ubuntu: Incomplete Bug description: This is a POTENTIAL REGRESSION. This issue only occurs on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: 1. Deploy this instance with AWS kernel (4.4.0-1052) 2. Enable -proposed, upgrade it and reboot. Result: * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743091] Re: Xubuntu 17.10 (32 bits)
Note: same issue as 'v4.15rc8' with 'v4.15.0 mainline build' from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743091 Title: Xubuntu 17.10 (32 bits) Status in linux package in Ubuntu: Expired Bug description: Bug ticket opened after I asked this question : https://answers.launchpad.net/ubuntu/+source/linux- meta/+question/663037 $ cat /proc/version_signature Ubuntu 4.13.0-21.24-generic 4.13.13 $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Memory Controller Hub [103c:30e8] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30e8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 6.500W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt+ HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 41e1 Capabilities: [90] Subsystem: Device [:] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01 Status:NegoPending- InProgress- Capabilities: [180 v1] Root Complex Link Desc: PortNumber=01 ComponentID=02 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=02 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed1c000 Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <256ns, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- A
[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints
** Summary changed: - retpoline hints: primary infrastructure + retpoline hints: primary infrastructure and initial hints -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758856 Title: retpoline hints: primary infrastructure and initial hints Status in linux package in Ubuntu: Confirmed Bug description: Tracking bug for the application of the retpoline hint tracking support. We are having terrible trouble with hints changing on every build. Upstream is moving to hinting those indirections which have been reviewed and are good. This includes direct hinting of PVOPS and the like which are the ones which change all the time as new ones appear and dissappear. Backport the hint support and add our own bespoke checkers against this data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758869] Re: Kernel panic with AWS 4.4.0-1053
** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758869 Title: Kernel panic with AWS 4.4.0-1053 Status in linux package in Ubuntu: Incomplete Bug description: This is a POTENTIAL REGRESSION. This issue only occurs on one of the AWS testing instance "c3.large" Reproduce rate: 100% (All jenkins deployment job failed with this instance) Steps: 1. Deploy this instance with AWS kernel (4.4.0-1052) 2. Enable -proposed, upgrade it and reboot. Result: * System can boot with 4.4.0-1052, but it won't be accessible after rebooting for 4.4.0-1053, from "aws ec2 get-console-output" command indicates it hang with kernel panic issue on boot. It looks like the intel-microcode is causing this issue. Output from the command: https://pastebin.ubuntu.com/p/3JvWNk5CTs/ (it's a bit difficult to get full output, the instance will keep rebooting itself) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755210] Re: linux-aws: 4.4.0-1015.15 -proposed tracker
Mark this as incomplete for a potential regression - Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty) (bug 1758869) 4.4.0-1015.15 - aws Regression test CMPL. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only spotted on t2.small, passed on the rest ubuntu_kernel_selftests - failed to build ubuntu_kvm_unit_tests - test disabled ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1755210 Title: linux-aws: 4.4.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757937] Re: zram smoke test failed on GCP 4.13 / AWS 4.15
Affecting Xenial AWS kernel as well 4.4.0-1053.62 ** Tags added: xenial ** Summary changed: - zram smoke test failed on GCP 4.13 / AWS 4.15 + zram smoke test failed on GCP 4.13 / AWS 4.15, 4.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757937 Title: zram smoke test failed on GCP 4.13 / AWS 4.15, 4.4 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: The zram smoke test failed due to the absence of the zram module. modprobe: FATAL: Module zram not found in directory /lib/modules/4.13.0-1012-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755217] Re: linux-aws: 4.4.0-1053.62 -proposed tracker
Mark this as incomplete for a potential regression - Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty) (bug 1758869) 4.4.0-1053.62 - aws Regression test CMPL. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3, only spotted on t2.small, passed on the rest ubuntu_kvm_unit_tests - test disabled ubuntu_lxc - lxc-test-ubunut failed (Failed to start networking in ubuntu-cloud container), only spotted on t2.small, passed on the rest ubuntu_zram_smoke_test - zram module not found (bug 1757937) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1755217 Title: linux-aws: 4.4.0-1053.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758886] [NEW] Bionic update to 4.15.13 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.15.13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.15.13 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758886 Title: Bionic update to 4.15.13 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.15.13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.15.13 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
Kernel for xenial (4.4.0) successfuly tested. Ghost devices does not appear. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscriptions -- Mailing list: https://launchpad.n
[Kernel-packages] [Bug 1758264] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2018-03-26 08:20 EDT---
Canonical,
Any update here ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758264
Title:
ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF"
on Witherspoon system due to java dumping
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - INDIRA P. JOGA - 2018-03-22
06:45:23 ==
Problem Description:
===
Unable to start "STAF" on Witherspoon system due to java dumping
Steps to re-create:
==
> System installed with Ubunu1804 build.
root@whip:# uname -a
Linux whip 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
> We are using staf framework to run the LTP test buckets.
> Unable to start the staf process.
> It fails to start and i see java dumping core.
> core details
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06
core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06
core.20180322.060603.4631.0001.dmp
> Attached core files
NOTE:-
--
System is on a private network. Access the private network via SSH to
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password.
(Banner itself is behind a BSO, so must authenticate through that first.)
Login details :
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]
Host login:-ssh -p 2200 root@bmc-wax (0penBmc) (or)
ssh root@wax (don2rry)
== Comment: #5 - INDIRA P. JOGA - 2018-03-22
07:09:14 ==
Unable to attach core file because huge size.
Please find the path from the system:
root@whip:/# pwd
/
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06
core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06
core.20180322.060603.4631.0001.dmp
root@whip:/#
Regards,
Indira
== Comment: #6 - INDIRA P. JOGA - 2018-03-22
07:20:12 ==
Also you can find them in banner
banner@banner:~> pwd
/home/banner
banner@banner:~> ls -l core*
-rw--- 1 banner banner 114753536 Mar 22 06:46
core.20180322.060600.4626.0001.dmp
-rw--- 1 banner banner 115736576 Mar 22 06:46
core.20180322.060603.4631.0001.dmp
== Comment: #8 - SEETEENA THOUFEEK - 2018-03-22
09:00:18 ==
Please pick
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1758264/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756254] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2018-03-26 08:19 EDT---
Canonical,
Please check comment from Paul M and verify this patch is in-corporated into
Bionic -proposed version.
.
-
6964e6a4e489 ("KVM: PPC: Book3S HV: Do SLB load/unload with guest LPCR value
loaded", 2018-01-11)
00608e1f007e ("KVM: PPC: Book3S HV: Allow HPT and radix on the same core
for POWER9 v2.2", 2018-01-11)
cda4a1473313 ("KVM: PPC: Book3S HV: Fix duplication of host SLB
entries", 2018-03-22)
The last one is in my kvm-ppc-fixes branch on kernel.org but not in the KVM
tree or Linus's tree yet.
--
We have tested with proposed version and still facing the same issue.
-- proposed as (4.15.0-13-generic) still facing same issue .
LOG:
root@system ~# uname -a
Linux system 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1756254
Title:
Ubuntu18.04[P9 DD2.2 Boston]:Unable to boot power8 compat mode
guests(ubuntu14.04.5) (kvm)
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
== Comment: #0 - Praveen K. Pandey - 2018-03-15
03:18:46 ==
Problem Description :
As Ubuntu18.04 as KVM Host installation of ubuntu ubuntu14.04.5 kvm
guest is hung to so not able to install using virt-install command
Reproducible Step:
1- Install ubuntu18.04 on Boston DD2.2
2- Configure system as KVM host
3- get ubuntu-14.04.5-server-ppc64el iso
4- start installation using virt-install using ubuntu-14.04.5 iso
LOG:
OF stdout device is: /vdevice/vty@3000
Preparing to boot Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-007)
(gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #50~14.04.1-Ubuntu SMP Wed
Jul 13 01:03:56 UTC 2016 (Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13)
Detected machine type: 0101
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support...
- it hung here --
root@system :/var/lib/libvirt/images/praveen# uname -a
Linux system4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
root@lsystem:/var/lib/libvirt/images/praveen#
root@system:/var/lib/libvirt/images/praveen# qemu-img create -f qcow2
pra-ubuntu14.qcow2 30G
Formatting 'pra-ubuntu14.qcow2', fmt=qcow2 size=32212254720
cluster_size=65536 lazy_refcounts=off refcount_bits=16
root@system:/var/lib/libvirt/images/praveen# virt-install --name
PRA-1404.5_vm1 --ram 2048 --disk
path=/var/lib/libvirt/images/praveen/pra-ubuntu14.qcow2 --vcpus 4 --os-type
linux --os-variant generic --network bridge=virbr0 --graphics none --console
pty,target_type=serial --cdrom
/var/lib/libvirt/images/isos/ubuntu-14.04.5-server-ppc64el.iso
WARNING CDROM media does not print to the text console by default, so you
likely will not see text install output. You might want to use --location. See
the man page for examples of using --location with CDROM media
Starting install...
Connected to domain PRA-1404.5_vm1
Escape character is ^]
Populating /vdevice methods
Populating /vdevice/vty@3000
Populating /vdevice/nvram@7100
Populating /pci@8002000
00 0800 (D) : 1af4 1000virtio [ net ]
00 1000 (D) : 1af4 1004virtio [ scsi ]
Populating /pci@8002000/scsi@2
SCSI: Looking for devices
100 CD-ROM : "QEMU QEMU CD-ROM 2.5+"
00 1800 (D) : 1b36 000dserial bus [ usb-xhci ]
00 2000 (D) : 1af4 1001virtio [ block ]
00 2800 (D) : 1af4 1002unknown-legacy-device*
No NVRAM common partition, re-initializing...
Scanning USB
XHCI: Initializing
Using default console: /vdevice/vty@3000
Welcome to Open Firmware
Copyright (c) 2004, 2017 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php
Trying to load: from: /pci@8002000/scsi@2/disk@100 ...
Successfully loaded
GNU GRUB version 2.02~beta2-9ubuntu1.11
|*Install
|
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
[Kernel-packages] [Bug 1758886] Re: Bionic update to 4.15.13 stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.15.13 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The 4.15.13 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD + The following patches from the 4.15.13 stable release shall be + applied: -The following patches from the 4.15.13 stable release shall be - applied: + 1d60b7802104 scsi: megaraid_sas: Do not use 32-bit atomic request descriptor for Ventura controllers + bcaf449b5809 staging: android: ashmem: Fix possible deadlock in ashmem_ioctl + 5ec3e522c556 drm/amdgpu: use polling mem to set SDMA3 wptr for VF + b646aada058d Bluetooth: hci_qca: Avoid setup failure on missing rampatch + e16154e6868b Bluetooth: btqcomsmd: Fix skb double free corruption + 3cb311196e5f cpufreq: longhaul: Revert transition_delay_us to 200 ms + aa5397213cc1 media: c8sectpfe: fix potential NULL pointer dereference in c8sectpfe_timer_interrupt + 09a00a4b1e8b drm/msm: fix leak in failed get_pages + be176a5c98e7 IB/ipoib: Warn when one port fails to initialize + 3669331be6fd RDMA/iwpm: Fix uninitialized error code in iwpm_send_mapinfo() + 8fbec85ecd00 hv_netvsc: Fix the receive buffer size limit + df365ce541c4 hv_netvsc: Fix the TX/RX buffer default sizes + 7f5739939eb3 tcp: allow TLP in ECN CWR + 340f5832b6a6 spi: sh-msiof: Avoid writing to registers from spi_master.setup() + b5817721ecea libbpf: prefer global symbols as bpf program name source + 3104c12838b2 rtlwifi: rtl_pci: Fix the bug when inactiveps is enabled. + 06647fbb496e rtlwifi: always initialize variables given to RT_TRACE() + db80bd4d5f62 media: bt8xx: Fix err 'bt878_probe()' + 784d1114823c ath10k: handling qos at STA side based on AP WMM enable/disable + 7bc49ffb1067 media: [RESEND] media: dvb-frontends: Add delay to Si2168 restart + ccf304a6607a qmi_wwan: set FLAG_SEND_ZLP to avoid network initiated disconnect + 42c35b150365 tty: goldfish: Enable 'earlycon' only if built-in + 0a607a064565 serial: 8250_dw: Disable clock on error + 68c1248b9a2d cros_ec: fix nul-termination for firmware build info + 3122d2f18ed9 watchdog: Fix potential kref imbalance when opening watchdog + 449c24e264d9 watchdog: Fix kref imbalance seen if handle_boot_enabled=0 + c78feb5f451c platform/chrome: Use proper protocol transfer function + 73f483aa65d6 dmaengine: zynqmp_dma: Fix race condition in the probe + 75157d4e4d15 drm/tilcdc: ensure nonatomic iowrite64 is not used + ca6b159fd207 mmc: avoid removing non-removable hosts during suspend + 176fb28073c9 mmc: block: fix logical error to avoid memory leak + f9e0be9def10 /dev/mem: Add bounce buffer for copy-out + 1d40cdd339cb net: phy: meson-gxl: check phy_write return value + b03b5f94dcf4 sfp: fix EEPROM reading in the case of non-SFF8472 SFPs + e9f486d7a859 sfp: fix non-detection of PHY + 1835bd639fa7 media: s5p-mfc: Fix lock contention - request_firmware() once + 80ac31ac404a rtc: ac100: Fix multiple race conditions + f333c18b5434 IB/ipoib: Avoid memory leak if the SA returns a different DGID + 4d529564d326 RDMA/cma: Use correct size when writing netlink stats + 20dbecabd107 IB/umem: Fix use of npages/nmap fields + 3a23663bda89 iser-target: avoid reinitializing rdma contexts for isert commands + 3c4ffeae6510 bpf/cgroup: fix a verification error for a CGROUP_DEVICE type prog + 18e595d70f17 PCI/ASPM: Calculate LTR_L1.2_THRESHOLD from device characteristics + 00aa57830cb5 vgacon: Set VGA struct resource types + a9b4a01508a9 omapdrm: panel: fix compatible vendor string for td028ttec1 + eafa4cd4d112 mmc: sdhci-xenon: wait 5ms after set 1.8V signal enable + e7b4a5ba3259 drm/omap: DMM: Check for DMM readiness after successful transaction commit + 71b009c13528 pty: cancel pty slave port buf's work in tty_release + 29a84f9707b1 coresight: Fix disabling of CoreSight TPIU + d306bb6c7952 PCI: designware-ep: Fix ->get_msi() to check MSI_EN bit + 61cbbb4f20d1 PCI: endpoint: Fix find_first_zero_bit() usage + 10843b30c385 PCI: rcar: Handle rcar_pcie_parse_request_of_pci_ranges() failures + 887fa839ee74 media: davinci: fix a de
[Kernel-packages] [Bug 1758886] Re: Bionic update to 4.15.13 stable release
** Changed in: linux (Ubuntu Bionic) 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/1758886 Title: Bionic update to 4.15.13 stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.15.13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.15.13 stable release shall be applied: 1d60b7802104 scsi: megaraid_sas: Do not use 32-bit atomic request descriptor for Ventura controllers bcaf449b5809 staging: android: ashmem: Fix possible deadlock in ashmem_ioctl 5ec3e522c556 drm/amdgpu: use polling mem to set SDMA3 wptr for VF b646aada058d Bluetooth: hci_qca: Avoid setup failure on missing rampatch e16154e6868b Bluetooth: btqcomsmd: Fix skb double free corruption 3cb311196e5f cpufreq: longhaul: Revert transition_delay_us to 200 ms aa5397213cc1 media: c8sectpfe: fix potential NULL pointer dereference in c8sectpfe_timer_interrupt 09a00a4b1e8b drm/msm: fix leak in failed get_pages be176a5c98e7 IB/ipoib: Warn when one port fails to initialize 3669331be6fd RDMA/iwpm: Fix uninitialized error code in iwpm_send_mapinfo() 8fbec85ecd00 hv_netvsc: Fix the receive buffer size limit df365ce541c4 hv_netvsc: Fix the TX/RX buffer default sizes 7f5739939eb3 tcp: allow TLP in ECN CWR 340f5832b6a6 spi: sh-msiof: Avoid writing to registers from spi_master.setup() b5817721ecea libbpf: prefer global symbols as bpf program name source 3104c12838b2 rtlwifi: rtl_pci: Fix the bug when inactiveps is enabled. 06647fbb496e rtlwifi: always initialize variables given to RT_TRACE() db80bd4d5f62 media: bt8xx: Fix err 'bt878_probe()' 784d1114823c ath10k: handling qos at STA side based on AP WMM enable/disable 7bc49ffb1067 media: [RESEND] media: dvb-frontends: Add delay to Si2168 restart ccf304a6607a qmi_wwan: set FLAG_SEND_ZLP to avoid network initiated disconnect 42c35b150365 tty: goldfish: Enable 'earlycon' only if built-in 0a607a064565 serial: 8250_dw: Disable clock on error 68c1248b9a2d cros_ec: fix nul-termination for firmware build info 3122d2f18ed9 watchdog: Fix potential kref imbalance when opening watchdog 449c24e264d9 watchdog: Fix kref imbalance seen if handle_boot_enabled=0 c78feb5f451c platform/chrome: Use proper protocol transfer function 73f483aa65d6 dmaengine: zynqmp_dma: Fix race condition in the probe 75157d4e4d15 drm/tilcdc: ensure nonatomic iowrite64 is not used ca6b159fd207 mmc: avoid removing non-removable hosts during suspend 176fb28073c9 mmc: block: fix logical error to avoid memory leak f9e0be9def10 /dev/mem: Add bounce buffer for copy-out 1d40cdd339cb net: phy: meson-gxl: check phy_write return value b03b5f94dcf4 sfp: fix EEPROM reading in the case of non-SFF8472 SFPs e9f486d7a859 sfp: fix non-detection of PHY 1835bd639fa7 media: s5p-mfc: Fix lock contention - request_firmware() once 80ac31ac404a rtc: ac100: Fix multiple race conditions f333c18b5434 IB/ipoib: Avoid memory leak if the SA returns a different DGID 4d529564d326 RDMA/cma: Use correct size when writing netlink stats 20dbecabd107 IB/umem: Fix use of npages/nmap fields 3a23663bda89 iser-target: avoid reinitializing rdma contexts for isert commands 3c4ffeae6510 bpf/cgroup: fix a verification error for a CGROUP_DEVICE type prog 18e595d70f17 PCI/ASPM: Calculate LTR_L1.2_THRESHOLD from device characteristics 00aa57830cb5 vgacon: Set VGA struct resource types a9b4a01508a9 omapdrm: panel: fix compatible vendor string for td028ttec1 eafa4cd4d112 mmc: sdhci-xenon: wait 5ms after set 1.8V signal enable e7b4a5ba3259 drm/omap: DMM: Check for DMM readiness after successful transaction commit 71b009c13528 pty: cancel pty slave port buf's work in tty_release 29a84f9707b1 coresight: Fix disabling of CoreSight TPIU d306bb6c7952 PCI: designware-ep: Fix ->get_msi() to check MSI_EN bit 61cbbb4f20d1 PCI: endpoint: Fix find_first_zero_bit() usage 10843b30c385 PCI: rcar: Handle rcar_pcie_parse_request_of_pci_ranges() failures 887fa839ee74 media: davinci: fix a debug printk 48228438f263 clk: check ops pointer on clock register b96b31ce0517 dt-bindings: display: panel: Fix compatible string for Toshiba LT089AC29000 f64b3c51d512 clk: use round rate to bail out early in set_rate 35e54f441f0e pinctrl: Really fo
[Kernel-packages] [Bug 1748487] Re: Please upgrade to get kernel management
Upstream thinks its solved now: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/?h=linux-next if bionic does not get kernel 4.16 soon, then the required patches need to be backported to 4.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748487 Title: Please upgrade to get kernel management Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Bionic still has that old version from 2013 Debian have a more recent version: http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog Actual source: http://www.uefi.org/acpi Kernel (upstream) is supposed to have fixed the problem: https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195 Does ubuntu kernel apply that patch ? https://bugzilla.kernel.org/show_bug.cgi?id=117671 Because kernel 4.15.0-9 still log these errors: kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210) kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252) kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20170831/tbxfload-228) kernel: ACPI Error: 1 table load failures, 5 successful (20170831/tbxfload-246) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: acpi-support 0.142 ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2 Uname: Linux 4.15.0-9-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 9 17:49:39 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi-support UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758264] Re: ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF" on Witherspoon system due to java dumping
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758264
Title:
ISST-LTE: Witherspoon:Ubuntu1804:PowerNV:whip :Unable to start "STAF"
on Witherspoon system due to java dumping
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - INDIRA P. JOGA - 2018-03-22
06:45:23 ==
Problem Description:
===
Unable to start "STAF" on Witherspoon system due to java dumping
Steps to re-create:
==
> System installed with Ubunu1804 build.
root@whip:# uname -a
Linux whip 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux
> We are using staf framework to run the LTP test buckets.
> Unable to start the staf process.
> It fails to start and i see java dumping core.
> core details
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06
core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06
core.20180322.060603.4631.0001.dmp
> Attached core files
NOTE:-
--
System is on a private network. Access the private network via SSH to
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password.
(Banner itself is behind a BSO, so must authenticate through that first.)
Login details :
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]
Host login:-ssh -p 2200 root@bmc-wax (0penBmc) (or)
ssh root@wax (don2rry)
== Comment: #5 - INDIRA P. JOGA - 2018-03-22
07:09:14 ==
Unable to attach core file because huge size.
Please find the path from the system:
root@whip:/# pwd
/
root@whip:/# ls -l core*
-rw--- 1 root root 20709376 Mar 22 06:07 core
-rw--- 1 root root 114753536 Mar 22 06:06
core.20180322.060600.4626.0001.dmp
-rw--- 1 root root 115736576 Mar 22 06:06
core.20180322.060603.4631.0001.dmp
root@whip:/#
Regards,
Indira
== Comment: #6 - INDIRA P. JOGA - 2018-03-22
07:20:12 ==
Also you can find them in banner
banner@banner:~> pwd
/home/banner
banner@banner:~> ls -l core*
-rw--- 1 banner banner 114753536 Mar 22 06:46
core.20180322.060600.4626.0001.dmp
-rw--- 1 banner banner 115736576 Mar 22 06:46
core.20180322.060603.4631.0001.dmp
== Comment: #8 - SEETEENA THOUFEEK - 2018-03-22
09:00:18 ==
Please pick
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1758264/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
The first kernel fixed is 4.16-rc5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+subscriptions --
