[Bug 1882093] Re: CVE-2020-{5963|5967} NVIDIA

2020-07-17 Thread Vic Liu
Tested 440.95-server on both bionic and focal, please find results and related 
log here:
https://docs.google.com/spreadsheets/d/1LTKLunx9yAMaP1nfvZXIhqs3pSNuhyupJfqA_DrS6eY/edit#gid=1557613599

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882093

Title:
  CVE-2020-{5963|5967} NVIDIA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1882093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers

2020-07-17 Thread Vic Liu
Tested 418.152-server and 440.95-server on both bionic and focal.
Please find results and related logs here: 
https://docs.google.com/spreadsheets/d/1LTKLunx9yAMaP1nfvZXIhqs3pSNuhyupJfqA_DrS6eY/edit#gid=1557613599

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881137

Title:
  Introduce the new NVIDIA 418-server and 440-server series, and update
  the current NVIDIA drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic

2020-07-14 Thread Vic Liu
GPU fallen off bus occurred on Dell Precision 5540 - NVIDIA Corporation
TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) while running SRU
test plan, here attached the apport log.

** Attachment added: "apport.xorg.ly_e_p31.apport"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+attachment/5392705/+files/apport.xorg.ly_e_p31.apport

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Bionic)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884060

Title:
  nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure
  with 5.4 kernels in Bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic

2020-07-14 Thread Vic Liu
Tested 435.21-0ubuntu0.18.04.3 on bionic with the following 3 nvidia cards on 
different platforms, GPU fallen off bus is observed during the testings.
Please find more details here: 
https://docs.google.com/spreadsheets/d/1LTKLunx9yAMaP1nfvZXIhqs3pSNuhyupJfqA_DrS6eY/edit#gid=566033014

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884060

Title:
  nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure
  with 5.4 kernels in Bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic

2020-07-14 Thread Vic Liu
Tested 435.21-0ubuntu0.18.04.3 on bionic with the following 3 nvidia
cards on different platforms, GPU fallen off bus is observed during the
testings.

Dell Inspiron 5583  NVIDIA Corporation GM108M [GeForce MX130] [10de:174d] 
(rev a2)
Dell Precision 5540 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] 
[10de:1fb9] (rev a1)
Dell G3 3590NVIDIA Corporation GP107M [GeForce GTX 1050 3 GB Max-Q] 
[10de:1c91] (rev a1)

Please find more details here:
https://docs.google.com/spreadsheets/d/1LTKLunx9yAMaP1nfvZXIhqs3pSNuhyupJfqA_DrS6eY/edit#gid=566033014

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884060

Title:
  nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure
  with 5.4 kernels in Bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic

2020-07-14 Thread Vic Liu
GPU fallen off bus occurred on Dell Precision 5540 - NVIDIA Corporation
TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) while running SRU
test plan, here attached the nvidia-bug-report.

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+attachment/5392704/+files/nvidia-bug-report.log.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884060

Title:
  nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure
  with 5.4 kernels in Bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879630] Re: No sound output from HDMI audio

2020-06-02 Thread Vic Liu
Thanks for the suggestion, I can have audio output from HDMI with the
following now by playing an audio clip instead of noise:

$ sudo amixer scontrols
$ sudo amixer set Master 100 unmute
$ sudo amixer set IEC958 100 unmute
$ sudo aplay -D plughw:0,7 /var/snap/alsa-utils/common/file_example_WAV_2MG.wav 
-v

** Changed in: snapd
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879630

Title:
  No sound output from HDMI audio

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879630] Re: No sound output from HDMI audio

2020-06-02 Thread Vic Liu
** Attachment added: "aplay-L.log"
   
https://bugs.launchpad.net/snapd/+bug/1879630/+attachment/5379677/+files/aplay-L.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879630

Title:
  No sound output from HDMI audio

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879630] Re: No sound output from HDMI audio

2020-06-02 Thread Vic Liu
** Attachment added: "aplay-l.log"
   
