[Kernel-packages] [Bug 1882273] Re: ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo IdeaPad S145' after installing Ubuntu 20

2020-06-28 Thread Kai-Heng Feng
[0.945276] pci :00:15.0: BAR 0: no space for [mem size 0x1000 64bit]
[0.945278] pci :00:15.0: BAR 0: failed to assign [mem size 0x1000 
64bit]
[0.945283] pci :00:15.1: BAR 0: no space for [mem size 0x1000 64bit]
[0.945285] pci :00:15.1: BAR 0: failed to assign [mem size 0x1000 
64bit]
[0.945288] pci :00:1f.5: BAR 0: no space for [mem size 0x1000]
[0.945290] pci :00:1f.5: BAR 0: trying firmware assignment [mem 
0xfe01-0xfe010fff]
[0.945293] pci :00:1f.5: BAR 0: [mem 0xfe01-0xfe010fff] conflicts 
with Reserved [mem 0xfc80-0xfe7f]
[0.945295] pci :00:1f.5: BAR 0: failed to assign [mem size 0x1000]

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882273

Title:
  ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo IdeaPad
  S145' after installing Ubuntu 20

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/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=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  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/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=04b3 Product=310b Version=0100
  N: Name="HID 04b3:310b"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04B3:310B.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b624 Version=1428
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  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/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  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:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  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:1f.3/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=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/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=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/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=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event13 
  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:1f.3/sound/card0/input14
  U: Uniq=
  H: Handlers=event14 
  B: 

[Kernel-packages] [Bug 1882273] Re: ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo IdeaPad S145' after installing Ubuntu 20

2020-06-28 Thread Kai-Heng Feng
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/

** 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/1882273

Title:
  ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo IdeaPad
  S145' after installing Ubuntu 20

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/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=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  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/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=04b3 Product=310b Version=0100
  N: Name="HID 04b3:310b"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04B3:310B.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Ideapad extra buttons"
  P: Phys=ideapad/input0
  S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=13
  B: KEY=81000800100c03 4430 0 2
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b624 Version=1428
  N: Name="Integrated Camera: Integrated C"
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  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/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event8 
  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:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  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:1f.3/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=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/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=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/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=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
  U: Uniq=
  H: Handlers=event13 
  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:1f.3/sound/card0/input14
  U: Uniq=
  H: Handlers=event14 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=11"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15
  U: Uniq=
  H: Handlers=event15 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=12"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16
  U: Uniq=
  H: Handlers=event16 
  B: PROP=0
  B: EV=21
  B: SW=140

  ProblemType: Bug
  

[Kernel-packages] [Bug 1885363] Re: Screen flickers after waking up from suspend

2020-06-28 Thread Daniel van Vugt
** Tags added: amdgpu

** Summary changed:

- Screen flickers after waking up from suspend
+ [amdgpu] Screen flickers after waking up from suspend

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885363

Title:
  [amdgpu] Screen flickers after waking up from suspend

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. 
Everything seems fine when running the system normally, however whenever I 
suspend the machine and then wake it back up, severe problems occur.
  The first time, the machine froze completely. Switching to a different TTY 
didn't work anymore and the keyboard LEDs didn't respond to caps and num lock 
anymore, so I had to force shutdown. The second time, it came back OK but the 
screen has been flickering heavily since. Restarting Gnome and unplugging and 
plugging monitors back in hasn't helped.

  Relevant specs:
  CPU: AMD® Ryzen 9 3900x 12-core processor × 24 
  GPU: AMD® Radeon rx 5600 xt (MSI RADEON RX 5600 XT MECH OC)
  Monitors: 1x Acer running at 3840x2160 60Hz, 2x Medion (showing up as 
"Messeltronik Dresden GmbH") both running at 1920x1080 60Hz.
  Gnome: 3.36.2
  X11
  Apt doesn't report any updates.

  The flickering is most pronounced on the Acer. On the Medions, it
  seems to only happen when something changes on the screen. I have
  tried to capture this on video: https://youtu.be/HWT1J76-x94

  
  This bug seem quite similar to this one 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588). I can also stop 
the flickering by switching the Acer to 1080p but when switching back to 4k, 
the problem reappears.

  I hope that ubuntu-bug has included all the necessary details. Let me
  know if you need anything else.

  Thank you very much for your help!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Jun 27 10:44:32 2020
  DistUpgraded: 2020-04-30 20:17:33,403 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-37-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 
5600 OEM/5600 XT / 5700/5700 XT] [1462:381e]
  InstallationDate: Installed on 2019-03-26 (458 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-30 (57 days ago)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: X570 Extreme4
  dmi.board.vendor: ASRock
  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.:bvrP2.60:bd04/08/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Extreme4:rvr: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.sku: 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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1864930] Re: brightness setting and sleep/suspend (echo mem > /sys/power/state) , s2ram and s2disk fail for 5.4.0 and s2disk fail for 5.4.22

2020-06-28 Thread Kai-Heng Feng
What's the output of `cat /sys/power/mem_sleep`?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1864930

Title:
  brightness setting  and sleep/suspend (echo mem > /sys/power/state) ,
  s2ram and s2disk fail for 5.4.0 and s2disk fail for 5.4.22

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) After resuming from suspend (uswsusp/s2ram) and/or after resuming
  from "echo mem > /sys/power/state" there is a black screen on laptop
  after resume with 5.4.0-14-generic kernel only.  Kernel seems to be
  working as CTRL+ALT+F2 and CTRL+ALT+DEL restarts laptop.

   A) 3 Different combinations of this distro with other kernels work
  well:

kubunut20.04  + linux-image-5.3.0-40-generic 
 (copied  from kubuntu 19.10 from /lib/modules/5.3.0-40-generic and 
/boot/vmlinuz-5.3.0-40-generic)

  Installed from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc3/

kubuntu20.04  + linux-image-unsigned-5.5.6-050506-generic  is working.
kubuntu20.04  + linux-image-unsigned-5.6.0-050600rc3-generic  is working.  
  
B) This kernel 5.4.0-14-generic when copied manually into kubuntu 19.10 
behaves the same as in  20.04 (NOT WORKING for suspend to ram)
   
  2) setting brightness with keys on laptop keyboard does not work for this 
kernel 5.4.0-14-generic only  
  Neither using this command line method
  marian@kubuntu2004:~/Downloads$ cat 
/sys/class/backlight/intel_backlight/max_brightness
  255
  marian@kubuntu2004:~/Downloads$ cat 
/sys/class/backlight/intel_backlight/max_brightness
  255
  marian@kubuntu2004:~/Downloads$ cat 
/sys/class/backlight/intel_backlight/actual_brightness
  255
  marian@kubuntu2004:~/Downloads$ cat 
/sys/class/backlight/intel_backlight/brightness
  242
  marian@kubuntu2004:~/Downloads$ echo 200 | sudo tee 
/sys/class/backlight/intel_backlight/brightness
  200
  marian@kubuntu2004:~/Downloads$ cat 
/sys/class/backlight/intel_backlight/brightness
  Again kernel 5.3 copied into kubuntu20.04 got working brigthness keys.

  However this works for all tested kernels above (including 5.4.0-14-generic) 
  xrandr --output eDP-1 --brightness 0.8

  3) after uswsusp/hibernate (s2disk) and  "echo disk > /sys/power/state" do 
not seem to resume/thaw  
  for those kernels: linux-image-5.4.0-14-generic, 
linux-image-unsigned-5.5.6-050506-generic , 
linux-image-unsigned-5.6.0-050600rc3-generic, on the other hand kernel 
linux-image-5.3.0-40-generic manually copied from kubuntu 19.10 into kubuntu 
20.04 seems to be working fine when thawing/resuming from hibernation.

Again I tested different combination of kernels and distros for this issue.
This kernel (5.4.0-14-generic) also does not work for hibernate/resume even 
when copied from kubuntu20.04  into kubuntu19.10

  
  4) 
  Starting kubuntu without installation from daily build from 25th Feb 2020 
shows the same problem for brightness setting and for black screen after 
resuming from sleep.

  http://cdimage.ubuntu.com/kubuntu/daily-live/current/

  Note I always recreated imagerd in target place when copied kernels manually:
  update-initramfs -u -k 5.3.0-40-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1214 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Feb 26 22:20:29 2020
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision FHD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=/dev/mapper/sysvg-ub2004deboot ro resume=/dev/nvme0n1p8 quiet splash 
resume=/dev/nvme0n1p8 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1865346] Re: Changing backlight no longer works with Linux 5.4

2020-06-28 Thread Kai-Heng Feng
Please boot with kernel parameter "drm.debug=0xe log_buf_len=16M" and
attach dmesg here.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865346

Title:
  Changing backlight no longer works with Linux 5.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As of upgrading to Ubuntu 20.04 (and with it Linux 5.4), adjusting
  brightness no longer works. `/sys/class/backlight/intel_backlight/`
  exists, but writing to
  `/sys/class/backlight/intel_backlight/brightness` doesn't have any
  effect. If I boot into Linux 5.3 instead, changing brightness works
  again. Complete dmesg output is attached, but I don't see anything
  interesting in it.

  My hardware is a Dell Inc. XPS 15 9575, with an Intel Core i7-8705G.

  More info:

  `lsb_release -rd`:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  `apt-cache policy linux-generic`:
  linux-generic:
Installed: 5.4.0.14.17
Candidate: 5.4.0.14.17
Version table:
   *** 5.4.0.14.17 500
  500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865346/+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 1881638] Re: touchpad not appearing in list of hardware devices

2020-06-28 Thread Kai-Heng Feng
Does the touchpad work at all?

** 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/1881638

