[Kernel-packages] [Bug 1786729] Re: execveat03 in ubuntu_ltp_syscalls failed on X/B
** Description changed:
- This is a new test case added 4 days ago.
- From the commit message it looks like this is a test case for a buggy commit
8db6c34f1dbc:
- The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
- file capabilities"). Overlayfs and possibly other networking filesystems
- unhash the dentry on unlink, fail on this test with above change.
+ == Justification ==
+ The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
+ ("Introduce v3 namespaced file capabilities"), should use
+ d_find_any_alias() instead of d_find_alias() do handle unhashed dentry
+ correctly. This is needed, for example, if execveat() is called with an
+ open but unlinked overlayfs file, because overlayfs unhashes dentry on
+ unlink.
+ This is a regression of real life application, first reported at
+ https://www.spinics.net/lists/linux-unionfs/msg05363.html
- This commit has been applied in the Xenial AWS kernel (14985d791) with
- bug 1778286
-
- This might have something to do with the way how we backport it (the
- EINVAL return value is the clue)
-
+ With the execveat03 test in the LTP test suite on an affected kernel, it will
fail with:
<<>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
- <<>>
- initiation_status="ok"
- duration=0 termination_type=exited termination_id=1 corefile=no
- cutime=0 cstime=0
- <<>>
+
+ == Fix ==
+ 355139a8 (cap_inode_getsecurity: use d_find_any_alias() instead of
+ d_find_alias())
+
+ It can be cherry-picked for Bionic, but it needs to be backported to
+ Xenial along with the logic when we backport 8db6c34f1dbc (bug 1778286).
+
+ The test kernel for Xenial / Bionic could be found here:
+ http://people.canonical.com/~phlin/kernel/lp-1786729-execveat03/
+
+ == Test Case ==
+ Run the reproducer in the commit message, or,
+ run the execveat03 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
+
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
== Justification ==
The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
("Introduce v3 namespaced file capabilities"), should use
d_find_any_alias() instead of d_find_alias() do handle unhashed dentry
correctly. This is needed, for example, if execveat() is called with an
open but unlinked overlayfs file, because overlayfs unhashes dentry on
unlink.
This is a regression of real life application, first reported at
https://www.spinics.net/lists/linux-unionfs/msg05363.html
With the execveat03 test in the LTP test suite on an affected kernel, it will
fail with:
<<>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
== Fix ==
355139a8 (cap_inode_getsecurity: use d_find_any_alias() instead of
- d_find_alias())
+ d_find_alias())
It can be cherry-picked for Bionic, but it needs to be backported to
Xenial along with the logic when we backport 8db6c34f1dbc (bug 1778286).
The test kernel for Xenial / Bionic could be found here:
http://people.canonical.com/~phlin/kernel/lp-1786729-execveat03/
+ This patch has already been cherry-picked into Cosmic and Unstable.
+
== Test Case ==
Run the reproducer in the commit message, or,
run the execveat03 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
-
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
[Kernel-packages] [Bug 1797069] Re: linux-oem: 4.15.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1797069 Title: linux-oem: 4.15.0-1024.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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: 1797061 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/1797069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276702] Re: iphone 5 issues
I forgot the cloud Password i try to recover it from forgot password but not able to change this. than i visit https://www.appletechnicalsupportnumbers.com/blog/how-to-change-the- icloud-password/ and successfully bale to change it. After that, i noticed that the other account log out automatically. I am unable to connect the Linux Mint 16 to my iPhone. I am using the iPhone 5. I searched many blogs and forums but not found any sufficient solution to solve the issue. help me! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276702 Title: iphone 5 issues Status in linux package in Ubuntu: Confirmed Bug description: Iphone 5 will not connect to linux mint 16 . asks me to trust and when i do it keeps asking. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andy 2309 F pulseaudio /dev/snd/controlC0: andy 2309 F pulseaudio /dev/snd/pcmC0D0p: andy 2309 F...m pulseaudio Date: Wed Feb 5 12:13:38 2014 InstallationDate: Installed on 2014-01-07 (28 days ago) InstallationMedia: Linux Mint 15 "Olivia" - Release amd64 (20130520) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 537 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=ab3c5ccb-1918-408b-b34a-634e14189331 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0U880P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/23/2009:svnDellInc.:pnInspiron537:pvr00:rvnDellInc.:rn0U880P:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 537 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1799228] Re: USB-ports do not work
Thank you for the swift response. I tried to upgrade from 16.04 to 18.04, however, the process failed and I had to interupt the upgrade (the script detected a problem in the printer driver, offered 3 options - maintain old / change to new / investigate; I selected the last one, the deviating contents of the drivers were shown, but it was impossible to leave that screen and continue the upgrade). After that, the system was broken and we had to re-install parts of the kernel. So far, the system works under 18.04, except from the 2 usb-ports (a 3rd one is still accessible). I will try to install the recommended kernel, but that may take another day, because I am not at home currently. thank you, Stefan Am 23. Oktober 2018 21:05:03 MESZ schrieb Joseph Salisbury : >Did this issue start happening after an update/upgrade? Was there a >prior kernel version where you were not having this particular problem? > >Would it be possible for you to test the latest upstream kernel? Refer >to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the >latest >v4.19 kernel[0]. > >If this bug is fixed in the mainline kernel, please add the following >tag 'kernel-fixed-upstream'. > >If the mainline kernel does not fix this bug, please add the tag: >'kernel-bug-exists-upstream'. > >Once testing of the upstream kernel is complete, please mark this bug >as >"Confirmed". > > >Thanks in advance. > >[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 > > >** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > >** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1799228 > >Title: > USB-ports do not work > >Status in linux package in Ubuntu: > Incomplete > >Bug description: > Two out of 3 USB-ports are not regognized anymore (i.e. when I insert > a USB-stick, it will not be shown in Nautilus). I tried various > workarounds from ubuntuusers, but they were not successful. Among them > to use "dpkg-reconfigure x-server". X-org now reported an error, > docuimented in the attachment. > > Earlier I wanted to create an image with Clonezilla and selected a > USB-stick at port #2 as target, however, the target was not detected > successfully and the backup-procedure stopped. I suspect that the > issues may be relatd. > > Kind regards, > Stefan > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 > Uname: Linux 4.15.0-36-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia >.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein >Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 >00:42:57 PDT 2018 > GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.4 > Architecture: amd64 > CompositorRunning: None > Date: Mon Oct 22 15:57:33 2018 >DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() >(E:Nicht gesperrt) > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: > nvidia, 390.48, 4.15.0-36-generic, x86_64: installed > nvidia, 390.48, 4.4.0-137-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA >controller]) >Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] >[1043:1ccd] > Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] > InstallationDate: Installed on 2016-07-21 (823 days ago) >InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 >(20160420.1) > MachineType: ASUSTeK COMPUTER INC. X555UB >ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic >root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash >pci=noaer acpi_osi= acpi_backlight=native vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago) > dmi.bios.date: 01/23/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X555UB.206 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X555UB > 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.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: X > dmi.product.name: X555UB > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.91-
[Kernel-packages] [Bug 1799066] Re: Trackpoint/trackpad unusable when trying to install 18.10 on X1 Carbon 6th
Does [1] help? [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/comments/63 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799066 Title: Trackpoint/trackpad unusable when trying to install 18.10 on X1 Carbon 6th Status in linux package in Ubuntu: Confirmed Bug description: When running the live CD iso from a USB stick on Lenovo X1 Carbon 6th, both the trackpad and trackpoint are unresponsive. xinput reports what seems to be proper input devices: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] ⎜ ↳ TPPS/2 Elan TrackPoint 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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] After some time of swiping my finger on the trackpad and trying to use the trackpoint, they sometimes start working. The xinput output is then slighly different: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouse 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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] I will include the dmesg output in the comment. I will also see if trackpad and trackpoint survive a suspend (which is an issue in 18.04). I assume it's still an issue, even with 18.10's kernel. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2224 F pulseaudio CasperVersion: 1.399 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 16:07:43 2018 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KH006KPB:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006KPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006KPB dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_
[Kernel-packages] [Bug 1799049] Re: [bionic]mlx5: reading SW stats through ifstat cause kernel crash
Thank you for your concern. I already sent the patch to the canonical kernel mailing list, and waiting for them to review it. Thanks, Talat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799049 Title: [bionic]mlx5: reading SW stats through ifstat cause kernel crash Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description of problem: Attempting to read SW stats (ifstat -x cpu_hit) on a system with probed VFs will crash the system. How reproducible: Always Steps to Reproduce: 1. Create a VF echo 1 > /sys/bus/pci/devices/\:82\:00.0/sriov_numvfs 2. read SW stats: ifstat -x cpu_hit Actual results: System will crash Expected results: No system crash Additional info: The reason for the crash is insufficient check on the helper that determines if a netdev is vf rep. will crash: $ ifstat -x cpu_hit will not crash: $ ifstat -x cpu_hit $VF_REP $ ifstat -x cpu_hit $UPLINK_REP We already have a fix for this issue, and it is accepted upstream. https://patchwork.ozlabs.org/patch/935193/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
Hello, I sumbitted the report on LXD since that is the only thing I have installed on the server that is actively running as Stéphane mentioned on https://github.com/lxc/lxd/issues/5197 I also thought it maybe hardware issue, but since upgrading to 18.04 in May I have experienced this on a variety of hardware, and even though I thought it may be upgrade issue it is also not the case. I also thought it was memory related, since now it occurs, as Stéphane mentiones around once a week, but in my case on different servers. THe last server where it happened didn't have any issue for the last maybe two months and was not that loaded in terms of memory, but it seems more frequent in servers that are actively used in both memory and CPU. It doesn't happen on blade hosts that only have 2-4 LXD containers and 4GB of RAM, it has only happened on 16GB, 24GB, 48GB and 128GB of RAM HP and Dell servers, that have a little more load (minimum 6 containers up to 20) At least I a not alone, but have no clue how to recreate or address this issue (since also logs provide no information) I could also try some kernels. On 4.4 as Stephane mentioned didn't happen, int only started happening on GA (as he also mentiones) of 18.04. I have been constantly upgrading the kernel to no avail. So it seems it could have been introduced before. strangely and thankfully it doesn't happen on my main production server (Except yesterday crash on one of them). Mostly on development servers that are actively used (developers are not happy) ** Bug watch added: LXD bug tracker #5197 https://github.com/lxc/lxd/issues/5197 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=
[Kernel-packages] [Bug 1785174] Re: [solved] nvidia driver - does not resume from suspend
Sorry, cannot add any logs, as system is completely freezed after resume. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785174 Title: [solved] nvidia driver - does not resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). This only happens with TWO MONITORS ATTACHED. One monitor: no problem. With nouveau driver, two monitors are working as well. ubuntu GNOME 18.04, clean install kernel 4.15.0-29-generic #31-Ubuntu Fujitsu-Siemens Celsius WT-380 nvidia GT 630 Tried nvidia340, 390 and 396 - all the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
Someone's probably working on it. I personally am. But have nothing to show yet. Most likely the same with whoever else is working on it currently -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working
If I could do that I'd fix my problem myself. I thought reporting a bug was so people who know how to do these things could take a crack at it. But it seems there's no one at Canonical who knows about these things either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)
[Expired for gnome-bluetooth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => Expired -- 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/1782893 Title: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174) Status in bluez package in Ubuntu: Expired Status in gnome-bluetooth package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: am 5501 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1782893 Title: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174) Status in bluez package in Ubuntu: Expired Status in gnome-bluetooth package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: am 5501 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788581] Re: Ubuntu shows blank screen after login
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788581 Title: Ubuntu shows blank screen after login Status in linux package in Ubuntu: Expired Bug description: After I log in, from normal boot, blank screen is displayed. When I hit 'Ctrl+Alt+F1' then I get the whole list of error messages... Failed command: Read DMA EXT When I select 'Ubuntu .. Recovery Mode' I see the error messages containing.. Failed command: Read FPDMA Queued My motherboard power supply IC got damaged, I got the IC replaced. Date was reset to old system date 1/1/2009. After motherboard got power functioning I checked the ubuntu running fine. I ve reset the BIOS, maybe this is the cause as few settins might have changed on my ASUS K55VM machine. This is the grub link : http://paste.ubuntu.com/p/c4ZRM4JDyk/ Please help me in fixing the issue. Thanks & Regards, Abhishek ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2754 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity Date: Thu Aug 23 08:51:10 2018 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. K55VM ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash -- RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VM.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VM 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.:bvrK55VM.202:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55VM 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/1788581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788559] Re: package linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788559 Title: package linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Status in linux package in Ubuntu: Expired Bug description: Sorry, something went wrong with your search. We've recorded what happened, and we'll fix it as soon as possible. (Error ID: OOPS- f3793fc86290cb64fd038a9fba6e9f71) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Wed Aug 22 18:02:08 2018 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2018-05-06 (108 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788860] Re: Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788860 Title: Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: https://forums.linuxmint.com/viewtopic.php?f=59&t=276201 Kernel 4.15.0-20 Work with prime Kernel 4.15.0-22 Work with prime Kernel 4.15.0-23 Black Screen Kernel 4.15.0-24 Black Screen Kernel 4.15.0-29 Black Screen Kernel 4.15.0-30 Black Screen Kernel 4.15.0-32 Black Screen Kernel 4.15.0-33 Black Screen When using any Kernel 4.15.0-23 and above I am getting a Black screen when setting my bios to use hybrid graphics (optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub menu and after that just black screen, I can blindly enter my linux Mint password and hear linux mint login chime. I can also use recover mode in grub and boot with screen using software mode. If I choose nvidia discrete graphics in bios i can boot using nvidia hardware driver v390 or V396 and it all works fine. Intel graphics are disabled and not used and no prime. My graphics are Intel HD Graphics 530 and nvidia GTX 1070. Found that any kernel later than 4.15.0-22 will cause Black Screen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firepower 1695 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-08-11 (12 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firepower 1695 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-08-11 (12 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.s
[Kernel-packages] [Bug 1788286] Re: [radeon] The screen collapses after getting out of sleep
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788286 Title: [radeon] The screen collapses after getting out of sleep Status in linux package in Ubuntu: Expired Bug description: E): enp2s0: link becomes ready Aug 20 13:49:02 M51SE kernel: [ 272.572110] radeon :01:00.0: ring 0 stalled for more than 10236msec Aug 20 13:49:02 M51SE kernel: [ 272.572126] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:03 M51SE kernel: [ 273.084086] radeon :01:00.0: ring 0 stalled for more than 10748msec Aug 20 13:49:03 M51SE kernel: [ 273.084099] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:03 M51SE kernel: [ 273.596091] radeon :01:00.0: ring 0 stalled for more than 11260msec Aug 20 13:49:03 M51SE kernel: [ 273.596107] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:04 M51SE kernel: [ 274.108084] radeon :01:00.0: ring 0 stalled for more than 11772msec Aug 20 13:49:04 M51SE kernel: [ 274.108098] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:04 M51SE kernel: [ 274.620076] radeon :01:00.0: ring 0 stalled for more than 12284msec Aug 20 13:49:04 M51SE kernel: [ 274.620088] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:05 M51SE kernel: [ 275.136059] radeon :01:00.0: ring 0 stalled for more than 12800msec Aug 20 13:49:05 M51SE kernel: [ 275.136069] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:05 M51SE kernel: [ 275.644077] radeon :01:00.0: ring 0 stalled for more than 13308msec Aug 20 13:49:05 M51SE kernel: [ 275.644090] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:06 M51SE kernel: [ 276.156083] radeon :01:00.0: ring 0 stalled for more than 13820msec Aug 20 13:49:06 M51SE kernel: [ 276.156097] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:06 M51SE kernel: [ 276.668078] radeon :01:00.0: ring 0 stalled for more than 14332msec Aug 20 13:49:06 M51SE kernel: [ 276.668090] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:07 M51SE kernel: [ 277.180071] radeon :01:00.0: ring 0 stalled for more than 14844msec Aug 20 13:49:07 M51SE kernel: [ 277.180083] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:07 M51SE kernel: [ 277.692072] radeon :01:00.0: ring 0 stalled for more than 15356msec Aug 20 13:49:07 M51SE kernel: [ 277.692085] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:08 M51SE kernel: [ 278.204077] radeon :01:00.0: ring 0 stalled for more than 15868msec Aug 20 13:49:08 M51SE kernel: [ 278.204090] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:08 M51SE kernel: [ 278.716072] radeon :01:00.0: ring 0 stalled for more than 16380msec Aug 20 13:49:08 M51SE kernel: [ 278.716085] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:09 M51SE kernel: [ 279.228080] radeon :01:00.0: ring 0 stalled for more than 16892msec Aug 20 13:49:09 M51SE kernel: [ 279.228093] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:09 M51SE kernel: [ 279.740071] radeon :01:00.0: ring 0 stalled for more than 17404msec Aug 20 13:49:09 M51SE kernel: [ 279.740083] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:10 M51SE kernel: [ 280.252071] radeon :01:00.0: ring 0 stalled for more than 17916msec Aug 20 13:49:10 M51SE kernel: [ 280.252083] radeon :01:00.0: GPU lockup (current fence id 0x48db last fence id 0x48f6 on ring 0) Aug 20 13:49:10 M51SE kernel: [ 280.764076] radeon :01:00.0: ring 0 stalled for more than 18428msec Aug 20 13:49:10 M51SE kernel: [ 280.764089] radeon :01:00.0: GPU lockup (current fence id 0x4
[Kernel-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1782893 Title: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174) Status in bluez package in Ubuntu: Expired Status in gnome-bluetooth package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: am 5501 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788860] Re: Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788860 Title: Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Bug description: https://forums.linuxmint.com/viewtopic.php?f=59&t=276201 Kernel 4.15.0-20 Work with prime Kernel 4.15.0-22 Work with prime Kernel 4.15.0-23 Black Screen Kernel 4.15.0-24 Black Screen Kernel 4.15.0-29 Black Screen Kernel 4.15.0-30 Black Screen Kernel 4.15.0-32 Black Screen Kernel 4.15.0-33 Black Screen When using any Kernel 4.15.0-23 and above I am getting a Black screen when setting my bios to use hybrid graphics (optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub menu and after that just black screen, I can blindly enter my linux Mint password and hear linux mint login chime. I can also use recover mode in grub and boot with screen using software mode. If I choose nvidia discrete graphics in bios i can boot using nvidia hardware driver v390 or V396 and it all works fine. Intel graphics are disabled and not used and no prime. My graphics are Intel HD Graphics 530 and nvidia GTX 1070. Found that any kernel later than 4.15.0-22 will cause Black Screen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firepower 1695 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-08-11 (12 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: firepower 1695 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-08-11 (12 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 MachineType: Notebook P65_67RSRP Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: tara Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Not
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
kao, Please boot with kernel parameter "usbcore.dyndbg=+p" and attach dmesg after the issue happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
[Kernel-packages] [Bug 1799471] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [cc1: error: unrecognized command line option "-fstack-protector-strong"]
*** This bug is a duplicate of bug 1526155 *** https://bugs.launchpad.net/bugs/1526155 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1526155, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build + nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [cc1: error: unrecognized command line option "-fstack-protector-strong"] ** This bug has been marked a duplicate of bug 1526155 nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799471 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [cc1: error: unrecognized command line option "-fstack- protector-strong"] Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: 系统更改了gcc 版本后就n卡不能启动了 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 DKMSKernelVersion: 4.15.0-34-generic Date: Tue Oct 23 21:47:56 2018 DuplicateSignature: dkms:nvidia-dkms-390:390.77-0ubuntu0.18.04.1:cc1: error: unrecognized command line option "-fstack-protector-strong" InstallationDate: Installed on 2018-09-20 (33 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 390.77-0ubuntu0.18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799389] Re: not use /etc/thermald/thermal-conf.xml by default
Hi srinivas-pandruvada, It's a workaround to update man to avoid confusing, but not really help the case which user would like to correct the behavior without change in BIOS. So, I propose to rename original /etc/thermald/thermal-conf.xml to /etc/thermald/thermal-conf.xml.template then change the code of thermald to read /etc/thermald/thermal-conf.xml first and fall back to /var/run/thermald/thermal-conf.xml.auto if /etc/thermald/thermal- conf.xml is not there. welcome any idea. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1799389 Title: not use /etc/thermald/thermal-conf.xml by default Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug description: from man thermal-conf.xml, thermald should use /etc/thermald/thermal-conf.xml by default. So, that user can control the behavior. " - If the ACPI data is not optimized or buggy. In this case thermal-conf.xml can be used to correct the behavior without change in BIOS. " But, current thermald will always use the one auto generated: /var/run/thermald/thermal-conf.xml.auto --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bionic-master+X32 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: thermald 1.7.0-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1024-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 According to the bug description this is not a kernel bug at all since ALSA is working. Please close the upstream kernel bug. ** No longer affects: linux (Ubuntu) ** Project changed: linux => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: Linux Kernel Bug Tracker #201501 => None ** No longer affects: ubuntu ** Summary changed: - ASUS Xonar D2X not detected in PulseAudio + ASUS Xonar D2X not detected in PulseAudio while timidity is running ** Package changed: pulseaudio (Ubuntu) => timidity (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio while timidity is running Status in timidity package in Ubuntu: New Bug description: https://bugzilla.kernel.org/show_bug.cgi?id=201501 --- https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/582 --- My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00
[Kernel-packages] [Bug 1799613] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Confirmed Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
I have an Apple MacBook Pro 11,2 running Cosmic with this same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Triaged Bug description: https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799389] Re: not use /etc/thermald/thermal-conf.xml by default
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High ** Tags added: somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1799389 Title: not use /etc/thermald/thermal-conf.xml by default Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: New Bug description: from man thermal-conf.xml, thermald should use /etc/thermald/thermal-conf.xml by default. So, that user can control the behavior. " - If the ACPI data is not optimized or buggy. In this case thermal-conf.xml can be used to correct the behavior without change in BIOS. " But, current thermald will always use the one auto generated: /var/run/thermald/thermal-conf.xml.auto --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bionic-master+X32 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: thermald 1.7.0-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1024-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+attachment/5204718/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Attachment added: "get-edid.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+attachment/5204716/+files/get-edid.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+attachment/5204719/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Monitors: L24q-20 Graphics card: AMD RX 560 Let me know what other information I should attach, this is my first bug report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+attachment/5204720/+files/uname-a.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+attachment/5204717/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799613] [NEW] In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Public bug reported: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "xrandr_4.14.59.log" https://bugs.launchpad.net/bugs/1799613/+attachment/5204715/+files/xrandr_4.14.59.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux-meta package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796469] Re: aws s3 cp --recursive hangs on the last file on a large file transfer to instance
We ran into the exact same issue with pg_dump after upgrading to Bionic (4.15.0-1023-aws kernel) on r5.xlarge (a next-gen Nitro instance). After 16-80 MB of data is received, tcpdump shows the receive window collapsing to 1 (not quite suddenly, but quickly), and it never recovers. We have engaged with AWS support on this issue, and they referred us to this bug. Other than downgrading the kernel, has anyone discovered any other workarounds? -- 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/1796469 Title: aws s3 cp --recursive hangs on the last file on a large file transfer to instance Status in linux-aws package in Ubuntu: Confirmed Bug description: aws s3 cp --recursive hangs on the last file on a large transfer to an instance I have confirmed that this works on version Linux/4.15.0-1021-aws aws cli version aws-cli/1.16.23 Python/2.7.15rc1 Linux/4.15.0-1023-aws botocore/1.12.13 Ubuntu version Description: Ubuntu 18.04.1 LTS Release: 18.04 eu-west-1 - ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20180912 - ami-00035f41c82244dab Package version linux-aws: Installed: 4.15.0.1023.23 Candidate: 4.15.0.1023.23 Version table: *** 4.15.0.1023.23 500 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1796469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799393] Comment bridged from LTC Bugzilla
--- Comment From cls...@us.ibm.com 2018-10-23 19:47 EDT--- (In reply to comment #8) > I built a test kernel with commit 37fdffb217a45609edccbb8b407d031143f551c0. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1799393 > > Can you test this kernel and see if it resolves this bug? > > Note about installing test kernels: > ? If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > ? If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! Hi I was able to verify this with this kernel 4.18.0-10-generic #12~lp1799393 SMP Tue Oct 23 19:04:13 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux I did a ping flood and I can see that I am not getting wqe_err right way like before. #netstat -in Kernel Interface table Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg enP2p1s0 1500 4295 0 9 0 271 0 0 0 BMRU enp1s0f0 1500 5608322 0 0 0 5606566 0 0 0 BMRU lo 65536 12 0 0 012 0 0 0 LRU virbr015000 0 0 0 0 0 0 0 BMU # ethtool -S enp1s0f0 | grep rx_wqe_err rx_wqe_err: 0 Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799393 Title: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-10-18 11:34:40 == ---Problem Description--- At the system if u do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 Will see that rx side is hitting issue. ---Additional Hardware Info--- Mellanox CX5 Ethernet 100G lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Using a CX5 Ethernet 100G card lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] just configure IP ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up then partner system configure IP and then try ping -f ping -f 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 5413 packets transmitted, 5373 received, 0% packet loss, time 934ms rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms # ping 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1071ms then at the recv system then do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 you will see rx_wqe_err with a counter non-zero. This is fixed by this patch: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0 == Comment: #1 - Carol L. Soto - 2018-10-18 11:46:00 == I did a git clone to the cosmic tree and loaded the kernel in a system. kernel 4.18.12 and I can recreate it. lspci | grep Mell | grep ConnectX-5 :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :~# ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 2 rx0_wqe_err: 1 rx1_wqe_err: 1 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/582 -- Cristian Aravena Romero (caravena) ** Description changed: + https://bugzilla.kernel.org/show_bug.cgi?id=201501 + + --- + + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/582 + + --- + My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 - State: SUSPENDED - Name: alsa_output.pci-_00_1b.0.analog-stereo - Description: Built-in Audio Analog Stereo - Driver: module-alsa-card.c - Sample Specification: s32le 2ch 48000Hz - Channel Map: front-left,front-right - Owner Module: 7 - Mute: no - Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB - balance 0.00 - Base Volume: 65536 / 100% / 0.00 dB - Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor - Latency: 0 usec, configured 0 usec - Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY - Properties: - alsa.resolution_bits = "32" - device.api = "alsa" - device.class = "sound" - alsa.class = "generic" - alsa.subclass = "generic-mix" - alsa.name = "ALC892 Analog" - alsa.id = "ALC892 Analog" - alsa.subdevice = "0" - alsa.subdevice_name = "subdevice #0" - alsa.device = "0" - alsa.card = "2" - alsa.card_name = "HDA Intel PCH" - alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" - alsa.driver_name = "snd_hda_intel" - device.bus_path = "pci-:00:1b.0" - sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" - device.bus = "pci" - device.vendor.id = "8086" - device.vendor.name = "Intel Corporation" - device.product.id = "1c20" - device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" - device.form_factor = "internal" - device.string = "front:2" - device.buffering.buffer_size = "65536" - device.buffering.fragment_size = "32768" - device.access_mode = "mmap+timer" - device.profile.name = "analog-stereo" - device.profile.description = "Analog Stereo" - device.description = "Built-in Audio Analog Stereo" - alsa.mixer_name = "Realtek ALC892" - alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" - module-udev-detect.discovered = "1" - device.icon_name = "audio-card-pci" - Ports: - analog-output-lineout: Line Out (priority: 9900, available) - analog-output-headphones: Headphones (priority: 9000, not available) - Active Port: analog-output-lineout - Formats: - pcm + State: SUSPENDED + Name: alsa_output.pci-_00_1b.0.analog-stereo + Description: Built-in Audio Analog Stereo + Driver: module-alsa-card.c + Sample Specification: s32le 2ch 48000Hz + Channel Map: front-left,front-right + Owner Module: 7 + Mute: no + Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB + balance 0.00 + Base Volume: 65536 / 100% / 0.00 dB + Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor + Latency: 0 usec, configured 0 usec + Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY + Properties: + alsa.resolution_bits = "32" + device.api = "alsa" + device.class = "sound" + alsa.class = "generic" + alsa.subclass = "generic-mix" + alsa.name = "ALC892 Analog" + alsa.id = "ALC892 Analog" + alsa.subdevice = "0" + alsa.subdevice_name = "subdevice #0" + alsa.device = "0" + alsa.card = "2" + alsa.card_name = "HDA Intel PCH" + alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" + alsa.driver_name = "snd_hda_intel" +
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
https://bugzilla.kernel.org/show_bug.cgi?id=201501 -- Cristian Aravena Romero (caravena) ** Bug watch added: Linux Kernel Bug Tracker #201501 https://bugzilla.kernel.org/show_bug.cgi?id=201501 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201501 Importance: Unknown Status: Unknown ** Also affects: pulseaudio (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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2"
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
I think I found the source of the problem. Apparently, I had running the timidity daemon, which grabbed the ALSA PCM device and caused the "Device or resource busy" error. The "fuser -v /dev/snd/*" command didn't show this as I ran it as an unprivileged user and the daemon runs under a different "timidity" user. When I stopped the daemon and restarted pulseaudio, it recognized the D2X card. I'm sure I didn't install timidity manually, so I guess it is preinstalled either by default Ubuntu installation or it was added during the upgrade to 18.10. Or it was configured previously so that it didn't cause the conflict with PulseAudio. In any case, I think this conflict needs to be resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Fl
[Kernel-packages] [Bug 1799389] Re: not use /etc/thermald/thermal-conf.xml by default
Good observation. We need to update man page. I am looking for volunteer for updating man page. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1799389 Title: not use /etc/thermald/thermal-conf.xml by default Status in thermald package in Ubuntu: New Bug description: from man thermal-conf.xml, thermald should use /etc/thermald/thermal-conf.xml by default. So, that user can control the behavior. " - If the ACPI data is not optimized or buggy. In this case thermal-conf.xml can be used to correct the behavior without change in BIOS. " But, current thermald will always use the one auto generated: /var/run/thermald/thermal-conf.xml.auto --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+bionic-master+X32 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: thermald 1.7.0-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1024-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1799389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
I can add that I've also tried with the kernel 4.15.0-36.39 from Ubuntu 18.04 and the problem also reproduced. Right now I also suspect systemd/udev or userspace ALSA components because, although I can play sounds on the "default" and "sysdefault" devices, I cannot play on "D2X" or "surround51" devices: $ aplay -D hw:D2X /usr/share/sounds/alsa/Front_Center.wav aplay: main:828: audio open error: Device or resource busy I know no application is using the sound device, "fuser -v /dev/snd/*" output is empty. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor"
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
The problem reproduces with generic kernel 4.19.0. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2"
[Kernel-packages] [Bug 1799541] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204680/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus =
[Kernel-packages] [Bug 1799541] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204682/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus
[Kernel-packages] [Bug 1799541] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204681/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci"
[Kernel-packages] [Bug 1799541] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204679/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bu
[Kernel-packages] [Bug 1799541] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204676/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2"
[Kernel-packages] [Bug 1799541] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204678/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" dev
[Kernel-packages] [Bug 1799541] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204675/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bu
[Kernel-packages] [Bug 1799541] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204677/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bu
[Kernel-packages] [Bug 1799541] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204674/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci"
[Kernel-packages] [Bug 1799541] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204673/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci"
[Kernel-packages] [Bug 1799541] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204670/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci"
[Kernel-packages] [Bug 1799541] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204672/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "p
[Kernel-packages] [Bug 1799541] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1799541/+attachment/5204671/+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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Confirmed Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
apport information ** Tags added: apport-collected ** Description changed: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.st
[Kernel-packages] [Bug 1785174] 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 1785174 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 ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785174 Title: [solved] nvidia driver - does not resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). This only happens with TWO MONITORS ATTACHED. One monitor: no problem. With nouveau driver, two monitors are working as well. ubuntu GNOME 18.04, clean install kernel 4.15.0-29-generic #31-Ubuntu Fujitsu-Siemens Celsius WT-380 nvidia GT 630 Tried nvidia340, 390 and 396 - all the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
Hi Vincent, thanks for your report - really good research, even indicating a potential fix. I manage to reproduce this issue using the following steps: 1) Be sure to run Ubuntu 16.04 on both guest and host, both running kernel 4.4.0 (could be latest version of this kernel) 2) In the guest, install the package "msr-tools", like: "sudo apt install msr-tools" 3) Still on guest, run: "sudo modprobe msr; sudo wrmsr 0x48 1" This will enable the MSR bit for IBRS inside the guest 4) Now the host shows bad performance If we run "sudo wrmsr 0x48 0" in the guest, host gets its performance back. I'll investigate some commits upstream, including the one you suggested, and once we figure the exact fix for this, will request SRU to the kernel team. Thanks, Guilherme ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764956 Title: Guests using IBRS incur a large performance penalty Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hello! As of Linux 4.4.0-119, when a KVM guest is using IBRS, this incurs a very large performance penalty on the hosts and other guests. From my understanding, the patch f676aa34b4027d1a7a4bbcc58b81b20c68c7ce0c is incomplete. If host doesn't handle IBRS itself (which is now the case by default since 4.4.0-116: it relies on retpoline instead) but the guest does (eg running an earlier kernel), the guest will set IBRS for the CPU it is running on from time to time but if it gets preempted at some point, the IBRS bit will stay, incurring a major performance penalty for all other users of the CPU (host userland, host kernel and other guests not caring about IBRS). The equivalent patch in mainline (d28b387fb74da95d69d2615732f50cceb38e9a4d) ensure the appropriate MSR is correctly restored when switching from one guest to another or from one guest to host. The issue is easy to reproduce: host running 4.4.0-119, exposing "spec_ctrl" to a guest running CentOS 7.4 with its January kernel. Wait a few minutes and the host will become pretty slow. A simple shell loop will take 10 more times to execute. Executing "sysctl -w kernel.ibrs_dump=1" will show that most real cores have now their IBRS bit set to 1. A workaround is to reeanble IBRS on the host (sysctl -w kernel.ibrs_enabled=1). This way, IBRS will be correctly disabled when changing context. A long term solution would be to properly backport the patch from mainline. It is not part of the 4.4 stable branch and it seems not trivial to port. A mid term solution could be to remove the faulty patch (not exposing IBRS), since most VM don't need it anymore. This also salvage the ability to use IBPB (which doesn't seem to alter performance that much) but it isn't believed to be essential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785174] Re: [solved] nvidia driver - does not resume from suspend
** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785174 Title: [solved] nvidia driver - does not resume from suspend Status in linux package in Ubuntu: New Bug description: System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). This only happens with TWO MONITORS ATTACHED. One monitor: no problem. With nouveau driver, two monitors are working as well. ubuntu GNOME 18.04, clean install kernel 4.15.0-29-generic #31-Ubuntu Fujitsu-Siemens Celsius WT-380 nvidia GT 630 Tried nvidia340, 390 and 396 - all the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785174] [NEW] [solved] nvidia driver - does not resume from suspend
You have been subscribed to a public bug: System gets to sleep (systemctl suspend), when pressing a key to resume from sleep, the system will power up (fans and hard disk can be heard), but screens remain dark. Not even terminals can be accessed (ctrl-alt-F2...6). This only happens with TWO MONITORS ATTACHED. One monitor: no problem. With nouveau driver, two monitors are working as well. ubuntu GNOME 18.04, clean install kernel 4.15.0-29-generic #31-Ubuntu Fujitsu-Siemens Celsius WT-380 nvidia GT 630 Tried nvidia340, 390 and 396 - all the same result. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- [solved] nvidia driver - does not resume from suspend https://bugs.launchpad.net/bugs/1785174 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
that said, the commit in xserver is trivial.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: Fix Committed Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799305] Re: No desktop at boot after upgrade form 18.04 to 18.10
** Description changed: - I upgrade from 18.04 to 18.10 and now the desktop does not start on a + I upgraded from 18.04 to 18.10 and now the desktop does not start on a fresh boot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected from a clean boot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 22 22:32:04 2018 InstallationDate: I
[Kernel-packages] [Bug 1796553] Re: BT mouse getting reset during operation
btusb.enable_autosuspend=0 definitely made the issue go away.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Bug description:
(note: It's unclear to me if that's a kernel regression or an issue with
bluez)
I've been using this particular combination of Bluetooth mouse ("TECKNET
BM306") & laptop ("Dell Latitude E7240") for over a year now.
It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
a strange disconnect behaviour:
1) Mouse is working ok
2) Mouse suddenly stops
3) Disabling and enabling bluetooth on the laptop makes the mouse work again.
when this happens, dmesg reports:
[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
ehci-pci
Disabling bluetooth and enabling it again results in:
[57833.455866] usb 1-1.3: USB disconnect, device number 18
[57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
[57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
[57837.016248] usb 1-1.3: New USB device found, idVendor=8087,
idProduct=07dc, bcdDevice= 0.01
[57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
[57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
[57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
[57841.724587] input: TECKNET BM306 Mouse as
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
[57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05
$ bluetoothctl --version
bluetoothctl: 5.50
$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: FC:F8:AE:45:3C:05 ACL MTU: 1021:5 SCO MTU: 96:5
UP RUNNING PSCAN
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6) Revision: 0x500
LMP Version: 4.0 (0x6) Subversion: 0x500
Manufacturer: Intel Corp. (2)
$ bluetoothctl
Agent registered
[TECKNET BM306]# show
Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
[TECKNET BM306]# devices
Device 20:9B:A5:68:AE:67 SoundBuds Flow
Device DC:2C:26:01:24:23 TECKNET BM306
Device 88:71:E5:0E:6B:99 Echo-HPT
Device 00:0B:E4:A0:A2:14 Nokia BH-103
Device A8:96:75:8B:4F:49 Moto G5S Plus
Device 00:02:5B:20:75:3C Trust SPK-02
Device 88:75:98:F2:5C:9E NS9+
Device 00:E0:4C:D5:E0:F5 SoundCore mini
[TECKNET BM306]# info DC:2C:26:01:24:23
Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129
$ rfkill list
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
4: dell-wwan: Wireless WAN
Soft blocked: yes
[Kernel-packages] [Bug 1799388] Re: TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Cosmic)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799388
Title:
TM (Hardware Transactional Memory) instructions halt application on
baremetal POWER9 DD2.1
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-10-15
08:55:55 ==
+++ This bug was initially created as a clone of Bug #167756 +++
---Problem Description---
TM (Hardware Transactional Memory) instructions halt application on baremetal
POWER9 DD2.1
Contact Information = grom...@br.ibm.com
---Additional Hardware Info---
POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon.
Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr
004e 1201) with the latest firmware [1] (Firmware level [2] was also tested
with the same result) and running Linux from Linus' upstream tree [3] or
powerpc/next branch [4] is not working as expected. Once a TM instruction is
executed in a process (any instruction), the process halts completely and has
to be killed.
A simple test case is to execute a 'tend.' which accordingly to POWER8
behaviour and the ISA v3.00 if executed "in Non-transactional state is
treated as a no-op." [5]. It means that the instruction in the test
case below should be treated simply as a 'nop' instruction and the
process would terminate normally but instead it halts and the process
never terminates:
root@io83:~/gromero# cat t.c
int main() { asm ("tend.;"); }
root@io83:~/gromero# make t
make: 't' is up to date.
root@io83:~/gromero# ./t
^C
Ubuntu stock kernel 4.15.0-20-generic was also tested with the same
result.
I confirmed with Erich Hauptli (FW team) that FW stack levels [1]
contain all the TM fixes we have at the moment.
Thus, that issue affects any application that uses TM on a baremetal
POWER9 DD2.1 (pvr 004e 1201).
[1]
IBM-witherspoon-ibm-OP9_v1.19_1.160
op-build-v1.21.2-255-g6ad1636-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.5-op910-1
hostboot-ed53939
linux-4.14.24-openpower1-paed97e8
petitboot-v1.6.6-p41a158a
machine-xml-4af
occ-ef5d466
hostboot-binaries-6a92b6d
capp-ucode-p9-dd2-v3
sbe-7e02c23
[2]
open-power-witherspoon-v1.22-82-gebe1295-dirty
buildroot-2018.02.1-6-ga8d11267c2
skiboot-v6.0-rc1
hostboot-d9bf361-p6755b85
occ-f741c41
linux-4.16.7-openpower1-p945838d
petitboot-v1.7.1-pd695626
machine-xml-7cd20a6
hostboot-binaries-53aece6
capp-ucode-p9-dd2-v4
sbe-8e0105e
hcode-hw050318a.op920
[3] https://github.com/torvalds/linux.git (master)
[4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next)
[5] Power ISA - Book II, p. 894
Stack trace output:
no
Oops output:
no
Userspace tool common name: any tool using TM instruction set
Userspace rpm: not relevant
The userspace tool has the following bit modes: 64-bit
System Dump Info:
The system is not configured to capture a system dump.
Userspace tool obtained from project website: na
*Additional Instructions for grom...@br.ibm.com:
-Attach sysctl -a output output to the bug.
-Attach ltrace and strace of userspace application.
The following patch fixes this issue:
http://patchwork.ozlabs.org/patch/968375/
Author: Michael Neuling
Date: Tue Sep 11 13:07:56 2018 +1000
powerpc/tm: Fix HFSCR bit for no suspend case
Currently on P9N DD2.1 we end up taking infinite TM facility
unavailable exceptions on the first TM usage by userspace.
In the special case of TM no suspend (P9N DD2.1), Linux is told TM is
off via CPU dt-ftrs but told to (partially) use it via
[Kernel-packages] [Bug 1799228] Re: USB-ports do not work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799228 Title: USB-ports do not work Status in linux package in Ubuntu: Incomplete Bug description: Two out of 3 USB-ports are not regognized anymore (i.e. when I insert a USB-stick, it will not be shown in Nautilus). I tried various workarounds from ubuntuusers, but they were not successful. Among them to use "dpkg-reconfigure x-server". X-org now reported an error, docuimented in the attachment. Earlier I wanted to create an image with Clonezilla and selected a USB-stick at port #2 as target, however, the target was not detected successfully and the backup-procedure stopped. I suspect that the issues may be relatd. Kind regards, Stefan ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Oct 22 15:57:33 2018 DistUpgraded: 2018-10-03 09:25:30,625 DEBUG failed to SystemUnLock() (E:Nicht gesperrt) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.4.0-137-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1ccd] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2016-07-21 (823 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X555UB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=664e835e-2af1-414d-af49-66620923cba1 ro quiet splash pci=noaer acpi_osi= acpi_backlight=native vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-03 (19 days ago) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 22 15:43:15 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Kernel-packages] [Bug 1796693] Re: PCI/internal sound card not detected
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796693 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Incomplete Bug description: I can't hear anything. And in the settings isn't any device like speaker or headphones. I run Ubuntu on ASUS X205TA. Thank you so much for your help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.10.0-041000-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Oct 8 16:51:54 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA 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.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X205TA 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/1796693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799359] Re: Network remains disabled after waking up laptop from sleep
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799359 Title: Network remains disabled after waking up laptop from sleep Status in linux package in Ubuntu: Incomplete Bug description: The reconnection to network works in linux 4.13.0-45 but not in 4.15.0-x so far. Latest vesion 38. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647511] Re: During kernel upgrade, /usr/sbin/dkms falsely reports that initrd.img won't be created
seeing this error message on 18.04 Setting up linux-headers-4.15.0-38-generic (4.15.0-38.41) ... /etc/kernel/header_postinst.d/dkms: Warning: Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1647511 Title: During kernel upgrade, /usr/sbin/dkms falsely reports that initrd.img won't be created Status in DKMS: Confirmed Status in One Hundred Papercuts: Confirmed Status in dkms package in Ubuntu: Confirmed Bug description: Ubuntu release == Description: Ubuntu 16.04.1 LTS Release: 16.04 Version of package == dkms: Installed: 2.2.0.3-2ubuntu11.3 Candidate: 2.2.0.3-2ubuntu11.3 Version table: *** 2.2.0.3-2ubuntu11.3 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 2.2.0.3-2ubuntu11 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages The problem === When setting up `linux-image-4.4.0-53-generic`, the following warning appears three times: : Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. However, when setting up `linux-image-extra-4.4.0-53-generic`, the following message appears: update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic The text "Unable to find an initial ram disk" appears in `/usr/sbin/dkms`, though it may appear elsewhere. What should happen == The warning message should not appear. Messages when setting up the two packages = Setting up linux-image-4.4.0-53-generic (4.4.0-53.74) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic : Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. : Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. : Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.4.0-53-generic Found initrd image: /boot/initrd.img-4.4.0-53-generic Found linux image: /boot/vmlinuz-4.4.0-51-generic Found initrd image: /boot/initrd.img-4.4.0-51-generic Found linux image: /boot/vmlinuz-4.4.0-47-generic Found initrd image: /boot/initrd.img-4.4.0-47-generic Adding boot menu entry for EFI firmware configuration done Setting up linux-image-extra-4.4.0-53-generic (4.4.0-53.74) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic update-initramfs: Generating /boot/initrd.img-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-53-generic /boot/vmlinuz-4.4.0-53-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.4.0-53-generic Found initrd image: /boot/initrd.img-4.4.0-53-generic Found linux image: /boot/vmlinuz-4
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
Thank you for taking the time to report this bug and helping to make Ubuntu better. Execute the following command in the terminal: $ apport-collect -p linux 1799541 Best regards, -- Cristian Aravena Romero (caravena) ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** 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/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Incomplete Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45"
[Kernel-packages] [Bug 1799541] Re: ASUS Xonar D2X not detected in PulseAudio
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799541 Title: ASUS Xonar D2X not detected in PulseAudio Status in linux package in Ubuntu: Incomplete Bug description: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor
[Kernel-packages] [Bug 1799541] [NEW] ASUS Xonar D2X not detected in PulseAudio
You have been subscribed to a public bug: My ASUS Xonar D2X (AV200) is not detected and not present in the PulseAudio list of sinks (pactl list sinks) or sources (pactl list sources). It is detected by ALSA, as shown by "cat /proc/asound/cards" and "aplay -L". When PulseAudio is not running, I can also play audio by "aplay -D default /usr/share/sounds/alsa/Front_Center.wav" on the D2X card, I can hear the sound, so the sound card is physically working. This problem appeared after an upgrade from Kubuntu 18.04 to 18.10. D2X in PulseAudio was working fine in 18.04. $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 28172 / 43% / -22.00 dB, front-right: 28172 / 43% / -22.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "32" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC892 Analog" alsa.id = "ALC892 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:2" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC892" alsa.components = "HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 9900, available) analog-output-headphones: Headphones (priority: 9000, not available) Active Port: analog-output-lineout Formats: pcm $ pactl list sources Source #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s32le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "2" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7f2 irq 45" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card2" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "2" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Formats: pcm Source #1 State: SUSPENDED Name: alsa_input.pci-_00_1b.0.ana
[Kernel-packages] [Bug 1799393] Re: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
I built a test kernel with commit 37fdffb217a45609edccbb8b407d031143f551c0. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1799393 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799393 Title: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-10-18 11:34:40 == ---Problem Description--- At the system if u do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 Will see that rx side is hitting issue. ---Additional Hardware Info--- Mellanox CX5 Ethernet 100G lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Using a CX5 Ethernet 100G card lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] just configure IP ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up then partner system configure IP and then try ping -f ping -f 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 5413 packets transmitted, 5373 received, 0% packet loss, time 934ms rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms # ping 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1071ms then at the recv system then do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 you will see rx_wqe_err with a counter non-zero. This is fixed by this patch: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0 == Comment: #1 - Carol L. Soto - 2018-10-18 11:46:00 == I did a git clone to the cosmic tree and loaded the kernel in a system. kernel 4.18.12 and I can recreate it. lspci | grep Mell | grep ConnectX-5 :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :~# ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 2 rx0_wqe_err: 1 rx1_wqe_err: 1 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... Let me check if the proposed patch needs backport or not. == Comment: #3 - Carol L. Soto - 2018-10-18 13:34:46 == I was able to apply the proposed patch as it to the cosmic git tree and no issue. (no need to backport) using a kernel 4.18.12+. With the proposed patch I do not see wqe err and ping does not stop. ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 0 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/17
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
This workaround in comment #72 works for me; two finger scrolling and click-and-drag work after resuming from suspend. Add the following line to this file: `/etc/defaults/grub` > GRUB_CMDLINE_LINUX_DEFAULT="quiet splash psmouse.synaptics_intertouch=0" Then run `update-grub` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799388] Re: TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1
I built a test kernel with commit dd9a8c5a87395b6f0555. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1799388
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799388
Title:
TM (Hardware Transactional Memory) instructions halt application on
baremetal POWER9 DD2.1
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-10-15
08:55:55 ==
+++ This bug was initially created as a clone of Bug #167756 +++
---Problem Description---
TM (Hardware Transactional Memory) instructions halt application on baremetal
POWER9 DD2.1
Contact Information = grom...@br.ibm.com
---Additional Hardware Info---
POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon.
Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr
004e 1201) with the latest firmware [1] (Firmware level [2] was also tested
with the same result) and running Linux from Linus' upstream tree [3] or
powerpc/next branch [4] is not working as expected. Once a TM instruction is
executed in a process (any instruction), the process halts completely and has
to be killed.
A simple test case is to execute a 'tend.' which accordingly to POWER8
behaviour and the ISA v3.00 if executed "in Non-transactional state is
treated as a no-op." [5]. It means that the instruction in the test
case below should be treated simply as a 'nop' instruction and the
process would terminate normally but instead it halts and the process
never terminates:
root@io83:~/gromero# cat t.c
int main() { asm ("tend.;"); }
root@io83:~/gromero# make t
make: 't' is up to date.
root@io83:~/gromero# ./t
^C
Ubuntu stock kernel 4.15.0-20-generic was also tested with the same
result.
I confirmed with Erich Hauptli (FW team) that FW stack levels [1]
contain all the TM fixes we have at the moment.
Thus, that issue affects any application that uses TM on a baremetal
POWER9 DD2.1 (pvr 004e 1201).
[1]
IBM-witherspoon-ibm-OP9_v1.19_1.160
op-build-v1.21.2-255-g6ad1636-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.5-op910-1
hostboot-ed53939
linux-4.14.24-openpower1-paed97e8
petitboot-v1.6.6-p41a158a
machine-xml-4af
occ-ef5d466
hostboot-binaries-6a92b6d
capp-ucode-p9-dd2-v3
sbe-7e02c23
[2]
open-power-witherspoon-v1.22-82-gebe1295-dirty
buildroot-2018.02.1-6-ga8d11267c2
skiboot-v6.0-rc1
hostboot-d9bf361-p6755b85
occ-f741c41
linux-4.16.7-openpower1-p945838d
petitboot-v1.7.1-pd695626
machine-xml-7cd20a6
hostboot-binaries-53aece6
capp-ucode-p9-dd2-v4
sbe-8e0105e
hcode-hw050318a.op920
[3] https://github.com/torvalds/linux.git (master)
[4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next)
[5] Power ISA - Book II, p. 894
Stack trace output:
no
Oops output:
no
Userspace tool common name: any tool using TM instruction set
Userspace rpm: not relevant
The userspace tool has the following bit modes: 64-bit
System Dump Info:
The system is not configured to capture a system dump.
Userspace tool obtained from project website: na
*Additional Instructions for grom...@br.ibm.com:
-Attach sysctl -a output output to the bug.
-Attach ltrace and strace of userspace application.
The following patch fixes this issue:
http://patchwork.ozlabs.org/patch/968375/
Author: Michael Neuling
Date: Tue Sep 11 13:07:56 2018 +1000
powerpc/tm: Fix HFSCR bit for no suspend case
Currently on P9N DD2.1 we end up taking infinite TM facility
unavailable exceptions on the first TM usage by userspace.
In the special case of TM no suspend (P9N DD2.1), Linux is told TM is
off via CPU dt-ftrs but told to (partially) use it via
OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED. So HFSCR[TM] will be off from
dt-ftrs but we need to turn it on for the no suspend case.
This patch fixes this by enabling HFSCR TM in this case.
Cc: sta...@vger.kernel
[Kernel-packages] [Bug 1799388] Re: TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799388
Title:
TM (Hardware Transactional Memory) instructions halt application on
baremetal POWER9 DD2.1
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-10-15
08:55:55 ==
+++ This bug was initially created as a clone of Bug #167756 +++
---Problem Description---
TM (Hardware Transactional Memory) instructions halt application on baremetal
POWER9 DD2.1
Contact Information = grom...@br.ibm.com
---Additional Hardware Info---
POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon.
Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr
004e 1201) with the latest firmware [1] (Firmware level [2] was also tested
with the same result) and running Linux from Linus' upstream tree [3] or
powerpc/next branch [4] is not working as expected. Once a TM instruction is
executed in a process (any instruction), the process halts completely and has
to be killed.
A simple test case is to execute a 'tend.' which accordingly to POWER8
behaviour and the ISA v3.00 if executed "in Non-transactional state is
treated as a no-op." [5]. It means that the instruction in the test
case below should be treated simply as a 'nop' instruction and the
process would terminate normally but instead it halts and the process
never terminates:
root@io83:~/gromero# cat t.c
int main() { asm ("tend.;"); }
root@io83:~/gromero# make t
make: 't' is up to date.
root@io83:~/gromero# ./t
^C
Ubuntu stock kernel 4.15.0-20-generic was also tested with the same
result.
I confirmed with Erich Hauptli (FW team) that FW stack levels [1]
contain all the TM fixes we have at the moment.
Thus, that issue affects any application that uses TM on a baremetal
POWER9 DD2.1 (pvr 004e 1201).
[1]
IBM-witherspoon-ibm-OP9_v1.19_1.160
op-build-v1.21.2-255-g6ad1636-dirty
buildroot-2017.11-5-g65679be
skiboot-v5.10.5-op910-1
hostboot-ed53939
linux-4.14.24-openpower1-paed97e8
petitboot-v1.6.6-p41a158a
machine-xml-4af
occ-ef5d466
hostboot-binaries-6a92b6d
capp-ucode-p9-dd2-v3
sbe-7e02c23
[2]
open-power-witherspoon-v1.22-82-gebe1295-dirty
buildroot-2018.02.1-6-ga8d11267c2
skiboot-v6.0-rc1
hostboot-d9bf361-p6755b85
occ-f741c41
linux-4.16.7-openpower1-p945838d
petitboot-v1.7.1-pd695626
machine-xml-7cd20a6
hostboot-binaries-53aece6
capp-ucode-p9-dd2-v4
sbe-8e0105e
hcode-hw050318a.op920
[3] https://github.com/torvalds/linux.git (master)
[4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next)
[5] Power ISA - Book II, p. 894
Stack trace output:
no
Oops output:
no
Userspace tool common name: any tool using TM instruction set
Userspace rpm: not relevant
The userspace tool has the following bit modes: 64-bit
System Dump Info:
The system is not configured to capture a system dump.
Userspace tool obtained from project website: na
*Additional Instructions for grom...@br.ibm.com:
-Attach sysctl -a output output to the bug.
-Attach ltrace and strace of userspace application.
The following patch fixes this issue:
http://patchwork.ozlabs.org/patch/968375/
Author: Michael Neuling
Date: Tue Sep 11 13:07:56 2018 +1000
powerpc/tm: Fix HFSCR bit for no suspend case
Currently on P9N DD2.1 we end up taking infinite TM facility
unavailable exceptions on the first TM usage by userspace.
In the special case of TM no suspend (P9N DD2.1), Linux is told TM is
off via CPU dt-ftrs but told to (partially) use it via
OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED. So HFSCR[TM] will be off from
dt-ftrs but we need to turn it on for the no suspend case.
This patch fixes this by enabling HFSCR TM in this case.
Cc: sta...@vger.kernel.org # 4.15+
Signed-off-by: Michael Neuling
== Comment: #2 - Michael Ranweiler - 2018-10-15
13:52:13 ==
This is in the powerpc -next branch:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=dd9a8c5a87395b6f05552c3b44e42fdc95760552
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1799388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-pac
[Kernel-packages] [Bug 1799393] Re: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799393 Title: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-10-18 11:34:40 == ---Problem Description--- At the system if u do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 Will see that rx side is hitting issue. ---Additional Hardware Info--- Mellanox CX5 Ethernet 100G lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Using a CX5 Ethernet 100G card lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] just configure IP ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up then partner system configure IP and then try ping -f ping -f 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 5413 packets transmitted, 5373 received, 0% packet loss, time 934ms rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms # ping 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1071ms then at the recv system then do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 you will see rx_wqe_err with a counter non-zero. This is fixed by this patch: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0 == Comment: #1 - Carol L. Soto - 2018-10-18 11:46:00 == I did a git clone to the cosmic tree and loaded the kernel in a system. kernel 4.18.12 and I can recreate it. lspci | grep Mell | grep ConnectX-5 :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :~# ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 2 rx0_wqe_err: 1 rx1_wqe_err: 1 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... Let me check if the proposed patch needs backport or not. == Comment: #3 - Carol L. Soto - 2018-10-18 13:34:46 == I was able to apply the proposed patch as it to the cosmic git tree and no issue. (no need to backport) using a kernel 4.18.12+. With the proposed patch I do not see wqe err and ping does not stop. ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 0 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1799393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799490] Re: Kernel 4.15 boot error on XenServer
In response to the kernel bot, I am not able to get to a point that I can gather logs. @jsalisbury I tried running 4.19.0-041900 with similar issue. Unfortunately the exact error and trace scroll by faster than I can capture them, but the trace appears to be the same. Based on the posts, I will add a tag kernel-bug-exists-upstream and mark Confirmed. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 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- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax
apport information
** Tags added: apport-collected
** Description changed:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.4
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-10-23 (0 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
+ IwConfig:
+ lono wireless extensions.
+
+ enp0s3no wireless extensions.
+ Lsusb:
+ Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+ Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcFB:
+
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
+ RelatedPackageVersions:
+ linux-restricted-modules-4.15.0-36-generic N/A
+ linux-backports-modules-4.15.0-36-generic N/A
+ linux-firmware 1.173.1
+ RfKill:
+
+ Tags: bionic
+ Uname: Linux 4.15.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/01/2006
+ dmi.bios.vendor: innotek GmbH
+ dmi.bios.version: VirtualBox
+ dmi.board.name: VirtualBox
+ dmi.board.vendor: Oracle Corporation
+ dmi.board.version: 1.2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Oracle Corporation
+ dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
+ dmi.product.family: Virtual Machine
+ dmi.product.name: VirtualBox
+ dmi.product.version: 1.2
+ dmi.sys.vendor: innotek GmbH
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204640/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
[Kernel-packages] [Bug 1799237] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204641/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204647/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204648/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204650/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204649/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204644/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204643/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204645/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204646/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799237] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1799237/+attachment/5204642/+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/1799237
Title:
mprotect fails on ext4 with dax
Status in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a file located on ext4 mounted with "dax". When I call mmap on that
file with protection flag different than PROT_NONE and pass the returned
address to mprotect(..., PROT_NONE) it fails with:
mprotect: Permission denied
This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu
kernel-specific.
Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic
Below is a code which can be used to reproduce the issue.
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
if (argc < 3) {
fprintf(stderr, "usage %s file size\n",
argv[0]);
return 1;
}
int size = atoi(argv[2]);
int fd = open(argv[1], O_RDWR);
if (fd < 0) {
perror("open");
return 1;
}
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE,
MAP_SHARED, fd, 0);
if (addr == MAP_FAILED) {
perror("mmap");
return 1;
}
if(mprotect(addr, size, PROT_NONE)) {
perror("mprotect");
return 1;
}
return 0;
}
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-23 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
RfKill:
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1799237/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
This same thing happens to all distros - I've seen a bug report like this on Redhat's bug tracker (Fedora), and tried other distros, such as Manjaro. So it's not just Debian or Ubuntu I guess. I assume developers that take care of individual distros can make changes to the kernel and then send them up to the mainline version to be available for everyone. It's just that nobody cares enough, since it's not a super popular model I guess. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1799393] Re: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799393 Title: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-10-18 11:34:40 == ---Problem Description--- At the system if u do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 Will see that rx side is hitting issue. ---Additional Hardware Info--- Mellanox CX5 Ethernet 100G lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Using a CX5 Ethernet 100G card lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] just configure IP ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up then partner system configure IP and then try ping -f ping -f 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 5413 packets transmitted, 5373 received, 0% packet loss, time 934ms rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms # ping 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1071ms then at the recv system then do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 you will see rx_wqe_err with a counter non-zero. This is fixed by this patch: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0 == Comment: #1 - Carol L. Soto - 2018-10-18 11:46:00 == I did a git clone to the cosmic tree and loaded the kernel in a system. kernel 4.18.12 and I can recreate it. lspci | grep Mell | grep ConnectX-5 :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :~# ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 2 rx0_wqe_err: 1 rx1_wqe_err: 1 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... Let me check if the proposed patch needs backport or not. == Comment: #3 - Carol L. Soto - 2018-10-18 13:34:46 == I was able to apply the proposed patch as it to the cosmic git tree and no issue. (no need to backport) using a kernel 4.18.12+. With the proposed patch I do not see wqe err and ping does not stop. ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 0 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1799393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@dr-strangehate Thanks. I am no expert either. It seems to me that the problem could owe either to Lenovo's hardware, or to the kernel, or to Ubuntu, or to Debian. Complicating matters, if Lenovo's driver is buggy then it is the kernel's job to compensate for that, I suppose. If the bug should be reported to the kernel, the questions arise: has it been and, if it has not been, who is going to do it? I myself have no experience reporting bugs to/for the kernel 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1799497] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1799497/+attachment/5204636/+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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.
[Kernel-packages] [Bug 1799497] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1799497/+attachment/5204637/+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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ub
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
Note that I've deleted the wifisyslog and currentdmesg as they're not relevant (current boot) and included information that I'd rather not have exposed publicly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.
[Kernel-packages] [Bug 1799497] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1799497/+attachment/5204639/+files/WifiSyslog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+attachment/5204633/+files/CurrentDmesg.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799497/+attachment/5204639/+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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rn
[Kernel-packages] [Bug 1799470] Re: slow boot in kubuntu 18.04
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799470 Title: slow boot in kubuntu 18.04 Status in linux package in Ubuntu: Incomplete Bug description: I have the bug with the Kubuntu 18.04 sb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 Before, i was using the 16 (LTS) version and the boot was quick. I have first try un update and i have the problem, with a fresh install, i have also the same problem. In the boot, i have a long time (33s) without message and action In this extract of the dmesg, you can see the 33 seconds without messages [5.434266] sdc: sdc1 sdc2 [5.434268] sd 11:0:0:0: [sdd] 537234768 512-byte logical blocks: (275 GB/256 GiB) [5.434288] sd 11:0:0:0: [sdd] Write Protect is off [5.434290] sd 11:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [5.434312] sd 11:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [5.434404] ata12.00: Enabling discard_zeroes_data [5.434436] sd 5:0:0:0: [sdc] Attached SCSI disk [5.435541] sdd: sdd1 sdd2 [5.435661] ata12.00: Enabling discard_zeroes_data [5.435893] sd 11:0:0:0: [sdd] supports TCG Opal [5.435895] sd 11:0:0:0: [sdd] Attached SCSI disk [ 38.317233] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 38.439463] ip_tables: (C) 2000-2006 Netfilter Core Team [ 38.548456] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 38.568547] systemd[1]: Detected architecture x86-64. [ 38.572697] systemd[1]: Set hostname to . [ 38.649301] systemd[1]: Created slice User and Session Slice. [ 38.649610] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 38.649680] systemd[1]: Created slice System Slice. [ 38.649716] systemd[1]: Listening on fsck to fsckd communication Socket. [ 38.649740] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 38.649760] systemd[1]: Listening on udev Kernel Socket. [ 38.649768] systemd[1]: Reached target Slices. [ 38.667706] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro With the command sudo systemd-analyze time [sudo] Mot de passe de jacky : Startup finished in 12.351s (firmware) + 11.414s (loader) + 38.418s (kernel) + 1.902s (userspace) = 1min 4.086s graphical.target reached after 1.898s in userspace You can see the 38 seconds in the kernel mode In the blame, there is any long action sudo systemd-analyze blame 352ms disk-tera.mount 321ms NetworkManager.service 273ms dev-mapper-kubuntu\x2d\x2dvg\x2droot.device 264ms udisks2.service 236ms networkd-dispatcher.service 234ms snapd.service 201ms systemd-logind.service 196ms mpd.service 192ms ModemManager.service 170ms disk-sdb.mount 157ms systemd-timesyncd.service 132ms systemd-resolved.service 130ms accounts-daemon.service 84ms thermald.service 79ms alsa-restore.service 76ms pppd-dns.service 74ms keyboard-setup.service 74ms plymouth-quit.service 71ms systemd-journal-flush.service 68ms wpa_supplicant.service 61ms lvm2-pvscan@8:50.service 58ms gpu-manager.service 57ms colord.service 56ms systemd-udev-trigger.service 53ms systemd-udevd.service 52ms upower.service 51ms packagekit.service 49ms lvm2-monitor.service 49ms apparmor.service 46ms rsyslog.service 44ms user@119.service 42ms systemd-journald.service 41ms grub-common.service 39ms polkit.service 27ms systemd-modules-load.service 27ms plymouth-start.service 26ms user@1000.service
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Sorry, but it seems the kernels 4.15.0-38 in bionic-updates and in bionic-proposed are the same. I have tested it already (#57), the bug is in place. I would be happy to help test other kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1799497/+attachment/5204638/+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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sourc
[Kernel-packages] [Bug 1799490] Re: Kernel 4.15 boot error on XenServer
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799490 Title: Kernel 4.15 boot error on XenServer Status in linux package in Ubuntu: Incomplete Bug description: I recently upgraded an ubuntu VM from 16.04.1 to 18.04.1 running on XenServer 7.1. The upgrade itself was fine, but several kernel updates after the upgrade have caused the VM to fail to boot. All kernels that fail to boot seem to be from 4.15. Current, the latest kernel I've tried is 4.15.0-38, though, day-to-day I'm running a 4.4 kernel since the VM is necessary to my environment. The error message on boot is: unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x9806c04a (native_read_msr+0xa/0x30) The trace is attached as a screenshot. I haven't been able to get a log containing the output. user@host:~$ cat /proc/version_signature Ubuntu 4.4.0-112.135-generic 4.4.98 user@host:~$ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Physical Slot: 0 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- [disabled] 00:03.0 SCSI storage controller [0100]: XenSource, Inc. Xen Platform Device [5853:0001] (rev 02) Subsystem: XenSource, Inc. Xen Platform Device [5853:0001] Physical Slot: 3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Same problem on Thinkpad X1 Carbon 3rd Gen with Ubuntu 18.04 and 18.10. Currently using kernel 4.18.0-10-generic. Commands in #16 resolve the problem for 18.10, not tested for 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I built the next test kernel, up to the following commit:
68cc38ff33f38424d0456f9a1ecfec4683226a7e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.
Thanks in advance
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