https://bugs.launchpad.net/snapd/+bug/1879630/+attachment/5379676/+files/aplay-l.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879630

Title:
  No sound output from HDMI audio

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879630] Re: No sound output from HDMI audio

2020-05-31 Thread Vic Liu
apport is not supported in uc20 (tried beta apport snap, not working),
please let me know what kind of log could help.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879630

Title:
  No sound output from HDMI audio

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878928] [NEW] Call trace occurred when running `netplan apply` after an yaml is removed

2020-05-15 Thread Vic Liu
Public bug reported:

Call trace occurred when running `netplan apply` after an yaml was
removed.

System: Intel NUC7CJYH
Image: Ubuntu Core 20 beta daily build (20200514.2)

Steps to Reproduce:
1. $ sudo rm /etc/netplan/n-wpa.yaml 
2. $ sudo netplan apply, then the following call trace occurred:

Warning: The unit file, source configuration file or drop-ins of 
netplan-wpa-wlo2.service changed on disk. Run 'systemctl daemon-reload' to 
reload units.
Failed to start netplan-wpa-wlo2.service: Unit netplan-wpa-wlo2.service not 
found.
Traceback (most recent call last):
  File "/usr/sbin/netplan", line 23, in 
netplan.main()
  File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
self.run_command()
  File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
self.func()
  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 46, in run
self.run_command()
  File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
self.func()
  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 173, in 
command_apply
utils.systemctl_networkd('start', sync=sync, extra_services=netplan_wpa)
  File "/usr/share/netplan/netplan/cli/utils.py", line 86, in systemctl_networkd
subprocess.check_call(command)
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['systemctl', 'start', '--no-block', 
'systemd-networkd.service', 'netplan-wpa-wlo2.service']' returned non-zero exit 
status 5.

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878928

Title:
  Call trace occurred when running `netplan apply` after an yaml is
  removed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1878928/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878926] Re: Call trace occurred after a wrong wireless interface mistakenly applied once in the yaml

2020-05-15 Thread Vic Liu
** Description changed:

  Call trace occurred every time when running `netplan apply` after a
- wireless interface was once described in the yaml.
+ wrong wireless interface was once described in the yaml.
  
  System: Intel NUC7PJYH
  Image: Ubuntu Core 20 beta daily build (20200514.2)
  
  Steps to Reproduce:
  1. On this Intel NUC7PJYH I tested, its wireless interface is wlo2 instead of 
wlan0, I mistakenly described the wireless interface as wlan0 in the yaml at 
the first time, corrected it to wlo2 as far as I found the wireless connection 
is unreachable.
  
  2. After the wireless interface was corrected to wlo2, following call
  trace happened every time running `netplan apply`:
  
- $ sudo netplan apply 
+ $ sudo netplan apply
  Failed to start netplan-wpa-wlan0.service: Unit netplan-wpa-wlan0.service not 
found.
  Traceback (most recent call last):
-   File "/usr/sbin/netplan", line 23, in 
- netplan.main()
-   File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
- self.run_command()
-   File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
- self.func()
-   File "/usr/share/netplan/netplan/cli/commands/apply.py", line 46, in run
- self.run_command()
-   File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
- self.func()
-   File "/usr/share/netplan/netplan/cli/commands/apply.py", line 173, in 
command_apply
- utils.systemctl_networkd('start', sync=sync, extra_services=netplan_wpa)
-   File "/usr/share/netplan/netplan/cli/utils.py", line 86, in 
systemctl_networkd
- subprocess.check_call(command)
-   File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
- raise CalledProcessError(retcode, cmd)
+   File "/usr/sbin/netplan", line 23, in 
+ netplan.main()
+   File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
+ self.run_command()
+   File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
+ self.func()
+   File "/usr/share/netplan/netplan/cli/commands/apply.py", line 46, in run
+ self.run_command()
+   File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
+ self.func()
+   File "/usr/share/netplan/netplan/cli/commands/apply.py", line 173, in 
command_apply
+ utils.systemctl_networkd('start', sync=sync, extra_services=netplan_wpa)
+   File "/usr/share/netplan/netplan/cli/utils.py", line 86, in 
systemctl_networkd
+ subprocess.check_call(command)
+   File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
+ raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['systemctl', 'start', '--no-block', 
'systemd-networkd.service', 'netplan-wpa-wlo2.service', 
'netplan-wpa-wlan0.service']' returned non-zero exit status 5.
  
  3. When a call trace happened, the wireless could still connect to the
  AP without problem. When system connected to the AP described in yaml,
  it still has the ability get an IP from it and ping the gateway on AP.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878926