Title:
  touchpad not appearing in list of hardware devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  touchpad has been frozen for ~1 hour. Doesn't appear when checking
  xinput --list or other lists of hardware connected to the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prachi 1669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  1 11:06:06 2020
  InstallationDate: Installed on 2020-05-18 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 15 7590
  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-33-generic 
root=UUID=3a384bca-9677-48c8-bd86-3395fc0e3565 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881638/+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 1881676] Re: HyperX Cloud Alpha microphone not detected

2020-06-28 Thread Kai-Heng Feng
The patch should be included via later stable updates.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881676

Title:
  HyperX Cloud Alpha microphone not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using the HyperX AMP, the microphone is not detected. This is a
  known issue with the mainline kernel, however was patched in release
  5.7.0. This occurs on Ubuntu 20.04 LTS.

  https://lkml.org/lkml/2020/4/4/197

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Jun  1 18:50:04 2020
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InstallationDate: Installed on 2020-05-23 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881676/+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 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep

2020-06-28 Thread Kai-Heng Feng
Please reproduce the issue and re-attach the logs.
Not seeing any suspend attempt in dmesg.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855628

Title:
  Ubuntu keeps having resolution issues and disconnects from the network
  after I wake it up from sleep

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Whenever I wake the computer up from sleep, the computer no longer
  connects to the Internet without my having to go into Settings and
  turn Wi-Fi off and then back on again.

  Please address this issue.

  Thank you!

  network-manager:
Installed: 1.10.6-2ubuntu1.2
Candidate: 1.10.6-2ubuntu1.2
Version table:
   *** 1.10.6-2ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.10.6-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 19:51:31 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  wifi  
1575852612  Sun 08 Dec 2019 07:50:12 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  28634e82-4c1c-3a61-b152-3bd92aaa6992  ethernet  
1575852610  Sun 08 Dec 2019 07:50:10 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp4s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1560 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0bda:0129 Realtek 

[Kernel-packages] [Bug 1881699] Re: No analog output

2020-06-28 Thread Kai-Heng Feng
I wonder if it's using SoundWire?

Can you please boot mainline kernel without "snd-intel-
dspcfg.dsp_driver=1"?

** 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/1881699

Title:
  No analog output

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a fresh boot and login, there is no analog output. Only HDMI and 
bluetooth are available.
  It becomes available when I kill pulseaudio with 'pulseaudio -k' but the 
sound indicator only shows 'dummy' output and I cannot control the output from 
the sound settings or the sound indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu3
  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.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-lallement  184080 F pulseaudio
   /dev/snd/controlC1:  j-lallement  184080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 06:32:09 2020
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  j-lallement   3669 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1
  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:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+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 1875099] Re: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530

2020-06-28 Thread Kai-Heng Feng
Does cold boot help?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875099

Title:
  RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on
  Lenovo Legion Y530

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading Ubuntu Mate  to 20.04 , my wifi crashed on Lenovo legion 
Y530. The strange thing is that it connects to the network, i have internet for 
some time (usually between 1 and 10 minutes) and then it disconnects.
  After that, the applet shows me something like device not ready and i can 
only restart the computer to connect. Then it crashes again... 
  I also tried a fresh install with the same results.
  I used 19.04 and 19.10 on the same laptop as my primary operating system and 
wifi worked flawlessly.

  Since I do my work on this laptop i was forced to downgrade back to 19.10 for 
now.
  This is my lshw -C network (from 19.10 If I remember correctly it was 
RTL8822BE also in 20.04)
*-network 
 description: Wireless interface
 product: RTL8822BE 802.11a/b/g/n/ac WiFi adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:07:00.0
 logical name: wlp7s0
 version: 00
 serial: dc:a2:66:80:7d:7d
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=rtw_pci 
driverversion=5.3.0-46-generic firmware=N/A ip=192.168.0.146 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11
 resources: irq:141 ioport:4000(size=256) memory:a430-a430
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:08:00.0
 logical name: enp8s0
 version: 15
 serial: 8c:16:45:e9:e9:a8
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII
 resources: irq:17 ioport:3000(size=256) memory:a4204000-a4204fff 
memory:a420-a4203fff

  and my lspci -nnk | grep -A2 0280

  07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter [10ec:b822]
Subsystem: Lenovo RTL8822BE 802.11a/b/g/n/ac WiFi adapter [17aa:b023]
Kernel driver in use: rtw_pci

  If you think it is necessary, I can try to install 20.04 on an external hard 
drive and give you some more info from there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  campus 1207 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-09 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: LENOVO 81FV
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=2ba3f662-50a5-4db8-a5e1-ddaf5e09d5a9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-29-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: 07/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8JCN43WW
  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: Lenovo Legion Y530-15ICH
  dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
  dmi.product.family: Legion Y530-15ICH
  dmi.product.name: 81FV
  dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
  dmi.product.version: Lenovo Legion Y530-15ICH
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1875099/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

2020-06-28 Thread Aaron Lichtman
I have the same problem on Ubuntu 20.10 using 440.100 driver. VLC +
Thunar on a single user system fills up the syslog.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1846374

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1885491] [NEW] firefor crashes ubuntu command terminal crashes

2020-06-28 Thread Sangam Giri
Public bug reported:

this is the ubuntu 20.04
i am using ubuntu as i faced blue screen in windows.After installing ubuntu i 
am not facing blue screen but some kind of crashes happen here too ...whatever 
the task i am performing it crashes automatically but now it is ok but can't 
say when it will crash again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: crash (not installed)
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 29 10:03:56 2020
InstallationDate: Installed on 2020-06-28 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: crash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1885491

Title:
  firefor crashes ubuntu command terminal crashes

Status in crash package in Ubuntu:
  New

Bug description:
  this is the ubuntu 20.04
  i am using ubuntu as i faced blue screen in windows.After installing ubuntu i 
am not facing blue screen but some kind of crashes happen here too ...whatever 
the task i am performing it crashes automatically but now it is ok but can't 
say when it will crash again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: crash (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 10:03:56 2020
  InstallationDate: Installed on 2020-06-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: crash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1885491/+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 1690085]

2020-06-28 Thread ashesh.ambasta
I’ll try that, but I doubt if at this stage it will have any effect.

Best,

Ashesh Ambasta

> On 27 Jun 2020, at 22:31, bugzilla-dae...@bugzilla.kernel.org wrote:
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
> 
> --- Comment #693 from Arup (arup.chowdh...@gmail.com) ---
> Before you discard the CPU if your BIOS has PBO option turn it off, with
> latest
> BIOS on my B350 motherboard version 5406 PBO is on by default and apart from
> causing high temperature it would lead to this kind of crashes and reboots
> with
> my Ryzen7. Turning off PBO fixed it and now I am running a Ryzen9 with the
> same
> board and all works fine with PBO off.
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the 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/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Expired
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 

[Kernel-packages] [Bug 1690085]

2020-06-28 Thread ashesh.ambasta
Moreover, from a bit of reading I see that PBO is related to how fast
the processor clock speeds are boosted. How is this related to crashes
when idle?

Best,

Ashesh Ambasta

> On 28 Jun 2020, at 07:23, Ashesh Ambasta  wrote:
> 
> I’ll try that, but I doubt if at this stage it will have any effect. 
> 
> Best,
> 
> Ashesh Ambasta 
> 
>> On 27 Jun 2020, at 22:31, bugzilla-dae...@bugzilla.kernel.org wrote:
>> 
>> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>> 
>> --- Comment #693 from Arup (arup.chowdh...@gmail.com) ---
>> Before you discard the CPU if your BIOS has PBO option turn it off, with
>> latest
>> BIOS on my B350 motherboard version 5406 PBO is on by default and apart from
>> causing high temperature it would lead to this kind of crashes and reboots
>> with
>> my Ryzen7. Turning off PBO fixed it and now I am running a Ryzen9 with the
>> same
>> board and all works fine with PBO off.
>> 
>> -- 
>> You are receiving this mail because:
>> You are on the CC list for the 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/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Expired
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've 

[Kernel-packages] [Bug 1715577] Re: linux-aws package lacks zram.ko, but builds it.

2020-06-28 Thread Launchpad Bug Tracker
[Expired for linux-aws (Ubuntu) because there has been no activity for
60 days.]

