[Kernel-packages] [Bug 1886890] Re: sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4
More info for T-4.4
This issue cannot be found on lowlatency kernel.
Still failing on T-4.4 amd64 generic and i386 generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886890
Title:
sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
== SRU Justification ==
A new regression test case "sched_rr_get_interval01" for commit 975e155ed873
("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in
milliseconds"). Has been added to the LTP syscalls test suite.
On Xenial 4.4.0-186.216, this test is failing with:
startup='Wed Jul 8 10:36:58 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
sched_rr_get_interval01.c:43: INFO: Testing variant: vDSO or syscall with
libc spec
sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms
!= 100 got 25
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
sched_rr_get_interval01.c:43: INFO: Testing variant: syscall with old kernel
spec
sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms
!= 100 got 25
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=975e155ed873
Summary:
passed 4
failed 2
skipped 0
warnings 0
tag=sched_rr_get_interval01 stime=1594204618 dur=0 exit=exited stat=1
core=no cu=0 cs=0
== Fixes ==
975e155ed873 ("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice
tuning knob in milliseconds")
This patch can be cherry-picked in to the affected Xenial kernel. It's
already been applied in newer kernels.
== Test ==
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1886890-sched_rr_get_interval01/
With the patch applied, this test will pass without any issue.
And it can be simply tested with:
# echo 100 > /proc/sys/kernel/sched_rr_timeslice_ms
# cat /proc/sys/kernel/sched_rr_timeslice_ms
100
(was 25 before the patch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886890/+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 1886912] Re: DELL M3800 Touchscreen not working after login
here you can find the result of this test ** Attachment added: "dmesg_with_options.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+attachment/5391220/+files/dmesg_with_options.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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886912] Re: DELL M3800 Touchscreen not working after login
this test was done on the actual kernel 5.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886890] Re: sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4
Same thing on X-4.4, passed on lowlatency amd64 / i386
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886890
Title:
sched_rr_get_interval01 from ubuntu_ltp_syscalls failed on 4.4
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
== SRU Justification ==
A new regression test case "sched_rr_get_interval01" for commit 975e155ed873
("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in
milliseconds"). Has been added to the LTP syscalls test suite.
On Xenial 4.4.0-186.216, this test is failing with:
startup='Wed Jul 8 10:36:58 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
sched_rr_get_interval01.c:43: INFO: Testing variant: vDSO or syscall with
libc spec
sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms
!= 100 got 25
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
sched_rr_get_interval01.c:43: INFO: Testing variant: syscall with old kernel
spec
sched_rr_get_interval01.c:60: PASS: sched_rr_get_interval() passed
sched_rr_get_interval01.c:68: PASS: Time quantum 0s 1ns
sched_rr_get_interval01.c:75: FAIL: /proc/sys/kernel/sched_rr_timeslice_ms
!= 100 got 25
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=975e155ed873
Summary:
passed 4
failed 2
skipped 0
warnings 0
tag=sched_rr_get_interval01 stime=1594204618 dur=0 exit=exited stat=1
core=no cu=0 cs=0
== Fixes ==
975e155ed873 ("sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice
tuning knob in milliseconds")
This patch can be cherry-picked in to the affected Xenial kernel. It's
already been applied in newer kernels.
== Test ==
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1886890-sched_rr_get_interval01/
With the patch applied, this test will pass without any issue.
And it can be simply tested with:
# echo 100 > /proc/sys/kernel/sched_rr_timeslice_ms
# cat /proc/sys/kernel/sched_rr_timeslice_ms
100
(was 25 before the patch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886890/+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 1887124] [NEW] [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq
You have been subscribed to a public bug: So, after this is now all upstream in mainline and I found some time to test this properly on Ubuntu, here is the backport request. Some time ago we noticed - Fedor Loshakov did - that our DIV and DIX support in zfcp broke at some point (by "broke" I mean, the kernel will unconditionally crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked that down to a commit made for v5.4 (737eb78e82d5), but we didn't notice it back than, because our CI doesn't currently run with either DIV, nor DIX enabled (time allowing this is something we want to improve so we catch stuff like this earlier). It also turned out that the commit in v5.4 was not really the root-cause, and was only making the problem visible more easy. In short: zfcp used to allocate/add the shost object for a HBA before knowing all the HBA's capabilities, and we later patched the shost object to make more of the capabilities known - including the protection capabilities. Back when we still had the old blk queue, this worked fine; after scsi_mod switched to blk-mq and because requests are now all allocated during allocation time of the blk-mq tag-set, this doesn't work anymore. Changes we make later to the protection capabilities don't get reflected into the tag-set's requests, and they are missing parts. When we then try to send I/O, scsi_mod tries to access the protection payload data, who are not there, and it crashes the kernel. So instead, I now want to allocate/add the shost object for a HBA after we know all of its base capabilities. This solves the bug. Because we had this modus operandi for a very long time, I had to touch many places that assume the shost object was already allocated - explaining the rather big patchset for a 'fix'. And because this also involves/depends on code that went upstream in v5.5 and v5.7 we now have a rather complicated situation for backports of the fix. Nothing "just" applies. The easiest and most straight forward way to deal with that is to basically backport most everything that is involved - which is most of the stuff that went upstream since v5.5 for our driver. I complied a list of the upstream commits that would have to be picked in order to be merge-conflict free: 92953c6e0aa77 scsi: zfcp: signal incomplete or error for sync exchange config/port data 7e418833e6894 scsi: zfcp: diagnostics buffer caching and use for exchange port data 088210233e6fc scsi: zfcp: add diagnostics buffer for exchange config data a10a61e807b0a scsi: zfcp: support retrieval of SFP Data via Exchange Port Data 6028f7c4cd87c scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver 8155eb0785279 scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs 5a2876f0d1ef2 scsi: zfcp: introduce sysfs interface to read the local B2B-Credit 8a72db70b5ca3 scsi: zfcp: implicitly refresh config-data diagnostics when reading sysfs 48910f8c35cfd scsi: zfcp: move maximum age of diagnostic buffers into a per-adapter variable e76acc5194264 scsi: zfcp: proper indentation to reduce confusion in zfcp_erp_required_act a3fd4bfe85fbb scsi: zfcp: fix wrong data and display format of SFP+ temperature e05a10a055098 scsi: zfcp: expose fabric name as common fc_host sysfs attribute 538c6e910baea scsi: zfcp: wire previously driver-specific sysfs attributes also to fc_host 7e0e4e0958ef7 scsi: zfcp: fix fc_host attributes that should be unknown on local link down 185f2d2d595c2 scsi: zfcp: auto variables for dereferenced structs in open port handler a17c78460093a scsi: zfcp: report FC Endpoint Security in sysfs f0d26ae847489 scsi: zfcp: log FC Endpoint Security of connections 616da39e0060f scsi: zfcp: trace FC Endpoint Security of FCP devices and connections e53d92856e9f1 scsi: zfcp: enhance handling of FC Endpoint Security errors 42cabdaf103be scsi: zfcp: log FC Endpoint Security errors cec9cbac5244b scsi: zfcp: use fallthrough; 978857c7e367d scsi: zfcp: Move shost modification after QDIO (re-)open into fenced function bd1684817d7d8 scsi: zfcp: Move shost updates during xconfig data handling into fenced function 52e61fde5ec95 scsi: zfcp: Move fc_host updates during xport data handling into fenced function 990486f3a8508 scsi: zfcp: Fence fc_host updates during link-down handling ac007adc4d2d9 scsi: zfcp: Move p-t-p port allocation to after xport data 971f2abb4ca40 scsi: zfcp: Fence adapter status propagation for common statuses 71159b6ecb067 scsi: zfcp: Fence early sysfs interfaces for accesses of shost objects d0dff2ac98dd4 scsi: zfcp: Move allocation of the shost object to after xconf- and xport-data I test this with the kernel you provide @ git://kernel.ubuntu.com/ubuntu /ubuntu-focal.git, added Linus' tree as secondary remote (@ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) and ran: git cherry-pic
[Kernel-packages] [Bug 1887124] [NEW] [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq
Public bug reported: So, after this is now all upstream in mainline and I found some time to test this properly on Ubuntu, here is the backport request. Some time ago we noticed - Fedor Loshakov did - that our DIV and DIX support in zfcp broke at some point (by "broke" I mean, the kernel will unconditionally crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked that down to a commit made for v5.4 (737eb78e82d5), but we didn't notice it back than, because our CI doesn't currently run with either DIV, nor DIX enabled (time allowing this is something we want to improve so we catch stuff like this earlier). It also turned out that the commit in v5.4 was not really the root-cause, and was only making the problem visible more easy. In short: zfcp used to allocate/add the shost object for a HBA before knowing all the HBA's capabilities, and we later patched the shost object to make more of the capabilities known - including the protection capabilities. Back when we still had the old blk queue, this worked fine; after scsi_mod switched to blk-mq and because requests are now all allocated during allocation time of the blk-mq tag-set, this doesn't work anymore. Changes we make later to the protection capabilities don't get reflected into the tag-set's requests, and they are missing parts. When we then try to send I/O, scsi_mod tries to access the protection payload data, who are not there, and it crashes the kernel. So instead, I now want to allocate/add the shost object for a HBA after we know all of its base capabilities. This solves the bug. Because we had this modus operandi for a very long time, I had to touch many places that assume the shost object was already allocated - explaining the rather big patchset for a 'fix'. And because this also involves/depends on code that went upstream in v5.5 and v5.7 we now have a rather complicated situation for backports of the fix. Nothing "just" applies. The easiest and most straight forward way to deal with that is to basically backport most everything that is involved - which is most of the stuff that went upstream since v5.5 for our driver. I complied a list of the upstream commits that would have to be picked in order to be merge-conflict free: 92953c6e0aa77 scsi: zfcp: signal incomplete or error for sync exchange config/port data 7e418833e6894 scsi: zfcp: diagnostics buffer caching and use for exchange port data 088210233e6fc scsi: zfcp: add diagnostics buffer for exchange config data a10a61e807b0a scsi: zfcp: support retrieval of SFP Data via Exchange Port Data 6028f7c4cd87c scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver 8155eb0785279 scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs 5a2876f0d1ef2 scsi: zfcp: introduce sysfs interface to read the local B2B-Credit 8a72db70b5ca3 scsi: zfcp: implicitly refresh config-data diagnostics when reading sysfs 48910f8c35cfd scsi: zfcp: move maximum age of diagnostic buffers into a per-adapter variable e76acc5194264 scsi: zfcp: proper indentation to reduce confusion in zfcp_erp_required_act a3fd4bfe85fbb scsi: zfcp: fix wrong data and display format of SFP+ temperature e05a10a055098 scsi: zfcp: expose fabric name as common fc_host sysfs attribute 538c6e910baea scsi: zfcp: wire previously driver-specific sysfs attributes also to fc_host 7e0e4e0958ef7 scsi: zfcp: fix fc_host attributes that should be unknown on local link down 185f2d2d595c2 scsi: zfcp: auto variables for dereferenced structs in open port handler a17c78460093a scsi: zfcp: report FC Endpoint Security in sysfs f0d26ae847489 scsi: zfcp: log FC Endpoint Security of connections 616da39e0060f scsi: zfcp: trace FC Endpoint Security of FCP devices and connections e53d92856e9f1 scsi: zfcp: enhance handling of FC Endpoint Security errors 42cabdaf103be scsi: zfcp: log FC Endpoint Security errors cec9cbac5244b scsi: zfcp: use fallthrough; 978857c7e367d scsi: zfcp: Move shost modification after QDIO (re-)open into fenced function bd1684817d7d8 scsi: zfcp: Move shost updates during xconfig data handling into fenced function 52e61fde5ec95 scsi: zfcp: Move fc_host updates during xport data handling into fenced function 990486f3a8508 scsi: zfcp: Fence fc_host updates during link-down handling ac007adc4d2d9 scsi: zfcp: Move p-t-p port allocation to after xport data 971f2abb4ca40 scsi: zfcp: Fence adapter status propagation for common statuses 71159b6ecb067 scsi: zfcp: Fence early sysfs interfaces for accesses of shost objects d0dff2ac98dd4 scsi: zfcp: Move allocation of the shost object to after xconf- and xport-data I test this with the kernel you provide @ git://kernel.ubuntu.com/ubuntu /ubuntu-focal.git, added Linus' tree as secondary remote (@ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) and ran: git cherry-pick 92953c6e0aa7~1..e76
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Edit to #181: - Test Case: Cold boot to Ubuntu 20.04. NO COMMAND EXECUTED, just the patched kernel from #177. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1886912] Re: DELL M3800 Touchscreen not working after login
Can you please test if enabling "automatic login" makes any difference? 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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1887124] Re: [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Critical ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-z-systems 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/1887124 Title: [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: So, after this is now all upstream in mainline and I found some time to test this properly on Ubuntu, here is the backport request. Some time ago we noticed - Fedor Loshakov did - that our DIV and DIX support in zfcp broke at some point (by "broke" I mean, the kernel will unconditionally crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked that down to a commit made for v5.4 (737eb78e82d5), but we didn't notice it back than, because our CI doesn't currently run with either DIV, nor DIX enabled (time allowing this is something we want to improve so we catch stuff like this earlier). It also turned out that the commit in v5.4 was not really the root-cause, and was only making the problem visible more easy. In short: zfcp used to allocate/add the shost object for a HBA before knowing all the HBA's capabilities, and we later patched the shost object to make more of the capabilities known - including the protection capabilities. Back when we still had the old blk queue, this worked fine; after scsi_mod switched to blk-mq and because requests are now all allocated during allocation time of the blk-mq tag-set, this doesn't work anymore. Changes we make later to the protection capabilities don't get reflected into the tag-set's requests, and they are missing parts. When we then try to send I/O, scsi_mod tries to access the protection payload data, who are not there, and it crashes the kernel. So instead, I now want to allocate/add the shost object for a HBA after we know all of its base capabilities. This solves the bug. Because we had this modus operandi for a very long time, I had to touch many places that assume the shost object was already allocated - explaining the rather big patchset for a 'fix'. And because this also involves/depends on code that went upstream in v5.5 and v5.7 we now have a rather complicated situation for backports of the fix. Nothing "just" applies. The easiest and most straight forward way to deal with that is to basically backport most everything that is involved - which is most of the stuff that went upstream since v5.5 for our driver. I complied a list of the upstream commits that would have to be picked in order to be merge-conflict free: 92953c6e0aa77 scsi: zfcp: signal incomplete or error for sync exchange config/port data 7e418833e6894 scsi: zfcp: diagnostics buffer caching and use for exchange port data 088210233e6fc scsi: zfcp: add diagnostics buffer for exchange config data a10a61e807b0a scsi: zfcp: support retrieval of SFP Data via Exchange Port Data 6028f7c4cd87c scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver 8155eb0785279 scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs 5a2876f0d1ef2 scsi: zfcp: introduce sysfs interface to read the local B2B-Credit 8a72db70b5ca3 scsi: zfcp: implicitly refresh config-data diagnostics when reading sysfs 48910f8c35cfd scsi: zfcp: move maximum age of diagnostic buffers into a per-adapter variable e76acc5194264 scsi: zfcp: proper indentation to reduce confusion in zfcp_erp_required_act a3fd4bfe85fbb scsi: zfcp: fix wrong data and display format of SFP+ temperature e05a10a055098 scsi: zfcp: expose fabric name as common fc_host sysfs attribute 538c6e910baea scsi: zfcp: wire previously driver-specific sysfs attributes also to fc_host 7e0e4e0958ef7 scsi: zfcp: fix fc_host attributes that should be unknown on local link down 185f2d2d595c2 scsi: zfcp: auto variables for dereferenced structs in open port handler a17c78460093a scsi: zfcp: report FC Endpoint Security in sysfs f0d26ae847489 scsi: zfcp: log FC Endpoint Security of connections 616da39e0060f scsi: zfcp: trace FC Endpoint Security of FCP devices and connections e53d92856e9f1 scsi: zfcp: enhance handling of FC Endpoint Security errors 42cabdaf103be scsi: zfcp: log FC Endpoint Security errors cec9cbac5244b scsi: zfcp: use fallthrough; 978857c7e367d scsi: zfcp: Move shost modification after
[Kernel-packages] [Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
** Tags added: beaver-osp1-melisa ** Tags added: oem-priority ** Also affects: oem-priority 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/1884940 Title: after login to gnome, kern.log slowly fills with snd_hda_intel :00:1f.3: No response from codec Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Dell XPS 2020 9300 Pre-loaded with Ubuntu 18.04 LTS Latest BIOS, latest available kernel, all updates applied linux kernel 5.0.0-1059-oem-osp1 After I log to Gnome, the kern.log fills itself with lines reporting this : Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2063b000 One per second. This lasts 10 to 15 seconds. Then, I see some lines but I do not know if they are related to this : Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10) (20181213/exoparg2-396) Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are initialized for Method [GINF] Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for Method [GINF]: (2 arguments defined for method invocation) Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2 Integer 003D Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9 Integer Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20278103 Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11 Then it scrolls very quickly and I get a huge amount of "hsw_power_well_enable" No idea if this is related to the messages with the sound card. Those "hsw_power_well_enable" things are also/maybe/no idea related to another reported bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670 Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here ] Jun 24 14:47:09 asgard kernel: [ 205.219413] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at /build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915] Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64 crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor Jun 24 14:47:09 asgard kernel: [ 205.219508] iwlwifi snd soundcore hid_sensor_als hid_sensor_trigger rtsx_pci_ms industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common idma64 virt_dma cfg80211 memstick mei industrialio intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid acpi_pad intel_hid int3400_thermal sp
[Kernel-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
** Tags added: beaver-osp1-melisa ** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1886827] Re: Machine hangs when doing a normal reboot
Please apply this patch and attach dmesg. ** Patch added: "lp1886827-test.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+attachment/5391227/+files/lp1886827-test.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/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 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 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+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 1884981] Re: The touchpad soesn't work at all
Please attach acpidump. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+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 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
** Tags removed: disco ** 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/1884940 Title: after login to gnome, kern.log slowly fills with snd_hda_intel :00:1f.3: No response from codec Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Dell XPS 2020 9300 Pre-loaded with Ubuntu 18.04 LTS Latest BIOS, latest available kernel, all updates applied linux kernel 5.0.0-1059-oem-osp1 After I log to Gnome, the kern.log fills itself with lines reporting this : Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2063b000 One per second. This lasts 10 to 15 seconds. Then, I see some lines but I do not know if they are related to this : Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10) (20181213/exoparg2-396) Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are initialized for Method [GINF] Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for Method [GINF]: (2 arguments defined for method invocation) Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2 Integer 003D Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9 Integer Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20278103 Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11 Then it scrolls very quickly and I get a huge amount of "hsw_power_well_enable" No idea if this is related to the messages with the sound card. Those "hsw_power_well_enable" things are also/maybe/no idea related to another reported bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670 Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here ] Jun 24 14:47:09 asgard kernel: [ 205.219413] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at /build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915] Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64 crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor Jun 24 14:47:09 asgard kernel: [ 205.219508] iwlwifi snd soundcore hid_sensor_als hid_sensor_trigger rtsx_pci_ms industrialio_triggered_buffer kfifo_buf mei_me hid_sensor_iio_common idma64 virt_dma cfg80211 memstick mei industrialio intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid acpi_pad intel_hid int3400_thermal sparse_keymap acpi_tad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_t
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
** Changed in: linux (Ubuntu Focal) Status: Fix Released => 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/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+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 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
@gilbert
We are not able to reproudce the issue using 5.0.0-1064-oem-osp1 kernel,
need more debug information from you using apport.
It seems you may have a permission problem with the your home folder, maybe you
can fix by running the following command
$ sudo chown -R $UID ${HOME}/.cache/apport
$ apport-collect 1884940
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => Rex Tsai (chihchun)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884940
Title:
after login to gnome, kern.log slowly fills with snd_hda_intel
:00:1f.3: No response from codec
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Laptop : Dell XPS 2020 9300
Pre-loaded with Ubuntu 18.04 LTS
Latest BIOS, latest available kernel, all updates applied
linux kernel 5.0.0-1059-oem-osp1
After I log to Gnome, the kern.log fills itself with lines reporting
this :
Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel
:00:1f.3: No response from codec, resetting bus: last
cmd=0x2063b000
One per second. This lasts 10 to 15 seconds.
Then, I see some lines but I do not know if they are related to this :
Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error:
AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10)
(20181213/exoparg2-396)
Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are
initialized for Method [GINF]
Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for
Method [GINF]: (2 arguments defined for method invocation)
Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2
Integer 003D
Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9
Integer
Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method
parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method
parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method
parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method
parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method
parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531)
Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method
parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT
(20181213/psparse-531)
Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20278103
Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2:
Unable to sync register 0x2f8100. -11
Then it scrolls very quickly and I get a huge amount of
"hsw_power_well_enable"
No idea if this is related to the messages with the sound card.
Those "hsw_power_well_enable" things are also/maybe/no idea related to
another reported bug :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670
Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here
]
Jun 24 14:47:09 asgard kernel: [ 205.219413]
WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) *
2)), (0x1 << ((pw_idx) * 2)), 1))
Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at
/build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308
hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915]
Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac
bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb
videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic
hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl
x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp
snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda
snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core
snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel
snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep
crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event
snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64
crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas
snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof
intel_wmi_thunderbolt dell_wmi_descriptor
Jun 24 14:47:09 asgard kernel: [ 205.219508]
[Kernel-packages] [Bug 1886827] Re: Machine hangs when doing a normal reboot
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 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 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+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 1885862] Re: Add in-tree Realtek 8821CE wireless module support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1885862 Title: Add in-tree Realtek 8821CE wireless module support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Incomplete Status in linux-firmware source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Incomplete Status in linux-firmware source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: 8821ce is being upstreamed in https://lore.kernel.org/linux- wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce . To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885862/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I'm sure around 99% it's Intel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
Yeah! I hope this will be backported into 5.4 for Ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Bug description: New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Well, let's start from `apport-collect 1871721`. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1879360] Re: ubuntu_bpf test failed to build on F-OEM-5.6
On Groovy it seems clang was pointed to clang-10, so no further fixes were needed for now. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1879360 Title: ubuntu_bpf test failed to build on F-OEM-5.6 Status in ubuntu-kernel-tests: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Bug description: Test build failed with: Couldn't find kernel BTF; set VMLINUX_BTF to specify its location. Please find attachment for the complete build log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1010-oem 5.6.0-1010.10 ProcVersionSignature: User Name 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 18 16:03:17 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879360/+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 1879308] Re: ubuntu_aufs_smoke_test failed on Focal OEM 5.6
Passed with 5.6.0-1020.20 Focal OEM Thank you! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1879308 Title: ubuntu_aufs_smoke_test failed on Focal OEM 5.6 Status in ubuntu-kernel-tests: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: Issue found on OEM 5.6 (5.6.0-1010.10-oem) Test failed with: mount: /tmp/aufs/aufs-root: unknown filesystem type 'aufs'. Need to check if 5.6 supports aufs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879308/+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 1881576] Re: seccomp_benchmark times out on eoan
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: ubuntu-kernel-tests Status: Invalid => 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/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. == As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wo
@Prajwal, We could not find that machine to debug, since this issue happens randomly, we have no idea what introduces this issue. Could you try the latest mainline kernel to see if it works or not (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/), if it still could not work, it is better to report this issue to upstream kernel bugzilla (https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers), let community help fix this bug, then we will integrate the fix to ubuntu 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/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in linux package in Ubuntu: Incomplete Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852067/+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 1880519] Re: System stops responding while entering S3 with SD card installed
https://lists.ubuntu.com/archives/kernel-team/2020-July/111958.html ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Description changed: + [SRU Justfication] + [Impact] The system stops responding while entering S3, screen will be lit up if touchpad is triggered by finger. Cursor could be seen with black background, but system is not responding to any input. [Fix] b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM f0c472a6da51 xhci: Return if xHCI doesn't support LPM - [test] - With the above patch applied: - - 4.15.0-1081-oem PASSED (30/30) - bionic PASSED (30/30) - bionic-oem PASSED (30/30) - bionic-oem-osp1 PASSED (30/30) - eoan PASSED (30/30) - focal PASSED (30/30) - focal-oem PASSED (30/30) - ubuntu-unstable PASSED (30/30) - - [Regression Potential] + [Fix] + Patchset[1] for fix this issue currently landed in upstream, + so we backported them: + + [1]: + b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM + f0c472a6da51 xhci: Return if xHCI doesn't support LPM + + [Test] + With the above patch applied, run: + sudo fwts --s3-sleep-delay=30 --s3-multiple=30 -p s3 + + Can passed 30 times. + + [Regression Potential] + Low, the patch is just like a safeguard, + doesn't really change any behavior. [Reproduce Steps] 1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso 2. Upgrade kernel to 4.15.0-1080-oem 3. Boot the system with 4.15.0-1080-oem kernel 4. Insert SD card 5. Suspend the system to S3 ** Tags added: suspend-resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880519 Title: System stops responding while entering S3 with SD card installed Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Won't Fix Status in linux-oem source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Status in lin
[Kernel-packages] [Bug 1884940] Re: after login to gnome, kern.log slowly fills with snd_hda_intel 0000:00:1f.3: No response from codec
@chihchun see bug 1879389 for the apport dump. Because the kernel logs fill up with WARN_ON(intel_wait_for_register(...))/hsw_wait_for_power_well_enable it's hard to find specific other issues. I have observed the sound driver being crashy/sad on the same hardware but it's possibly improved with subsequent updates? Hard to tell with intermittent issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884940 Title: after login to gnome, kern.log slowly fills with snd_hda_intel :00:1f.3: No response from codec Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: Laptop : Dell XPS 2020 9300 Pre-loaded with Ubuntu 18.04 LTS Latest BIOS, latest available kernel, all updates applied linux kernel 5.0.0-1059-oem-osp1 After I log to Gnome, the kern.log fills itself with lines reporting this : Jun 24 14:46:22 asgard kernel: [ 158.134245] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2063b000 One per second. This lasts 10 to 15 seconds. Then, I see some lines but I do not know if they are related to this : Jun 24 14:47:08 asgard kernel: [ 203.874519] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x0003D) is beyond end of object (length 0x10) (20181213/exoparg2-396) Jun 24 14:47:08 asgard kernel: [ 203.874538] No Local Variables are initialized for Method [GINF] Jun 24 14:47:08 asgard kernel: [ 203.874539] Initialized Arguments for Method [GINF]: (2 arguments defined for method invocation) Jun 24 14:47:08 asgard kernel: [ 203.874540] Arg0: 69cda4c2 Integer 003D Jun 24 14:47:08 asgard kernel: [ 203.874543] Arg1: 806e1ac9 Integer Jun 24 14:47:08 asgard kernel: [ 203.874546] ACPI Error: Method parse/execution failed \_SB.GINF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874550] ACPI Error: Method parse/execution failed \_SB.GADR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874553] ACPI Error: Method parse/execution failed \_SB.SGOV, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874556] ACPI Error: Method parse/execution failed \_SB.CGWR, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874559] ACPI Error: Method parse/execution failed \_SB.TBFP, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:08 asgard kernel: [ 203.874562] ACPI Error: Method parse/execution failed \_SB.WMTF.WMTF, AE_AML_PACKAGE_LIMIT (20181213/psparse-531) Jun 24 14:47:09 asgard kernel: [ 204.515539] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20278103 Jun 24 14:47:09 asgard kernel: [ 204.515545] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f8100. -11 Then it scrolls very quickly and I get a huge amount of "hsw_power_well_enable" No idea if this is related to the messages with the sound card. Those "hsw_power_well_enable" things are also/maybe/no idea related to another reported bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670 Jun 24 14:47:09 asgard kernel: [ 205.219410] [ cut here ] Jun 24 14:47:09 asgard kernel: [ 205.219413] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) Jun 24 14:47:09 asgard kernel: [ 205.219489] WARNING: CPU: 6 PID: 2794 at /build/linux-oem-osp1-cysXhs/linux-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915] Jun 24 14:47:09 asgard kernel: [ 205.219489] Modules linked in: ccm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth media ecdh_generic hid_multitouch 8250_dw snd_hda_codec_hdmi dell_laptop arc4 intel_rapl x86_pkg_temp_thermal sof_pci_dev nls_iso8859_1 intel_powerclamp snd_sof_intel_hda_common coretemp snd_soc_hdac_hda snd_sof_intel_hda snd_sof_xtensa_dsp kvm_intel snd_sof snd_hda_codec_realtek snd_hda_ext_core snd_hda_codec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq aesni_intel dell_wmi dell_smbios iwlmvm aes_x86_64 crypto_simd cryptd glue_helper intel_cstate input_leds joydev dcdbas snd_seq_device intel_rapl_perf snd_timer mac80211 serio_raw wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor Jun 24 14:47:09 asgard kernel: [ 205.219508] iwlwifi snd soundcore hid_sensor_als hid_sensor_trigger rtsx_pci_ms industrialio_triggered_buffer kfifo_bu
[Kernel-packages] [Bug 1886165] Re: [WD19TB] external DP failed with DRM error message
Verification on TGL machine PASSED (10/10)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1886165
Title:
[WD19TB] external DP failed with DRM error message
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Bug description:
[SRU Justfication]
TGL platform can't output external monitor on WD19TB docking.
There's no screen on the external monitor.
error in dmesg:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO
underru
[Fix]
According to Intel's suggestion,
we need this: https://patchwork.freedesktop.org/series/78909/
Also for dependency, the following patches are landed in drm-tip
and necessary for support TGL platform:
* commit f4ece33f51d8 ("drm/i915/tgl+: Fix TBT DPLL fractional divider for
38.4MHz ref clock")
* commit a6e96d6948c8 ("drm/i915/tgl+: Use the correct DP_TP_* register
instances in MST encoders")
* commit f822a79734e1 ("drm/i915/dc3co: Avoid full modeset when EXITLINE
needs to be changed")
* commit 1a7e82efaa8a ("drm/i915/tgl: Add HBR and HBR2+ voltage swing table")
* commit 80907edcc6ed ("UBUNTU: SAUCE: drm/i915/bios: add
intel_bios_hdmi_level_shift()")
* commit 6df896896c8d ("drm/i915/tgl: Implement WA_16011163337")
* commit cb730fe971f0 ("drm/i915/tgl: Update TC DP vswing table")
[Test]
The WD19TB can output HDMI/DP to external monitor.
[Regression Potential]
Medium, in order to support TGL platform, we also include two patches:
drm/i915/bios: add intel_bios_hdmi_level_shift()
drm/i915/dc3co: Avoid full modeset when EXITLINE needs to be changed
The two patches are not related to TGL, but for dependency.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1886165/+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 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
Thanks for the advice for bisecting! I found the commits causing the problem: After bb4fb62a863ea6131bdac77b21faa9444a605c58 (SUNRPC: Add "@len" parameter to gss_unwrap()) NFS with Kerberos is completely broken: $ mount -v /nfs/share mount.nfs: trying text-based options 'sec=krb5p,soft,intr,bg,timeo=100,retrans=2,vers=4.2,addr=:::1::1,clientaddr=:::1::dbfb' mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed After c711ec1aa0c8ff7d979d7f12d1d09df46f349d61 (SUNRPC: Fix GSS privacy computation of auth->au_ralign) mounts work again but the crashes shown in the previous comments occur. ** 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 0
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
Same issue with kernel 5.6.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+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 1887156] [NEW] USB ports not working on the Pi 4 rev 1.4 board
Public bug reported: On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Bug description: On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+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 1881346] Re: linux-kvm should support nftables
** Description changed: - LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, - and groovy: + [Impact] + + LXD can't use nftables on the latest linux-kvm kernels for Eoan and + Focal, since nftables support is off in those kernels (contrary to + generic, where nftables is enabled). + + [Fix] + + Apply the attached config change + + [Regression potential] + + Low, we are enabling new CONFIG_NF* options widely used in generic since + a while. + + Boot performance wise, the config change has been tested on a isolated + KVM instance, iterating over 100 reboots and we didn't notice any + evident regression: + + 5.4.0-1018-kvm 20.04 focal (CPUS=1): + + kernel: 2.16371, user: 7.58647, total: 9.75018 + kernel_std: .03405, user_std: .33445, total_std: .33524 + + 5.4.0-1018-kvm~nft 20.04 focal (CPUS=1): + + kernel: 2.15961, user: 7.63694, total: 9.79655 + kernel_std: .03420, user_std: .36585, total_std: .37049 + + + --- + LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. ** Description changed: [Impact] - LXD can't use nftables on the latest linux-kvm kernels for Eoan and - Focal, since nftables support is off in those kernels (contrary to - generic, where nftables is enabled). + LXD can't use nftables on the latest Focal/linux-kvm kernel, since + nftables support is off (contrary to generic, where nftables is + enabled). [Fix] Apply the attached config change [Regression potential] - Low, we are enabling new CONFIG_NF* options widely used in generic since - a while. + Low, we are enabling CONFIG_NF* options widely used in generic since a + while. Boot performance wise, the config change has been tested on a isolated KVM instance, iterating over 100 reboots and we didn't notice any evident regression: 5.4.0-1018-kvm 20.04 focal (CPUS=1): kernel: 2.16371, user: 7.58647, total: 9.75018 kernel_std: .03405, user_std: .33445, total_std: .33524 5.4.0-1018-kvm~nft 20.04 focal (CPUS=1): kernel: 2.15961, user: 7.63694, total: 9.79655 kernel_std: .03420, user_std: .36585, total_std: .37049 - --- LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. -- 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/1881346 Title: linux-kvm should support nftables Status in linux-kvm package in Ubuntu: New Bug description: [Impact] LXD can't use nftables on the latest Focal/linux-kvm kernel, since nftables support is off (contrary to generic, where nftables is enabled). [Fix] Apply the attached config change [Regression potential] Low, we are enabling CONFIG_NF* options widely used in generic since a while. Boot performance wise, the config change has been tested on a isolated KVM instance, iterating over 100 reboots and we didn't notice any evident regression: 5.4.0-1018-kvm 20.04 focal (CPUS=1): kernel: 2.16371, user: 7.58647, total: 9.75018 kernel_std: .03405, user_std: .33445, total_std: .33524 5.4.0-1018-kvm~nft 20.04 focal (CPUS=1): kernel: 2.15961, user: 7.63694, total: 9.79655 kernel_std: .03420, user_std: .36585, total_std: .37049 --- LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1881346/+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 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Status in linux-raspi2 source package in Eoan: New Bug description: On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+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 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
Running now on 5.6.0-1010-oem, and sound is working! That includes the internal microphone. Thank you, Hui Wang and Corbin! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO d
[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
I do observe the exactly same on a HP elitebook 840 G6 with the phone pickup and hangup keys and other HP fancy keys i usually do not need. They either mapp to left_ctrl left_meta or left_ctrl elft_alt. Event: time 1594376396.025858, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d Event: time 1594376396.025858, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1594376396.025858, -- SYN_REPORT Event: time 1594376396.026015, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38 Event: time 1594376396.026015, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1594376396.026015, -- SYN_REPORT Event: time 1594376396.026120, type 4 (EV_MSC), code 4 (MSC_SCAN), value 65 Event: time 1594376396.026120, -- SYN_REPORT Event: time 1594376622.906330, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38 Event: time 1594376622.906330, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1594376622.906330, -- SYN_REPORT Event: time 1594376622.906498, type 4 (EV_MSC), code 4 (MSC_SCAN), value 66 Event: time 1594376622.906498, -- SYN_REPORT Event: time 1594376622.906682, type 4 (EV_MSC), code 4 (MSC_SCAN), value db Event: time 1594376622.906682, type 1 (EV_KEY), code 125 (KEY_LEFTMETA), value 0 Event: time 1594376622.906682, -- SYN_REPORT Checking the scanvalue it turns out that pressing left_alt and left_ctrl produce the same individual key codes as returned for one key press of the special HP keys. Event: time 1594376291.093583, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38 Event: time 1594376291.093583, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1594376291.093583, -- SYN_REPORT Event: time 1594376291.240595, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38 Event: time 1594376291.240595, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1594376291.240595, -- SYN_REPORT Event: time 1594376295.981981, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d Event: time 1594376295.981981, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1594376295.981981, -- SYN_REPORT Event: time 1594376296.095764, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d Event: time 1594376296.095764, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0 Event: time 1594376296.095764, -- SYN_REPORT Looking at the scans it seems as if these special keys would produce three keystrokes at the same time code 0x1d, 0x38, 0x65 code 0x38, 0x66, 0xdb The codes 0x65 and 0x66 seem to be ignored by the kernel or udev and thus the keypress is seems to be shortened to code 0x1d, 0x38 -> which maps to and this is fatal in my case cause directly underneath the phone hangup button with too little space in between is the backspace button located. Yes!!! whenever i hit inbetween the two keys the X-Server thinks I requested him to zap. Looking at the event code table printed by evtest it seems as if the code 101 = 0x65 is not used or mapped. I tried to make an appropriate udev rule to map 0x65 and 0x66 to some key but this is not applied thus i still stuck with having to too close keys acting as ctrl alt bksp which is the good old Xorg zap combination which i do not want to disable. But whatever i try exempt reboot yet to map missing codes to keys does not work. neither udev method nor setkeycodes in xorg works. nor reboot. It is a bit unluckily annoying the situation, at least i know to watchout when hitting backspace key not to accidentially also hit phone hangup key. I'm using kernel 5.3.0-40-lowlatency which is currently the latest packaged by ubuntu hwe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: Triaged Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Curren
[Kernel-packages] [Bug 1881015] Re: Fn Lock light does not come on to indicate when Fn Lock is enabled
Kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=207841 ** Bug watch added: Linux Kernel Bug Tracker #207841 https://bugzilla.kernel.org/show_bug.cgi?id=207841 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881015 Title: Fn Lock light does not come on to indicate when Fn Lock is enabled Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo E595 running Ubuntu 20.04. The "Fn Lock" feature on the keyboard works in terms of how it modifies subsequent presses of the F1-F12 keys, but the little light on the Esc key doesn't show the current state. Example: 1. I press F5 a few times, and the screen brightness is adjusted. 2. I press Fn+Esc, and "Fn Lock" is now on, but the light hasn't changed. 3. I press F5 again, or several times, and it acts as a normal F5 (ie my browser might refresh the page). 4. I press Fn+Esc again, and "Fn Lock" is now off, but again the light hasn't changed. So, "Fn Lock" works in the sense that it modifies what keypresses do, but the little light on the Esc key doesn't come on. Under Windows the light does toggle, to show the current status. The behaviour is the same on Xorg and Wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.31.36 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2138 F pulseaudio /dev/snd/controlC0: paul 2138 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 21:37:47 2020 InstallationDate: Installed on 2020-05-13 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f7c34228-ee6f-4043-931c-f4752ad503c8 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881015/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
We are working with HP on this issue. Please stay tuned. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: Triaged Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1886257] Re: Touchpad detection issue in Fujitsu Lifebook UH554
@You-Sheng Yang (vicamo) , the touchpad is now working properly . Thank you for that update . ->check the attachment ** Attachment added: "dmesg output , after update" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886257/+attachment/5391306/+files/check_this.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/1886257 Title: Touchpad detection issue in Fujitsu Lifebook UH554 Status in linux package in Ubuntu: Incomplete Bug description: Laptop model : Fujitsu Lifebook UH554 Ram : 8 GB HDD : 500 GB Processor : i5 Manufacturer of the Touchpad : Unknown When the symptom first appeared : After installing the OS 20.04 itself --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shingade 1340 F pulseaudio /dev/snd/controlC0: shingade 1340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04c5:1330 Fujitsu, Ltd Bus 001 Device 003: ID 04f2:b3df Chicony Electronics Co., Ltd FJ Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK UH554 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e9d4e33d-952d-4e3b-b8dc-1c374b7c329b ro quiet splash i8042.notimeout i8042.nomux vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/28/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.25 dmi.board.name: FJNBB34 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.25:bd05/28/2014:svnFUJITSU:pnLIFEBOOKUH554:pvr:rvnFUJITSU:rnFJNBB34:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK UH554 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886257/+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 1886257] Re: Touchpad detection issue in Fujitsu Lifebook UH554
You didn't boot into my kernels, and please remove those grub parameters before testing them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886257 Title: Touchpad detection issue in Fujitsu Lifebook UH554 Status in linux package in Ubuntu: Incomplete Bug description: Laptop model : Fujitsu Lifebook UH554 Ram : 8 GB HDD : 500 GB Processor : i5 Manufacturer of the Touchpad : Unknown When the symptom first appeared : After installing the OS 20.04 itself --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shingade 1340 F pulseaudio /dev/snd/controlC0: shingade 1340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04c5:1330 Fujitsu, Ltd Bus 001 Device 003: ID 04f2:b3df Chicony Electronics Co., Ltd FJ Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK UH554 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e9d4e33d-952d-4e3b-b8dc-1c374b7c329b ro quiet splash i8042.notimeout i8042.nomux vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/28/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.25 dmi.board.name: FJNBB34 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.25:bd05/28/2014:svnFUJITSU:pnLIFEBOOKUH554:pvr:rvnFUJITSU:rnFJNBB34:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK UH554 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886257/+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 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board
Looks like we need to backport patches from branch rpi-5.4.x to ubuntu rpi eoan kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Status in linux-raspi2 source package in Eoan: New Bug description: On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+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 1886257] Re: Touchpad detection issue in Fujitsu Lifebook UH554
@You-Sheng Yang (vicamo) , first : I removed those grub parameters . second : sudo apt update third : sudo apt upgrade fourth : took dmesg is there any more steps or any other steps required to be carried out ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886257 Title: Touchpad detection issue in Fujitsu Lifebook UH554 Status in linux package in Ubuntu: Incomplete Bug description: Laptop model : Fujitsu Lifebook UH554 Ram : 8 GB HDD : 500 GB Processor : i5 Manufacturer of the Touchpad : Unknown When the symptom first appeared : After installing the OS 20.04 itself --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shingade 1340 F pulseaudio /dev/snd/controlC0: shingade 1340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04c5:1330 Fujitsu, Ltd Bus 001 Device 003: ID 04f2:b3df Chicony Electronics Co., Ltd FJ Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK UH554 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e9d4e33d-952d-4e3b-b8dc-1c374b7c329b ro quiet splash i8042.notimeout i8042.nomux vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/28/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.25 dmi.board.name: FJNBB34 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.25:bd05/28/2014:svnFUJITSU:pnLIFEBOOKUH554:pvr:rvnFUJITSU:rnFJNBB34:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK UH554 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886257/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/387217 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
apport information ** Tags added: apport-collected third-party-packages ubuntu ** Description changed: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) - PD: When you select a specific resolution, the second monitor "works", - but it blinks, the image showed via HDMI on the second monitor blinks. - So is impossible to work with it. Since all this time I was searching - about this and I'm almost sure this is a problem of the GPU's Intel. But - I saw this problem on askubuntu just with laptops with hybrid graphics. - Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if - they have the same problem here). + PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). + --- + ProblemType: Bug + .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.suspend: suspend hibernate resume + .proc.driver.nvidia.suspend_depth: default modeset uvm + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 + GCC version: + ApportVersion: 2.20.11-0ubuntu
[Kernel-packages] [Bug 1871721] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391340/+files/BootLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.dri
[Kernel-packages] [Bug 1871721] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391342/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm
[Kernel-packages] [Bug 1871721] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391344/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.n
[Kernel-packages] [Bug 1871721] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391345/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.d
[Kernel-packages] [Bug 1871721] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391341/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm
[Kernel-packages] [Bug 1871721] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391343/+files/DpkgLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.dri
[Kernel-packages] [Bug 1871721] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391346/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.n
[Kernel-packages] [Bug 1871721] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391352/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset u
[Kernel-packages] [Bug 1871721] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391347/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.dri
[Kernel-packages] [Bug 1871721] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391348/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.dri
[Kernel-packages] [Bug 1871721] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391351/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default m
[Kernel-packages] [Bug 1871721] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391353/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .
[Kernel-packages] [Bug 1871721] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391356/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .pr
[Kernel-packages] [Bug 1871721] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391357/+files/Xrandr.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver
[Kernel-packages] [Bug 1871721] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391354/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver
[Kernel-packages] [Bug 1871721] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391355/+files/XorgLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.dri
[Kernel-packages] [Bug 1871721] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391350/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .
[Kernel-packages] [Bug 1871721] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391349/+files/NvidiaBugReportLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default m
[Kernel-packages] [Bug 1871721] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391359/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.d
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
PD: The mesa driver of intel's working with the same version of git, just trying to make it work. But with the stable version doesn't work neither. Just in case you wanted to know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.sus
[Kernel-packages] [Bug 1871721] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1871721/+attachment/5391358/+files/nvidia-settings.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Can you please try Wayland? Seems to be an X11 bug... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/ If mainline kernel works, then we need to backport some commits to filling gap between v5.4 and the offending commit. If mainline kernel doesn't work, we need to raise the issue to upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP:
[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd
AMD is currently bringing proper support for LPS0 device. Please stay tuned. ** Changed in: linux (Ubuntu) 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/1886937 Title: limited hardware support AMD 4700u HP Envy x360 13-ay003nd Status in linux package in Ubuntu: Confirmed Bug description: Suspend/Hibernate: screen goes off, nothing else happens. After user interaction, screen turns on. Login screen is shown. Sometimes screen does not turn on: physical reboot required. kernel upgrade to 5.8rc3 or 5.8rc4 has no effect. Brightness: Adjusting brightness has no effect, nightmode has no effect. Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, brightness can be adjusted and nightmode works But after a reboot brightness is always at max. Also brightness cannot be lowered as much as normally expected. CPU & fan: CPU is always high, 5.8rc3 solves this partially, fan is still always on and quite high (after clean Ubuntu install, nothing configured or installed). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: asterix 881 F pulseaudio /dev/snd/controlC1: asterix 881 F pulseaudio /dev/snd/controlC0: asterix 881 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jul 9 12:21:02 2020 InstallationDate: Installed on 2020-07-09 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 1D5H9EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886937/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I tried with Wayland but only with Intel (there's no option with Nvidia), same result. Maybe 'cause's working under XWayland? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.v
[Kernel-packages] [Bug 1885463] Re: [amdgpu] display and input freeze
Possible to use 20.04 instead? If 18.04 is required, please use HWE stack: https://wiki.ubuntu.com/Kernel/LTSEnablementStack And please keep BIOS up-to-date. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885463 Title: [amdgpu] display and input freeze Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Newly installed Ubuntu on a Lenovo laptop - less than 24 hours old. Just now, I revived laptop from sleep or hibernate and the display was frozen and corrupted. The bottom 1/3 of display was a patchwork of small squares of junk in green, pink, blue; top 2/3 of screen was a slightly distorted version of the default orange/purple background and the clock. I couldn't interact with the computer with mouse or keyboard - no mouse pointer, no control-alt-delete, no control- backspace. I found alt-PrtSc-reisub on google and was able to reboot from the keyboard. I'm running 18.04.4 LTS, on 2017ish Lenovo E450 with AMD Carrizo graphics card ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 18:33:57 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon R5 Graphics [17aa:5118] MachineType: LENOVO 20H4CTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R0EET41W (1.15) dmi.board.asset.tag: Not Available dmi.board.name: 20H4CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0EET41W(1.15):bd06/06/2017:svnLENOVO:pn20H4CTO1WW:pvrThinkPadE475:rvnLENOVO:rn20H4CTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E475 dmi.product.name: 20H4CTO1WW dmi.product.version: ThinkPad E475 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885463/+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 1882088] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2020-07-10 11:24 EDT--- Here is a proper link: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=fb4f79264c0fc6fd5a68ffe3e31bfff97311e1f1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wo
Hello @Hui Wang, I have created a alsa-info.sh when the sound is working normally.I have attached both links for working sound and not working sound cases. Please take a look at it. May be you could get some idea from it? Sound Not working from internal speakers. http://alsa-project.org/db/?f=752ec2e16ade480b7793f110e2bdaf30dfb75af6 Sound Working from internal Speakers. http://alsa-project.org/db/?f=85278199fe60dad58925ffecee6005273fe18261 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in linux package in Ubuntu: Incomplete Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852067/+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 1885397] Re: Touchpad not detected
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 ** This bug has been marked a duplicate of bug 1885573 Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885397 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Touchpad (with microsoft precision drivers) can't recognize by linux. No touchpad manufacture can't be identified Laptop: Lenovo IdeaPad 5 15IIL05. Occurence: Direct after installing ubuntu. Thank you for your support. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 23:29:48 2020 InstallationDate: Installed on 2020-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=6673529c-7bec-4811-99fa-d7f1f6492f6b ro i8042.reset quit splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN41WW:bd04/10/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885397/+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 1875236] Re: Different kernel gives different RAM results
Please attach dmesg when booting from Live USB. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875236 Title: Different kernel gives different RAM results Status in linux package in Ubuntu: Confirmed Bug description: Kernel from installed distro doesn't recognize all available memory on my laptop (Acer Swift 5 SF514-54T-59VD, Ubuntu Focal Fossa 20.04). When I load Linux distro (Focal Fossa 20.04 release) from installation USB-stick Kernel detects all memory (over 7Gb, part of memory used by graphic, on laptop installed 8Gb memory). Kernel from installed distro shows only 1.5 Gb available memory. Output of commands for installed system: $ lsb_release -a; uname -a; free -m No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux mxmaki 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 1628 806 110 163 711 498 Swap: 2047 24 2023 Output of commands for system from installation USB-stick: $ lsb_release -a; uname -a; free -m Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 7641 763 3323 675 3554 5903 Swap: 0 0 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-18 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: Acer Swift SF514-54T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=52fa8c38-ee95-4b49-834a-f21af8e7e904 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Yebisu_IL dmi.board.vendor: IL dmi.board.version: V1.13 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd12/19/2019:svnAcer:pnSwiftSF514-54T:pvrV1.13:rvnIL:rnYebisu_IL:rvrV1.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-54T dmi.product.sku: dmi.product.version: V1.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875236/+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 1870014] Re: task blocked too long
Ok, this looks like a regression. Which kernel is the 16.04 laptop use? Can you please test kernel v4.9 and v4.10? I guess the regression was introduce between these two versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long Status in linux package in Ubuntu: Confirmed Bug description: I plugged in the EasyCap device, then started VLC to read from it. Nothing worked, and I saw the following call traces from the kernel: Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB device number 41 using xhci_hcd Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power cycle Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to enumerate USB device Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB device number 44 using xhci_hcd Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 altsetting 1 bulk endpoint 0x83 has invalid maxpa cket 256 Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device found, idVendor=1b71, idProduct=3002 Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device strings: Mfr=3, Product=4, SerialNumber=2 Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007 Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: fushicai Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 3002 Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai USBTV007 Audio-Video Grabber Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, device number 44 Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long (3978 > 3967), lowering kernel.perf_event_max_sam ple_rate to 50250 Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus kernel: [50024.968512] Tainted: G IOE 4.15.0-94-generic #95-Ubuntu Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251 1 0x Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace: Mar 31 23:55:36 cerberus kernel: [50024.968535] __schedule+0x24e/0x880 Mar 31 23:55:36 cerberus kernel: [50024.968539] schedule+0x2c/0x80 Mar 31 23:55:36 cerberus kernel: [50024.968542] schedule_preempt_disabled+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968547] __mutex_lock.isra.5+0x276/0x4e0 Mar 31 23:55:36 cerberus kernel: [50024.968551] __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968554] ? __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968557] mutex_lock+0x2f/0x40 Mar 31 23:55:36 cerberus kernel: [50024.968569] _vb2_fop_release+0x29/0xa0 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968573] vb2_fop_release+0x31/0x40 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968593] v4l2_release+0x38/0x80 [videodev] Mar 31 23:55:36 cerberus kernel: [50024.968600] __fput+0xea/0x220 Mar 31 23:55:36 cerberus kernel: [50024.968604] fput+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968611] task_work_run+0x9d/0xc0 Mar 31 23:55:36 cerberus kernel: [50024.968620] exit_to_usermode_loop+0xc0/0xd0 Mar 31 23:55:36 cerberus kernel: [50024.968623] do_syscall_64+0x121/0x130 Mar 31 23:55:36 cerberus kernel: [50024.968630] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 EFLAGS: 0293 ORIG_RAX: 0003 Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX: RBX: 0064 RCX: 7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX: RSI: 7f63da9bd930 RDI: 0064 Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP: R08: R09: Mar 31 23:55:36 cerberus kernel: [50024.968642] R10: R11: 0293 R12: 7f628d4c5fa0 Mar 31 23:55:36 cerberus kernel: [50024.968644] R13: R14: 7f640422d381 R15: 7f63da9bd930 Mar 31 23:55:36 cerberus
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Please test latest drm-tip kernel with kernel parameter "drm.debug=0xe log_buf_len=16M": https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ ...and attach dmesg here... Hopefully this is not another LSPCON bug... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: sus
[Kernel-packages] [Bug 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board
** Changed in: linux-raspi2 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-raspi2 (Ubuntu Bionic) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi2 (Ubuntu Eoan) Importance: Undecided => High ** Changed in: linux-raspi2 (Ubuntu Eoan) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Status in linux-raspi2 source package in Eoan: New Bug description: On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+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 1880835] Re: pulse audio hangs in kernel call
Mario, It's Precision 7540 and dma_pte_clear_level()... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880835/+subscriptions -- Mailing list: https://laun
[Kernel-packages] [Bug 1883012] Re: CPU stuck for 22s
Oh I have the exact same setup. Please set "Typical Current Idle" in the BIOS and see if it helps. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883012 Title: CPU stuck for 22s Status in linux package in Ubuntu: Incomplete Bug description: I get regularly system freezes, so that nothing works anymore. The only thing I can do, is a hard reset. These are the last kernel logs: Jun 10 21:34:47 stefano-linux anacron[6995]: Anacron 2.3 started on 2020-06-10 Jun 10 21:34:47 stefano-linux anacron[6995]: Normal exit (0 jobs run) Jun 10 21:35:41 stefano-linux rtkit-daemon[1169]: Supervising 12 threads of 8 processes of 2 users. Jun 10 21:35:41 stefano-linux rtkit-daemon[1169]: Supervising 12 threads of 8 processes of 2 users. Jun 10 21:39:03 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:39:16 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:42:43 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:42:57 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:47:41 stefano-linux kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [JS Helper:2153] Jun 10 21:47:41 stefano-linux kernel: Modules linked in: snd_usb_audio snd_usbmidi_lib gspca_vc032x uvcvideo gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc snd_hda_codec_hdmi edac_mce_amd kvm_amd kvm nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(> Jun 10 21:47:41 stefano-linux kernel: CPU: 1 PID: 2153 Comm: JS Helper Tainted: P O 5.4.0-37-generic #41-Ubuntu Jun 10 21:47:41 stefano-linux kernel: Hardware name: System manufacturer System Product Name/PRIME B350-PLUS, BIOS 5407 12/31/2019 Jun 10 21:47:41 stefano-linux kernel: RIP: 0010:smp_call_function_many+0x203/0x270 Jun 10 21:47:41 stefano-linux kernel: Code: 73 08 e8 90 0e 96 00 3b 05 5e d4 6f 01 89 c7 0f 83 9b fe ff ff 48 63 c7 48 8b 0b 48 03 0c c5 80 59 04 9e 8b 41 18 a8 01 74 0a 90 8b 51 18 83 e2 01 75 f6 eb c8 89 cf 48 c7 c2 60 ae 44 9e 4c Jun 10 21:47:41 stefano-linux kernel: RSP: 0018:98bc02edbb58 EFLAGS: 0202 ORIG_RAX: ff13 Jun 10 21:47:41 stefano-linux kernel: RAX: 0003 RBX: 8890ce86bc80 RCX: b8bbfe817680 Jun 10 21:47:41 stefano-linux kernel: RDX: 0001 RSI: RDI: 0008 Jun 10 21:47:41 stefano-linux kernel: RBP: 98bc02edbb98 R08: 8890bfedc788 R09: 8890bfedc018 Jun 10 21:47:41 stefano-linux kernel: R10: 8890bfedc788 R11: R12: 9cc88c80 Jun 10 21:47:41 stefano-linux kernel: R13: 8890ce86a640 R14: 0001 R15: 0020 Jun 10 21:47:41 stefano-linux kernel: FS: 7f3c91505700() GS:8890ce84() knlGS: Jun 10 21:47:41 stefano-linux kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 10 21:47:41 stefano-linux kernel: CR2: 7fdb7324afe0 CR3: 000396ff CR4: 003406e0 Jun 10 21:47:41 stefano-linux kernel: Call Trace: Jun 10 21:47:41 stefano-linux kernel: native_flush_tlb_others+0x55/0x170 Jun 10 21:47:41 stefano-linux kernel: flush_tlb_mm_range+0xb4/0xe0 Jun 10 21:47:41 stefano-linux kernel: tlb_flush_mmu+0xb0/0x140 Jun 10 21:47:41 stefano-linux kernel: tlb_finish_mmu+0x42/0x80 Jun 10 21:47:41 stefano-linux kernel: unmap_region+0xf9/0x130 Jun 10 21:47:41 stefano-linux kernel: __do_munmap+0x291/0x4c0 Jun 10 21:47:41 stefano-linux kernel: mmap_region+0x240/0x670 Jun 10 21:47:41 stefano-linux kernel: do_mmap+0x3b4/0x5c0 Jun 10 21:47:41 stefano-linux kernel: vm_mmap_pgoff+0xcb/0x120 Jun 10 21:47:41 stefano-linux kernel: ksys_mmap_pgoff+0x5b/0x2a0 Jun 10 21:47:41 stefano-linux kernel: ? free_cpumask_var+0x9/0x10 Jun 10 21:47:41 stefano-linux kernel: __x64_sys_mmap+0x33/0x40 Jun 10 21:47:41 stefano-linux kernel: do_syscall_64+0x57/0x190 Jun 10 21:47:41 stefano-linux kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 10 21:47:41 stefano-linux kernel: RIP: 0033:0x7f3ca311f70d Jun 10 21:47:41 stefano-linux kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 f7 0c 00 f7 d8 64 89 01 48 Jun 10 21:47:41 stefano-linux kernel: RSP: 002b:7f3c91504b08 EFLAGS: 0246 ORIG_RAX: 0009 Jun 10 21:47:41 stefano-linux kernel: RAX: ffda RBX: RCX: 7f3
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
max w beckett, What you are seeing is a completely different bug. Please file a separate one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880835/+subscri
[Kernel-packages] [Bug 1885423] Re: Attempt to upgrade to 20.04
** Package changed: linux (Ubuntu) => update-manager (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/1885423 Title: Attempt to upgrade to 20.04 Status in update-manager package in Ubuntu: Confirmed Bug description: The software updater keeps presenting the option to update to 20.04 and each time I attempt it fails. Continued to ensure that 19.10 is fully update but it still does not update. Also tried using terminal commands to update. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-61-generic 5.3.0-61.55 ProcVersionSignature: Ubuntu 5.3.0-61.55-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laptop 2946 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 14:44:22 2020 MachineType: Dell Inc. Latitude E4300 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-06-28 (0 days ago) dmi.bios.date: 09/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0D201R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd09/27/2011:svnDellInc.:pnLatitudeE4300:pvr:rvnDellInc.:rn0D201R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E4300 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1885423/+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 1880835] Re: pulse audio hangs in kernel call
csita, Please see if disabling Secureboot helps.Secureboot and Preboot DMA protection go hand in hand on Dell systems. This is an IOMMU bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpa
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I have an Intel (Ironlake) CoreI5 & Integrated Graphics I have no HDMI listed in Sound This is happening on: - Linux Mint - LMDE - Debian Buster - Debian Sid Everything is fine on: kernel 4.18.15-041815-generic x86_64 Sound server ALSA version: k4.18.15-041815-generic But anything later, even trying recent kernels does not fix this issue kernel 5.6.0-0.bpo.2-amd64 x86_64 Sound server ALSA version:k5.6.0-0.bpo.2-amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P 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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1884897] Re: touchpad not working (not in the lsit of my devices) I use a laptop chuwi
*** This bug is a duplicate of bug 1884288 *** https://bugs.launchpad.net/bugs/1884288 ** This bug has been marked a duplicate of bug 1884288 LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884897 Title: touchpad not working (not in the lsit of my devices) I use a laptop chuwi Status in linux package in Ubuntu: Incomplete Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0003 Vendor=0c45 Product=6366 Version=0100 N: Name="USB 2.0 Camera: USB Camera" P: Phys=usb-:00:15.0-7/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-7/1-7:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=046d Product=4008 Version=0111 N: Name="Logitech M185" P: Phys=usb-:00:15.0-6/input1:1 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-6/1-6:1.1/0003:046D:C52F.0002/0003:046D:4008.0003/input/input23 U: Uniq=4008-03-e8-c0-b4 H: Handlers=kbd mouse0 event14 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 0001 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1943 B: ABS=1 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.
[Kernel-packages] [Bug 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
Thx for sharing the updated and upstream link, Stefan! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
So now I can operate the PC and its great! Now I need to get the microphone working. @anton-azib wrote that it was possible using the sof subsystem in the kernel. @anton-azib, could you please elaborate on what that means and how I can configure it to get it working? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Status in Gentoo Linux: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I should add that under 4.18.15-041815, the command "aplay -l" returns **List of PLAYBACK Hardware Devices ** card 0: Intel [HDA Intel], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog] Subdevices: 1/1 Subdevices #0: subdevice #0 card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevices #0: subdevice #0 card 0: Intel [HDA Intel], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevices #0: subdevice #0 and under 5.6.0-0.bpo.2, the command "aplay -l" returns **List of PLAYBACK Hardware Devices ** card 0: Intel [HDA Intel], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog] Subdevices: 1/1 Subdevices #0: subdevice #0 that's 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/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P 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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
@Hui, thanks, I uploaded to the bionic SRU queue now One comment, the bottom entry of the changelog (the line with the name of the uploader) has an extra trailing space, in git and in the debdiff, which screws dpkg parsing utilities. Another of your changes this week has the problem, could you check if there something buggy on your side that leads to those problems? ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Critical => High ** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
** Changed in: ubuntu-z-systems Status: Incomplete => 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/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Done. Here's the file. PD: I was thinking the same when I read the "LSPCON" Intel's funcionality ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871721/+attachment/5391375/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver
[Kernel-packages] [Bug 1882088] Re: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations
** Changed in: linux (Ubuntu Groovy) Status: New => Triaged ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Frank Heimes (fheimes) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+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 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I had a look at my /proc/asound/card0 folder, and there are big differences between the non-working 5.6 kernel and the working 4.18 kernel. In Kernel 5.6, in the folder /proc/asound/card0 there are 2 only folders, and 3 files. Folders: pcm0c pcm0p Both folders refer to the analog, for example the info file in the second reads card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: 92HD81B1X5 Analog name: 92HD81B1X5 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 The three files are codec#0, codec#3, and id. (see the codec#3 attached) ** Attachment added: "codec#3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5391376/+files/codec%233 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P 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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1886827] Re: Machine hangs when doing a normal reboot
Currently on vacation - will be back in 3 weeks. Is the patch is for 5.8-rc4 or for 4.15.0-99? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 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 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+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 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
In kernel 4.18, there are 4 folders pcm0c pcm0p pcm3p pcm7p the info file in the last folder pcm7p, reads card: 0 device: 7 subdevice: 0 stream: PLAYBACK id: HDMI 1 name: HDMI 1 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 and there are 5 files now codec#0, codec#3, eld#3.0, eld#3.1 and id. (see the codec#3 attached) eld#3.0 just says monitor_present 0 eld_valid 0 Attached is the eld#3.1 file I tried copying the missing files/folders from the launch under 4.18 to the launch under 5.6 kernel but keep being told there is not enough room - which makes little sense, the files/folders are tiny, and I've plenty of space. ** Attachment added: "eld#3.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5391377/+files/eld%233.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P 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.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+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 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
I've installed https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/ and the problem seems to have been solved. My laptop is a HP-Pavilion- Laptop-15-cw1xxx, CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel: amdgpu_job_timedout+0x103/0x130 [amdgp
[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login
I tried with live usb from original iso and all is working as expected. uname -a Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux you can find dmesg took with live usb in attachment ** Attachment added: "dmesg_liveusb.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+attachment/5391378/+files/dmesg_liveusb.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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1386 F pulseaudio /dev/snd/controlC1: rom1 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Dell Precision M3800 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f3d704ff-25ed-45e9-903c-a94edcbb011c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal wayland-session Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/14/2019:svnDellInc.:pnDellPrecisionM3800:pvrA13:rvnDellInc.:rnDellPrecisionM3800:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886912] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1886912/+attachment/5391382/+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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1386 F pulseaudio /dev/snd/controlC1: rom1 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Dell Precision M3800 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f3d704ff-25ed-45e9-903c-a94edcbb011c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal wayland-session Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/14/2019:svnDellInc.:pnDellPrecisionM3800:pvrA13:rvnDellInc.:rnDellPrecisionM3800:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886912] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1886912/+attachment/5391388/+files/Lsusb-v.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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1386 F pulseaudio /dev/snd/controlC1: rom1 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Dell Precision M3800 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f3d704ff-25ed-45e9-903c-a94edcbb011c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal wayland-session Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/14/2019:svnDellInc.:pnDellPrecisionM3800:pvrA13:rvnDellInc.:rnDellPrecisionM3800:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886912] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1886912/+attachment/5391394/+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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1386 F pulseaudio /dev/snd/controlC1: rom1 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Dell Precision M3800 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f3d704ff-25ed-45e9-903c-a94edcbb011c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal wayland-session Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/14/2019:svnDellInc.:pnDellPrecisionM3800:pvrA13:rvnDellInc.:rnDellPrecisionM3800:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886912] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1886912/+attachment/5391389/+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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1386 F pulseaudio /dev/snd/controlC1: rom1 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Dell Precision M3800 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f3d704ff-25ed-45e9-903c-a94edcbb011c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal wayland-session Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/14/2019:svnDellInc.:pnDellPrecisionM3800:pvrA13:rvnDellInc.:rnDellPrecisionM3800:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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 1886912] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1886912/+attachment/5391386/+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/1886912 Title: DELL M3800 Touchscreen not working after login Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1386 F pulseaudio /dev/snd/controlC1: rom1 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Dell Precision M3800 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f3d704ff-25ed-45e9-903c-a94edcbb011c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal wayland-session Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/14/2019:svnDellInc.:pnDellPrecisionM3800:pvrA13:rvnDellInc.:rnDellPrecisionM3800:rvrA13:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886912/+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