Title:
  Call trace occurred after a wrong wireless interface mistakenly
  applied once in the yaml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1878926/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878926] [NEW] Call trace occurred after a wrong wireless interface mistakenly applied once in the yaml

2020-05-15 Thread Vic Liu
Public bug reported:

Call trace occurred every time when running `netplan apply` after a
wrong wireless interface was once described in the yaml.

System: Intel NUC7PJYH
Image: Ubuntu Core 20 beta daily build (20200514.2)

Steps to Reproduce:
1. On this Intel NUC7PJYH I tested, its wireless interface is wlo2 instead of 
wlan0, I mistakenly described the wireless interface as wlan0 in the yaml at 
the first time, corrected it to wlo2 as far as I found the wireless connection 
is unreachable.

2. After the wireless interface was corrected to wlo2, following call
trace happened every time running `netplan apply`:

$ sudo netplan apply
Failed to start netplan-wpa-wlan0.service: Unit netplan-wpa-wlan0.service not 
found.
Traceback (most recent call last):
  File "/usr/sbin/netplan", line 23, in 
netplan.main()
  File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
self.run_command()
  File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
self.func()
  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 46, in run
self.run_command()
  File "/usr/share/netplan/netplan/cli/utils.py", line 179, in run_command
self.func()
  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 173, in 
command_apply
utils.systemctl_networkd('start', sync=sync, extra_services=netplan_wpa)
  File "/usr/share/netplan/netplan/cli/utils.py", line 86, in systemctl_networkd
subprocess.check_call(command)
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['systemctl', 'start', '--no-block', 
'systemd-networkd.service', 'netplan-wpa-wlo2.service', 
'netplan-wpa-wlan0.service']' returned non-zero exit status 5.

3. When a call trace happened, the wireless could still connect to the
AP without problem. When system connected to the AP described in yaml,
it still has the ability get an IP from it and ping the gateway on AP.

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878926