** Changed in: linux-aws (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1715577

Title:
  linux-aws package lacks zram.ko, but builds it.

Status in linux-aws package in Ubuntu:
  Expired

Bug description:
  The linux-aws package lacks zram.ko module, but according to delivered
  /boot/config-*-aws, the zram is built. Would it be possible to add the
  zram module into linux-aws package in Ubuntu 16.04 just like linux-
  image-lowlatency have? (Or via linux-image-extra packages, like other
  variants have)

  I've checked linux-aws-4.4.0.1032.34 and no module is present there,
  the 'apt-file search zram.ko' did not yield any of the 'aws' packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1715577/+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 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.

2020-06-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875189

Title:
  [amdgpu] Screen Flickers when it wakes from suspend/sleep.

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Expired

Bug description:
  I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 (
  Raven Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh
  rate of 120Hz.

  Whenever I shut the laptop lid or it auto-suspends it catches screen
  flickers when it wakes up.

  I think it's some kernel issue some deadlock maybe.

  I already filed a bug on fedora bugzilla forum for the same aswell.

  Here is the link for the same :

  https://bugzilla.redhat.com/show_bug.cgi?id=1748042

  I hope it gets' fixed this time :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 20:33:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
  ProcKernelCmdLine: audit=0  
BOOT_IMAGE=/@/boot/vmlinuz-5.6.0-7.1-liquorix-amd64 
root=UUID=c6a5aea4-fe87-480e-9b59-d3b0077d5842 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DT.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DT_FX505DT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875189/+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 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.

2020-06-28 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875189

Title:
  [amdgpu] Screen Flickers when it wakes from suspend/sleep.

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Expired

Bug description:
  I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 (
  Raven Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh
  rate of 120Hz.

  Whenever I shut the laptop lid or it auto-suspends it catches screen
  flickers when it wakes up.

  I think it's some kernel issue some deadlock maybe.

  I already filed a bug on fedora bugzilla forum for the same aswell.

  Here is the link for the same :

  https://bugzilla.redhat.com/show_bug.cgi?id=1748042

  I hope it gets' fixed this time :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 20:33:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
  ProcKernelCmdLine: audit=0  
BOOT_IMAGE=/@/boot/vmlinuz-5.6.0-7.1-liquorix-amd64 
root=UUID=c6a5aea4-fe87-480e-9b59-d3b0077d5842 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DT.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DT_FX505DT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875189/+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 1875189] Re: [amdgpu] Screen Flickers when it wakes from suspend/sleep.

2020-06-28 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875189

Title:
  [amdgpu] Screen Flickers when it wakes from suspend/sleep.

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Expired

Bug description:
  I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 (
  Raven Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh
  rate of 120Hz.

  Whenever I shut the laptop lid or it auto-suspends it catches screen
  flickers when it wakes up.

  I think it's some kernel issue some deadlock maybe.

  I already filed a bug on fedora bugzilla forum for the same aswell.

  Here is the link for the same :

  https://bugzilla.redhat.com/show_bug.cgi?id=1748042

  I hope it gets' fixed this time :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 20:33:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
  ProcKernelCmdLine: audit=0  
BOOT_IMAGE=/@/boot/vmlinuz-5.6.0-7.1-liquorix-amd64 
root=UUID=c6a5aea4-fe87-480e-9b59-d3b0077d5842 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DT.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: TUF Gaming FX505DT_FX505DT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875189/+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 1875921] Re: Intel Centrino Advanced-N 6235 [8086:088e] Subsystem [8086:4060] WiFi doesnt connect when I come back from sleep mode

2020-06-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875921

Title:
  Intel Centrino Advanced-N 6235 [8086:088e] Subsystem [8086:4060] WiFi
  doesnt connect when I come back from sleep mode

Status in linux package in Ubuntu:
  Expired

Bug description:
  It tries to connect when I come back from sleep mode but isn't able to
  connect. I always need to restart laptop to start using it again.

  Also while using google chrome on pressing chrome button the alignment
  of screens in mini view is towards left and has too much extra space
  on write and it doesn't gets resize according to the view of the
  screen instead gets stretched making it unable to identify.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinayak1953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 20:48:10 2020
  InstallationDate: Installed on 2018-12-15 (501 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=23b1456b-56d2-43ad-8ddb-4743100e6d3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (3 days ago)
  dmi.bios.date: 07/27/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.72
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.19
  dmi.chassis.asset.tag: CNU408BGZM
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.72:bd07/27/2018:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.sku: D5Y13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875921/+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 1885334] Re: Nvidia kernel crashes when running World of Warcrat with wine/vulkan

2020-06-28 Thread Daniel van Vugt
** Summary changed:

- Crashes when running World of Warcrat with wine/vulkan
+ Nvidia kernel crashes when running World of Warcrat with wine/vulkan

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440
(Ubuntu)

-- 
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/1885334

Title:
  Nvidia kernel crashes when running World of Warcrat with wine/vulkan

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  while version 440.82-0ubuntu0~0.18.04.2 ran with out any problems
  440.100-0ubuntu0.18.04.1 crashes after a while with the following
  errors:

  Jun 26 22:41:31 imobil2 kernel: [ 1548.518774] NVRM: GPU at PCI::01:00: 
GPU-059d1eda-0ee6-ba17-38a2-5e6330b325f1
  Jun 26 22:41:31 imobil2 kernel: [ 1548.518779] NVRM: Xid (PCI::01:00): 
31, pid=1108, Ch 0012, intr 1000. MMU Fault: ENGINE GRAPHICS 
GPCCLIENT_PROP_0 faulted @ 0x1_12844000. Fault is of type 
FAULT_INFO_TYPE_UNSUPPORTED_KIND ACCESS_TYPE_WRITE
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747689] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 1 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747698] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 2 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747704] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 3 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747708] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 5 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747713] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 9 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747718] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 10 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747723] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 18 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747728] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: Shader Program Header 19 Error
  Jun 26 22:47:32 imobil2 kernel: [ 1909.747735] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: ESR 0x405840=0x8e0c062e
  Jun 26 22:47:32 imobil2 kernel: [ 1909.748005] NVRM: Xid (PCI::01:00): 
13, pid=1265, Graphics Exception: ChID 0008, Class a097, Offset 1614, 
Data 
  Jun 26 22:47:33 imobil2 kernel: [ 1910.876226] NVRM: Xid (PCI::01:00): 
62, pid=1265, 0110(25dc) 840008ce c415c455

  This happend multiple times. Unfortunately the old driver version is
  not available anymore and I can't check if this is really caused by
  the driver update.

  Best regards,
  Matthias

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.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:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Fri Jun 26 22:59:14 2020
  DistUpgraded: 2020-04-09 19:50:27,912 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 4.15.0-106-generic, x86_64: installed
   nvidia, 440.100, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 
770] [1462:2825]
  InstallationDate: Installed on 2013-12-15 (2384 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: MSI MS-7821
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=10f3ba43-ad16-4df4-b3b4-e86b64e9f96e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-04-09 (78 days ago)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-G45 GAMING (MS-7821)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Kernel-packages] [Bug 1885334] [NEW] Nvidia kernel crashes when running World of Warcrat with wine/vulkan

2020-06-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi,

while version 440.82-0ubuntu0~0.18.04.2 ran with out any problems
440.100-0ubuntu0.18.04.1 crashes after a while with the following
errors:

Jun 26 22:41:31 imobil2 kernel: [ 1548.518774] NVRM: GPU at PCI::01:00: 
GPU-059d1eda-0ee6-ba17-38a2-5e6330b325f1
Jun 26 22:41:31 imobil2 kernel: [ 1548.518779] NVRM: Xid (PCI::01:00): 31, 
pid=1108, Ch 0012, intr 1000. MMU Fault: ENGINE GRAPHICS 
GPCCLIENT_PROP_0 faulted @ 0x1_12844000. Fault is of type 
FAULT_INFO_TYPE_UNSUPPORTED_KIND ACCESS_TYPE_WRITE
Jun 26 22:47:32 imobil2 kernel: [ 1909.747689] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 1 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747698] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 2 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747704] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 3 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747708] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 5 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747713] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 9 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747718] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 10 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747723] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 18 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747728] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: Shader Program Header 19 Error
Jun 26 22:47:32 imobil2 kernel: [ 1909.747735] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: ESR 0x405840=0x8e0c062e
Jun 26 22:47:32 imobil2 kernel: [ 1909.748005] NVRM: Xid (PCI::01:00): 13, 
pid=1265, Graphics Exception: ChID 0008, Class a097, Offset 1614, Data 

Jun 26 22:47:33 imobil2 kernel: [ 1910.876226] NVRM: Xid (PCI::01:00): 62, 
pid=1265, 0110(25dc) 840008ce c415c455

This happend multiple times. Unfortunately the old driver version is not
available anymore and I can't check if this is really caused by the
driver update.

Best regards,
Matthias

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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.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:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: i3
Date: Fri Jun 26 22:59:14 2020
DistUpgraded: 2020-04-09 19:50:27,912 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.100, 4.15.0-106-generic, x86_64: installed
 nvidia, 440.100, 4.15.0-108-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 770] 
[1462:2825]
InstallationDate: Installed on 2013-12-15 (2384 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: MSI MS-7821
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=10f3ba43-ad16-4df4-b3b4-e86b64e9f96e ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-04-09 (78 days ago)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-G45 GAMING (MS-7821)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd07/21/2014:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ87-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7821
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition

2020-06-28 Thread Tiffany
Feedback from vendor SK Hynix:
Currently, Host send the Write Zeros CMD with NLB 0x100(0~257). But PC400 can 
support Max 0xFF (0~256)
Now we suggest that Canonical try to test with 0xFF instead of 0x100.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872383

Title:
  blk_update_request error when mount nvme partition

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Can't install on this nvme with a focal server installer.

  As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel
  endless blk_update_request error will exists in kernel dmesg.
  the nvme module: PC400 NVMe SK hynix 512GB

  While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (11 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200330)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT 
mode device
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: Dell Inc. Precision 3930 Rack
  Package: linux-generic 5.4.0.21.25
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 02/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3930 Rack
  dmi.product.sku: 0873
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872383/+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 1885031] Re: supervisor write access in kernel mode

2020-06-28 Thread Martin Gerdzhev
So far haven't been able to reproduce this again.

uname -rv:
`5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020`

Will update if it happens again.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885031

Title:
  supervisor write access in kernel mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  machine froze. Only mouse could be moved.

  BUG: kernel NULL pointer dereference, address: 
  Jun 24 18:56:43 MartoBeast kernel: #PF: supervisor write access in kernel mode
  Jun 24 18:56:43 MartoBeast kernel: #PF: error_code(0x0002) - not-present page

  
  Ubuntu 20.04 

  Linux MartoBeast 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2649 F pulseaudio
   /dev/snd/controlC0:  martin 2649 F pulseaudio
   /dev/snd/controlC2:  martin 2649 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-12-08 (199 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash 
acpi_enforce_resources=lax vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (61 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885031/+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 1873718] Status changed to Confirmed

2020-06-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

-- 
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/1873718

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  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.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3: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.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

2020-06-28 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Expired => New

** Changed in: linux (Ubuntu)
   Status: Expired => New

-- 
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/1873718

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  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.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3: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.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1885422] Re: Intel Wireless 8265 / 8275 [8086:24fd] Subsystem [8086:1014] Bluetooth doesn't pair with other devices

