[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Patchset has already landed in Cosmic / Disco, marking the linux package as fix released. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: === SRU Justification === [Impact] NULL pointer dereference in netvsc_probe(). Module hv_netvsc is included in initramfs, so this blocks the boot process. For Hyper-V only supports single channel, rndis_filter_device_add() bails early and jump to tag "out". Subsequent code calls rndis_filter_device_remove() and returns ERR_PTR(ret), where ret is 0 (sucess). Because of that, it passes IS_ERR(nvdev) check in netvsc_probe() and cause a NULL pointer dereference, as nvdev now is 0: ... if (nvdev->num_chn > 1) schedule_work(>subchan_work); [Fix] Correctly return net_device at the end of rndis_filter_device_add(). [Test] Users report positive result. [Regression Potenial] Low. Trivial change, patches are in upstream sometime. === Original Bug Report === Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot
Patch to dump amdgpu_wb usage. Confirmed amdgpu_wb_free() is called with
an offset returned from amdgpu_wb_get(), and yet it skips actual release
call because offset is larger than AMDGPU_MAX_WB.
** Patch added: "0001-drm-amdgpu-dump-amdgpu_wb-usage.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825074/+attachment/5256463/+files/0001-drm-amdgpu-dump-amdgpu_wb-usage.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825074
Title:
amdgpu resume failure: failed to allocate wb slot
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after
resume from S3 at 112nd S3.
The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test
failed (-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id =
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18,
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1,
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04]
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f
64bit pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[Reproduce Steps]
1.
[Kernel-packages] [Bug 1825089] [NEW] enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished
Public bug reported: On a s390x KVM, the enosys test is still running even the test has completed $ ps uax| grep stress ubuntu2037 0.0 0.4 93020 9564 ?Ssl 03:46 0:00 python3 ckct/runner --cloud maas ubuntu_stress_smoke_test root 2383 0.0 0.6 24248 13416 ?S03:46 0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control root 2384 0.0 0.6 24248 13416 ?S03:46 0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control ubuntu 13161 0.0 0.0 6072 696 ttysclp0 S+ 05:31 0:00 grep --color=auto stress root 19352 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 19395 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 19449 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 19481 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable 04:03:13 INFO | enosys STARTING 04:03:13 INFO | enosys RETURNED 0 04:03:13 INFO | enosys PASSED 04:03:13 WARNI| Please verify /home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395 for more info 04:03:13 INFO | GOOD ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1555473793 localtime=Apr 17 04:03:13 completed successfully 04:03:13 INFO | END GOOD ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1555473793 localtime=Apr 17 04:03:13 04:03:13 DEBUG| Persistent state client._record_indent now set to 1 04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted 04:03:13 INFO | END GOODtimestamp=1555473793 localtime=Apr 17 04:03:13 04:03:13 DEBUG| Persistent state client._record_indent now set to 0 And the job on jenkins will eventually times out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed Apr 17 05:28:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic package-from-proposed s390x uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825089 Title: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: On a s390x KVM, the enosys test is still running even the test has completed $ ps uax| grep stress ubuntu2037 0.0 0.4 93020 9564 ?Ssl 03:46 0:00 python3 ckct/runner --cloud maas ubuntu_stress_smoke_test root 2383 0.0 0.6 24248 13416 ?S03:46 0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control root 2384 0.0 0.6 24248 13416 ?S03:46 0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control ubuntu 13161 0.0 0.0 6072 696 ttysclp0 S+ 05:31 0:00 grep --color=auto stress root 19352 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5
[Kernel-packages] [Bug 1822793] Re: linux-gcp: 4.18.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822792 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1822793 Title: linux-gcp: 4.18.0-1009.10 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822792 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 01:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822794] Re: linux-kvm: 4.18.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 00:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1822794 Title: linux-kvm: 4.18.0-1010.10 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822796 phase: Testing phase-changed: Thursday, 04. April 2019 00:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822833 (trusty/linux-lts-xenial), bug 1824775 (trusty/linux-aws) derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822834 Title: linux: 4.4.0-146.172 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822833 (trusty/linux-lts-xenial), bug 1824775 (trusty/linux-aws) derivatives: bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips), bug 1824774 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794232] Re: Geneve tunnels don't work when ipv6 is disabled
I tested a fully up to date cosmic VM using the reproducer steps in the description, and found that I could not create a geneve tunnel when ipv6 is disabled. I compiled a new cosmic kernel off the master-next branch with this commit included: "geneve: correctly handle ipv6.disable module parameter" Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7 The commit was a clean cherry-pick, and when the patched kernel was installed, I was able to successfully create a geneve tunnel when ipv6 is disabled. I also tested the latest disco daily build, and found that disco is not effected, as I can successfully create a geneve tunnel when ipv6 is disabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794232 Title: Geneve tunnels don't work when ipv6 is disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Fix Released Bug description: [Impact] When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in an OS environment with open vswitch, where ipv6 has been disabled, the create fails with the error : “ovs-vsctl: Error detected while setting up 'geneve0': could not add network device geneve0 to ofproto (Address family not supported by protocol)." [Fix] There is an upstream commit for this in v5.0 mainline (and in Disco and later Ubuntu kernels). "geneve: correctly handle ipv6.disable module parameter" Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7 This fix is needed on all our series prior to Disco and the v5.0 kernel: X, C, B. It is identical to the fix we implemented and tested internally with, but had not pushed upstream yet. [Test Case] (Best to do this on a kvm guest VM so as not to interfere with your system's networking) 1. On any Ubuntu Xenial kernel, disable ipv6. This example is shown with the4.15.0-23-generic kernel (which differs slightly from 4.4.x in symptoms): - Edit /etc/default/grub to add the line: GRUB_CMDLINE_LINUX="ipv6.disable=1" - # update-grub - Reboot 2. Install OVS # apt install openvswitch-switch 3. Create a Geneve tunnel # ovs-vsctl add-br br1 # ovs-vsctl add-port br1 geneve1 -- set interface geneve1 type=geneve options:remote_ip=192.168.x.z (where remote_ip is the IP of the other host) You will see the following error message: "ovs-vsctl: Error detected while setting up 'geneve1'. See ovs-vswitchd log for details." From /var/log/openvswitch/ovs-vswitchd.log you will see: "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system: failed to add geneve1 as port: Address family not supported by protocol" You will notice from the "ifconfig" output that the device genev_sys_6081 is not created. If you do not disable IPv6 (remove ipv6.disable=1 from /etc/default/grub + update-grub + reboot), the same 'ovs-vsctl add-port' command completes successfully. You can see that it is working properly by adding an IP to the br1 and pinging each host. On kernel 4.4 (4.4.0-128-generic), the error message doesn't happen using the 'ovs-vsctl add-port' command, no warning is shown in ovs-vswitchd.log, but the device genev_sys_6081 is also not created and ping test won't work. With the fixed test kernel, the interfaces and tunnel is created successfully. [Regression Potential] * Low -- affects the geneve driver only, and when ipv6 is disabled, and since it doesn't work in that case at all, this fix gets the tunnel up and running for the common case. [Other Info] * Analysis Geneve tunnels should work with either IPv4 or IPv6 environments as a design and support principle. Currently, however, what's in the implementation requires support for ipv6 for metadata-based tunnels which geneve is: rather than: a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled b) ipv4 + metadata + ipv6 What enforces this in the current 4.4.0-x code when opening a Geneve tunnel is the following in geneve_open() : bool ipv6 = geneve->remote.sa.sa_family == AF_INET6; bool metadata = geneve->collect_md; ... #if IS_ENABLED(CONFIG_IPV6) geneve->sock6 = NULL; if (ipv6 || metadata) ret = geneve_sock_add(geneve, true); #endif if (!ret && (!ipv6 || metadata)) ret = geneve_sock_add(geneve, false); CONFIG_IPV6 is enabled, IPv6 is disabled at boot, but even though ipv6 is false, metadata is always true for a geneve open as it is set unconditionally in ovs: In /lib/dpif_netlink_rtnl.c : case OVS_VPORT_TYPE_GENEVE: nl_msg_put_flag(, IFLA_GENEVE_COLLECT_METADATA); The second argument of
[Kernel-packages] [Bug 1815925] Re: wifi doesnt work.
[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/1815925 Title: wifi doesnt work. Status in linux package in Ubuntu: Expired Bug description: wifi card doesnt get detected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 21:32:28 2019 IwConfig: lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 1018:1006 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1 hid.ignore_special_drivers=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: ilife.Wi314.NANNEBN09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZED AIR dmi.board.vendor: I-Life Digital Technologies LLC dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: 10.1 Tablet PC dmi.product.name: ZED AIR dmi.product.version: V1.00.01 dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821027] Re: fwupd.service causing boot time increase since 4.15.0-46 on Dell G7 7588
Hello, It looks like this fwupd.service issue cannot be 100% reproduced. It will just gone after reboot for this laptop at hand. I will change the title here. As your systemd-analyze blame indicates the hiccup happens in the kernel, which I cannot reproduce here, can you help us by providing the following output with an older kernel? * dmesg * systemd-analyze * systemd-analyze blame * lspci --nnv * sudo dmidecode -s bios-version Thanks! ** Summary changed: - fwupd.service causing boot time increase since 4.15.0-46 on Dell G7 7588 + Boot time increase since 4.15.0-46 on Dell G7 7588 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821027 Title: Boot time increase since 4.15.0-46 on Dell G7 7588 Status in linux package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap
** Description changed: - Under memory pressure, my VM locks up. This has been reported upstream - though I don't know how far any solution has progressed. + == Justification == + When using z3fold and zswap on a VM under overcommitted memory stress, + z3fold will complains about an "unknown buddy id 0" and fail to get a + pointer to the mapped allocation in z3fold_map(). + + z3fold: unknown buddy id 0 + WARNING: CPU: 2 PID: 1584 at mm/z3fold.c:971 z3fold_zpool_map+0xce/0x100 [z3fold] + + And it will leads to a null pointer dereference in zswap + + BUG: unable to handle kernel NULL pointer dereference at + PGD 0 P4D 0 + Oops: [#1] SMP PTI + CPU: 2 PID: 1584 Comm: stress Tainted: GW 4.18.0-17-generic #18-Ubuntu + Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 + RIP: 0010:zswap_writeback_entry+0x4d/0x360 + + == Fix == + ca0246bb (z3fold: fix possible reclaim races) + + This patch has already in Disco, and can be cherry-picked into B/C. + Not needed for Xenial and older kernels as z3fold is not supported. + + == Test == + Test kernels for Bionic / Cosmic could be found here: + http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Bionic/ + http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Cosmic/ + + This issue can be reproduced easily in a KVM with the following setup: + * 8G disk, 4G RAM, 4 CPUs + * 1G swap + * "zswap.enabled=1 zswap.zpool=z3fold zswap.max_pool_percent=7" added to grub + * "z3fold" module added into /etc/initramfs-tools/modules + + Stress it with two childs running: + * stress --vm-bytes 512M --vm 4 --vm-hang 3 + * stress --vm-bytes 512M --vm 4 --vm-hang 7 + + The VM is expected to crash within 5 minutes. + + With the patched kernel, the VM can withstand this stress for over an + hour with crashing with this issue + + == Regression potential == + Small. + + Fix limited to z3fold. User needs to enable it explicitly for this + feature. + + + == Original Bug Report == + Under memory pressure, my VM locks up. This has been reported upstream though I don't know how far any solution has progressed. https://bugzilla.kernel.org/show_bug.cgi?id=201603 Feb 6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0 Feb 6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle kernel NULL pointer dereference at 0008 The little bit of log I managed to salvage is attached. This has happened to two identical VMs. Unusually it has not occurred on a third VM which is configured the same but has less RAM (fingers crossed it won't). Irrelevant information: I thought the lock-ups were due to me using a BTRFS filesystem, however I swapped over to NILFS2 and this still occurs. The only difference seems to be that I am now able to grab some of the kernel output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Feb 6 10:55:05 2019 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1814874 Title: NULL pointer dereference when using z3fold and zswap Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Justification == When using z3fold and zswap on a VM under overcommitted memory stress, z3fold will complains about an "unknown buddy id 0" and fail to get a pointer to the mapped allocation in z3fold_map(). z3fold: unknown buddy id 0 WARNING: CPU: 2 PID: 1584 at mm/z3fold.c:971 z3fold_zpool_map+0xce/0x100 [z3fold] And it will leads to a null pointer dereference in zswap BUG: unable to handle kernel NULL pointer dereference at PGD 0 P4D 0 Oops: [#1] SMP PTI CPU: 2 PID: 1584 Comm: stress Tainted: GW 4.18.0-17-generic #18-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 RIP: 0010:zswap_writeback_entry+0x4d/0x360 == Fix == ca0246bb (z3fold: fix possible reclaim races) This patch has already in Disco, and can be cherry-picked into B/C. Not needed for Xenial and older kernels as z3fold is not supported. == Test == Test kernels for Bionic / Cosmic could be found here:
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice (Reason: 3=DEAUTH_LEAVING) [ 437.133996] mac80211_hwsim: initializing netlink [ 437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' [ 437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' [ 437.140661] BUG: unable to handle kernel NULL pointer dereference at [ 437.140668] IP: hrtimer_active+0xd/0x50 [ 437.140689] PGD 0 P4D 0 [ 437.140692] Oops: [#1] SMP PTI [ 437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds joydev serio_raw snd_seq vmwgfx ttm drm_kms_helper snd_seq_device snd_timer snd drm fb_sys_fops
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a1881c9b8a1ed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice (Reason: 3=DEAUTH_LEAVING) [ 437.133996] mac80211_hwsim: initializing netlink [ 437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' [ 437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' [ 437.140661] BUG: unable to handle kernel NULL pointer dereference at [ 437.140668] IP: hrtimer_active+0xd/0x50 [ 437.140689] PGD 0 P4D 0 [ 437.140692] Oops: [#1] SMP PTI [ 437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds joydev serio_raw snd_seq
[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot
** Tags added: originate-from-1824453 somerville
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => 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/1825074
Title:
amdgpu resume failure: failed to allocate wb slot
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after
resume from S3 at 112nd S3.
The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test
failed (-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id =
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18,
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1,
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04]
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f
64bit pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[Reproduce Steps]
1. apt-get install -y fwts
2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60
[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot
commit 97407b63ea60 drm/amdgpu: use 256 bit buffers for all wb allocations (v2)
commit 63ae07ca4fb4 drm/amdgpu:fix wb_clear
These two commits introduced buggy resource management and are latter
fixed in commit 73469585510d "drm/amdgpu: fix for wb_clear".
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=97407b63ea60
[2]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63ae07ca4fb4
[3]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=73469585510d
** Also affects: linux (Ubuntu Bionic)
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/1825074
Title:
amdgpu resume failure: failed to allocate wb slot
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after
resume from S3 at 112nd S3.
The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test
failed (-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id =
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18,
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1,
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04]
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f
64bit pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8125.089361] amdgpu :01:00.0:
[Kernel-packages] [Bug 1825074] Re: amdgpu resume failure: failed to allocate wb slot
This only affects Bionic as Xenial doesn't come with the two commits and
Cosmic/Disco have already included the fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825074
Title:
amdgpu resume failure: failed to allocate wb slot
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after
resume from S3 at 112nd S3.
The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test
failed (-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id =
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18,
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1,
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04]
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f
64bit pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[Reproduce Steps]
1. apt-get install -y fwts
2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60
[Results]
Expected: pass the S3 stress test
Actual: system hung at 112nd S3
[Additional Information]
Kernel Version: 4.15.0-1035-oem
GPU: AMD RX550 (OPGA14) 1002:699f
To manage notifications about
[Kernel-packages] [Bug 1825074] 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 1825074
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
** Changed in: linux (Ubuntu Bionic)
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/1825074
Title:
amdgpu resume failure: failed to allocate wb slot
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after
resume from S3 at 112nd S3.
The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test
failed (-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id =
9202, serial_number = 1, manufacture_week = 29, manufacture_year = 18,
display_name = 92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1,
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04]
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f
64bit pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size
0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size
0x0020 64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
(-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[Kernel-packages] [Bug 1825074] [NEW] amdgpu resume failure: failed to allocate wb slot
Public bug reported:
[Summary]
When do the S3 stress test with AMD RX550 installed, the system hung after
resume from S3 at 112nd S3.
The kernel message:
[ 8120.977916] amdgpu :01:00.0: (-22) failed to allocate wb slot
[ 8120.977941] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 11 (-22).
[ 8120.979662] [drm] ib test on ring 12 succeeded
[ 8120.981952] [drm] ib test on ring 13 succeeded
[ 8120.984578] [drm] ib test on ring 14 succeeded
[ 8120.984813] [drm] ib test on ring 15 succeeded
[ 8120.984825] [drm:amdgpu_device_resume [amdgpu]] *ERROR* ib ring test failed
(-22).
[ 8120.997655] [drm] Type 1 DP-HDMI passive dongle 165Mhz:
[ 8121.022465] [drm] 92GH: [Block 0]
[ 8121.022465] [drm] 92GH: [Block 1]
[ 8121.022467] [drm] dc_link_detect: manufacturer_id = B838, product_id = 9202,
serial_number = 1, manufacture_week = 29, manufacture_year = 18, display_name =
92GH, speaker_flag = 1, audio_mode_count = 1
[ 8121.022467] [drm] dc_link_detect: mode number = 0, format_code = 1,
channel_count = 2, sample_rate = 7, sample_size = 7
[ 8121.022573] PM: resume of devices complete after 412.170 msecs
[ 8121.023076] acpi LNXPOWER:04: Turning OFF
[ 8121.023113] PM: Finishing wakeup.
[ 8121.023114] OOM killer enabled.
[ 8121.023114] Restarting tasks ...
[ 8121.023455] pci_bus :04: Allocating resources
[ 8121.023471] pci :03:00.0: bridge window [io 0x1000-0x0fff] to [bus 04]
add_size 1000
[ 8121.023473] pci :03:00.0: bridge window [mem 0x0010-0x000f 64bit
pref] to [bus 04] add_size 20 add_align 10
[ 8121.023474] pci :03:00.0: bridge window [mem 0x0010-0x000f] to
[bus 04] add_size 20 add_align 10
[ 8121.023476] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023477] pci :03:00.0: BAR 14: failed to assign [mem size 0x0020]
[ 8121.023478] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023478] pci :03:00.0: BAR 15: failed to assign [mem size 0x0020
64bit pref]
[ 8121.023479] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023479] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023481] pci :03:00.0: BAR 14: no space for [mem size 0x0020]
[ 8121.023481] pci :03:00.0: BAR 14: failed to assign [mem size 0x0020]
[ 8121.023482] pci :03:00.0: BAR 15: no space for [mem size 0x0020
64bit pref]
[ 8121.023482] pci :03:00.0: BAR 15: failed to assign [mem size 0x0020
64bit pref]
[ 8121.023483] pci :03:00.0: BAR 13: no space for [io size 0x1000]
[ 8121.023483] pci :03:00.0: BAR 13: failed to assign [io size 0x1000]
[ 8121.023485] pci :03:00.0: PCI bridge to [bus 04]
[ 8121.024358] done.
[ 8121.082344] video LNXVIDEO:00: Restoring backlight state
[ 8121.082346] PM: suspend exit
[ 8121.094634] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.112417] ata4: SATA link down (SStatus 4 SControl 300)
[ 8121.113212] ata3: SATA link down (SStatus 4 SControl 300)
[ 8121.113279] ata2: SATA link down (SStatus 4 SControl 300)
[ 8121.114133] ata1: SATA link down (SStatus 4 SControl 300)
[ 8121.192056] [drm] {1440x900, 1904x934@106500Khz}
[ 8121.282351] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 8121.298481] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8121.298517] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 8121.298536] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8122.183439] [drm] RC6 on
[ 8124.257908] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
Rx/Tx
[ 8124.258035] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 8124.269506] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8124.269539] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 8124.269558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[ 8125.089361] amdgpu :01:00.0: couldn't schedule ib on ring
[ 8125.089429] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 8125.089448] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!
[Reproduce Steps]
1. apt-get install -y fwts
2. fwts s3 --s3-multiple=1000 --s3-min-delay=60 --s3-max-delay=60
[Results]
Expected: pass the S3 stress test
Actual: system hung at 112nd S3
[Additional Information]
Kernel Version: 4.15.0-1035-oem
GPU: AMD RX550 (OPGA14) 1002:699f
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Incomplete
** Attachment added: "kernel log"
https://bugs.launchpad.net/bugs/1825074/+attachment/5256441/+files/kern.txt.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1825074
Title:
amdgpu resume failure: failed to allocate wb slot
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
[Kernel-packages] [Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1824661 Title: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty. Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in slick-greeter package in Ubuntu: Incomplete Bug description: Hello. I am having issues consistently with this laptop and the Nvidia drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie, and Ubuntu MATE. This is with both the recommended 418 driver as well as 390. Today I tried installing the latest daily of Ubuntu MATE with the proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a couple times. Can't get to tty. Reboot, editing grub to include nomodeset. Boots to underscore character in the top left. I can get tty at least. 418 driver is installed. Looking at logs but nothing seems obvious. If there's anything I can do to help with this please let me know. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 13 18:27:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-04-13 (0 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: TERM=cygwin PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1824661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256438/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256434/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256427/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256436/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
** 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/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice (Reason: 3=DEAUTH_LEAVING) [ 437.133996] mac80211_hwsim: initializing netlink [ 437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' [ 437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' [ 437.140661] BUG: unable to handle kernel NULL pointer dereference at [ 437.140668] IP: hrtimer_active+0xd/0x50 [ 437.140689] PGD 0 P4D 0 [ 437.140692] Oops: [#1] SMP PTI [ 437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds joydev serio_raw snd_seq vmwgfx ttm drm_kms_helper
[Kernel-packages] [Bug 1825071] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256428/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256437/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256435/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256431/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256432/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256430/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256439/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256433/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256429/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective
apport information ** Tags added: apport-collected ** Description changed: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. - I am not sure what other information you will need for this report. I - can provide more data upon request. + I am not sure what other information you will need for this report. I can provide more data upon request. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: jpsimkins 3108 F pulseaudio + /dev/snd/controlC1: jpsimkins 3108 F pulseaudio + /dev/snd/controlC0: jpsimkins 3108 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-22 (298 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H + NonfreeKernelModules: nvidia_modeset nvidia wl + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-47-generic N/A + linux-backports-modules-4.15.0-47-generic N/A + linux-firmware 1.173.3 + Tags: bionic + Uname: Linux 4.15.0-47-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/03/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F10 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Z97X-UD5H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: Z97X-UD5H + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1825071/+attachment/5256426/+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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
** Summary changed: - lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 + lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
okay I have another solution to the timing issue .. add two partition mounts to fstab .. my existing sda1 disco install has /home (sda2) and /home/store1 (sda5) mounted via fstab .. this was the original install configuration .. thus always a mount delay .. to test .. added the same partions to mount on /home/oldhome and /home/store1 respectively on newly installed sda9 - disco xubuntu final and no crashes .. ..plymouth shows up .. xorg/lightdm start normally ..just enough delay to let everything else happen .. all using the "foreign sda1 installed grub" .. so all the errors are due to "faster than expected storage media response time" .. some slumbering boot timing issues waiting to cause trouble .. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
[Kernel-packages] [Bug 1824669] Re: Live boot fails legacy boot Kubuntu 19.04
Boot issue fixed with latest release 19.04 candidate (16-04-19). Closing report. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824669 Title: Live boot fails legacy boot Kubuntu 19.04 Status in linux package in Ubuntu: Fix Released Bug description: Attempted to Live Boot 2 different legacy Dell laptops (Dell Vostro 1720 and Dell XPS M1530). Boot process hangs on the "Kubuntu 19.04 ." screen. Both laptops have NVidia cards, but unsure if NVidia cards have any bearing on the boot. Both laptops had Kubuntu 18.10 installed and have never had an issue with live booting over the last 10 years. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: syslinux (not installed) ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 13 20:56:00 2019 InstallationDate: Installed on 2019-04-14 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] 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 1825071 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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] [NEW] Super + p does not work as expected, it's defective
Public bug reported: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description:Ubuntu 18.04.2 LTS Release:18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1825071/+attachment/5256425/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
of course the sda1 partition (on the SSD) has never failed to work properly no matter which grub source (installs on sda1,sda6,sda7,sda8,sda9) is used plymouth always appears when sda1 boots.. this disco version was installed jan 10 with a bootstrap log date of oct 13, 2018 .. it has been updated regularly ever since .. daily from proposed .. without issues .. other partition installs through most of febuary tested about once per week not always reported .. appeared to have no issues .. so the question to be answered is what change in late february /early march could have influenced the timing of the boot sequence and the start of plymouth ? any ideas? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Kernel-packages] [Bug 1690085]
(In reply to Brendan Long from comment #589) > I strongly suspect that the graphics driver was the problem since my lockups > would cause the screen to become completely unresponsive, but sound > continued working, and in one case I had a lockup during a video call and > the other person could still see and hear me. What you're describing here is a new "feature" introduced between kernel 4.19.16 and 17 e.g. I can see exactly the same here with radeon hardware. The system is completely working (even VMs on the host are running well) except of graphics - even tty terminals are working sometimes. When ssh'ing the machine, I can always see log entries like these: radeon :0a:00.0: ring 0 stalled for more than 14084msec radeon :0a:00.0: GPU lockup (current fence id 0x00053ed7 last fence id 0x00053f0f on ring 0) ... I'm trying to near it down currently using git bisect. The suspicious changes left are at the moment: 2019-01-22 arm64: Don't trap host pointer auth use to EL2 Mark Rutland bad 2019-01-22 arm64/kvm: consistently handle host HCR_EL2 flags Mark Rutland 2019-01-22 scsi: target: iscsi: cxgbit: fix csk leak Varun Prakash 2019-01-22 scsi: target: iscsi: cxgbit: fix csk leak Varun Prakash 2019-01-22 Revert "scsi: target: iscsi: cxgbit: fix csk leak" Sasha Levin 2019-01-22 mmc: sdhci-msm: Disable CDR function on TX Loic Poulain 2019-01-22 netfilter: nf_conncount: fix argument order to find_next_bit 2019-01-22 netfilter: nf_conncount: speculative garbage collection on empty lists Pablo Neira Ayuso 2019-01-22 netfilter: nf_conncount: move all list iterations under spinlockPablo Neira Ayuso 2019-01-22 netfilter: nf_conncount: merge lookup and add functions Florian Westphal 2019-01-22 netfilter: nf_conncount: restart search when nodes have been erased Florian Westphal? 2019-01-22 netfilter: nf_conncount: split gc in two phases Florian Westphal 2019-01-22 netfilter: nf_conncount: don't skip eviction when age is negative Florian Westphal 2019-01-22 netfilter: nf_conncount: replace CONNCOUNT_LOCK_SLOTS with CONNCOUNT_SLOTS Shawn Bohrer 2019-01-22 can: gw: ensure DLC boundaries after CAN frame modification Oliver Hartkopp 2019-01-22 tty: Don't hold ldisc lock in tty_reopen() if ldisc present Dmitry Safonov 2019-01-22 tty: Simplify tty->count math in tty_reopen() Dmitry Safonov 2019-01-22 tty: Hold tty_ldisc_lock() during tty_reopen() Dmitry Safonov 2019-01-22 tty/ldsem: Wake up readers after timed out down_write() Dmitry Safonov As you're describing correctly, the problem seems to be network related. I'm getting this error two when watching videos from internet. I'm currently testing the changes between "restart search when nodes have been erased" and "Wake up readers after timed out down_write()". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2
[Kernel-packages] [Bug 1690085]
(In reply to Brendan Long from comment #589) > > I eventually did a from-scratch reinstall of Fedora 29 and it suddenly just > works (for 10+ hours, I don't leave my machine on overnight). Once it > started working, I set everything back to the defaults except for "Typical > Current Idle" (since I have a PSU from 2010 and I doubt it supports any > fancy features from 2013). a) Fedora 29 has very new kernels. In the last few weeks they rebased to 5.0 and 5.0 is supposed to have a lot of Ryzen fixes in it. b) For me "Typical Current Idle" (plus mwait) was all that was required to fix the problem. I'm pretty sure kernel 5.0 makes it so mwait override is not needed. > - Using the Nouvea driver (previously proprietary nVidia drivers) > - Booting in EFI mode now (previously legacy mode) > - Using ext4 (previously btrfs) We never used proprietary video driver and we both had the problem and fixed the problem. Same with EFI: we use just legacy mode. FS should not matter at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
okay turned back the clock .. to a spinning metal disk previously installed in this hardware .. ran a number of test installs all work fine .. cosmic/bionic/disco early version disco final all work boot normally .. always .. thus conclusion is a SSD is very fast and can respond to requests sooner than a spinning metal disk this throws off the timing of a number of boot processes .. which become out of sync.. due to the " slower processor " now the first boot into a fresh install is not effected as a very extended plymouth start occurs .. due to " automatic-updates?? or disk checks or something ?" the rest of the boots are too fast for even plymouth to load properly due to a not yet loaded kernel video module .. thus it only flashes the screen red briefly .. then xorg/lightdm crashes for the same reason(?).. delayed kernel module load .. then a second successful try if still booting from "native" grub ..else no retry and lock-up -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx
[Kernel-packages] [Bug 1690085]
I ran into similar problems to this with a Threadripper 1950X and none of the proposed workarounds did anything. Disabling C6 in the BIOS made it fail to boot for some reason. Setting "Typical Current Idle" in the BIOS, processor.max_cstate=1 in the kernel command line, or disabling C6 with ZenStates.py all had no effect. I also tried overclocking and underclocking. I eventually did a from-scratch reinstall of Fedora 29 and it suddenly just works (for 10+ hours, I don't leave my machine on overnight). Once it started working, I set everything back to the defaults except for "Typical Current Idle" (since I have a PSU from 2010 and I doubt it supports any fancy features from 2013). Unfortunately I can't easily narrow down all of the changes after the re-install, but the ones I'm aware of are: - Using the Nouvea driver (previously proprietary nVidia drivers) - Booting in EFI mode now (previously legacy mode) - Using ext4 (previously btrfs) I strongly suspect that the graphics driver was the problem since my lockups would cause the screen to become completely unresponsive, but sound continued working, and in one case I had a lockup during a video call and the other person could still see and hear me. I plan to try the proprietary drivers again sometime and I'll make a note if that brings the problem back for 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel:
[Kernel-packages] [Bug 1825058] 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 1825058 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/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Incomplete Bug description: The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice (Reason: 3=DEAUTH_LEAVING) [ 437.133996] mac80211_hwsim: initializing netlink [ 437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' [ 437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' [ 437.140661] BUG: unable to
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
The non-HWE kernel for 16.04 is unaffected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: New Bug description: The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice (Reason: 3=DEAUTH_LEAVING) [ 437.133996] mac80211_hwsim: initializing netlink [ 437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' [ 437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' [ 437.140661] BUG: unable to handle kernel NULL pointer dereference at [ 437.140668] IP: hrtimer_active+0xd/0x50 [ 437.140689] PGD 0 P4D 0 [ 437.140692] Oops: [#1] SMP PTI [ 437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds joydev serio_raw snd_seq vmwgfx ttm drm_kms_helper snd_seq_device snd_timer snd drm
[Kernel-packages] [Bug 1825058] [NEW] mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
Public bug reported: The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 437.039513] wlan1: deauthenticating from 02:00:00:00:00:00 by local choice (Reason: 3=DEAUTH_LEAVING) [ 437.133996] mac80211_hwsim: initializing netlink [ 437.138685] ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' [ 437.139801] ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' [ 437.140661] BUG: unable to handle kernel NULL pointer dereference at [ 437.140668] IP: hrtimer_active+0xd/0x50 [ 437.140689] PGD 0 P4D 0 [ 437.140692] Oops: [#1] SMP PTI [ 437.140693] Modules linked in: mac80211_hwsim(+) arc4 mac80211 cfg80211 coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_ens1371 snd_ac97_codec aesni_intel gameport ac97_bus vmw_balloon snd_pcm aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds joydev serio_raw snd_seq vmwgfx ttm drm_kms_helper snd_seq_device snd_timer snd drm fb_sys_fops soundcore syscopyarea sysfillrect sysimgblt shpchp mac_hid vmw_vsock_vmci_transport vsock vmw_vmci sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid psmouse mptspi ahci libahci e1000 mptscsih mptbase scsi_transport_spi i2c_piix4 pata_acpi [last unloaded: mac80211_hwsim] [ 437.140726] CPU: 0 PID: 27091 Comm: wpa_supplicant Not tainted 4.15.0-47-generic #50-Ubuntu [ 437.140727] Hardware name: VMware, Inc.
Re: [Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
On Tue, Apr 16, 2019 at 1:26 PM Jo Shields wrote:
>
> I'm an idiot and should have been trying the version from -proposed, of
> course. Working on it
Whups, yeah - so was I :) I thought for sure I had enabled -proposed
on my D05
Anyway, I was also an idiot and didn't realize I could just check our
weekly scheduled tests and see that the (correct) -proposed kernels
had both booted fine on D05, so I didn't need to do that test
manually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823216] Re: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG:
No faults detected since a week ago. Going to declare this fixed in the 4.4 kernel series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823216 Title: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG: Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: While trying to diagnose a problem with getting a kernel BUG: Bad page map in process retriever (retriever is the name of our serving binary), causing the serving binary to crash, we tried upgrading from 3.13.0-121-generic to 3.13.0-167-generic and instead started more regularly tripping a different bug that hardlocks the system when we attempt to stop & restart the affected process. We are running Trusty on AWS in i3.xlarge instances. BUG: unable to handle kernel paging request at eaf0 [89149.537277] IP: [] _raw_spin_lock+0xe/0x50 [89149.543462] PGD 0 [89149.545919] Oops: 0002 [#1] SMP [89149.549887] Modules linked in: 8021q garp stp mrp llc dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy [89149.574925] CPU: 3 PID: 21681 Comm: retriever Not tainted 3.13.0-167-generic #217-Ubuntu [89149.583168] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [89149.589649] task: 8807f2f7e000 ti: 88015b674000 task.ti: 88015b674000 [89149.597338] RIP: 0010:[] [] _raw_spin_lock+0xe/0x50 [89149.605845] RSP: :88015b675d88 EFLAGS: 00010206 [89149.611431] RAX: 0002 RBX: 00c0dee00020 RCX: f000cf53 [89149.618873] RDX: 8800 RSI: 00c0 RDI: eaf0 [89149.626336] RBP: 88015b675d88 R08: 3fe0 R09: 00a9 [89149.633705] R10: R11: f000ff53f000ff53 R12: 880037471900 [89149.641019] R13: 8807f49c57b8 R14: 8807f2eb2680 R15: eaf0 [89149.648287] FS: 7f92262dd700() GS:88081fc6() knlGS: [89149.657764] CS: 0010 DS: ES: CR0: 80050033 [89149.664294] CR2: eaf0 CR3: 0007f438 CR4: 00160670 [89149.672158] DR0: DR1: DR2: [89149.680246] DR3: DR6: fffe0ff0 DR7: 0400 [89149.688126] Stack: [89149.690903] 88015b675e20 811831fe 81e85225 8807f2eb2680 [89149.700310] 88015b675f20 88015b675e10 0007 f000cf53 [89149.709739] 00a9 f000ff53f000ff53 8800 8003 [89149.719331] Call Trace: [89149.722581] [] handle_mm_fault+0x27e/0xfb0 [89149.729984] [] __do_page_fault+0x183/0x570 [89149.737506] [] ? do_futex+0x10a/0x760 [89149.744529] [] ? set_next_entity+0x95/0xb0 [89149.752059] [] ? pick_next_task_fair+0x5f/0x1b0 [89149.76] [] ? sched_clock_cpu+0xb5/0x100 [89149.767489] [] do_page_fault+0x1a/0x70 [89149.774460] [] page_fault+0x28/0x30 [89149.781134] Code: 00 00 55 48 89 e5 f0 81 07 00 00 10 00 48 89 f7 57 9d 0f 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 [89149.820963] RIP [] _raw_spin_lock+0xe/0x50 [89149.828646] RSP [89149.833460] CR2: eaf0 [89149.843886] ---[ end trace 5e5ae13dbb1d0f6e ]--- BUG: unable to handle kernel paging request at eaf0 [66384.498399] IP: [] _raw_spin_lock+0xe/0x50 [66384.502611] PGD 0 [66384.504586] Oops: 0002 [#1] SMP [66384.507578] Modules linked in: 8021q garp stp mrp llc dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy [66384.525392] CPU: 1 PID: 21144 Comm: retriever Not tainted 3.13.0-167-generic #217-Ubuntu [66384.531418] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [66384.535812] task: 88074a9a9800 ti: 8807f411e000 task.ti: 8807f411e000 [66384.542092] RIP: 0010:[] [] _raw_spin_lock+0xe/0x50 [66384.548699] RSP: :8807f411fd88 EFLAGS: 00010206 [66384.552560] RAX: 0002 RBX: 00c2b0c0 RCX: f000cf53 [66384.557499] RDX: 8800 RSI: 00c0 RDI: eaf0 [66384.562419] RBP: 8807f411fd88 R08: 3fe0 R09: 00a9 [66384.567450] R10: R11: f000ff53f000ff53 R12: 8807f4af9f00 [66384.572935] R13: 8807f2ed9c30 R14: 8807f3ee2680 R15: eaf0 [66384.578165] FS: 7f9886ac4700() GS:88081fc2() knlGS: [66384.584224] CS: 0010 DS: ES: CR0: 80050033 [66384.588318] CR2:
Re: [Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
On Tue, Apr 16, 2019 at 1:50 PM Jo Shields wrote:
>
> OK, yes, confirmed I have ethernet with 4.15.0-48.51
Awesome, 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/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
video of sda9 boot using sda9 install of grub (native grub) .. note absence of plymouth .. flash at top edge of screen was missed .. note brief appearance of lightdm .. short gap then lightdm reappears .. xorg.0.log.old records the crash .. similar to others above xorg.0.log records successful xorg/lightdm start .. ** Attachment added: "video of self boot w/ crash and restart" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5256387/+files/20190416_111702.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
video of sda8 non-native grub boot (a disco-xubuntu iso install) sda9 has installed grub (also a disco-xubuntu iso install ) will show in next video uploaded note the red flash .. plymouth attempt to start .. then cursor appears and then lightdm briefly ** Attachment added: "video of failing boot -- with foreign grub" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5256380/+files/20190416_112248.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
OK, yes, confirmed I have ethernet with 4.15.0-48.51
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
I'm an idiot and should have been trying the version from -proposed, of
course. Working on it
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
This appears to not be included in 4.15.0-47-generic? I'm offline with
the kernel, and can't see anything useful in changelog.Debian.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue
I spend the better part of 2h to install java on an old windows to satisfy the IPMI needs. I was able to start SOL. BUT it is just a black windows displaying nothing. I give up. on this - sorry I do not know how to produce an better screenshot. (Yes I googled). IPMI Viewer produced the same bad results. Regards grub. Does this help: root@:~# update-grub2 Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-145-generic Found initrd image: /boot/initrd.img-4.4.0-145-generic Found linux image: /boot/vmlinuz-4.4.0-143-generic Found initrd image: /boot/initrd.img-4.4.0-143-generic done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824687 Title: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 After upgrading our server to this Kernel we experience frequent Kernel panics (Attachment). Every 3 hours. Our machine has a throuput of about 600 Mbits/s The Panics are around the area of ip6_expire_frag_queue. __pskb_pull_tail ip6_dst_lookup_tail _decode_session6 __xfrm_decode_session icmpv6_route_lookup icmp6_send It seems similar to Bug Report in Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488 According to the bug finder of above bug it also occurred after using a Kernel with the change of rewrite ip6_expire_frag_queue() Intermediate solution. We disabled IPv6 on this machine to avoid further Panics. Please let me know what information is missing. The ubuntu-bug linux was send. And I hope it is attached to this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 14 11:40:11 2019 InstallationDate: Installed on 2018-03-18 (391 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 21:04 seq crw-rw 1 root audio 116, 33 Apr 12 21:04 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1 InstallationDate: Installed on 2018-03-18 (393 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 RelatedPackageVersions: linux-restricted-modules-4.4.0-145-generic N/A linux-backports-modules-4.4.0-145-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-145-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F dmi.board.vendor: Supermicro dmi.board.version: 1.2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias:
[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault
No the altsetting is correct now. Possible to try it bare metal? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW
[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress -- 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/1824771 Title: linux-aws: 4.18.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 16:04 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault
Same messages with wrong altsetting. Audio device creates but all application freezing when play trough it. No sound on playback an recording. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256335/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256337/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256336/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256334/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256333/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256331/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256329/+files/PciMultimedia.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256332/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256328/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256330/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Card2.Amixer.values.txt
apport information ** Attachment added: "Card2.Amixer.values.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256326/+files/Card2.Amixer.values.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256327/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Card1.Amixer.values.txt
apport information ** Attachment added: "Card1.Amixer.values.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256325/+files/Card1.Amixer.values.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Card0.Codecs.codec97.0.ac97.0-0.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256323/+files/Card0.Codecs.codec97.0.ac97.0-0.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Card0.Codecs.codec97.0.ac97.0-0.regs.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.regs.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256324/+files/Card0.Codecs.codec97.0.ac97.0-0.regs.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256321/+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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256319/+files/ArecordDevices.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256322/+files/Card0.Amixer.values.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault
apport information ** Tags added: staging ** Description changed: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (66
[Kernel-packages] [Bug 1790595] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256318/+files/AplayDevices.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1814899] Re: [19.04 FEAT] qeth: Performance Improvements
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814899 Title: [19.04 FEAT] qeth: Performance Improvements Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Function: Improved performance for OSA and Hipersockets via general code improvements and and exploitation of further kernel infrastructure. Business Case: Improved network performance for Linux on Z Available with kernel 4.19: Git-Commit: s390/qeth: various buffer management cleanups [3b346c1814] s390/qeth: remove unused buffer->aob pointer [f67a43a73b] s390/qeth: fine-tune RX modesetting [9aa17df3b8] s390/qeth: clean up Output Queue selection [86c0cdb9e0] s390/qeth: consolidate ccwgroup driver definition [6d8769abe4] s390/qeth: clean up exported symbols [09960b3a0a] s390/qeth: increase GSO max size for eligible L3 devices [371a1e7a07] s390/qeth: add a L3 xmit wrapper [ea1d4a0c7f] s390/qeth: speed-up L3 IQD xmit [a647a02512] s390/qeth: speed-up IPv4 OSA xmit [fb321f25e5] s390/qeth: fix race in used-buffer accounting [a702349a40] s390/qeth: reset layer2 attribute on layer switch [70551dc46f] s390/qeth: remove redundant netif_carrier_ok() checks [addc5ee872] s390/qeth: allocate netdevice early [d3d1b205e8] s390/qeth: don't cache HW port number [92d2720969] s390/qeth: simplify max MTU handling [8ce7a9e064] s390/qeth: use core MTU range checking [72f219da79] s390/qeth: add statistics for consumed buffer elements [d2a274b25b] s390/qeth: merge linearize-check into HW header construction [ba86ceee9d] s390/qeth: add support for constrained HW headers [a7c2f4a332] s390/qeth: speed up L2 IQD xmit [5f89eca577] s390/qeth: extract helper for MPC protocol type [73657a3e5b] s390/qeth: reduce hard-coded access to ccw channels [750b162598] s390/qeth: use qeth_setup_ccw() to set up all CCWs [45ca2fd646] s390/qeth: do basic setup for data channel [24142fd8d8] s390/qeth: clean up card initialization [95f4d8b75a] s390/qeth: don't restrict qeth_card to DMA memory [f15cdaf237] s390/qeth: switch on SG by default for IQD devices [04db741d0d] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790595] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1790595/+attachment/5256320/+files/AudioDevicesInUse.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/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Confirmed Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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:
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
I've scheduled downtime on a host, it'll take an hour or two before I
can reboot into a test kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed -- 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/1824771 Title: linux-aws: 4.18.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 16:04 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811354] Re: [19.04 FEAT] in-kernel crypto: support protected keys generated by random in paes module
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811354 Title: [19.04 FEAT] in-kernel crypto: support protected keys generated by random in paes module Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: Allow the protected key AES (paes) module to derive protected keys from clear keys. This allows simple use of protected keys w/o requiring CryptoExpress adapters in case the keys are ephemeral, that their life time does not extend over different boot or machine migrations. An example of such keys are keys used to encrypt swap volumes of non-migratable systems. Function will be provided via kernel 4.20 . Important: Install file s390-pkey.conf introduced with this commit into /usr/lib/modules-load.d/ (or /etc/modules-load.d) Addl. Information for integration. Kernel module pkey is loaded too late during system startup. Kernel module pkey uses the CPU feature match mechanism to get loaded automatically when the CPU supports crypto. However, it gets loaded too late by the feature match mechanism. When using the support added with "in-kernel crypto: support protected keys generated by random in paes module" to encrypt a swap disk with a randomly generated protected key, the pkey module must have been loaded before the /etc/crypttab is processed. It turned out that the automatic loading via CPU feature match is too late for that, and pkey is not yet loaded at the required point in time. The kernel module pkey should therefor loaded explicitly via /usr/lib/modules.load.d/.(or /etc/modules-load.d/). This is performed early enough, i.e. before /etc/crypttab is processed. Please integrate upstream commit https://github.com/ibm-s390-tools/s390-tools/commit/dffd41943e5c01be2f343da7726edabf9d2ec05e titled "pkey: Support autoloading kernel pkey module". -> comes with kernel 4.20. Important: Install file s390-pkey.conf introduced with this commit into /usr/lib/modules-load.d/ (or /etc/modules-load.d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1811354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805793] Re: [19.04 FEAT] qeth: Full-blown TCP Segmentation Offload
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805793 Title: [19.04 FEAT] qeth: Full-blown TCP Segmentation Offload Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: As of now, qeth only supports TCP Segmentation Offload (TSO) for IPv4 in Layer3 devices. This feature extends the existing support to IPv6, and adds support for TSO in both IP variants for Layer2. Improved performance via improved TCP Segmentation offload also extended to IPv6 and for layer 2 devices kernel 4.20: Git-Commit: will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
** Attachment added: "installer syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+attachment/5256316/+files/syslog ** Changed in: ubiquity (Ubuntu) Status: Incomplete => 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824669] 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 1824669 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824669 Title: Live boot fails legacy boot Kubuntu 19.04 Status in linux package in Ubuntu: Incomplete Bug description: Attempted to Live Boot 2 different legacy Dell laptops (Dell Vostro 1720 and Dell XPS M1530). Boot process hangs on the "Kubuntu 19.04 ." screen. Both laptops have NVidia cards, but unsure if NVidia cards have any bearing on the boot. Both laptops had Kubuntu 18.10 installed and have never had an issue with live booting over the last 10 years. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: syslinux (not installed) ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 13 20:56:00 2019 InstallationDate: Installed on 2019-04-14 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
@directhex: Are you able to test this on your XR320? I've regression
tested on a HiSilicon D05 which uses the same driver (it worked before,
still works now).
ubuntu@d05-5:~$ cat /proc/version
Linux version 4.15.0-47-generic (buildd@bos02-arm64-022) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #50-Ubuntu SMP Wed Mar 13 10:42:02 UTC 2019
ubuntu@d05-5:~$ ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enahisic2i0: mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether a0:8c:f8:62:5b:58 brd ff:ff:ff:ff:ff:ff
inet 10.228.68.94/24 brd 10.228.68.255 scope global enahisic2i0
valid_lft forever preferred_lft forever
inet6 fe80::a28c:f8ff:fe62:5b58/64 scope link
valid_lft forever preferred_lft forever
3: enahisic2i1: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether a0:8c:f8:62:5b:59 brd ff:ff:ff:ff:ff:ff
4: enahisic2i2: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether a0:8c:f8:62:5b:5a brd ff:ff:ff:ff:ff:ff
5: enahisic2i3: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether a0:8c:f8:62:5b:5b brd ff:ff:ff:ff:ff:ff
6: enP10p17s0f0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether ec:0d:9a:2f:d0:12 brd ff:ff:ff:ff:ff:ff
7: enP10p17s0f1: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether ec:0d:9a:2f:d0:13 brd ff:ff:ff:ff:ff:ff
ubuntu@d05-5:~$ cat /proc/version
Linux version 4.18.0-17-generic (buildd@bos02-arm64-075) (gcc version 7.3.0
(Ubuntu/Linaro 7.3.0-16ubuntu3)) #18~18.04.1-Ubuntu SMP Fri Mar 15 15:27:57 UTC
2019
ubuntu@d05-5:~$ ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enahisic2i0: mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether a0:8c:f8:62:5b:58 brd ff:ff:ff:ff:ff:ff
inet 10.228.68.94/24 brd 10.228.68.255 scope global enahisic2i0
valid_lft forever preferred_lft forever
inet6 fe80::a28c:f8ff:fe62:5b58/64 scope link
valid_lft forever preferred_lft forever
3: enahisic2i1: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether a0:8c:f8:62:5b:59 brd ff:ff:ff:ff:ff:ff
4: enahisic2i2: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether a0:8c:f8:62:5b:5a brd ff:ff:ff:ff:ff:ff
5: enahisic2i3: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether a0:8c:f8:62:5b:5b brd ff:ff:ff:ff:ff:ff
6: enP10p17s0f0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether ec:0d:9a:2f:d0:12 brd ff:ff:ff:ff:ff:ff
7: enP10p17s0f1: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether ec:0d:9a:2f:d0:13 brd ff:ff:ff:ff:ff:ff
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818294
Title:
HiSilicon HNS ethernet broken in 4.15.0-45
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The 1G NICs on the Huawei XR320 system do not detect link on initial boot,
resulting in broken networking. This is a regression caused by:
308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
after rmmod.")
While that fixed an issue with phys after reloading the driver, it
caused an issue with some phys on initial load.
[Test Case]
dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
(With enahisic2i2 properly wired up)
[Fix]
This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING
when hns modules installed"). While the commit message suggests this was for a
separate issue that we are not seeing (a WARNING message), it also resolves
this issue.
[Regression Risk]
Restricted to the hns driver, which is only used by certain HiSilicon SOCs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824669] Re: Live boot fails legacy boot Kubuntu 19.04
The system booted, so it's not a syslinux issue. Maybe kernel? I'm unsure, as I didn't see anything obviously wrong (to me) in the attached logs, but the mtrr messages are unusual and warrant some further investigation. Reassigning to linux. ** Package changed: syslinux (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/1824669 Title: Live boot fails legacy boot Kubuntu 19.04 Status in linux package in Ubuntu: New Bug description: Attempted to Live Boot 2 different legacy Dell laptops (Dell Vostro 1720 and Dell XPS M1530). Boot process hangs on the "Kubuntu 19.04 ." screen. Both laptops have NVidia cards, but unsure if NVidia cards have any bearing on the boot. Both laptops had Kubuntu 18.10 installed and have never had an issue with live booting over the last 10 years. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: syslinux (not installed) ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 13 20:56:00 2019 InstallationDate: Installed on 2019-04-14 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824669] [NEW] Live boot fails legacy boot Kubuntu 19.04
You have been subscribed to a public bug: Attempted to Live Boot 2 different legacy Dell laptops (Dell Vostro 1720 and Dell XPS M1530). Boot process hangs on the "Kubuntu 19.04 ." screen. Both laptops have NVidia cards, but unsure if NVidia cards have any bearing on the boot. Both laptops had Kubuntu 18.10 installed and have never had an issue with live booting over the last 10 years. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: syslinux (not installed) ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 13 20:56:00 2019 InstallationDate: Installed on 2019-04-14 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco iso-testing kubuntu -- Live boot fails legacy boot Kubuntu 19.04 https://bugs.launchpad.net/bugs/1824669 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 1799472] Re: [19.04 FEAT] Enable graphical distro installer to run natively with virtio-gpu
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799472 Title: [19.04 FEAT] Enable graphical distro installer to run natively with virtio-gpu Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Installer update request for completing [19.04 FEAT| Enable virtio-gpu for s390x https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799467 Addl description: The graphical installers either require VNC to be set up on s390x to run or are not supported at all. With virtio-gpu support the installers can start an X Windows server locally as they would on an x86 system. The distributor most likely only needs to disable s390x specific handling in the installer (like starting a VNC server) and just launch the graphical UI used for installation if a virtio-gpu device is present. Business Value: Allows to install s390x KVM guests without any extra setup activities, providing the same user experience as on other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809843] Re: sky2 ethernet card link not up after suspend
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809843 Title: sky2 ethernet card link not up after suspend Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Fix Released Bug description: Issue is as described by the user 'kris' in #1798921 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921). Sometimes when bringing my laptop up from suspended state my Ethernet card shows link connection and activity via port LEDs but ethtool indicates the link is not up. This does not happen every time I resume from suspend, about one in 5 times. When it does happen, the following additional message is present in my dmesg output: [ 686.804877] do_IRQ: 1.37 No irq handler for vector The lspci -vvnn output for the Ethernet card is: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10) Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet Controller [1025:028e] 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/1798921/comments/34, in the hopes that this specific card will be added to the relevant MSI quirks table. If I do not suffer from the same issue as kris in the above linked issue, I will be happy to provide any additional information, test fixes etc. I would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if possible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: maridius 2260 F...m pulseaudio /dev/snd/controlC0: maridius 2260 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862 InstallationDate: Installed on 2015-09-01 (1212 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gateway P-79 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 79.07.00 dmi.board.name: Godzilla-N10 dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A: dmi.product.name: P-79 dmi.product.version: 0100 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809843] Re: sky2 ethernet card link not up after suspend
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809843 Title: sky2 ethernet card link not up after suspend Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Fix Released Bug description: Issue is as described by the user 'kris' in #1798921 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921). Sometimes when bringing my laptop up from suspended state my Ethernet card shows link connection and activity via port LEDs but ethtool indicates the link is not up. This does not happen every time I resume from suspend, about one in 5 times. When it does happen, the following additional message is present in my dmesg output: [ 686.804877] do_IRQ: 1.37 No irq handler for vector The lspci -vvnn output for the Ethernet card is: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10) Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet Controller [1025:028e] 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/1798921/comments/34, in the hopes that this specific card will be added to the relevant MSI quirks table. If I do not suffer from the same issue as kris in the above linked issue, I will be happy to provide any additional information, test fixes etc. I would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if possible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: maridius 2260 F...m pulseaudio /dev/snd/controlC0: maridius 2260 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862 InstallationDate: Installed on 2015-09-01 (1212 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gateway P-79 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 79.07.00 dmi.board.name: Godzilla-N10 dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A: dmi.product.name: P-79 dmi.product.version: 0100 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741904] Re: [18.04 FEAT] dm-crypt with protected keys - s390 tools part
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741904 Title: [18.04 FEAT] dm-crypt with protected keys - s390 tools part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Extend dm-crypt to use protected keys to encrypt partitions. This feature has a - kernel part, - part in the "crypt setup tool" as part of multipath tools - part in s390-tools for the zkey This is the part for s390-tools part > 2.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1741904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
>From reading the logs that's what it looks like -- it appears the lid was closed at 21:48:40 and then suspend was successful at 21:49:10 or 21:49:25, but then the system immediately resumes at 21:49:25, and doesn't fully recover -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]:
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
(but unlike the on-suspend lockup, the journal continues to accumulate some entries -- possible the system wasn't fully locked up but the display was?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr
[Kernel-packages] [Bug 1817786] Re: tcm_loop.ko: move from modules-extra into main modules package
Confirmed on Bionic and Cosmic the tcm_loop.ko module is now shipped by main linux-modules-* package. ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1817786 Title: tcm_loop.ko: move from modules-extra into main modules package Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-gcp source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Please move the tcm_loop.ko module from the linux-modules-extra-* to main linux-modules-* package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822808 phase: Testing phase-changed: Thursday, 11. April 2019 12:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1822807 Title: linux-gcp: 4.15.0-1030.32~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822808 phase: Testing phase-changed: Thursday, 11. April 2019 12:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
The log file wasn't actually attached, could you find it again and add it? ** Changed in: ubiquity (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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1822807 Title: linux-gcp: 4.15.0-1030.32~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822808 phase: Testing phase-changed: Thursday, 11. April 2019 12:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822834 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 16:32 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1824774 Title: linux-aws: 4.4.0-1081.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822834 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 16:32 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