Title:
  Call trace occurred after a wrong wireless interface mistakenly
  applied once in the yaml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1878926/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820768] Re: [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

2019-12-26 Thread Vic Liu
I verified following functions in fwupd 1.2.10 on Dell Latitude 5300:

`sudo fwupdmgr refresh`: Could connect to remote server and update metadata.
u@u-Latitude-5300:~$ sudo fwupdmgr refresh
[sudo] password for u: 
Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz
Downloading… [***]
Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

`sudo fwupdmgr get-devices`: Could show device firmware correctly.
u@u-Latitude-5300:~$ sudo fwupdmgr get-devices
Latitude 5300 System Firmware
  DeviceId: b03588a447340830af90b63cd5830a54455504fb
  Guid: 93634829-10b8-4098-a617-d52d056a4dd8
  Plugin:   uefi
  Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
  Version:  0.1.4.1
  VersionLowest:0.1.4.1
  VersionFormat:quad
  Icon: computer
  Created:  2019-12-27
  UpdateState:  success

PC401 NVMe SK hynix 512GB
  DeviceId: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f
  Guid: 2260c743-963b-566e-93f1-8223c3e6b87b <- 
NVME\VEN_1C5C_1527
  Guid: c28fdadd-607d-578c-b6ed-60ac49682904 <- PC401 NVMe SK 
hynix 512GB
  Serial:   MI88N047510608S6M
  Summary:  NVM Express Solid State Drive
  Plugin:   nvme
  Flags:internal|updatable|require-ac|registered|needs-reboot
  VendorId: NVME:0x1C5C
  Version:  80007E00
  VersionFormat:plain
  Icon: drive-harddisk
  Created:  2019-12-27

`sudo fwupdmgr get-updates`: Could get latest update of system firmware from 
remote server.
u@u-Latitude-5300:~$ sudo fwupdmgr get-updates
Latitude 5300 System Firmware has firmware updates:
Device ID:   b03588a447340830af90b63cd5830a54455504fb
GUID:93634829-10b8-4098-a617-d52d056a4dd8
ID:  com.dell.uefi93634829.firmware
Update Version:  0.1.5.0
Update Name: Latitude 5X00 System Update Update
Update Summary:  Firmware for the Dell Latitude 5X00
Update Remote ID:lvfs
Update Checksum: SHA1(51b9269d0dc93635610f86ce149a7103bc6e5b68)
Update Location: 
https://fwupd.org/downloads/ffbf931509f73fd26b410ff8358b51f3eaa20e7f-firmware.cab
Update Description:  Fixes and Enhancements:- Enhances the security of the 
system. Important - Once the BIOS is upgraded, you cannot downgrade BIOS EXE/ 
Recovery (RCV) to the versions before 1.2.0 due to restrictions.

`sudo fwupdmgr update`: Could update system firmware successfully from remote 
server.
u@u-Latitude-5300:~$ sudo fwupdmgr update
BIOS got updated successfully.

`sudo fwupdmgr install ffbf931509f73fd26b410ff8358b51f3eaa20e7f-firmware.cab`: 
Could update system firmware with local capsule file.
Though if update the same version of system firmware currently running on 
system, fwupdmgr would not block firmware update even without 
`--allow-reinstall` option.

u@u-Latitude-5300:~/Downloads$ sudo fwupdmgr install 
ffbf931509f73fd26b410ff8358b51f3eaa20e7f-firmware.cab 
Decompressing…   [***]
Authenticating…  [***]
Installing on Latitude 5300 System Firmware… ]
Scheduling…  [***]

An update requires a reboot to complete. Restart now? [Y|n]:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820768

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835001] Re: System does not auto detect disconnection of external monitor

2019-08-16 Thread Vic Liu
I can no longer reproduce this issue with kernel linux-oem-osp1 - 5.0.0-1018.20 
on a previously reproducible system with kernel 4.15.0-1042-oem.
I tried to reproduce 10 times, the reproduce rate is 0/10 with linux-oem-osp1 - 
5.0.0-1018.20.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835001

Title:
  System does not auto detect disconnection of external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835001] Re: System does not auto detect disconnection of external monitor

2019-08-16 Thread Vic Liu
Note to comment #16: I tried to reproduce 10 times, the reproduce rate
is 0/10 with linux-oem - 4.15.0-1050.57.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835001

Title:
  System does not auto detect disconnection of external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835001] Re: System does not auto detect disconnection of external monitor

2019-08-16 Thread Vic Liu
I can no longer reproduce this issue with kernel linux-oem -
4.15.0-1050.57 on a previously reproducible system with kernel
4.15.0-1042-oem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835001

Title:
  System does not auto detect disconnection of external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

2019-03-25 Thread Vic Liu
** Description changed:

  To simplify reproduce steps, one only has to:
  1. install (tested so far) Ubuntu Bionic
  2. switch to other tty by pressing Ctrl+Alt+Fn
  3. login and logout
  Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.
  
  Some more findings:
  
  1. So far we know all other newer Ubuntu versions are immune, e.g.
  Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).
  
  2. login _and_ logout from another virtual console is required.
  Switching between text console and GUI back and forth before logging out
  doesn't trigger this bug. So this might(?) also involves systemd-logind
  as well;
  
  3. while gdm locked up, kernel and the rest of the system are actually
  still alive. Networking is still available, and even the input devices
  are still functioning well. Only gdm fails to grab the device inputs.
  
  4. when gdm locks up due to either resume from suspend or vt-switch,
  restart gdm (from remote ssh) will bring the system back.
  
  ### Disco
  | |4.15|4.18|4.19|5.0
  |---||||---
  |nouveau| | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410|Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  
   Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