2020-06-28 Thread You-Sheng Yang
Hi, could you run btmon to dump bluetooth traffic data while trying to
pair with other devices?

  1. Run `sudo btmon -w btsnoop.log` in a terminal,

  2. Open GNOME Settings to scan devices and try to pair one of them,

  3. When failed, terminate btmon by Ctrl+C and attach that log file
here.

** 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/1885422

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] Subsystem [8086:1014] Bluetooth
  doesn't pair with other devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi everyone, I've installed ubuntu 20.04 one week ago for the first time and 
I'm not expert. I have some issue with my bluetooth adapter: from 
settings/bluetooth it can find other bluetooth devices, but cannot pair with 
them. The adapter isn't shown typing *dmesg | grep -i blue* or typing *dmesg | 
grep -i blue*
  I'm shure I have a bluetooth adapter because it was working on windows.

  Typing *sudo cat /sys/kernel/debug/usb/devices* this is shown:

  
  T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 4
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.3
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0a2b Rev= 0.10
  C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=1ms
  E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms

  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=1 MxCh= 4
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0003 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.3
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.4
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
  D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0408 ProdID=1020 Rev= 0.13
  S:  Manufacturer=SunplusIT Inc
  S:  Product=hm1091_techfront
  C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
  A:  FirstIf#= 0 IfCount= 2 Cls=0e(video) Sub=03 Prot=00
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
  E:  Ad=87(I) Atr=03(Int.) MxPS=  16 Ivl=16ms
  I:* If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  I:  If#= 1 Alt= 1 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 192 Ivl=125us
  I:  If#= 1 Alt= 2 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 384 Ivl=125us
  I:  If#= 1 Alt= 3 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=125us
  I:  If#= 1 Alt= 4 #EPs= 1 Cls=0e(video) 

[Kernel-packages] [Bug 1885422] Re: Bluetooth issues

2020-06-28 Thread You-Sheng Yang
** Tags added: hwe-bluetooth

** Summary changed:

- Bluetooth issues
+ Intel Wireless 8265 / 8275 [8086:24fd] Subsystem [8086:1014] Bluetooth 
doesn't pair with other devices

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885422

Title:
  Intel Wireless 8265 / 8275 [8086:24fd] Subsystem [8086:1014] Bluetooth
  doesn't pair with other devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone, I've installed ubuntu 20.04 one week ago for the first time and 
I'm not expert. I have some issue with my bluetooth adapter: from 
settings/bluetooth it can find other bluetooth devices, but cannot pair with 
them. The adapter isn't shown typing *dmesg | grep -i blue* or typing *dmesg | 
grep -i blue*
  I'm shure I have a bluetooth adapter because it was working on windows.

  Typing *sudo cat /sys/kernel/debug/usb/devices* this is shown:

  
  T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 4
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.3
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0a2b Rev= 0.10
  C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=1ms
  E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms

  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=1 MxCh= 4
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0003 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.3
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.4
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
  D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0408 ProdID=1020 Rev= 0.13
  S:  Manufacturer=SunplusIT Inc
  S:  Product=hm1091_techfront
  C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
  A:  FirstIf#= 0 IfCount= 2 Cls=0e(video) Sub=03 Prot=00
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
  E:  Ad=87(I) Atr=03(Int.) MxPS=  16 Ivl=16ms
  I:* If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  I:  If#= 1 Alt= 1 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 192 Ivl=125us
  I:  If#= 1 Alt= 2 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 384 Ivl=125us
  I:  If#= 1 Alt= 3 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=125us
  I:  If#= 1 Alt= 4 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 640 Ivl=125us
  I:  If#= 1 Alt= 5 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 800 

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Califa101
I hope so.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1885461] Re: HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button event on a clickpad

2020-06-28 Thread You-Sheng Yang
** Tags added: hwe-touchpad

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885461

Title:
  HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button
  event on a clickpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After some time using the computer, the context menu suddenly opens
  and then the touchpad left button starts acting like the right button
  (left button starts opening the context menu instead of clicking).
  Looking at Xorg.0.log, I can see some "kernel bug" messages related to
  the touchpad. On dmesg, there is some error messages related to the
  touchpad too.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1495 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1495 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:09:48 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885461/+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 1885462] Status changed to Confirmed

2020-06-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1885462

Title:
  snd_hda_intel :00:0e.0: No response from codec, resetting bus:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I connect headphones after the system boot or if I boot the system
  with headphone connected and after boot disconnect the headphone
  without reproducing any sound before, the system starts flooding dmesg
  with messages like "snd_hda_intel :00:0e.0: No response from
  codec, resetting bus: last cmd=0x01470500" and becomes very slow. If I
  boot the system and reproduce any sound before disconnecting
  headphone, everything works normally.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1515 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:48:44 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885462/+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 1885462] Re: snd_hda_intel 0000:00:0e.0: No response from codec, resetting bus:

2020-06-28 Thread Leimar
There are also some messages like "snd_hda_codec_realtek hdaudioC0D0:
Unable to sync register 0x2b8000. -11".

** Description changed:

  If I connect headphones after the system boot or if I boot the system
  with headphone connected and after boot disconnect the headphone without
  reproducing any sound before, the system starts flooding dmesg with
  messages like "snd_hda_intel :00:0e.0: No response from codec,
- resetting bus: last cmd=0x01470500". If I boot the system and reproduce
- any sound before disconnecting headphone, everything works normally.
+ resetting bus: last cmd=0x01470500" and becomes very slow. If I boot the
+ system and reproduce any sound before disconnecting headphone,
+ everything works normally.
  
  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  user   1515 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  user   1515 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:48:44 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
-  Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
-  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
+  Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
+  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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
+  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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885462

Title:
  snd_hda_intel :00:0e.0: No response from codec, resetting bus:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I connect headphones after the system boot or if I boot the system
  with headphone connected and after boot disconnect the headphone
  without reproducing any sound before, the system starts flooding dmesg
  with messages like "snd_hda_intel :00:0e.0: No response from
  codec, resetting bus: last cmd=0x01470500" and becomes very slow. If I
  boot the system and reproduce any sound before disconnecting
  headphone, everything works normally.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1515 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:48:44 2020
  InstallationDate: 

[Kernel-packages] [Bug 1885462] [NEW] snd_hda_intel 0000:00:0e.0: No response from codec, resetting bus:

2020-06-28 Thread Leimar
Public bug reported:

If I connect headphones after the system boot or if I boot the system
with headphone connected and after boot disconnect the headphone without
reproducing any sound before, the system starts flooding dmesg with
messages like "snd_hda_intel :00:0e.0: No response from codec,
resetting bus: last cmd=0x01470500" and becomes very slow. If I boot the
system and reproduce any sound before disconnecting headphone,
everything works normally.

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
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  user   1515 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 28 20:48:44 2020
InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya 
Technology Corp.) 300k Pixel Camera
 Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Positivo Tecnologia SA N1240
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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: 07/15/2019
dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
dmi.bios.version: V1.09.X
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: N14DP6
dmi.board.vendor: Positivo Tecnologia SA
dmi.board.version: 11139547
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Positivo Tecnologia SA
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
dmi.product.family: MASTER
dmi.product.name: N1240
dmi.product.sku: 3052532
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Positivo Tecnologia SA

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal

** Attachment added: "Dmesg with error messages"
   https://bugs.launchpad.net/bugs/1885462/+attachment/5388008/+files/dmesg.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/1885462

Title:
  snd_hda_intel :00:0e.0: No response from codec, resetting bus:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I connect headphones after the system boot or if I boot the system
  with headphone connected and after boot disconnect the headphone
  without reproducing any sound before, the system starts flooding dmesg
  with messages like "snd_hda_intel :00:0e.0: No response from
  codec, resetting bus: last cmd=0x01470500" and becomes very slow. If I
  boot the system and reproduce any sound before disconnecting
  headphone, everything works normally.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1515 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:48:44 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1885461] Status changed to Confirmed

2020-06-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1885461

Title:
  HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button
  event on a clickpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After some time using the computer, the context menu suddenly opens
  and then the touchpad left button starts acting like the right button
  (left button starts opening the context menu instead of clicking).
  Looking at Xorg.0.log, I can see some "kernel bug" messages related to
  the touchpad. On dmesg, there is some error messages related to the
  touchpad too.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1495 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1495 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:09:48 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885461/+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 1878507] Re: No HDMI audio in ubuntu 20.04

2020-06-28 Thread paulwill
Using Audacity (2.3.3) I noticed the HDMI output was available and does
work. Refers to it as "HDA ATI HDMI: 0(hw:1,3)"

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1878507

Title:
  No HDMI audio in ubuntu 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound settings does not offer hdmi audio in 20.04, but was there in 16 and 18 
LTSs.
  New HDMI monitor is fine but no audio. Reboot to Ubuntu 16.04.1 LTS (16.04) 
{linux /boot/vmlinuz-4.4.0-24-generic} and all is well.

  ALSA Information Script v 0.4.65 ran giving result at:
  http://alsa-project.org/db/?f=84926788cff2eb5d8d305d6a896608514495ce2f

  Deleting ~/.config/pulse/* broke all the sound but ok again when
  restored

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1715 F pulseaudio
   /dev/snd/controlC1:  paul   1715 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 01:06:50 2020
  HibernationDevice: RESUME=UUID=6ee76bfb-393c-47bf-807f-6d0d8929c120
  InstallationDate: Installed on 2016-06-15 (1428 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=a0ad560d-ee6e-4f49-b40f-d239ecfcf167 ro persistent 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-06 (7 days ago)
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0915
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0915:bd12/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878507/+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 1885461] [NEW] HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button event on a clickpad

2020-06-28 Thread Leimar
Public bug reported:

After some time using the computer, the context menu suddenly opens and
then the touchpad left button starts acting like the right button (left
button starts opening the context menu instead of clicking). Looking at
Xorg.0.log, I can see some "kernel bug" messages related to the
touchpad. On dmesg, there is some error messages related to the touchpad
too.

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
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  user   1495 F pulseaudio
 /dev/snd/pcmC0D0p:   user   1495 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 28 20:09:48 2020
InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya 
Technology Corp.) 300k Pixel Camera
 Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Positivo Tecnologia SA N1240
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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: 07/15/2019
dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
dmi.bios.version: V1.09.X
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: N14DP6
dmi.board.vendor: Positivo Tecnologia SA
dmi.board.version: 11139547
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Positivo Tecnologia SA
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
dmi.product.family: MASTER
dmi.product.name: N1240
dmi.product.sku: 3052532
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Positivo Tecnologia SA

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885461

Title:
  HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button
  event on a clickpad

Status in linux package in Ubuntu:
  New

Bug description:
  After some time using the computer, the context menu suddenly opens
  and then the touchpad left button starts acting like the right button
  (left button starts opening the context menu instead of clicking).
  Looking at Xorg.0.log, I can see some "kernel bug" messages related to
  the touchpad. On dmesg, there is some error messages related to the
  touchpad too.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1495 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1495 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:09:48 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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
  

[Kernel-packages] [Bug 1885461] Re: HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button event on a clickpad

2020-06-28 Thread Leimar
** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885461/+attachment/5388007/+files/Xorg.0.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/1885461

Title:
  HTIX5288:00 0911:5288 Touchpad: kernel bug: received BTN_RIGHT button
  event on a clickpad

Status in linux package in Ubuntu:
  New

Bug description:
  After some time using the computer, the context menu suddenly opens
  and then the touchpad left button starts acting like the right button
  (left button starts opening the context menu instead of clicking).
  Looking at Xorg.0.log, I can see some "kernel bug" messages related to
  the touchpad. On dmesg, there is some error messages related to the
  touchpad too.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1495 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1495 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 28 20:09:48 2020
  InstallationDate: Installed on 2020-06-26 (2 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 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=cb8580f2-9833-4c7c-a906-d1fc1f61cb53 ro quiet 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: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885461/+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 1885010] Re: NULL deference in nfs4_get_valid_delegation

2020-06-28 Thread Matthew Ruffell
Hi Elvis, excellent to hear your long production job finishes
successfully on your test kernel and on 5.4.0-40 from -proposed.

Looking at the schedule, 5.4.0-40 should be released to -updates in the
next day or two, and it will be exactly the same package that was in
-proposed. I'll mark this bug as fixed released when the kernel is
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/1885010

Title:
  NULL deference in nfs4_get_valid_delegation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  We are getting the following on an NFSv4 client running focal (kernel
  5.4.0-33.37):

  [296787.347971] BUG: unable to handle page fault for address: ffb0
  [296787.350255] #PF: supervisor read access in kernel mode
  [296787.352315] #PF: error_code(0x) - not-present page
  [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 
  [296787.355798] Oops:  [#2] SMP NOPTI
  [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P  D
OE 5.4.0-33-generic #37-Ubuntu
  [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 
10/04/2019
  [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc]
  [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4]
  [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 
55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 
67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44
  [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246
  [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: 

  [296787.370648] RDX: 8000 RSI:  RDI: 

  [296787.372559] RBP: b7b1634a7da0 R08:  R09: 
8080808080808080
  [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 
9ef781f22600
  [296787.376330] R13:  R14: 9efe1db4bc00 R15: 
c0cc2950
  [296787.378220] FS:  () GS:9ef78fc4() 
knlGS:
  [296787.380165] CS:  0010 DS:  ES:  CR0: 80050033
  [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 
003406e0
  [296787.384031] Call Trace:
  [296787.385985]  nfs4_open_prepare+0x89/0x1e0 [nfsv4]
  [296787.387973]  rpc_prepare_task+0x1f/0x30 [sunrpc]
  [296787.389971]  __rpc_execute+0x8c/0x3a0 [sunrpc]
  [296787.391903]  rpc_async_schedule+0x30/0x50 [sunrpc]
  [296787.393787]  process_one_work+0x1eb/0x3b0
  [296787.395617]  worker_thread+0x4d/0x400
  [296787.397431]  kthread+0x104/0x140
  [296787.399166]  ? process_one_work+0x3b0/0x3b0
  [296787.400868]  ? kthread_park+0x90/0x90
  [296787.402518]  ret_from_fork+0x1f/0x40
  [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter 
br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache 
libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif 
nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec 
snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm 
snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore 
k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp 
parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) 
ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm 
glue_helper xfrm_algo
  [296787.404232]  drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect 
sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci 
ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu
  [296787.421858] CR2: ffb0
  [296787.423680] ---[ end trace 2cf3edda87955a36 ]---
  [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4]
  [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 
55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 
67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44
  [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246
  [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: 

  [296787.434922] RDX: 8000 RSI:  RDI: 

  [296787.436810] RBP: b7b1615e3da0 R08:  R09: 
8080808080808080
  [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 
9ef7817cfa00
  [296787.440539] 

[Kernel-packages] [Bug 1707695] Re: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec

2020-06-28 Thread urnenfeld
I have the same effects as the description with the following graphics
card:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] RV630 PRO [Radeon HD 2600 PRO AGP]

- IRCC Ubuntu 16 would not spot any problems.
- Lubuntu 18.04 kernel 4.15.0-88-generic would spot the problem very seldom, at 
undetermined situations. You can live with the problem...
- Lubuntu 20.04 kernel 5.4.0-39-generic the problem is reproducible 
deterministacally with certain actions. Opening specific websites, or simply 
open a video with VLC (you cannot live with the problem)


** Attachment added: "journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707695/+attachment/5387984/+files/radeon_error_5.4.39

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707695

Title:
  radeon :03:00.0: ring 0 stalled for more than 1msec

Status in Linux:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system intermittently locks up every few days. It does not seem to
  correspond to a particular program or action.  When that happens, the
  screen goes to black, then returns after a few seconds. At that point,
  the time on the clock is static and indicates that the screen is
  frozen, but audio continues to play for 30 seconds to a minute. The
  keyboard and mouse do not affect what's being displayed, but I can Alt
  - SysRq - REISUB to restart.

  Every time (7 crashes and counting), /var/log/kern.log indicates that

  kernel: [353692.378886] radeon :03:00.0: ring 0 stalled for more than 
10280msec
  kernel: [353692.378896] radeon :03:00.0: GPU lockup (current fence id 
0x006e96e5 last fence id 0x006e96e9 on ring 0)

  just before the system locks. Different ring numbers are reported as
  stalling at different times.

  As per the instructions, I posted a question about this issue at:

  https://askubuntu.com/questions/937792/system-lockup-radeon-ring-
  stalled-for-more-than-10280msec?noredirect=1#comment1486875_937792

  but I have not received many responses.

  I'm running 16.04 LTS. 
  :~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  According to the Software Center, I am running Ubuntu Software 3.20.1.

  I have a Radeon HD graphics card.

  :~$ lspci | grep VGA
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]

  :~$ lspci -v -s 03:00.0
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Cedar [Radeon HD 5000/6000/7350/8350 
Series]
  Flags: bus master, fast devsel, latency 0, IRQ 53
  Memory at c000 (64-bit, prefetchable) [size=256M]
  Memory at d3d2 (64-bit, non-prefetchable) [size=128K]
  I/O ports at 7000 [size=256]
  Expansion ROM at d3d0 [disabled] [size=128K]
  Capabilities: 
  Kernel driver in use: radeon
  Kernel modules: radeon

  Please let me know if additional information would be useful, and I
  will be glad to provide it.  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clapp  3889 F pulseaudio
   /dev/snd/controlC2:  clapp  3889 F pulseaudio
   /dev/snd/controlC1:  clapp  3889 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 31 14:02:27 2017
  HibernationDevice: RESUME=UUID=1b30dad6-8c48-42cf-ae26-66ab8b0eb446
  InstallationDate: Installed on 2013-09-04 (1425 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Precision T7600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=33722f76-37fd-4289-b071-d7f48b65dd32 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/03/2013:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  

[Kernel-packages] [Bug 1885450] Missing required logs.

2020-06-28 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1885450

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885450

Title:
  hangs on shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC.

  The shutdown image is shown. Then I switch to text mode and there are
  some messages.

  Attached are two screenshots of the console in about 30 second
  interval.

  After that I can reboot by SysReq keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+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 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Ian Hand
@Califa101, that unix.exchange.com question looks very promising, I will
have a look at it over the next day or two and see if I can get
somewhere with it.

In the meantime, it would be great if one of the programmers and/or
developers that have already assisted with this bug could have a look at
that potential solution you found and confirm if this is a worthwhile
solution for our specific situation.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  

[Kernel-packages] [Bug 1885450] Re: hangs on shutdown

2020-06-28 Thread David Balažic
** Attachment added: "ububug_sd_2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+attachment/5387974/+files/ububug_sd_2.jpg

** Description changed:

  Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC.
  
+ The shutdown image is shown. Then I switch to text and there are some
+ messages.
+ 
  Attached are two screenshots of the console in about 30 second interval.
+ 
+ After that I can reboot by SysReq keys.

** Description changed:

  Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC.
  
- The shutdown image is shown. Then I switch to text and there are some
- messages.
+ The shutdown image is shown. Then I switch to text mode and there are
+ some messages.
  
  Attached are two screenshots of the console in about 30 second interval.
  
  After that I can reboot by SysReq keys.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885450

Title:
  hangs on shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC.

  The shutdown image is shown. Then I switch to text mode and there are
  some messages.

  Attached are two screenshots of the console in about 30 second
  interval.

  After that I can reboot by SysReq keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+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 1885450] [NEW] hangs on shutdown

2020-06-28 Thread David Balažic
Public bug reported:

Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC.

The shutdown image is shown. Then I switch to text mode and there are
some messages.

Attached are two screenshots of the console in about 30 second interval.

After that I can reboot by SysReq keys.

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

** Attachment added: "ububug_sd_1.jpg"
   
https://bugs.launchpad.net/bugs/1885450/+attachment/5387973/+files/ububug_sd_1.jpg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885450

Title:
  hangs on shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC.

  The shutdown image is shown. Then I switch to text mode and there are
  some messages.

  Attached are two screenshots of the console in about 30 second
  interval.

  After that I can reboot by SysReq keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+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 1884546] Re: Lenovo T440s hangs on the dock when unsleeping the monitor

2020-06-28 Thread Martin D. Weinberg
** Attachment added: "kern.log containing a dead hang"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387972/+files/kern.log.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/1884546

Title:
  Lenovo T440s hangs on the dock when unsleeping the monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue has been a persistent but infrequent problem for many years
  with the T440s.  It only occurs when the laptop is docked.  I have
  reported this bug several times.  However, with the current kernel
  release, 5.4.0-37, this occurs at least once a day.  The kern.log
  lines are:

  Jun 21 16:44:23 magpie kernel: [13992.853712] 
[drm:intel_set_cpu_fifo_underrun_r
  eporting [i915]] *ERROR* uncleared fifo underrun on pipe B
  Jun 21 16:44:23 magpie kernel: [13992.853749] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  Jun 21 17:17:00 magpie kernel: [15950.119066] 
[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo 
underrun on pipe B
  Jun 21 17:17:00 magpie kernel: [15950.119101] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  followed by a dead hang.   The pattern is the same each time.

  My current work around is to use the previous version of the released
  kernel, 5.4.0-33, which does not have this issue.   I'm hoping someone
  has an idea.  It's very frustrating.

  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  weinberg   3505 F pulseaudio
   /dev/snd/controlC1:  weinberg   3505 F pulseaudio
   /dev/snd/controlC0:  weinberg   3505 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 22 10:02:42 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (832 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 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: Upgraded to focal on 2020-04-24 (58 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+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 1884546] Re: Lenovo T440s hangs on the dock when unsleeping the monitor

2020-06-28 Thread Martin D. Weinberg
** Attachment added: "syslog surrounding the dead hang"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+attachment/5387971/+files/syslog.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/1884546

Title:
  Lenovo T440s hangs on the dock when unsleeping the monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue has been a persistent but infrequent problem for many years
  with the T440s.  It only occurs when the laptop is docked.  I have
  reported this bug several times.  However, with the current kernel
  release, 5.4.0-37, this occurs at least once a day.  The kern.log
  lines are:

  Jun 21 16:44:23 magpie kernel: [13992.853712] 
[drm:intel_set_cpu_fifo_underrun_r
  eporting [i915]] *ERROR* uncleared fifo underrun on pipe B
  Jun 21 16:44:23 magpie kernel: [13992.853749] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  Jun 21 17:17:00 magpie kernel: [15950.119066] 
[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo 
underrun on pipe B
  Jun 21 17:17:00 magpie kernel: [15950.119101] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  followed by a dead hang.   The pattern is the same each time.

  My current work around is to use the previous version of the released
  kernel, 5.4.0-33, which does not have this issue.   I'm hoping someone
  has an idea.  It's very frustrating.

  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  weinberg   3505 F pulseaudio
   /dev/snd/controlC1:  weinberg   3505 F pulseaudio
   /dev/snd/controlC0:  weinberg   3505 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 22 10:02:42 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (832 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 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: Upgraded to focal on 2020-04-24 (58 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+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 1884546] Re: Lenovo T440s hangs on the dock when unsleeping the monitor

2020-06-28 Thread Martin D. Weinberg
I ran it until it happened again.   I'm attaching the syslog and
kern.log from the time of the crash, which was Jun 28 at about 15:30.
Doesn't seem to be a lot to go on here . . .

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884546

Title:
  Lenovo T440s hangs on the dock when unsleeping the monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue has been a persistent but infrequent problem for many years
  with the T440s.  It only occurs when the laptop is docked.  I have
  reported this bug several times.  However, with the current kernel
  release, 5.4.0-37, this occurs at least once a day.  The kern.log
  lines are:

  Jun 21 16:44:23 magpie kernel: [13992.853712] 
[drm:intel_set_cpu_fifo_underrun_r
  eporting [i915]] *ERROR* uncleared fifo underrun on pipe B
  Jun 21 16:44:23 magpie kernel: [13992.853749] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  Jun 21 17:17:00 magpie kernel: [15950.119066] 
[drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo 
underrun on pipe B
  Jun 21 17:17:00 magpie kernel: [15950.119101] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  followed by a dead hang.   The pattern is the same each time.

  My current work around is to use the previous version of the released
  kernel, 5.4.0-33, which does not have this issue.   I'm hoping someone
  has an idea.  It's very frustrating.

  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  weinberg   3505 F pulseaudio
   /dev/snd/controlC1:  weinberg   3505 F pulseaudio
   /dev/snd/controlC0:  weinberg   3505 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 22 10:02:42 2020
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (832 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 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: Upgraded to focal on 2020-04-24 (58 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+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 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Califa101
Surfing the net, I have seen this that could be the solution. I have
been seeing it but it escapes my meager knowledge. Try to see if you are
lucky and if you succeed, I would appreciate it if you would contact me.
Thank you.

Link: https://unix.stackexchange.com/questions/512280/chuwi-lapbook-
air-14-touchpad-recognized-but-not-fully-working

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

2020-06-28 Thread Darko Veberic
interesting observation: if i close the lid for, say, 1 sec, and then
open it again, after similar time delay as observed in the previous
comment, my thinkpad goes into suspend although i am working in my
desktop (obviously with the lid open). the lid close seems to trigger
the suspend which comes 30 seconds later, no matter what...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829399

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Califa101
Do not worry @Ian Hand. But as an important fact and for the record in
this post, comment on what I said earlier, with Windows the touchpad
works, in case someone is interested in having it present to try to give
a solution. I know that there are many of us affected by this problem,
even if they do not appear in this forum.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Ian Hand
@Califa101, I can also confirm that my BIOS is from 2019.

I do not have a partition set up on my laptop, I completely removed
Windows from it when installing Ubuntu, so unfortunately I will not be
able to test this.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Califa101
I would also like to add that my BIOS is from the year 2019, so I do not think 
it is outdated. My BIOS is as follows: APTIO SETUP UTILITY 2.20.1270.
I have also enabled the TOUCHPAD option in the BIOS which was disabled 
(attachment). And the TOUCHPAD still doesn't work on (K) Ubuntu. I suppose if 
it were a hardware failure it wouldn't work on Windows either.
Ian Hand, does TOUCHPAD work for you on Windows? It would be interesting to 
know to find out if the same thing happens to me and to find out if it is a 
hardware or software failure.

** Attachment added: "photo_2020-06-28_18-33-03.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+attachment/5387951/+files/photo_2020-06-28_18-33-03.jpg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   

[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle

2020-06-28 Thread Kostadin Stoilov
Hi Colin Ian King,

I tested the revert kernels from here
https://kernel.ubuntu.com/~cking/lp-1853044/.

The results from Powertop can be found here
https://postimg.cc/gallery/TTmWSfX. I also included the latest 5.3.0-61
kernel for reference.

The test system is an XPS 9550 with HD Graphics 530, Intel Core i7
6700HQ

For all kernels I booted up, ran powertop, waited to idle and made
screenshots.

Hope this helps.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853044

Title:
  5.3.0-23-generic causes fans to spin when idle

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:
  SRU Justification

  Impact: "drm/i915/gen8+: Add RC6 CTX corruption WA" makes it
  effectively impossible to enter RC6 for some Intel GPUs when a display
  server is running. This results in increased energy usage and
  temperature.

  Fix: Upstream has changed too much to make the fixes there applicable,
  but Chris Wilson has provided a patch for 5.3, here:
  https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

  Test Case: See test results below. On an affected machine powertop
  will show increased RC6 usage on an idle desktop after the patch, and
  other symptoms of excessive power use should also subside.

  Regression Potential: The 5.3 patch is pretty straightforward, and
  only adds running of an existing delayed worker to retire GPU
  requests. No regressions have been reported in testing so far.

  ---

  After upgrading to 5.3.0-23-generic the fans in my machine don't stop
  running. They always sound like something is utilizing CPU - even with
  no applications running after boot.

  If I boot back to 5.3.0-19-generic it's fine.

  My microcode version is reported as 0xd4 and iucode-tool reports:

  iucode-tool: system has processor(s) with signature 0x000506e3

  Let me know if you need anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   2898 F pulseaudio
   /dev/snd/pcmC2D0p:   dean   2898 F...m pulseaudio
   /dev/snd/controlC0:  dean   2898 F pulseaudio
   /dev/snd/controlC1:  dean   2898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 13:03:34 2019
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (482 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+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 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Ian Hand
@Califa101, I raised a ticket on 26/06/2020 with Chuwi to obtain an
update for my BIOS, I haven't received a reply yet so I am not sure if
this is something that Chuwi will issue us with or if it will actually
solve the problem.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

2020-06-28 Thread Califa101
Hi. I have the same problem as this user and I would like to know if it
has been solved. I have to add that I don't know why it doesn't give an
error in Windows, but it does with Ubuntu, in my case, Kubuntu.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884288

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  

[Kernel-packages] [Bug 1885423] Status changed to Confirmed

2020-06-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1885423

Title:
  Attempt to upgrade to 20.04

Status in linux 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/linux/+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 1885423] [NEW] Attempt to upgrade to 20.04

2020-06-28 Thread Clifton Williams
Public bug reported:

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.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug eoan

** Attachment added: "Screenshot from 2020-06-28 10-57-51.png"
   
https://bugs.launchpad.net/bugs/1885423/+attachment/5387876/+files/Screenshot%20from%202020-06-28%2010-57-51.png

-- 
You 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 linux 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/linux/+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 1885422] Status changed to Confirmed

2020-06-28 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1885422

Title:
  Bluetooth issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi everyone, I've installed ubuntu 20.04 one week ago for the first time and 
I'm not expert. I have some issue with my bluetooth adapter: from 
settings/bluetooth it can find other bluetooth devices, but cannot pair with 
them. The adapter isn't shown typing *dmesg | grep -i blue* or typing *dmesg | 
grep -i blue*
  I'm shure I have a bluetooth adapter because it was working on windows.

  Typing *sudo cat /sys/kernel/debug/usb/devices* this is shown:

  
  T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 4
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.3
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12   MxCh= 0
  D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0a2b Rev= 0.10
  C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=1ms
  E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms

  T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=1 MxCh= 4
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0003 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.3
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
  B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
  D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=1d6b ProdID=0002 Rev= 5.04
  S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
  S:  Product=xHCI Host Controller
  S:  SerialNumber=:02:00.4
  C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
  E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

  T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
  D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0408 ProdID=1020 Rev= 0.13
  S:  Manufacturer=SunplusIT Inc
  S:  Product=hm1091_techfront
  C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
  A:  FirstIf#= 0 IfCount= 2 Cls=0e(video) Sub=03 Prot=00
  I:* If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
  E:  Ad=87(I) Atr=03(Int.) MxPS=  16 Ivl=16ms
  I:* If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  I:  If#= 1 Alt= 1 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 192 Ivl=125us
  I:  If#= 1 Alt= 2 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 384 Ivl=125us
  I:  If#= 1 Alt= 3 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=125us
  I:  If#= 1 Alt= 4 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 640 Ivl=125us
  I:  If#= 1 Alt= 5 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 800 Ivl=125us
  I:  If#= 1 Alt= 6 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
  E:  Ad=81(I) Atr=05(Isoc) MxPS= 944 Ivl=125us
  I:  If#= 1 Alt= 7 #EPs= 1 Cls=0e(video) 

[Kernel-packages] [Bug 1885422] [NEW] Bluetooth issues

2020-06-28 Thread Tommaso Tragno
Public bug reported:

Hi everyone, I've installed ubuntu 20.04 one week ago for the first time and 
I'm not expert. I have some issue with my bluetooth adapter: from 
settings/bluetooth it can find other bluetooth devices, but cannot pair with 
them. The adapter isn't shown typing *dmesg | grep -i blue* or typing *dmesg | 
grep -i blue*
I'm shure I have a bluetooth adapter because it was working on windows.

Typing *sudo cat /sys/kernel/debug/usb/devices* this is shown:


T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 4
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.04
S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=:02:00.3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0a2b Rev= 0.10
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=1ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=1 MxCh= 4
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.10 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 5.04
S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=:02:00.3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.04
S:  Manufacturer=Linux 5.4.0-37-generic xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=:02:00.4
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0408 ProdID=1020 Rev= 0.13
S:  Manufacturer=SunplusIT Inc
S:  Product=hm1091_techfront
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
A:  FirstIf#= 0 IfCount= 2 Cls=0e(video) Sub=03 Prot=00
I:* If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
E:  Ad=87(I) Atr=03(Int.) MxPS=  16 Ivl=16ms
I:* If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
I:  If#= 1 Alt= 1 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS= 192 Ivl=125us
I:  If#= 1 Alt= 2 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS= 384 Ivl=125us
I:  If#= 1 Alt= 3 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=125us
I:  If#= 1 Alt= 4 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS= 640 Ivl=125us
I:  If#= 1 Alt= 5 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS= 800 Ivl=125us
I:  If#= 1 Alt= 6 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS= 944 Ivl=125us
I:  If#= 1 Alt= 7 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS=1280 Ivl=125us
I:  If#= 1 Alt= 8 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS=1600 Ivl=125us
I:  If#= 1 Alt= 9 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS=1984 Ivl=125us
I:  If#= 1 Alt=10 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E:  Ad=81(I) Atr=05(Isoc) MxPS=2880 Ivl=125us
I:  If#= 1 Alt=11 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 

[Kernel-packages] [Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation

2020-06-28 Thread Elvis Stansvik
The test on 5.4.0-40.44 from focal-proposed was successful, so I would
say that the fix did it. Thanks for including it!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885010

Title:
  NULL deference in nfs4_get_valid_delegation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  We are getting the following on an NFSv4 client running focal (kernel
  5.4.0-33.37):

  [296787.347971] BUG: unable to handle page fault for address: ffb0
  [296787.350255] #PF: supervisor read access in kernel mode
  [296787.352315] #PF: error_code(0x) - not-present page
  [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 
  [296787.355798] Oops:  [#2] SMP NOPTI
  [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P  D
OE 5.4.0-33-generic #37-Ubuntu
  [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 
10/04/2019
  [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc]
  [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4]
  [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 
55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 
67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44
  [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246
  [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: 

  [296787.370648] RDX: 8000 RSI:  RDI: 

  [296787.372559] RBP: b7b1634a7da0 R08:  R09: 
8080808080808080
  [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 
9ef781f22600
  [296787.376330] R13:  R14: 9efe1db4bc00 R15: 
c0cc2950
  [296787.378220] FS:  () GS:9ef78fc4() 
knlGS:
  [296787.380165] CS:  0010 DS:  ES:  CR0: 80050033
  [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 
003406e0
  [296787.384031] Call Trace:
  [296787.385985]  nfs4_open_prepare+0x89/0x1e0 [nfsv4]
  [296787.387973]  rpc_prepare_task+0x1f/0x30 [sunrpc]
  [296787.389971]  __rpc_execute+0x8c/0x3a0 [sunrpc]
  [296787.391903]  rpc_async_schedule+0x30/0x50 [sunrpc]
  [296787.393787]  process_one_work+0x1eb/0x3b0
  [296787.395617]  worker_thread+0x4d/0x400
  [296787.397431]  kthread+0x104/0x140
  [296787.399166]  ? process_one_work+0x3b0/0x3b0
  [296787.400868]  ? kthread_park+0x90/0x90
  [296787.402518]  ret_from_fork+0x1f/0x40
  [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter 
br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache 
libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif 
nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec 
snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm 
snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore 
k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp 
parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) 
ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm 
glue_helper xfrm_algo
  [296787.404232]  drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect 
sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci 
ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu
  [296787.421858] CR2: ffb0
  [296787.423680] ---[ end trace 2cf3edda87955a36 ]---
  [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4]
  [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 
55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 
67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44
  [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246
  [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: 

  [296787.434922] RDX: 8000 RSI:  RDI: 

  [296787.436810] RBP: b7b1615e3da0 R08:  R09: 
8080808080808080
  [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 
9ef7817cfa00
  [296787.440539] R13: 0004 R14: 9ef8bdeb0400 R15: 
c0cc2950
  [296787.442400] FS:  () GS:9ef78fc4() 
knlGS:
  [296787.444289] CS:  0010 DS:  ES:  CR0: 

[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]

2020-06-28 Thread Sairam D
$ modinfo iwlwifi | grep 9260
firmware:  iwlwifi-9260-th-b0-jf-b0-46.ucode


$ dmesg | grep firmware
[   14.894863] iwlwifi :3b:00.0: loaded firmware version 46.6bf1df06.0 
op_mode iwlmvm
[   15.050919] iwlwifi :3b:00.0: Allocated 0x0040 bytes for firmware 
monitor.
[13966.871684] iwlwifi :3b:00.0: Loaded firmware version: 46.6bf1df06.0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848921

Title:
  iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem
  [8086:0010]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10
  Kernel 5.3.0-18-generic
  Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card.

  Expected: Wifi connects, uploads/downloads as normal

  Symptom: Wifi connects, as soon as an upload/download (any heavy
  traffic) start, the system comes to a crawl, becomes barely usable,
  and I end up opening a prompt to reboot.

  The system is unusable. This happens even with the Live USB version.

  The only solution I found was to download a different (newer) firmware.
  Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi

  This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz

  I then manually copy the contained firmware to /lib/firmware, remove
  all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode
  that the kernel expects to load.

  This completely resolves the issue.

  This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh 
installs):
  
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending 
SCAN_CFG_CMD: time out after 2000ms.
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue 
read_ptr 64 write_ptr 65
  Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting 
before reading
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, 
count: 609870115
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 
46.6bf1df06.0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | 
ADVANCED_SYSASSERT  
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | 
trm_hw_status0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | 
trm_hw_status1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | 
interruptlink1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | 
interruptlink2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode 
revision type
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode 
version major
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode 
version minor
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board 
version
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | 
l2p_addr_match
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler
  Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error 

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2020-06-28 Thread marqus
Same here:

Linux VivoBook-ASUSLaptop-X421JQ-K433JQ 5.4.0-39-generic #43-Ubuntu SMP
Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Linux version 5.4.0-39-generic (buildd@lcy01-amd64-016) (gcc version
9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC
2020

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/1810183

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+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 1885239] Re: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] Subsystem [10de:12fa] Freeze after upgrading 18.04 LTS to 20.04 LTS with NVIDIA's driver.

2020-06-28 Thread Janne Heikkinen
*** This bug is a duplicate of bug 1879949 ***
https://bugs.launchpad.net/bugs/1879949

This might not be duplicate of bug #1879949, as I get the freeze also
with linux 5.4.0-26-generic, which is said to work in bug #1879949
report.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885239

Title:
  NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] [10de:1e07] Subsystem
  [10de:12fa] Freeze after upgrading 18.04 LTS to 20.04 LTS with
  NVIDIA's driver.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading 18.04 LTS to 20.04 LTS X started to freeze at the
  login when using NVIDIA's driver 440.82 or 440.100.

  When investigating log files, the following was found in Xorg.0.log:

  "(EE) NVIDIA(GPU-0): Failed to acquire modesetting permission."

  To prevent the freeze, adding kernel command line parameter
  "nvidia_drm.modeset=1" was required.

  Nouveau driver had already been blacklisted, as it has never been stable on 
the computer in question.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jamse  1570 F pulseaudio
   /dev/snd/controlC0:  jamse  1570 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=346c2d17-3996-4471-8dbd-02abeb7c4798
  InstallationDate: Installed on 2018-07-03 (724 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X10DAx
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=28b3c329-b0b5-41aa-973e-64e82767b05f ro quiet splash 
nvidia_drm.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-06-25 (1 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10DAX
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02
  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.:bvr3.0a:bd02/23/2018:svnSupermicro:pnX10DAx:pvr123456789:rvnSupermicro:rnX10DAX:rvr1.02:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: SMC X10
  dmi.product.name: X10DAx
  dmi.product.sku: 083615D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885239/+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 1879949] Re: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission

2020-06-28 Thread Janne Heikkinen
"After upgrading from linux 5.4.0-26-generic to 5.4.0-31-generic
...
 Package: linux-image-5.4.0-26-generic 5.4.0-26.30"

I now tried that same 5.4.0-26.30 and I get freeze with it too.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879949

Title:
  NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can
  not log in: Failed to acquire modesetting permission

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to
  5.4.0-31-generic I could not log in anymore. I was stuck in the
  display manager. Then I rebooted into the old kernel and sent these
  reports. I'm not sure if this is related but I can't put my display
  onto the correct resolution anymore.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jesko  3203 F pulseaudio
   /dev/snd/controlC1:  jesko  3203 F pulseaudio
   /dev/snd/controlC2:  jesko  3203 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:07:25 2020
  InstallationDate: Installed on 2020-05-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B79
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+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 1885010] Re: NULL deference in nfs4_get_valid_delegation

2020-06-28 Thread Elvis Stansvik
The long production job with the custom built kernel finished
successfully. I'm very confident this fixes our issue. Now running with
5.4.0-40.44 from focal-proposed as a test. I'll let it run for a few
hours. It usually hits the crash in an hour or so.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1885010

Title:
  NULL deference in nfs4_get_valid_delegation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  We are getting the following on an NFSv4 client running focal (kernel
  5.4.0-33.37):

  [296787.347971] BUG: unable to handle page fault for address: ffb0
  [296787.350255] #PF: supervisor read access in kernel mode
  [296787.352315] #PF: error_code(0x) - not-present page
  [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 
  [296787.355798] Oops:  [#2] SMP NOPTI
  [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P  D
OE 5.4.0-33-generic #37-Ubuntu
  [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 
10/04/2019
  [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc]
  [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4]
  [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 
55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 
67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44
  [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246
  [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: 

  [296787.370648] RDX: 8000 RSI:  RDI: 

  [296787.372559] RBP: b7b1634a7da0 R08:  R09: 
8080808080808080
  [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 
9ef781f22600
  [296787.376330] R13:  R14: 9efe1db4bc00 R15: 
c0cc2950
  [296787.378220] FS:  () GS:9ef78fc4() 
knlGS:
  [296787.380165] CS:  0010 DS:  ES:  CR0: 80050033
  [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 
003406e0
  [296787.384031] Call Trace:
  [296787.385985]  nfs4_open_prepare+0x89/0x1e0 [nfsv4]
  [296787.387973]  rpc_prepare_task+0x1f/0x30 [sunrpc]
  [296787.389971]  __rpc_execute+0x8c/0x3a0 [sunrpc]
  [296787.391903]  rpc_async_schedule+0x30/0x50 [sunrpc]
  [296787.393787]  process_one_work+0x1eb/0x3b0
  [296787.395617]  worker_thread+0x4d/0x400
  [296787.397431]  kthread+0x104/0x140
  [296787.399166]  ? process_one_work+0x3b0/0x3b0
  [296787.400868]  ? kthread_park+0x90/0x90
  [296787.402518]  ret_from_fork+0x1f/0x40
  [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter 
br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache 
libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif 
nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec 
snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm 
snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore 
k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp 
parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) 
ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm 
glue_helper xfrm_algo
  [296787.404232]  drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect 
sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci 
ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu
  [296787.421858] CR2: ffb0
  [296787.423680] ---[ end trace 2cf3edda87955a36 ]---
  [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4]
  [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 
55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 
67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44
  [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246
  [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: 

  [296787.434922] RDX: 8000 RSI:  RDI: 

  [296787.436810] RBP: b7b1615e3da0 R08:  R09: 
8080808080808080
  [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 
9ef7817cfa00
  [296787.440539] R13: 0004 R14: 9ef8bdeb0400 R15: 
c0cc2950
  [296787.442400] FS:  

[Kernel-packages] [Bug 1879949] Re: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission

2020-06-28 Thread Janne Heikkinen
I now have tried also 5.6.0 and 5.6.1 vanillas and they both worked
without the nvidia_drm.modeset parameter.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879949

Title:
  NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can
  not log in: Failed to acquire modesetting permission

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to
  5.4.0-31-generic I could not log in anymore. I was stuck in the
  display manager. Then I rebooted into the old kernel and sent these
  reports. I'm not sure if this is related but I can't put my display
  onto the correct resolution anymore.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jesko  3203 F pulseaudio
   /dev/snd/controlC1:  jesko  3203 F pulseaudio
   /dev/snd/controlC2:  jesko  3203 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:07:25 2020
  InstallationDate: Installed on 2020-05-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B79
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+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 1876491] Re: Ubuntu 20.04 Freezes

2020-06-28 Thread Marco
Hi! I'm experiencing exactly the same problem. I've added the package
name. Hope someone can help me/us

** Package changed: linux (Ubuntu) => gdm3 (Ubuntu)

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1876491

Title:
  Ubuntu 20.04 Freezes

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I am running into full system freezes while using 20.04, i did a clean 
install and the issue is still there it will randomly freeze the whole system 
sometimes the mouse pointer is moving. 
  Ends up hard resetting by holding the power button to restart the pc.
  I am using AMD Ryzen 5 2500U , and while it boots up it has showed some gpu 
error while booting ubuntu. Some error realating to kernel is showed ,  amd gpu 
kernel  like that. So i think its kernel related issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1876491/+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 1879949] Re: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission

2020-06-28 Thread Janne Heikkinen
Also vanilla 5.6.19 works but 5.6.0-1017-oem does not.

I also checked that the nvidia_drm.modeset parameted was really
disabled:

  $ sudo cat /sys/module/nvidia_drm/parameters/modeset 
  N

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879949

Title:
  NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can
  not log in: Failed to acquire modesetting permission

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to
  5.4.0-31-generic I could not log in anymore. I was stuck in the
  display manager. Then I rebooted into the old kernel and sent these
  reports. I'm not sure if this is related but I can't put my display
  onto the correct resolution anymore.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jesko  3203 F pulseaudio
   /dev/snd/controlC1:  jesko  3203 F pulseaudio
   /dev/snd/controlC2:  jesko  3203 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:07:25 2020
  InstallationDate: Installed on 2020-05-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B79
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+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 1879949] Re: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission

2020-06-28 Thread Janne Heikkinen
"I tried the suggested 5.6.0-1008-oem kernel"

I built latest stable vanilla kernel 5.7.6 using 5.4.0-39-generic's
.config with "make oldconfig" and using defaults for all the new
options. And that kernel worked without the "nvidia_drm.modeset=1"
parameter.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879949

Title:
  NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can
  not log in: Failed to acquire modesetting permission

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to
  5.4.0-31-generic I could not log in anymore. I was stuck in the
  display manager. Then I rebooted into the old kernel and sent these
  reports. I'm not sure if this is related but I can't put my display
  onto the correct resolution anymore.

  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
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jesko  3203 F pulseaudio
   /dev/snd/controlC1:  jesko  3203 F pulseaudio
   /dev/snd/controlC2:  jesko  3203 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:07:25 2020
  InstallationDate: Installed on 2020-05-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7B79
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PLUS (MS-7B79)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B79
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+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

2020-06-28 Thread Louis-Michel Raynauld
I got another set of log after booting on mainline (appended below) and
touchpad not working. The log shows up that first before the "controller
timed out spamming" starts:

i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
i2c_designware AMDI0010:00: controller timed out
i2c_hid i2c-MSFT0004:00: failed to retrieve report from device.

Now, I found these 3 exact log messages related to a touchpad issue in
this kernel commit to fix another DELL Win8 touchpad in 2015:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.8-rc2=6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095

>From this commit it seems like a similar failure occurs with the MSFT
touchpad.

-- 
You 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