-* 5.0.0-7-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
+    * 5.0.0-7-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 240-6ubuntu1
+    * 240-6ubuntu1
  * gdm3:
-* 3.31.4+git20190225-1ubuntu1
+    * 3.31.4+git20190225-1ubuntu1
   Hardware
  * 201811-26623
  
  Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
  all kernel versions tested. In contrary, nVIDIA driver fails every case.
  
-  ### Cosmic
+  ### Cosmic
  | |4.15|4.18|4.19|5.0
  |-||||---
  |nouveau | | | |
  |nvidia-390 bionic|Affected|Affected|Affected|Affected
  |nvidia-390 cosmic|Affected|Affected|Affected|Affected
  |nvidia-410 |Affected|Affected|Affected|Affected
  Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
   Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
-* 5.0.0-7-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
+    * 5.0.0-7-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 239-7ubuntu10
+    * 239-7ubuntu10
  * gdm3:
-* 3.30.1-1ubuntu5
+    * 3.30.1-1ubuntu5
   Hardware
  * 201811-26623
  
  Summary: in Ubuntu Cosmic, same with Disco.
  
  # Bionic
  | |4.15|4.18 |4.19
  |-|||
  |nouveau|Affected[1]| |Affected[1]
  |hwe xorg|Affected[1]| |Affected[1]
  |nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
  |nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
  |nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
  |nvidia-410 |Affected[2]|Affected[1]|Affected[3]
  [1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
  [2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
  [3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
  ## Packages:
  * kernel:
-* 4.15.0-46-generic
-* 4.18.0-16-generic
-* 4.19.0-13-generic
+    * 4.15.0-46-generic
+    * 4.18.0-16-generic
+    * 4.19.0-13-generic
  * nvidia-driver:
-* 390.116-0ubuntu0.18.04.1
-* 390.116-0ubuntu0.18.10.1
-* 410.104-0ubuntu1
+    * 390.116-0ubuntu0.18.04.1
+    * 390.116-0ubuntu0.18.10.1
+    * 410.104-0ubuntu1
  * systemd:
-* 237-3ubuntu10.12
+    * 237-3ubuntu10.12
  * gdm3:
-* 3.28.3-0ubuntu18.04.3
+    * 3.28.3-0ubuntu18.04.3
  ## Hardware
  * 201811-26623
  
  Summary: only 4.18 kernel with nouveau driver is immune from this issue,
  which follows some changes in user land should be necessary to stabilize
  all the (nouveau) cases. But even with that, from previous results of
  Cosmic/Disco, there should still some works to be done in the nvidia
  driver.
+ 
+ OEM-tag: LP: #1804607

-- 
You received this bug notification because you are a 

[Bug 1821194] [NEW] Screen frozen after switch to other tty and do login & logout

2019-03-21 Thread Vic Liu
Public bug reported:

To simplify reproduce steps, one only has to:
1. install (tested so far) Ubuntu Bionic
2. switch to other tty by pressing Ctrl+Alt+Fn
3. login and logout
Then it should try to switch back to GDM (no matter you have logged in GUI or 
not), triggers vt-switch bug and lock up.

Some more findings:

1. So far we know all other newer Ubuntu versions are immune, e.g.
Ubuntu Cosmic's gdm(version 3.30.1-1ubuntu5).

2. login _and_ logout from another virtual console is required.
Switching between text console and GUI back and forth before logging out
doesn't trigger this bug. So this might(?) also involves systemd-logind
as well;

3. while gdm locked up, kernel and the rest of the system are actually
still alive. Networking is still available, and even the input devices
are still functioning well. Only gdm fails to grab the device inputs.

4. when gdm locks up due to either resume from suspend or vt-switch,
restart gdm (from remote ssh) will bring the system back.

### Disco
| |4.15|4.18|4.19|5.0
|---||||---
|nouveau| | | |
|nvidia-390 bionic|Affected|Affected|Affected|Affected
|nvidia-390 cosmic|Affected|Affected|Affected|Affected
|nvidia-410|Affected|Affected|Affected|Affected
Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.

 Packages:
* kernel:
   * 4.15.0-46-generic
   * 4.18.0-16-generic
   * 4.19.0-13-generic
   * 5.0.0-7-generic
* nvidia-driver:
   * 390.116-0ubuntu0.18.04.1
   * 390.116-0ubuntu0.18.10.1
   * 410.104-0ubuntu1
* systemd:
   * 240-6ubuntu1
* gdm3:
   * 3.31.4+git20190225-1ubuntu1
 Hardware
* 201811-26623

Summary: in Ubuntu Disco, nouveau driver is immune from this issue in
all kernel versions tested. In contrary, nVIDIA driver fails every case.

 ### Cosmic
| |4.15|4.18|4.19|5.0
|-||||---
|nouveau | | | |
|nvidia-390 bionic|Affected|Affected|Affected|Affected
|nvidia-390 cosmic|Affected|Affected|Affected|Affected
|nvidia-410 |Affected|Affected|Affected|Affected
Affected: only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
 Packages:
* kernel:
   * 4.15.0-46-generic
   * 4.18.0-16-generic
   * 4.19.0-13-generic
   * 5.0.0-7-generic
* nvidia-driver:
   * 390.116-0ubuntu0.18.04.1
   * 390.116-0ubuntu0.18.10.1
   * 410.104-0ubuntu1
* systemd:
   * 239-7ubuntu10
* gdm3:
   * 3.30.1-1ubuntu5
 Hardware
* 201811-26623

Summary: in Ubuntu Cosmic, same with Disco.

# Bionic
| |4.15|4.18 |4.19
|-|||
|nouveau|Affected[1]| |Affected[1]
|hwe xorg|Affected[1]| |Affected[1]
|nvidia-390 bionic+hwe xorg|Affected[1]|Affected[1]|Affected[1]
|nvidia-390 bionic|Affected[2]|Affected[1]|Affected[1]
|nvidia-390 cosmic|Affected[1]|Affected[1]|Affected[1]
|nvidia-410 |Affected[2]|Affected[1]|Affected[3]
[1]: no vt-switch inside gnome-shell. Press Ctrl+Alt+Fn in gdm instead. Only 
gdm(vt-1) fails to grab further input. Use `chvt` to switch to other vt in a 
remote shell.
[2]: vt-switch inside gnome-shell causes lockup. Cannot switch to vt in gdm 
(but no system lockup). Only gdm(vt-1) fails to grab further input. Use `chvt` 
to switch to other vt in a remote shell.
[3]: vt-switch inside gnome-shell causes lockup. Press Ctrl+Alt+Fn in gdm 
instead. Only gdm(vt-1) fails to grab further input. Use `chvt` to switch to 
other vt in a remote shell.
## Packages:
* kernel:
   * 4.15.0-46-generic
   * 4.18.0-16-generic
   * 4.19.0-13-generic
* nvidia-driver:
   * 390.116-0ubuntu0.18.04.1
   * 390.116-0ubuntu0.18.10.1
   * 410.104-0ubuntu1
* systemd:
   * 237-3ubuntu10.12
* gdm3:
   * 3.28.3-0ubuntu18.04.3
## Hardware
* 201811-26623

Summary: only 4.18 kernel with nouveau driver is immune from this issue,
which follows some changes in user land should be necessary to stabilize
all the (nouveau) cases. But even with that, from previous results of
Cosmic/Disco, there should still some works to be done in the nvidia
driver.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821194

Title:
  Screen frozen after switch to other tty  and do login & logout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs