Re: [Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Douglas]

Hello Brothers!

Shouldn't Quanta or Acer accurately propose a patch to make your device
work natively on recent kernels?
Or do they do this but the team that maintains the kernel takes a while to
accept the changes?

 []s

Em sex., 29 de set. de 2023 às 09:00, Giuliano Lotta <
2000...@bugs.launchpad.net> escreveu:

> @devyca
>
> Hi, truly speaking, Ubuntu 22.04 uses are NOT supposed to follow #37 ...
>
> they are supposed to use ONLY
>
> https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/compile_module.sh
>
> I understand your problem, but cannot follow each particular method users
> are choosing to patch the camera...
> sorry  :-(
>
>
> Giulano
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2000947
>
> Title:
>   UVC  Quanta 0408:4035  camera PROBLEM
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
>   USB 0408:4035.
>
>   The camera is reported to have problems by many users:
>   https://linux-hardware.org/?id=usb:0408-4035
>   The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the
> camera is “recongized” but fails installation.
>
>   My console commands report similar info to other users:
>
> https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58
>
>
>   PROPOSED SOLUTION
>   I got in contact with laurent.pinch...@ideasonboard.com   and with
> riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists.
> And  me...@vger.kernel.org mailinglist.
>
>   Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
>   version, and loaded it on github
>
>   https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
>   Facing-0x0408-0x4035-/blob/main/uvc_driver.c
>
>   I offered to test the fix, so I tried to compile the module with the
>   new source.
>
>   COMPILING PROBLEMS
>   I’m running **Ubuntu 22.04.1 LTS, with kernel
>   giuliano@Astra2A:/usr/src$ cat /proc/version_signature
>   Ubuntu 5.15.0-56.62-generic 5.15.64
>
>   BUT  the linux-source that I found installed seems to be different
>   tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
>   lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 ->
> linux-source-5.15.0/linux-source-5.15.0.tar.bz2
>
>   I expanded  the tar file, configured the IDE and compiled without error
> any errors…
>   I manually copied the uvcvideo.ko in
>   /lib/modules/5.15.0-56-
>   sudo cp…...
>
>   then tryed to intall the new uvcvideo.ko module
>   sudo rmmod uvcvideo && sudo modprobe uvcvideo
>
>   BUT… IT FAILS
>   giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
>   modprobe: ERROR: could not insert 'uvcvideo': Exec format error
>
>   and dmesg shows
>   [25961.151982] usbcore: registered new interface driver uvcvideo
>   [26323.125534] usbcore: deregistering interface driver uvcvideo
>   [26323.189294] uvcvideo: disagrees about version of symbol module_layout
>
>
>   These are the TWO modinfo from the old and new uvcvideo modules
>   https://pastebin.com/tSj8Exm6
>   Basically
>   OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions
>   NEW module: vermagic: 5.15.64 SMP mod_unload modversions
>
>
>   -kindly ASK
>
>   HOW can FORCE the uvcdriver.c to match mi kernel version ?
>   Have I got OTHER ways to make the kernel module I’m compiling, match my
> running system ?
>
>   I would like to test the module so to confirm the patch and let it
>   enter the kernel main stream...
>
>
>   BR
>   Giuliano
>
>   PS
>   btw…. to allow Eclipse to compile the kernel, I had to pass this commands
>   scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
>   scripts/config --disable SYSTEM_REVOCATION_KEYS
>   scripts/config --disable SYSTEM_TRUSTED_KEYS
>
>   hope that this does not affect the module layout & checking
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu82.3
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  giuliano   2142 F pulseaudio
>/dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
>/dev/snd/controlC0:  giuliano   2142 F pulseaudio
>   CRDA: N/A
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 22.04
>   InstallationDate: Installed on 2022-11-03 (66 days ago)
>   InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
> (20220809.1)
>   MachineType: Acer Nitro AN517-55
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic
> root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   

[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

I just found many similar reports.

1. https://github.com/QubesOS/qubes-issues/issues/6923
2. https://gitlab.freedesktop.org/drm/amd/-/issues/2266
3. https://gitlab.freedesktop.org/drm/amd/-/issues/822

They all have the same amdgpu errors:

```
mar 01 23:01:25 workstation1 kernel: [drm:psp_load_non_psp_fw [amdgpu]] *ERROR* 
Failed to start rlc autoload
mar 01 23:01:25 workstation1 kernel: [drm:psp_resume [amdgpu]] *ERROR* PSP 
resume failed
mar 01 23:01:25 workstation1 kernel: [drm:amdgpu_device_fw_loading [amdgpu]] 
*ERROR* resume of IP block >
mar 01 23:01:25 workstation1 kernel: [drm] Skip scheduling IBs!
mar 01 23:01:25 workstation1 kernel: [drm] Skip scheduling IBs!
mar 01 23:01:25 workstation1 kernel: amdgpu :03:00.0: amdgpu: GPU reset(1) 
failed
mar 01 23:01:25 workstation1 kernel: amdgpu :03:00.0: amdgpu: GPU reset end 
with ret = -22
```

** Bug watch added: github.com/QubesOS/qubes-issues/issues #6923
   https://github.com/QubesOS/qubes-issues/issues/6923

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2266
   https://gitlab.freedesktop.org/drm/amd/-/issues/2266

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #822
   https://gitlab.freedesktop.org/drm/amd/-/issues/822

** Description changed:

  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen; in
  both cases it's completely unresponsive.
  
  The only way out is to force a reboot with the SYSRQ "REISUB" key combo.
  I tried switching VT with Ctrl+Alt+F{1-7}, but it does not respond.
  
  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.
- 
- I didn't have this problem with other flavors (used Xubuntu and Ubuntu,
- 22.04 and 22.10), so I guess it's a Kubuntu bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  

[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

It happened again. Notice the same amdgpu errors near the end.

** Attachment added: "second_freeze.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5650838/+files/second_freeze.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/2008118

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  I didn't have this problem with other flavors (used Xubuntu and
  Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+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 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

** Tags added: 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/2008118

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  I didn't have this problem with other flavors (used Xubuntu and
  Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+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 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

This only affects automatic suspension (activated by idle time).
Manually suspending the system works as expected.

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

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  I didn't have this problem with other flavors (used Xubuntu and
  Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+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 2008118] Re: Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

This contains the logs from the resume attempt that failed.

** Attachment added: "logs from the relevant boot (sudo journalctl -b -1)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5649176/+files/journalctl.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/2008118

Title:
  Freeze on resume from suspend (amdgpu errors)

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
  resuming from suspend-to-RAM, the system will freeze. Sometimes the
  screen is all black, while other times it is showing the lock screen;
  in both cases it's completely unresponsive.

  The only way out is to force a reboot with the SYSRQ "REISUB" key
  combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
  respond.

  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.

  I didn't have this problem with other flavors (used Xubuntu and
  Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1217 F pulseaudio
   /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+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 2008118] [NEW] Freeze on resume from suspend (amdgpu errors)

[Douglas Silva]

Public bug reported:

I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen; in
both cases it's completely unresponsive.

The only way out is to force a reboot with the SYSRQ "REISUB" key combo.
I tried switching VT with Ctrl+Alt+F{1-7}, but it does not respond.

From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.

I didn't have this problem with other flavors (used Xubuntu and Ubuntu,
22.04 and 22.10), so I guess it's a Kubuntu bug.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 1217 F pulseaudio
 /dev/snd/controlC1:  dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-60-generic N/A
 linux-backports-modules-5.15.0-60-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug jammy

** Description changed:

  I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
- resuming from suspend, the system will freeze. Sometimes the screen is
- all black, while other times it is showing the lock screen; in both
- cases it's completely unresponsive.
+ resuming from suspend-to-RAM, the system will freeze. Sometimes the
+ screen is all black, while other times it is showing the lock screen; in
+ both cases it's completely unresponsive.
  
  The only way out is to force a reboot with the SYSRQ "REISUB" key combo.
  
  From a quick look at the logs I can see that it shows a lot of red-
  colored error lines from the kernel about amdgpu.
  
  I didn't have this problem with other flavors (used Xubuntu and Ubuntu,
  22.04 and 22.10), so I guess it's a Kubuntu bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dsilva 1217 F pulseaudio
-  /dev/snd/controlC1:  dsilva 1217 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dsilva 1217 F pulseaudio
+  /dev/snd/controlC1:  dsilva 1217 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Feb 22 14:55:20 2023
  InstallationDate: Installed on 2023-02-19 (2 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-60-generic N/A
-  linux-backports-modules-5.15.0-60-generic  N/A
-  linux-firmware 20220329.git681281e4-0ubuntu3.10
+  linux-restricted-modules-5.15.0-60-generic N/A
+  linux-backports-modules-5.15.0-60-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
-  0: 

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Douglas]

Thanks for your support @giuliano69

With a broken heart, I ended up deciding to kiss Linux goodbye. At least for a 
while.
This process of compiling and searching for solutions does not fit into my 
day-to-day life.
In addition to the webcam problem, the headset microphone does not work, the 
video card depends on complex configuration to run on the notebook monitor and 
on the secondary monitor, the boot had to be corrected in txts, and even so it 
kept showing the annoying message " not enougth memory".
I need to use MS Teams for my work, and it works with limitations on Linux. So, 
bye linux, at least for now.

Today linux has -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/2000947

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware   

[Kernel-packages] [Bug 2007633] Re: amdgpu fails to init with kernel 5.19.0

[Douglas Wiedemann]

I'm having the same problem with one of my systems. Same family of GPU, Tahiti.
This bug https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249 
is very similar to what is happening. However, I'm able to get all the way to 
an X session, but functionality of the card is affected (can't change display 
refresh rate). Something must have changed, because the machine has the 
relevant firmware files in /lib/firmware/amdgpu.

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-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: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Douglas]

Same problema here!

I bougth a new Acer Nitro 5, and this problem is very boring.

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  

[Kernel-packages] [Bug 2000445] Re: Xbox game controller disabled after resuming from suspend

[Douglas Silva]

I thought it was a bug in the kernel, but I just found out it is
reproducible on Windows too. Closing.

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

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

Title:
  Xbox game controller disabled after resuming from suspend

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have an Xbox One controller plugged in to the computer via USB.
  Every time I resume from suspend (to RAM), the controller doesn't turn
  itself back on. Its lights are off, and it doesn't respond in any way.
  It still appears in `lsusb` output, though.

  ```
  Bus 001 Device 007: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller 
(model 1914)
  ```

  My workaround is to pull the plug and put it back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-26-generic 5.19.0-26.27
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1292 F pulseaudio
   /dev/snd/controlC1:  dsilva 1292 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Dec 25 20:06:37 2022
  InstallationDate: Installed on 2022-11-25 (30 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=UUID=55f3533e-1820-497b-ae27-0c1f7707b943 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-26-generic N/A
   linux-backports-modules-5.19.0-26-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000445/+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 2000445] Re: Xbox game controller disabled after resuming from suspend

[Douglas Silva]

** Description changed:

  I have an Xbox One controller plugged in to the computer via USB. Every
  time I resume from suspend (to RAM), the controller doesn't turn itself
- back on. Its lights are off, and it doesn't respond in any way.
+ back on. Its lights are off, and it doesn't respond in any way. It still
+ appears in `lsusb` output, though.
  
  ```
  Bus 001 Device 007: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller 
(model 1914)
  ```
  
  My workaround is to pull the plug and put it back on.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-26-generic 5.19.0-26.27
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dsilva 1292 F pulseaudio
-  /dev/snd/controlC1:  dsilva 1292 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dsilva 1292 F pulseaudio
+  /dev/snd/controlC1:  dsilva 1292 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Dec 25 20:06:37 2022
  InstallationDate: Installed on 2022-11-25 (30 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  IwConfig:
-  lono wireless extensions.
-  
-  enp6s0no wireless extensions.
-  
-  docker0   no wireless extensions.
+  lono wireless extensions.
+ 
+  enp6s0no wireless extensions.
+ 
+  docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=UUID=55f3533e-1820-497b-ae27-0c1f7707b943 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.19.0-26-generic N/A
-  linux-backports-modules-5.19.0-26-generic  N/A
-  linux-firmware 20220923.gitf09bebf3-0ubuntu1.1
+  linux-restricted-modules-5.19.0-26-generic N/A
+  linux-backports-modules-5.19.0-26-generic  N/A
+  linux-firmware 20220923.gitf09bebf3-0ubuntu1.1
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  Xbox game controller disabled after resuming from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Xbox One controller plugged in to the computer via USB.
  Every time I resume from suspend (to RAM), the controller doesn't turn
  itself back on. Its lights are off, and it doesn't respond in any way.
  It still appears in `lsusb` output, though.

  ```
  Bus 001 Device 007: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller 
(model 1914)
  ```

  My workaround is to pull the plug and put it back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-26-generic 5.19.0-26.27
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1292 F pulseaudio
   /dev/snd/controlC1:  dsilva 1292 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Dec 25 20:06:37 2022
  InstallationDate: Installed on 2022-11-25 (30 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=UUID=55f3533e-1820-497b-ae27-0c1f7707b943 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-26-generic N/A
   linux-backports-modules-5.19.0-26-generic  N/A
   linux-firmware   

[Kernel-packages] [Bug 2000445] [NEW] Xbox game controller disabled after resuming from suspend

[Douglas Silva]

Public bug reported:

I have an Xbox One controller plugged in to the computer via USB. Every
time I resume from suspend (to RAM), the controller doesn't turn itself
back on. Its lights are off, and it doesn't respond in any way. It still
appears in `lsusb` output, though.

```
Bus 001 Device 007: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller 
(model 1914)
```

My workaround is to pull the plug and put it back on.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-26-generic 5.19.0-26.27
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 1292 F pulseaudio
 /dev/snd/controlC1:  dsilva 1292 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sun Dec 25 20:06:37 2022
InstallationDate: Installed on 2022-11-25 (30 days ago)
InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
IwConfig:
 lono wireless extensions.

 enp6s0no wireless extensions.

 docker0   no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=UUID=55f3533e-1820-497b-ae27-0c1f7707b943 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-26-generic N/A
 linux-backports-modules-5.19.0-26-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
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.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug kinetic

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

Title:
  Xbox game controller disabled after resuming from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Xbox One controller plugged in to the computer via USB.
  Every time I resume from suspend (to RAM), the controller doesn't turn
  itself back on. Its lights are off, and it doesn't respond in any way.
  It still appears in `lsusb` output, though.

  ```
  Bus 001 Device 007: ID 045e:0b12 Microsoft Corp. Xbox Wireless Controller 
(model 1914)
  ```

  My workaround is to pull the plug and put it back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-26-generic 5.19.0-26.27
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1292 F pulseaudio
   /dev/snd/controlC1:  dsilva 1292 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Dec 25 20:06:37 2022
  InstallationDate: Installed on 2022-11-25 (30 days ago)
  InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=UUID=55f3533e-1820-497b-ae27-0c1f7707b943 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-26-generic N/A
   linux-backports-modules-5.19.0-26-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  

[Kernel-packages] [Bug 1978133] Re: System freeze followed by kernel panic or blank screen

[Douglas Silva]

I can no longer reproduce. Running Xubuntu 22.10.

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

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

Title:
  System freeze followed by kernel panic or blank screen

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Invalid

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1978133/+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 1978133] Re: System freeze followed by kernel panic or blank screen

[Douglas Silva]

** Bug watch added: Debian Bug tracker #1013211
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013211

** Also affects: linux via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013211
   Importance: Unknown
   Status: Unknown

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

Title:
  System freeze followed by kernel panic or blank screen

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

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1978133/+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 1975516] Re: System freeze

[Douglas Silva]

*** This bug is a duplicate of bug 1978133 ***
https://bugs.launchpad.net/bugs/1978133

** This bug has been marked a duplicate of bug 1978133
   System freeze followed by kernel panic or blank screen

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had LibreOffice Writer open at the time, but it was idle. The system
  became completely unresponsive and a power reset was the only way to
  shut it down. The "REISUB" command didn't work.

  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+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 1978133] Re: System freeze followed by kernel panic or blank screen

[Douglas Silva]

It happens more often when the laptop is idle.

In the logs I see a pattern of messages like:

"systemd-logind: hibernation is restricted; see man kernel_lockdown.7"

and they intensify right before the system hangs.

Secure boot is enabled, and hibernation is disabled by default. I only
use suspend-to-ram after 20 minutes of inactivity, set through GNOME
settings.

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

Title:
  System freeze followed by kernel panic or blank screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+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 1978133] Re: System freeze followed by kernel panic or blank screen

[Douglas Silva]

** Attachment added: "journalctl blank screen"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+attachment/5595973/+files/journalctl-blank-screen.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/1978133

Title:
  System freeze followed by kernel panic or blank screen

Status in linux package in Ubuntu:
  New

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+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 1978133] [NEW] System freeze followed by kernel panic or blank screen

[Douglas Silva]

Public bug reported:

System keeps freezing in many different circumstances. I don't know how
to reproduce this.

Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu
impish and Debian bullseye.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-37-generic 5.15.0-37.39
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 1593 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun  9 12:22:34 2022
InstallationDate: Installed on 2022-06-09 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 3583
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-37-generic N/A
 linux-backports-modules-5.15.0-37-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2022
dmi.bios.release: 1.19
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.0
dmi.board.name: 0DC2CG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "journalctl kernel panic"
   
https://bugs.launchpad.net/bugs/1978133/+attachment/5595953/+files/journalctl-kernel-panic.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/1978133

Title:
  System freeze followed by kernel panic or blank screen

Status in linux package in Ubuntu:
  New

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1975516] Re: System freeze

[Douglas Silva]

It happened again, with the laptop idle same as before.

This time the screen went dark (backlight off) and the fans were
spinning fast. I could feel the laptop was a bit hot.

I had Transmission, LibreOffice Writer and GNOME Files running at the
time.

** Attachment added: "journalctl log of the second freeze"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592731/+files/journalctl_2.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/1975516

Title:
  System freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had LibreOffice Writer open at the time, but it was idle. The system
  became completely unresponsive and a power reset was the only way to
  shut it down. The "REISUB" command didn't work.

  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

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

[Douglas Silva]

** Description changed:

  I had LibreOffice Writer open at the time, but it was idle. The system
- was completely unresponsive and a power reset was the only way to shut
- it down. The "REISUB" command didn't work.
+ became completely unresponsive and a power reset was the only way to
+ shut it down. The "REISUB" command didn't work.
  
  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dsilva 1511 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
-  Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
-  Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
-  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 003: ID 0c45:671e Microdia Integrated_Webcam_HD
+  Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-33-generic N/A
-  linux-backports-modules-5.15.0-33-generic  N/A
-  linux-firmware 20220329.git681281e4-0ubuntu3
+  linux-restricted-modules-5.15.0-33-generic N/A
+  linux-backports-modules-5.15.0-33-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had LibreOffice Writer open at the time, but it was idle. The system
  became completely unresponsive and a power reset was the only way to
  shut it down. The "REISUB" command didn't work.

  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  

[Kernel-packages] [Bug 1975516] Re: System freeze

[Douglas Silva]

** Attachment added: "dmesg log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592340/+files/dmesg.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/1975516

Title:
  System freeze

Status in linux package in Ubuntu:
  New

Bug description:
  I had LibreOffice Writer open at the time, but it was idle. The system
  was completely unresponsive and a power reset was the only way to shut
  it down. The "REISUB" command didn't work.

  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

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

[Douglas Silva]

Public bug reported:

I had LibreOffice Writer open at the time, but it was idle. The system
was completely unresponsive and a power reset was the only way to shut
it down. The "REISUB" command didn't work.

I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
with them.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-33-generic 5.15.0-33.34
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 1511 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 13:48:05 2022
InstallationDate: Installed on 2022-05-23 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 3583
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-33-generic N/A
 linux-backports-modules-5.15.0-33-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2021
dmi.bios.release: 1.13
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.13.0
dmi.board.name: 0DC2CG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "journalctl log"
   
https://bugs.launchpad.net/bugs/1975516/+attachment/5592320/+files/journalctl.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/1975516

Title:
  System freeze

Status in linux package in Ubuntu:
  New

Bug description:
  I had LibreOffice Writer open at the time, but it was idle. The system
  was completely unresponsive and a power reset was the only way to shut
  it down. The "REISUB" command didn't work.

  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug 

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Douglas Santos]

I've tried to change /etc/pulse/daemon.conf (default-sample-rate =
48000) but did not work for me.

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1966066] Re: audio from external sound card is distorted

[Douglas Santos]

I have the same issue, but with another USB sound device: Yamaha Thr10x
amp (which is also an audio interface).

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19)

[Douglas Silva]

I'm now using Ubuntu 21.04 hirsute, and this bug can no longer be
reproduced :) Kernel 5.11.0-25-generic.

I've done 3 tests. No crashes so far.

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] acpidump.txt

[Douglas Silva]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479070/+files/acpidump.txt

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

** Changed in: linux-hwe-5.8 (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/1917674

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications 

[Kernel-packages] [Bug 1917674] WifiSyslog.txt

[Douglas Silva]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479069/+files/WifiSyslog.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] UdevDb.txt

[Douglas Silva]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1917674/+attachment/5479068/+files/UdevDb.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] ProcModules.txt

[Douglas Silva]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479066/+files/ProcModules.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] Lsusb-v.txt

[Douglas Silva]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479062/+files/Lsusb-v.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] ProcInterrupts.txt

[Douglas Silva]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479065/+files/ProcInterrupts.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] CRDA.txt

[Douglas Silva]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1917674/+attachment/5479056/+files/CRDA.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] IwConfig.txt

[Douglas Silva]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479058/+files/IwConfig.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] Lspci.txt

[Douglas Silva]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1917674/+attachment/5479059/+files/Lspci.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] ProcCpuinfo.txt

[Douglas Silva]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479063/+files/ProcCpuinfo.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] Lsusb-t.txt

[Douglas Silva]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479061/+files/Lsusb-t.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/1917674

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] ProcCpuinfoMinimal.txt

[Douglas Silva]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479064/+files/ProcCpuinfoMinimal.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] CurrentDmesg.txt

[Douglas Silva]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479057/+files/CurrentDmesg.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] Lspci-vt.txt

[Douglas Silva]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479060/+files/Lspci-vt.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/1917674

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1884 F pulseaudio
   /dev/snd/controlC1:  dsilva 1884 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-31 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
   Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
  Package: linux-hwe-5.8
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  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.8.0-45-generic N/A
   linux-backports-modules-5.8.0-45-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/27/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: B460M DS3H
  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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B460 MB
  dmi.product.name: B460MDS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM (started in 5.7.0, not in 5.6.19)

[Douglas Silva]

apport information

** Tags added: apport-collected

** Description changed:

  Automatic suspension causes the system to freeze on resume. This doesn't
  happen if I suspend it manually by opening the system menu and pressing
  the suspend button. Suspension works flawlessly when it is triggered
  manually.
  
  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says something
  like "system will suspend shortly due to inactivity". It never goes
  away.
  
  The keyboard responds during this (at least for a while). The CAPS LOCK
  LED turns on and off as I press it (with no delay). Sometimes I can even
  switch to another TTY and kill the X server, which is why I'm reporting
  it against gnome-shell. When switching TTY is impossible, I use the
  "REISUB" combination to shut down. Either way, I always lose the running
  session.
  
  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.
  
  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dsilva 1884 F pulseaudio
+  /dev/snd/controlC1:  dsilva 1884 F pulseaudio
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-01-31 (49 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 004: ID 0951:16de Kingston Technology HyperX Pulsefire Core
+  Bus 001 Device 003: ID 0951:16d2 Kingston Technology HyperX Alloy FPS Pro 
Mechanical Gaming Keyboard
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
+ Package: linux-hwe-5.8
+ ProcEnviron:
+  LANGUAGE=pt_BR:pt:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
+ 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.8.0-45-generic N/A
+  linux-backports-modules-5.8.0-45-generic  N/A
+  linux-firmware1.187.10
+ RfKill:
+  
+ Tags:  focal
+ Uname: Linux 5.8.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 05/27/2020
+ dmi.bios.release: 5.17
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F3
+ dmi.board.asset.tag: Default string
+ dmi.board.name: B460M DS3H
+ 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.:bvrF3:bd05/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: B460 MB
+ dmi.product.name: B460MDS3H
+ dmi.product.sku: Default string
+ dmi.product.version: Default string
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1917674/+attachment/5479055/+files/AlsaInfo.txt

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM
  (started in 5.7.0, not in 5.6.19)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend 

[Kernel-packages] [Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM

[Douglas Silva]

Kernel 5.6.19: OK

If I'm not mistaken, this was the last version before 5.7, so the bug
must have been introduced in 5.7.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/1917674

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM

[Douglas Silva]

I've finished the tests, here are the results:

5.0.0: OK
5.4.0: OK
5.6.0: OK
5.7.0: BUG
5.8.0: 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/1917674

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM

[Douglas Silva]

Nevermind, I was running 5.8, not 5.0.0. I forgot to select 5.0.0 in the
boot menu.

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

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM

[Douglas Silva]

I was able to reproduce this with kernel 5.0.0 too. Isn't it possible
that this is not caused by the kernel? I don't think I had this issue
back then - it's something more recent.

** Attachment added: "Logs from a previous session that crashed with kernel 
5.0.0"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+attachment/5476815/+files/prevboot.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/1917674

Title:
  [amdgpu] kernel crash when resuming from automatic suspension to RAM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Automatic suspension causes the system to freeze on resume. This
  doesn't happen if I suspend it manually by opening the system menu and
  pressing the suspend button. Suspension works flawlessly when it is
  triggered manually.

  When the system resumes from automatic suspension, the lock screen is
  visible but does not respond. It's frozen. A notification says
  something like "system will suspend shortly due to inactivity". It
  never goes away.

  The keyboard responds during this (at least for a while). The CAPS
  LOCK LED turns on and off as I press it (with no delay). Sometimes I
  can even switch to another TTY and kill the X server, which is why I'm
  reporting it against gnome-shell. When switching TTY is impossible, I
  use the "REISUB" combination to shut down. Either way, I always lose
  the running session.

  This is reproducible about 60% of the time. Eventually I ended up
  disabling it and relying only on manual suspension.

  # Additional information:
  1) Ubuntu 20.04.2 LTS / Release: 20.04
  2) gnome-shell 3.36.4-1ubuntu1~20.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  3 16:56:01 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-01-31 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+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 1908894] Re: USB controllers disconnects after random time

[Simon Douglas]

Can report today the same issue - this happened on my Asrock x300
running popos 20.04 LTS

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

Title:
  USB controllers disconnects after random time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu on my new convertible laptop, I got issues with the 
USB. Just after boot my USB controller is working properly (I can connect usb 
sticks, mices, and my internal camera works) and at some point long after it 
suddenly stop working (mices suddenly stop moving even when used, webcam and 
sticks no more detected).
  This can happend few minuts after boot, or several days after.
  Yet I have not been able to find what triggers the failure. It happends at 
any time during normal usage of the computer, including during the usb usage.

  more concrete infos:
  after failure, I get
  $ dmesg

  [ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
  [ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq 
Ptr command & xHCI internal state.
  [ 3262.197927] xhci_hcd :03:00.3: ep deq seg = 8dafef36, deq ptr 
= 5f96ce32
  [ 3262.198052] xhci_hcd :03:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x]
  [ 3267.250397] xhci_hcd :03:00.3: xHCI host not responding to stop 
endpoint command.
  [ 3267.250428] xhci_hcd :03:00.3: xHCI host controller not responding, 
assume dead
  [ 3267.250463] xhci_hcd :03:00.3: HC died; cleaning up
  [ 3267.250499] usb 1-3: USB disconnect, device number 2
  [ 3267.311251] usb 1-4: USB disconnect, device number 3

  and lsusb doesn't show my devices anymore, even the newly inserted
  ones

  config: Asus Zenbook flip 14 UM462DA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jimy   1523 F pulseaudio
   /dev/snd/controlC0:  jimy   1523 F pulseaudio
   /dev/snd/pcmC1D0p:   jimy   1523 F...m pulseaudio
   /dev/snd/timer:  jimy   1523 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Dec 21 11:51:08 2020
  InstallationDate: Installed on 2020-07-28 (146 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 003 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX462DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=ba0f4ac4-b614-4882-83d6-485690f9a61a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX462DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX462DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX462DA.307:bd09/28/2020:svnASUSTeKCOMPUTERINC.:pnZenBookUX462DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX462DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX462DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908894/+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 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

[Douglas]

My Notebook is a Acer Aspire E5-573G-72UF

With headset pluged or not:

sudo hdajacksensetest -a 
Pin 0x05 ( Digital Out, HDMI): present = No
Pin 0x06 ( Digital Out, HDMI): present = No
Pin 0x07 ( Digital Out, HDMI): present = No


My headset is an Hyper-X Cloud Stinger.



** Attachment added: "My als-info"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821269/+attachment/5366862/+files/alsa-info.txt.aZ2lbL86WS

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821269/+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 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

[Douglas]

My Notebook is a Acer Aspire E5-573G-72UF

With headset pluged or not:

sudo hdajacksensetest -a 
Pin 0x05 ( Digital Out, HDMI): present = No
Pin 0x06 ( Digital Out, HDMI): present = No
Pin 0x07 ( Digital Out, HDMI): present = No


My headset is an Hyper-X Cloud Stinger.



** Attachment added: "My als-info"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821269/+attachment/5366861/+files/alsa-info.txt.aZ2lbL86WS

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821269/+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 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

[Douglas]

Hello!

I have the same problem as my friend! I tried to follow the steps, but I
believe that something I did on other tests may be causing the problem.
Can anyone help me check what may be wrong?

Note: My primary system is Mint 19.3, but I just ran the test on Ubuntu 20.04 
live and the latest ubuntu doesn't work either.
I have dual boot with windows, and it works there :(


Thanks

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821269/+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 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters

[Douglas Silva]

You mean I should try an older version? Then I think I should try v5.0.x
first. As you can see, it takes time to reproduce it again. I don't know
how to intentionally reproduce 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/1860793

Title:
  [amdgpu] Severe freezes that begin with minor stutters

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

Bug description:
  It starts with very subtle stuttering that you notice when moving
  windows around, then keeps getting worse and worse until it starts
  freezing the UI for many seconds. I could only reproduce it twice in a
  couple of days.

  The applications open at the time are usually Atom, Firefox, Hexchat,
  GNOME Files and occasionally Eye of GNOME. I checked resource
  consumption at the time of the stutters. Memory consumption was about
  50% of 8GB, while the swap partition was nearly full (after a long
  gaming session). Storage device is a SATA SSD. During the stutters and
  freezes, CPU usage is normal. Through the process list of System
  Monitor I cannot see any application overusing resources. Temperatures
  are also normal.

  One potentially problematic hardware device is the GPU: AMD RX 560 4GB
  (open source AMDGPU). Its temperature and fan speed were also normal
  at the time.

  I know my system is capable of handling this workload. Also, this is
  only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of
  Ubuntu (18.04.3) is unaffected. I have used it for months before
  switching to the latest non-LTS version.

  What I've tried to stop the freezes:
  - Closed all running applications and waited.

  It didn't improve the situation, so I restarted my user session. The
  freezes continued, so I performed a system reboot, which finally
  helped normalize things.

  I did not try to reproduce this on the Wayland session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 11:13:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-12-27 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860793/+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 1838878] Re: Branch 430 does not support K1100M

[Douglas Russell]

Perhaps even more problematic is that the .430 driver does not have
support for the new T4 cards, whereas .418 does.

I am not an expert on Nvidia drivers, but it is very surprising to me
that the older version of the driver has support for a new piece of
hardware where the new driver does not, but either way, it would be very
useful to be able to install actual .418 driver on Ubuntu 18.04.

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

Title:
  Branch 430 does not support K1100M

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  New

Bug description:
  Branch 430 does not support K1100M, yet it is proposed as an update to
  branch 418 users with an nVidia K1100M GPU.

  Please see supported devices for 430 branch here
  https://www.nvidia.com/Download/driverResults.aspx/149138/en-us

  and 418 branch here
  https://www.nvidia.com/Download/driverResults.aspx/149219/en-us

  It is not possible to downgrade to 418 because the ppa package was
  replaced by a "transition layer" to branch 430.

  No changelog was presented by synaptic prior to upgrade to inform user
  that the nVidia K1100M support was dropped.

  $ apt-cache showpkg nvidia-driver-418
  Package: nvidia-driver-418
  Versions: 
  430.40-0ubuntu0~gpu18.04.1 
(/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages)
   Description Language: 
   File: 
/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages
MD5: 4827e73f0efd6022196ef03ec384d854
   Description Language: en
   File: 
/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_i18n_Translation-en
MD5: 4827e73f0efd6022196ef03ec384d854

  
  Reverse Depends: 
  Dependencies: 
  430.40-0ubuntu0~gpu18.04.1 - nvidia-driver-430 (0 (null)) 
  Provides: 
  430.40-0ubuntu0~gpu18.04.1 - 
  Reverse Provides:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1838878/+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 1830662] Re: Monitor does not wake up on input after DPMS turns it off, pressing the monitor power button wakes it up

[Douglas Silva]

Tested kernel 5.2-rc2. The issue is still reproducible.

To clarify it a bit more, let me explain that this happens when the
screen turns off by inactivity (screen locks) and also when you suspend
to RAM and then resume. The monitor will not turn back on when you press
any key.

I can continue pressing keys and mouse buttons, but it will remain dark.
I turn on the monitor manually, and I see the screen locker there
showing in the password input box that I've been pressing keys while the
monitor was dark.

However, when the computer hibernates or is shut down, and you turn it
on again, the monitor will go from standby to the powered on state, as
it should.

** Description changed:

  After the screen turns off (for inactivity, screen lock, etc.), mouse or
  keyboard input won't bring it back. When I come back to the computer to
  resume my work, I have to wake the system up, and press the power button
  on the monitor. If I don't manually bring the monitor back on, the
  system will resume and the screen will remain off.
  
  I believe this is a regression, because this cannot be reproduced in
  distributions as old as Debian Stretch 9. Any distribution newer than
- Debian causes this problem. This is also not reproducible on Windows 10.
+ Debian causes this problem, no matter what Desktop Environment, what
+ Display Manager or Screen Locker I choose. This is also not reproducible
+ on Windows 10.
  
  It's worth mentioning that this desktop runs the RX 560 AMD graphics card.
  Also, this is my monitor: https://www.lg.com/in/monitors/lg-22MP58VQ
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dsilva 1883 F pulseaudio
-  /dev/snd/controlC1:  dsilva 1883 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dsilva 1883 F pulseaudio
+  /dev/snd/controlC1:  dsilva 1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 27 22:45:13 2019
  InstallationDate: Installed on 2019-05-26 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
-  enp2s0no wireless extensions.
-  
-  lono wireless extensions.
+  enp2s0no wireless extensions.
+ 
+  lono wireless extensions.
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0951:16bc Kingston Technology 
-  Bus 001 Device 002: ID 0951:16d2 Kingston Technology 
-  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 003: ID 0951:16bc Kingston Technology
+  Bus 001 Device 002: ID 0951:16d2 Kingston Technology
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-15-generic N/A
-  linux-backports-modules-5.0.0-15-generic  N/A
-  linux-firmware1.178.1
+  linux-restricted-modules-5.0.0-15-generic N/A
+  linux-backports-modules-5.0.0-15-generic  N/A
+  linux-firmware1.178.1
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M GAMING HD
  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.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B360M GAMING HD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  Monitor does not wake up on input after DPMS turns it off, pressing
  the monitor power button wakes it up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the screen turns off (for inactivity, screen lock, etc.), mouse
  or keyboard input won't bring it back. When I come back to the
  computer to resume my work, I have to wake the system up, and press
  

[Kernel-packages] [Bug 1830652] Re: On shutdown, peripherals turn off, but fans keep spinning, power LED is lit and screen is frozen at the plymouth screen

[Douglas Silva]

I can no longer reproduce this with kernel 5.1.5.

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

Title:
  On shutdown, peripherals turn off, but fans keep spinning, power LED
  is lit and screen is frozen at the plymouth screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On shutdown, peripherals turn off (keyboard, mouse), but fans keep
  spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
  plymouth screen (no animations, frozen frame). The keyboard is turned
  off at this point, so the only way to properly shut down the computer
  is to press the power switch on the case for a few seconds.

  Without plymouth, the screen turns off as it should, but the other
  symptoms persist, such as fans never stop, power LED never turns off.

  Reboot works flawlessly. So does suspending and hibernating.

  This is currently reproducible on Arch Linux (Linux 5.1.4.arch1-1).
  See bug report: https://bugs.archlinux.org/task/62539.

  This is NOT reproducible on Ubuntu 18.10 or older. It started
  somewhere after Linux 5.0.X.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1883 F pulseaudio
   /dev/snd/controlC1:  dsilva 1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 27 18:27:29 2019
  InstallationDate: Installed on 2019-05-26 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0951:16bc Kingston Technology
   Bus 001 Device 002: ID 0951:16d2 Kingston Technology
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M GAMING HD
  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.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B360M GAMING HD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830652/+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 1830662] [NEW] Monitor does not wake up on input after DPMS turns it off, pressing the monitor power button wakes it up

[Douglas Silva]

Public bug reported:

After the screen turns off (for inactivity, screen lock, etc.), mouse or
keyboard input won't bring it back. When I come back to the computer to
resume my work, I have to wake the system up, and press the power button
on the monitor. If I don't manually bring the monitor back on, the
system will resume and the screen will remain off.

I believe this is a regression, because this cannot be reproduced in
distributions as old as Debian Stretch 9. Any distribution newer than
Debian causes this problem. This is also not reproducible on Windows 10.

It's worth mentioning that this desktop runs the RX 560 AMD graphics card.
Also, this is my monitor: https://www.lg.com/in/monitors/lg-22MP58VQ

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 1883 F pulseaudio
 /dev/snd/controlC1:  dsilva 1883 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon May 27 22:45:13 2019
InstallationDate: Installed on 2019-05-26 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0951:16bc Kingston Technology 
 Bus 001 Device 002: ID 0951:16d2 Kingston Technology 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-15-generic N/A
 linux-backports-modules-5.0.0-15-generic  N/A
 linux-firmware1.178.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12
dmi.board.asset.tag: Default string
dmi.board.name: B360M GAMING HD
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.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B360M GAMING HD
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug disco

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

Title:
  Monitor does not wake up on input after DPMS turns it off, pressing
  the monitor power button wakes it up

Status in linux package in Ubuntu:
  New

Bug description:
  After the screen turns off (for inactivity, screen lock, etc.), mouse
  or keyboard input won't bring it back. When I come back to the
  computer to resume my work, I have to wake the system up, and press
  the power button on the monitor. If I don't manually bring the monitor
  back on, the system will resume and the screen will remain off.

  I believe this is a regression, because this cannot be reproduced in
  distributions as old as Debian Stretch 9. Any distribution newer than
  Debian causes this problem. This is also not reproducible on Windows
  10.

  It's worth mentioning that this desktop runs the RX 560 AMD graphics card.
  Also, this is my monitor: https://www.lg.com/in/monitors/lg-22MP58VQ

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1883 F pulseaudio
   /dev/snd/controlC1:  dsilva 1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 27 22:45:13 2019
  InstallationDate: Installed on 2019-05-26 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0951:16bc Kingston Technology 
   Bus 001 Device 002: ID 0951:16d2 Kingston Technology 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  

[Kernel-packages] [Bug 1830652] Re: On shutdown, peripherals turn off, but fans keep spinning, power LED is lit and screen is frozen at the plymouth screen

[Douglas Silva]

** Description changed:

  On shutdown, peripherals turn off (keyboard, mouse), but fans keep
  spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
  plymouth screen (no animations, frozen frame). The keyboard is turned
  off at this point, so the only way to properly shut down the computer is
  to press the power switch on the case for a few seconds.
  
  Without plymouth, the screen turns off as it should, but the other
  symptoms persist, such as fans never stop, power LED never turns off.
+ 
+ Reboot works flawlessly. So does suspending and hibernating.
  
  This is currently reproducible on Arch Linux (Linux 5.1.4.arch1-1). See
  bug report: https://bugs.archlinux.org/task/62539.
  
  This is NOT reproducible on Ubuntu 18.10 or older. It started somewhere
  after Linux 5.0.X.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dsilva 1883 F pulseaudio
-  /dev/snd/controlC1:  dsilva 1883 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dsilva 1883 F pulseaudio
+  /dev/snd/controlC1:  dsilva 1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 27 18:27:29 2019
  InstallationDate: Installed on 2019-05-26 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
-  enp2s0no wireless extensions.
-  
-  lono wireless extensions.
+  enp2s0no wireless extensions.
+ 
+  lono wireless extensions.
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0951:16bc Kingston Technology 
-  Bus 001 Device 002: ID 0951:16d2 Kingston Technology 
-  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 003: ID 0951:16bc Kingston Technology
+  Bus 001 Device 002: ID 0951:16d2 Kingston Technology
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-15-generic N/A
-  linux-backports-modules-5.0.0-15-generic  N/A
-  linux-firmware1.178.1
+  linux-restricted-modules-5.0.0-15-generic N/A
+  linux-backports-modules-5.0.0-15-generic  N/A
+  linux-firmware1.178.1
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: B360M GAMING HD
  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.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B360M GAMING HD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  On shutdown, peripherals turn off, but fans keep spinning, power LED
  is lit and screen is frozen at the plymouth screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On shutdown, peripherals turn off (keyboard, mouse), but fans keep
  spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
  plymouth screen (no animations, frozen frame). The keyboard is turned
  off at this point, so the only way to properly shut down the computer
  is to press the power switch on the case for a few seconds.

  Without plymouth, the screen turns off as it should, but the other
  symptoms persist, such as fans never stop, power LED never turns off.

  Reboot works flawlessly. So does suspending and hibernating.

  This is currently reproducible on Arch Linux (Linux 5.1.4.arch1-1).
  See bug report: https://bugs.archlinux.org/task/62539.

  This is NOT reproducible on Ubuntu 18.10 or older. It started
  somewhere after Linux 5.0.X.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 

[Kernel-packages] [Bug 1830652] [NEW] On shutdown, peripherals turn off, but fans keep spinning, power LED is lit and screen is frozen at the plymouth screen

[Douglas Silva]

Public bug reported:

On shutdown, peripherals turn off (keyboard, mouse), but fans keep
spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
plymouth screen (no animations, frozen frame). The keyboard is turned
off at this point, so the only way to properly shut down the computer is
to press the power switch on the case for a few seconds.

Without plymouth, the screen turns off as it should, but the other
symptoms persist, such as fans never stop, power LED never turns off.

Reboot works flawlessly. So does suspending and hibernating.

This is currently reproducible on Arch Linux (Linux 5.1.4.arch1-1). See
bug report: https://bugs.archlinux.org/task/62539.

This is NOT reproducible on Ubuntu 18.10 or older. It started somewhere
after Linux 5.0.X.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 1883 F pulseaudio
 /dev/snd/controlC1:  dsilva 1883 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon May 27 18:27:29 2019
InstallationDate: Installed on 2019-05-26 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
 enp2s0no wireless extensions.

 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0951:16bc Kingston Technology
 Bus 001 Device 002: ID 0951:16d2 Kingston Technology
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-15-generic N/A
 linux-backports-modules-5.0.0-15-generic  N/A
 linux-firmware1.178.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12
dmi.board.asset.tag: Default string
dmi.board.name: B360M GAMING HD
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.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B360M GAMING HD
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug disco

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

Title:
  On shutdown, peripherals turn off, but fans keep spinning, power LED
  is lit and screen is frozen at the plymouth screen

Status in linux package in Ubuntu:
  New

Bug description:
  On shutdown, peripherals turn off (keyboard, mouse), but fans keep
  spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu
  plymouth screen (no animations, frozen frame). The keyboard is turned
  off at this point, so the only way to properly shut down the computer
  is to press the power switch on the case for a few seconds.

  Without plymouth, the screen turns off as it should, but the other
  symptoms persist, such as fans never stop, power LED never turns off.

  Reboot works flawlessly. So does suspending and hibernating.

  This is currently reproducible on Arch Linux (Linux 5.1.4.arch1-1).
  See bug report: https://bugs.archlinux.org/task/62539.

  This is NOT reproducible on Ubuntu 18.10 or older. It started
  somewhere after Linux 5.0.X.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1883 F pulseaudio
   /dev/snd/controlC1:  dsilva 1883 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 27 18:27:29 2019
  InstallationDate: Installed on 2019-05-26 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0951:16bc Kingston Technology
   

[Kernel-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Douglas Crooke]

OK, installing old kernels seems to be beyond me at the moment, trying
to install 4.20 & 4.19 following https://seagullbird.xyz/posts/how-to-
install-an-older-kernel/ or some askubuntu results so far leaves me with
non-booting kernels.  Is there a reliable beginners guide somewhere I
can follow?

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Douglas Crooke]

Using Gnome 3.32.1 on Xorg, (vanilla Ubuntu).
Current kernel 5.0.0-15-generic, same behaviour in 5.0.0-13-generic

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Douglas Crooke]

Re: #7 - I'm running vanilla Ubuntu on Xorg / Gnome shell.

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Douglas Crooke]

HP Pavilion model G6-2264sa

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+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 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

[Douglas Crooke]

Also have same symptoms following 19.04 upgrade.

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

teresaejunior, could you try that:

"Can you try 4.20-rc2 and boot with kernel parameter `pcie_aspm=off`?"

I suggest first trying 4.20-rcX and seeing if it freezes at least once.
If it does, try booting for a few days with pcie_aspm=off in the kernel
parameters. Post back results.

I can't do that right now, because I'm not currently running Ubuntu
18.10.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

** Attachment added: "output of journalctl -b -1 -k"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+attachment/5212302/+files/journal2.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/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

It happened again.
See the attachment of the output of journalctl -b -1 -k

This time I was just editing the position of widgets on the xfce4-panel.
I think it was around 11:45 on the clock.

And I do not have a .cache/thumbnails/fail folder.

** Also affects: linux (Arch Linux)
   Importance: Undecided
   Status: New

** No longer affects: linux (Arch Linux)

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

I have updated to A16 and so far no freezes, although it's still not
uncommon for these to stop happening for a while and then return.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

The problem is, it could take days before the system freezes. I don't
know how to reproduce, it simply happens. I don't even know where to
start. Maybe 4.17-rc1 and so on. But that's a huge task and one needs a
lot of patience to do it. I'm not sure I'll be able to.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

** Description changed:

  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then
  I try the "REISUB" command, but it doesn't do anything either. Only a
  hard reset works, pressing down the power button for a few seconds.
  
  How to reproduce?
- I couldn't figure out a consistent method. It is still random to me, although 
it seems to happen more often when I'm running Xfce (Xubuntu) on a recent 
kernel (4.17+). Xfce's default image viewer seems to be connected to it, as 
well. Most of the time I was having multiple instances of it when everything 
froze.
+ I couldn't figure out a consistent method. It is still random to me.
  
  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.
  
  Also happens under Arch Linux and Fedora.
+ I've talked to another user on IRC who seems to be having the same freezes.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  dsilva 1213 F pulseaudio
-  /dev/snd/controlC0:  dsilva 1213 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  dsilva 1213 F pulseaudio
+  /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-10-generic N/A
-  linux-backports-modules-4.18.0-10-generic  N/A
-  linux-firmware 1.175
+  linux-restricted-modules-4.18.0-10-generic N/A
+  linux-backports-modules-4.18.0-10-generic  N/A
+  linux-firmware 1.175
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

Affects the latest mainline build 4.19-rc8 as well.

Still cannot identify one way to reproduce it intentionally, although
most of the time it happens when I have a video playing and/or multiple
images being displayed with the image viewer.

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me, although 
it seems to happen more often when I'm running Xfce (Xubuntu) on a recent 
kernel (4.17+). Xfce's default image viewer seems to be connected to it, as 
well. Most of the time I was having multiple instances of it when everything 
froze.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

I am failing to boot from this new kernel. Downloaded the amd64 build
files, 'sudo dpkg -i ' on each of them, but upon trying to boot
from the new entries, it stops with "you need to load the kernel first".
I really need some help figuring out my mistake here. I did my homework
but no solutions yet. First time doing 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/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me, although 
it seems to happen more often when I'm running Xfce (Xubuntu) on a recent 
kernel (4.17+). Xfce's default image viewer seems to be connected to it, as 
well. Most of the time I was having multiple instances of it when everything 
froze.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

This is the bug report opened for Arch Linux [TASK FS#59483]:

https://bugs.archlinux.org/task/59483?string=freeze=1%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=%5B0%5D=open%5B0%5D

The OP reports 4.17.10-1 being the problematic kernel version. What I
can say for sure is that this problem did not exist in kernel versions
4.16 and older.

Yes, I can try the newest kernel, however these freezes are random and I
don't know how to trigger them. I will take some time to experiment with
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/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me, although 
it seems to happen more often when I'm running Xfce (Xubuntu) on a recent 
kernel (4.17+). Xfce's default image viewer seems to be connected to it, as 
well. Most of the time I was having multiple instances of it when everything 
froze.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1798961] [NEW] Random unrecoverable freezes on Ubuntu 18.10

[Douglas H. Silva]

Public bug reported:

First thing I notice is that the mouse cursor freezes as I'm using it,
then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then
I try the "REISUB" command, but it doesn't do anything either. Only a
hard reset works, pressing down the power button for a few seconds.

How to reproduce?
I couldn't figure out a consistent method. It is still random to me, although 
it seems to happen more often when I'm running Xfce (Xubuntu) on a recent 
kernel (4.17+). Xfce's default image viewer seems to be connected to it, as 
well. Most of the time I was having multiple instances of it when everything 
froze.

Version: Ubuntu 4.18.0-10.11-generic 4.18.12
System information attached.

Also happens under Arch Linux and Fedora.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dsilva 1213 F pulseaudio
 /dev/snd/controlC0:  dsilva 1213 F pulseaudio
CurrentDesktop: XFCE
Date: Sat Oct 20 09:54:50 2018
InstallationDate: Installed on 2018-10-20 (0 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: Dell Inc. Inspiron 5458
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic  N/A
 linux-firmware 1.175
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 09WGNT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5458
dmi.product.sku: Inspiron 5458
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "system hardware information"
   
https://bugs.launchpad.net/bugs/1798961/+attachment/5203301/+files/lspci-vnvn.log

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  New

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me, although 
it seems to happen more often when I'm running Xfce (Xubuntu) on a recent 
kernel (4.17+). Xfce's default image viewer seems to be connected to it, as 
well. Most of the time I was having multiple instances of it when everything 
froze.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal

[Douglas Lehr]

I can verify from IBM's standpoint, that we were able to use Volta gpu's
with POWER9.  The Nvidia driver enabled correctly.

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

Title:
  [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable
  Nvidia driver on bare metal

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  12 kernel patches have been identified as needed to support Nvidia Volta 
  on bare metal. All are accepted upstream in 4.17. Three of those are 
  already in bionic, leaving a total of 9 remaining commits needed in bionic.
  This pull request is for those other 9 commits.

  == Regression Potential ==
  All of the commits are specific to powerpc.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.


  == Comment: #0 - Barry B. Arndt  - 2018-05-23 13:40:33 ==
  12 kernel patches have been identified as needed to support Nvidia Volta on 
bare metal.  All are accepted upstream in 4.17.  Three of those are already in 
bionic, leaving a total of 9 remaining commits needed in bionic.  Those 9 
commits are:

  720c84046c26  powerpc/npu-dma.c: Fix crash after __mmu_notifier_register 
failure
  2b74e2a9b39d  powerpc/powernv/npu: Fix deadlock in mmio_invalidate()
  5ee573e8ef03  powerpc/powernv/mce: Don't silently restart the machine
  fb5924fddf9e  powerpc/mm: Flush cache on memory hot(un)plug
  7fd6641de28f  powerpc/powernv/memtrace: Let the arch hotunplug code flush 
cache
  28a5933e8d36  powerpc/powernv/npu: Add lock to prevent race in concurrent 
context init/destroy
  a1409adac748  powerpc/powernv/npu: Prevent overwriting of 
pnv_npu2_init_contex() callback parameters
  d0cf9b561ca9  powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a 
large address range
  75ecfb49516c  powerpc/mce: Fix a bug where mce loops on memory UE.

  We cherry-picked the commits, and all applied cleanly.  The resultant
  kernel built successfully and loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1772991/+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 1716258] Re: Keyboard input temporarily ignored when typing root encryption password

[Douglas H. Silva]

Tested kernel 4.13.4-200.fc26.x86_64, and is still reproducible. Arch is
free from this bug, but Fedora and Debian are not.

** Tags removed: kernel-fixed-upstream

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

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1716258] Re: Keyboard input temporarily ignored when typing root encryption password

[Douglas H. Silva]

Tested kernel 4.13 in Arch Linux. Cannot reproduce the bug with it.
Fedora is in 4.12.14-300.fc26 and is still reproducible there.

** Tags added: kernel-fixed-upstream

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

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1716258] Re: Keyboard input temporarily ignored when typing root encryption password

[Douglas H. Silva]

Sorry, can you tell me how to install the 4.13 kernel in Debian? It's
useless to do it in Ubuntu. As I said, Ubuntu is not affected. I might
have reported in the wrong place.

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

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1716258] Re: Keyboard input temporarily ignored when typing root encryption password

[Douglas H. Silva]

Fedora's kernel version: 4.12.13-300.fc26.x86_64
Debian's kernel version: 4.9.0-3-amd64

Both are affected. Ubuntu LTS is not, though. I don't remember 17.04.

I can install the mainline 4.13 kernel for Fedora. If Ubuntu is really
needed, I don't mind installing it 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/1716258

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1716258] [NEW] Keyboard input temporarily ignored when typing root encryption password

[Douglas H. Silva]

Public bug reported:

Symptoms:

The computer begins its boot process, then the root decryption password
prompt appears (via Plymouth) and I start typing. The first letters are
caught, but some letters are not captured. It's as if the keyboard shut
down during a few seconds and then returned, and I could type the whole
password properly.

Things I tried:

- Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
- Typing decryption password without Plymouth (this is not a Plymouth bug).


This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and possibly 
others. It cannot be reproduced with Ubuntu or other distributions with old 
packages. Some component introduced this problem recently.

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

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  New

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1709554] Re: package linux-image-4.4.0-89-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before installi

[Douglas Leeder]

apt-get -f install worked once I'd remounted /boot

I guess it would be nicer to report the problem more clearly, but I've
resolved it for me.

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

Title:
  package linux-image-4.4.0-89-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-89-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apt upgrade - not sure what failed.

  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-89-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-85.108-generic 4.4.73
  Uname: Linux 4.4.0-85-generic i686
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1966 F pulseaudio
lightdm   22384 F pulseaudio
  Date: Wed Aug  9 08:10:00 2017
  DuplicateSignature:
   package:linux-image-4.4.0-89-generic:(not installed)
   Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=2531f67d-911e-48ef-949a-9e660522b701
  InstallationDate: Installed on 2016-04-28 (467 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 05dc:a83a Lexar Media, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 024: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer NC-ES1-131-C0XB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-85-generic 
root=UUID=e8c99506-8652-4a33-bbd4-51b8b006dc17 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-4.4.0-89-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd11/13/2015:svnAcer:pnNC-ES1-131-C0XB:pvrV1.20:rvnAcer:rnGarp_BA:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NC-ES1-131-C0XB
  dmi.product.version: V1.20
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709554/+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 1709554] Re: package linux-image-4.4.0-89-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before installi

[Douglas Leeder]

I'm not sure what happened - maybe sda became sdb during a
hibernate/sleep cycle?

umount/e2fsck/mount seems to have mounted rw, and I'm now trying the
install 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/1709554

Title:
  package linux-image-4.4.0-89-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-89-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apt upgrade - not sure what failed.

  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-89-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-85.108-generic 4.4.73
  Uname: Linux 4.4.0-85-generic i686
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1966 F pulseaudio
lightdm   22384 F pulseaudio
  Date: Wed Aug  9 08:10:00 2017
  DuplicateSignature:
   package:linux-image-4.4.0-89-generic:(not installed)
   Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=2531f67d-911e-48ef-949a-9e660522b701
  InstallationDate: Installed on 2016-04-28 (467 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 05dc:a83a Lexar Media, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 024: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer NC-ES1-131-C0XB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-85-generic 
root=UUID=e8c99506-8652-4a33-bbd4-51b8b006dc17 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-4.4.0-89-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd11/13/2015:svnAcer:pnNC-ES1-131-C0XB:pvrV1.20:rvnAcer:rnGarp_BA:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NC-ES1-131-C0XB
  dmi.product.version: V1.20
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709554/+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 1709554] Re: package linux-image-4.4.0-89-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before installi

[Douglas Leeder]

/dev/sda5 on /boot type ext4 (ro,relatime,data=ordered)

Does look like /boot is mounted ro - but I don't remember doing that
explicitly.

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

Title:
  package linux-image-4.4.0-89-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-89-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apt upgrade - not sure what failed.

  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-89-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-85.108-generic 4.4.73
  Uname: Linux 4.4.0-85-generic i686
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1966 F pulseaudio
lightdm   22384 F pulseaudio
  Date: Wed Aug  9 08:10:00 2017
  DuplicateSignature:
   package:linux-image-4.4.0-89-generic:(not installed)
   Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=2531f67d-911e-48ef-949a-9e660522b701
  InstallationDate: Installed on 2016-04-28 (467 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 05dc:a83a Lexar Media, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 024: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer NC-ES1-131-C0XB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-85-generic 
root=UUID=e8c99506-8652-4a33-bbd4-51b8b006dc17 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-4.4.0-89-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd11/13/2015:svnAcer:pnNC-ES1-131-C0XB:pvrV1.20:rvnAcer:rnGarp_BA:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NC-ES1-131-C0XB
  dmi.product.version: V1.20
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709554/+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 1709554] Re: package linux-image-4.4.0-89-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before installi

[Douglas Leeder]

[38464.903593] EXT4-fs error (device sda5): ext4_find_entry:1450: inode #2: 
comm dpkg: reading directory lblock 0
[38464.974734] EXT4-fs error (device sda5): ext4_find_entry:1450: inode #2: 
comm postrm: reading directory lblock 0
[38464.974881] EXT4-fs error (device sda5): ext4_find_entry:1450: inode #2: 
comm postrm: reading directory lblock 0
[38464.976699] EXT4-fs error (device sda5): ext4_find_entry:1450: inode #2: 
comm postrm: reading directory lblock 0
[38464.978693] EXT4-fs error (device sda5): ext4_find_entry:1450: inode #2: 
comm postrm: reading directory lblock 0
[38464.981257] EXT4-fs error (device sda5): ext4_find_entry:1450: inode #2: 
comm postrm: reading directory lblock 0
[39424.980466] EXT4-fs error (device sda5): ext4_remount:4743: Abort forced by 
user
[39469.312549] EXT4-fs error (device sda5): ext4_remount:4743: Abort forced by 
user

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

Title:
  package linux-image-4.4.0-89-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-89-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apt upgrade - not sure what failed.

  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-89-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-85.108-generic 4.4.73
  Uname: Linux 4.4.0-85-generic i686
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1966 F pulseaudio
lightdm   22384 F pulseaudio
  Date: Wed Aug  9 08:10:00 2017
  DuplicateSignature:
   package:linux-image-4.4.0-89-generic:(not installed)
   Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=2531f67d-911e-48ef-949a-9e660522b701
  InstallationDate: Installed on 2016-04-28 (467 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 05dc:a83a Lexar Media, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 024: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer NC-ES1-131-C0XB
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-85-generic 
root=UUID=e8c99506-8652-4a33-bbd4-51b8b006dc17 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-4.4.0-89-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd11/13/2015:svnAcer:pnNC-ES1-131-C0XB:pvrV1.20:rvnAcer:rnGarp_BA:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NC-ES1-131-C0XB
  dmi.product.version: V1.20
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709554/+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 1709554] [NEW] package linux-image-4.4.0-89-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before instal

[Douglas Leeder]

Public bug reported:

apt upgrade - not sure what failed.

Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


# lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-89-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-85.108-generic 4.4.73
Uname: Linux 4.4.0-85-generic i686
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  douglas1966 F pulseaudio
  lightdm   22384 F pulseaudio
Date: Wed Aug  9 08:10:00 2017
DuplicateSignature:
 package:linux-image-4.4.0-89-generic:(not installed)
 Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb 
(--unpack):
  unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before 
installing another version: Read-only file system
ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
HibernationDevice: RESUME=UUID=2531f67d-911e-48ef-949a-9e660522b701
InstallationDate: Installed on 2016-04-28 (467 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
Lsusb:
 Bus 002 Device 003: ID 05dc:a83a Lexar Media, Inc. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 024: ID 0489:e095 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer NC-ES1-131-C0XB
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-85-generic 
root=UUID=e8c99506-8652-4a33-bbd4-51b8b006dc17 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
SourcePackage: linux
Title: package linux-image-4.4.0-89-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-89-generic' before installing another version: Read-only 
file system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Garp_BA
dmi.board.vendor: Acer
dmi.board.version: V1.20
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.20:bd11/13/2015:svnAcer:pnNC-ES1-131-C0XB:pvrV1.20:rvnAcer:rnGarp_BA:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: NC-ES1-131-C0XB
dmi.product.version: V1.20
dmi.sys.vendor: Acer

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-4.4.0-89-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-89-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apt upgrade - not sure what failed.

  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-89-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-85.108-generic 4.4.73
  Uname: Linux 4.4.0-85-generic i686
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1966 F pulseaudio
lightdm   22384 F pulseaudio
  Date: Wed Aug  9 08:10:00 2017
  DuplicateSignature:
   package:linux-image-4.4.0-89-generic:(not installed)
   Unpacking linux-image-4.4.0-89-generic (4.4.0-89.112) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-89-generic_4.4.0-89.112_i386.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-89-generic' before 
installi

[Kernel-packages] [Bug 1566400] Re: Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID Migration deletes the RAID array.

[Douglas Miller]

grammed to ignore it. (int)
  parm:   expose_physicals:Expose physical components of the arrays. 
-1=protect 0=off, 1=on (int)
  parm:   reset_devices:Force an adapter reset at initialization. (int)
  parm:   wwn:Select a WWN type for the arrays:
0 - Disable
1 - Array Meta Data Signature (default)
2 - Adapter Serial Number (int)

  With regards,
  Naveed

   State: Open by: nauahmed on 18 March 2016 00:17:41 

  Hi Noah,

  There is no out box driver built for Ubuntu 16.04 yet.. 
  Also we were asked to test inbox Ubuntu 16.04 driver.
  Hence except the driver reset everything is outbox. 

  Yes, this issue is RAID 1 to RAID 5 Migration failure.. not only
  failure, the existing RAID1 gets deleted by this action, which should
  not have happened at any cause.

  With regards,
  Naveed

  - Forwarded by Naveed Us Ahmed/India/IBM on 03/30/2016 11:10 AM -
  > From: Douglas Miller1/Rochester/IBM
  > To: Naveed Us Ahmed/India/IBM
  > Date: 03/29/2016 07:46 AM
  > Subject: Re: dkms driver
  > 
  > It would appear that Microsemi has not updated their out-of-box 
  > driver for kernel 4.4.
  > 
  > I think we've done our due diligence, and it's time to open a JIRA 
  > to Microsemi. Let them provide us with what is necessary to diagnose 
further.

  == Comment: #8 - Brian J. King - 2016-04-05 09:40:18 ==
  Once mirrored to Launchpad, please open to PMC-Sierra / Microsemi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1566400/+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 1694330] [NEW] package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Douglas Valdo]

Public bug reported:

The system keep show me this problem everytime i try to update the
System.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic 4.10.0-22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  keyersoze   1725 F pulseaudio
 /dev/snd/pcmC1D0p:   keyersoze   1725 F...m pulseaudio
 /dev/snd/controlC1:  keyersoze   1725 F pulseaudio
Date: Mon May 29 18:15:11 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=98a473d7-7aa6-46a3-8746-8f34ee5493a1
InstallationDate: Installed on 2017-04-17 (42 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Hewlett-Packard HP Pavilion Sleekbook 15 PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=f8b224c7-88d1-45e1-a321-24fbab882b79 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 18FD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 82.10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.00:bd08/10/2012:svnHewlett-Packard:pnHPPavilionSleekbook15PC:pvr087E103B590320100:rvnHewlett-Packard:rn18FD:rvr82.10:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Sleekbook 15 PC
dmi.product.version: 087E103B590320100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package need-duplicate-check package-from-proposed zesty

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

Title:
  package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system keep show me this problem everytime i try to update the
  System.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keyersoze   1725 F pulseaudio
   /dev/snd/pcmC1D0p:   keyersoze   1725 F...m pulseaudio
   /dev/snd/controlC1:  keyersoze   1725 F pulseaudio
  Date: Mon May 29 18:15:11 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=98a473d7-7aa6-46a3-8746-8f34ee5493a1
  InstallationDate: Installed on 2017-04-17 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion Sleekbook 15 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=f8b224c7-88d1-45e1-a321-24fbab882b79 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18FD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 82.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.00:bd08/10/2012:svnHewlett-Packard:pnHPPavilionSleekbook15PC:pvr087E103B590320100:rvnHewlett-Packard:rn18FD:rvr82.10:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Sleekbook 15 PC
  dmi.product.version: 

[Kernel-packages] [Bug 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)

[Douglas H. Silva]

I fixed it with `sudo systemctl enable bluetooth` followed by a reboot.
It will print something to the terminal when you enable. Something else
must have disabled bluetooth.

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

Title:
  serious bug on bluetooth (Ubuntu 16.04 LTS)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed ubuntu 16.04 LTS twice -and i discovered that
  the problem was from the tool katoolin so i didn't install it- after i
  installed ubuntu the bluetooth didn't work for me.

  P.S:the bluetooth was working when my laptop was ubuntu 15.04

  when i turn bluetooth on to connect my mouse the switch was on but it
  said that

  Bluetooth is disabled

  i entered the command

  sudo rfkill unblock bluetooth

  it worked but didn't connect to the mouse even after the next restart
  i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock 
bluetooth before last line and restarting)

  and i've tried **sudo hciconfig hci0 reset** with output

  > Can't init device hci0: Connection timed out (110)

  my lsusb; rfkill list output:

  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  0: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
   1: asus-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
   11: hci0: Bluetooth
    Soft blocked: no
   Hard blocked: no

  and output of **dmesg | grep -Ei 'ath3k|blue'**

  [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   34.157120] Bluetooth: Core ver 2.21
  [   34.157135] Bluetooth: HCI device and connection manager initialized
  [   34.157138] Bluetooth: HCI socket layer initialized
  [   34.157140] Bluetooth: L2CAP socket layer initialized
  [   34.157145] Bluetooth: SCO socket layer initialized
  [   35.604410] usbcore: registered new interface driver ath3k
  [   51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   53.810045] Bluetooth: hci0 command 0x0c25 tx timeout
  [   55.814079] Bluetooth: hci0 command 0x0c38 tx timeout
  [   57.818111] Bluetooth: hci0 command 0x0c39 tx timeout
  [   59.822149] Bluetooth: hci0 command 0x0c05 tx timeout
  [   66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   66.997552] Bluetooth: BNEP filters: protocol multicast
  [   66.997556] Bluetooth: BNEP socket layer initialized
  [  195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  195.328480] Bluetooth: RFCOMM TTY layer initialized
  [  195.328488] Bluetooth: RFCOMM socket layer initialized
  [  195.328495] Bluetooth: RFCOMM ver 1.11
  [  199.131870] Bluetooth: hci0 command 0x1009 tx timeout
  [  276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  294.258992] Bluetooth: hci0 command 0x1005 tx timeout
  [  296.263065] Bluetooth: hci0 command 0x0c23 tx timeout
  [  298.267076] Bluetooth: hci0 command 0x0c14 tx timeout
  [  306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  346.417970] Bluetooth: hci0 command 0x0c56 tx timeout
  [  348.421916] Bluetooth: hci0 command 0x0c45 tx timeout
  [  350.425782] Bluetooth: hci0 command 0x0c58 tx timeout
  [  352.429744] Bluetooth: hci0 command 0x1004 tx timeout
  [  366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  368.145218] Bluetooth: hci0 command 0x1001 tx timeout
  [  370.149130] Bluetooth: hci0 command 0x1009 tx timeout
  [  410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  421.612041] Bluetooth: hci0 command 0x0c23 tx timeout
  [  423.616060] Bluetooth: hci0 command 0x0c14 tx timeout
  [  425.620018] Bluetooth: hci0 command 0x0c25 tx timeout
  [  427.623984] Bluetooth: hci0 command 0x0c38 tx timeout
  [  442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  444.727752] Bluetooth: hci0 command 0x0c52 tx timeout
  [  446.731800] Bluetooth: hci0 command 0x0c45 tx timeout
  [  448.735743] Bluetooth: hci0 command 0x0c58 tx timeout
  [  450.739762] Bluetooth: hci0 command 0x1004 tx timeout
  [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller
  [ 4011.801141] Bluetooth: hci0 

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Douglas Miller]

Carsten, I am currently thinking there are two possibilities here.
Maybe three.

1) The fix I submitted is not in the kernel(s) you are running.
2) The s390 compiler does not produce the necessary code to implicitly convert 
long int to bool.
3) You are hitting a different bug that just happens to look the same.

For #2, a simple compiler test could be done to check what code is
produced when assigning a long int value to a bool (GCC _Bool). If you
want to pursue that let me know. I am not familiar with s390 object
code, so we might need someone to interpret the objdump. As far as I can
tell, the s390 Linux kernel does use GCC _Bool for the data type "bool",
so it would then be a matter of what code the s390 GCC produces in this
case.

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Douglas Miller]

I'm confused about the release mechanics, I guess. Looking at the git
repository, I see tag "Ubuntu-4.4.0-65.86" (for example) and that tag
commit does contain the fix. Is it then possible for a kernel labeled
"4.4.0-65-generic #86" to NOT contain that patch? Am I making a gross
assumption that these tags reflect what was 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/1670634

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] 

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Douglas Miller]

This looks a lot like the problem in LP #1662673, but that fix is
supposed to be in kernel 4.4.0-65-generic. Might be worth confirming
though. Or perhaps confirming that the fix actually works on the Z
architecture (depends on how the architecture/compiler handles 'bool').

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  

[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

[Douglas Haunsperger]

Christopher,
That's a tougher question than you might think. :)

The full system is a rack-scale product developed by Dell's Data Center
Solutions division called DSS9000. This is not a generally-available
system, but is produced only for hyperscale and other large-volume
clients. However, the motherboard used in the system (DSS 9500M) in
question is also used in the PowerEdge C6320 product, which is a
generally available product.

Canonical has qualified the half-width (DSS 9520) and full-width (DSS
9500) sled options within the DSS 9000 framework on Ubuntu 16.04.

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

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+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 1478696] Re: dell-laptop: Incorrect keyboard backlight detection

[Henry J. Douglas]

I'm seeing my logs spammed with "dell_laptop: Keyboard brightness level
control not supported" too. Have you reported the bug upstream already?

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

Title:
  dell-laptop: Incorrect keyboard backlight detection

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I own Dell Inspiron M5110 (Q15R). This laptop has no keyboard backlight, but 
dell-laptop claims otherwise.
  My syslog was getting spammed with "Keyboard brightness level control not 
supported" as dell-laptop was trying to get/set backlight values.

  In dell-laptop there is kbd_led_present variable, but on my M5110 it's
  being set to true:

ret = kbd_init_info();
(...)
if (kbd_token_bits != 0 || ret == 0)
kbd_led_present = true;

  kbd_token_bits is 0, but so is ret.
  kbd_init_info method is only returning != 0 if kbd_get_info is returning != 0

  (Basing on this: 
http://linux.dell.com/cgi-bin/cgit.cgi/libsmbios.git/tree/src/bin/smbios-keyboard-ctl#n667)
  kbd_get_info method returns only cbRES1 value of following smbios call :
  cbClass 4
  cbSelect 11
  cbArg1 0x0
  And it returns 0...
  I found that any cbRES of this call is giving me nothing but zeros, as if it 
wasn't defined in my BIOS. I have it's newest version for my laptop:
  [0.00] SMBIOS 2.7 present.
  [0.00] DMI: Dell Inc. Inspiron M5110/0X7W03, BIOS A05 03/22/2012

  However, if "cbRES3, byte2  Number of keyboard light brightness
  levels" is 0 as well, that should mean backlight is not available,
  right? I'm attaching possible fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478696/+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 1493943] Re: Mono reliably crashes on certain multithreaded code in 3.13.0-62-generic

[Douglas Roffel]

I have modified the description and status to Incomplete, as I cannot
provide an adequate test (that doesn't contain proprietary code) to
reproduce the issue at this time.

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

Title:
  Mono reliably crashes on certain multithreaded code in
  3.13.0-62-generic

Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-lts-utopic source package in Trusty:
  Incomplete
Status in linux source package in Vivid:
  Incomplete

Bug description:
  SRU Justification:

  [Impact]
  EDIT: The referenced bug was not causing the crashing.

  [Fix]
  None yet.

  [Test Case]
  If I can get a test case working without giving the code for my company's 
internal application, I will post it.

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  droffel1829 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  9 10:28:21 2015
  HibernationDevice: RESUME=UUID=c916917a-07a8-42ad-807a-b2f7c4ff9807
  InstallationDate: Installed on 2015-04-15 (146 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=51deb493-21fe-4016-9855-90d738549bff ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493943/+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 1493943] Re: Mono reliably crashes on certain multithreaded code in 3.13.0-62-generic

[Douglas Roffel]

Unfortunately, I was able to reproduce my segfault with a kernel version
before the parent's bug was introduced. This implies my issue lies
somewhere else. I'm pretty sure its something to do with threading in
the kernel, but the referenced issue is not this one.

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

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Incomplete

** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Incomplete

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: In Progress => Incomplete

** Description changed:

  SRU Justification:
  
  [Impact]
- This bug appears to be due to a regression of the fix for:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584
- 
- Specifically, the edit history for
- https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
- (one of the files that the parent mentioned needed patching for the fix)
- shows that the changes added for the fix were removed one month later.
+ EDIT: The referenced bug was not causing the crashing.
  
  [Fix]
- $ git describe --contains 73459e2a1ada09a68c02cc5b73f3116fc8194b3d
- v4.1-rc2~14^2
+ None yet.
  
  [Test Case]
- run mono in a multithreaded kvm vm
- bug 1450584 has some testcases
+ If I can get a test case working without giving the code for my company's 
internal application, I will post it.
  
  --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  droffel1829 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  9 10:28:21 2015
  HibernationDevice: RESUME=UUID=c916917a-07a8-42ad-807a-b2f7c4ff9807
  InstallationDate: Installed on 2015-04-15 (146 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
  
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=51deb493-21fe-4016-9855-90d738549bff ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
  
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

Title:
  Mono reliably crashes on certain multithreaded code in
  3.13.0-62-generic

Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-lts-utopic source package in Trusty:
  Incomplete
Status in linux source package in Vivid:
  Incomplete

Bug description:
  SRU Justification:

  [Impact]
  EDIT: The referenced bug was not causing the crashing.

  [Fix]
  None yet.

  [Test Case]
  If I can get a test case working without giving the code for my company's 
internal application, I will post it.

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  droffel1829 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  9 10:28:21 2015
  HibernationDevice: RESUME=UUID=c916917a-07a8-42ad-807a-b2f7c4ff9807
  InstallationDate: Installed on 2015-04-15 (146 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 

[Kernel-packages] [Bug 1493943] Re: Mono reliably crashes on certain multithreaded code in 3.13.0-62-generic

[Douglas Roffel]

Chris: My test case unfortunately depends on an internal application
that I am not able to share the code of. At the moment, I am building an
older kernel version to test whether the test works properly on it. I
will respond once I've determined that the bug I referenced is indeed
the same one i'm dealing with 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/1493943

Title:
  Mono reliably crashes on certain multithreaded code in
  3.13.0-62-generic

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  This bug appears to be due to a regression of the fix for:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584

  Specifically, the edit history for
  https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
  (one of the files that the parent mentioned needed patching for the
  fix) shows that the changes added for the fix were removed one month
  later.

  [Fix]
  $ git describe --contains 73459e2a1ada09a68c02cc5b73f3116fc8194b3d
  v4.1-rc2~14^2

  [Test Case]
  run mono in a multithreaded kvm vm
  bug 1450584 has some testcases

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  droffel1829 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  9 10:28:21 2015
  HibernationDevice: RESUME=UUID=c916917a-07a8-42ad-807a-b2f7c4ff9807
  InstallationDate: Installed on 2015-04-15 (146 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=51deb493-21fe-4016-9855-90d738549bff ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493943/+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 1493943] [NEW] Mono reliably crashes on certain multithreaded code in 3.13.0-62-generic

[Douglas Roffel]

Public bug reported:

This bug appears to be due to a regression of the fix for:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584

Specifically, the edit history for
https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
(one of the files that the parent mentioned needed patching for the fix)
shows that the changes added for the fix were removed one month later.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-62-generic 3.13.0-62.102
ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  droffel1829 F pulseaudio
CurrentDesktop: Unity
Date: Wed Sep  9 10:28:21 2015
HibernationDevice: RESUME=UUID=c916917a-07a8-42ad-807a-b2f7c4ff9807
InstallationDate: Installed on 2015-04-15 (146 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=51deb493-21fe-4016-9855-90d738549bff ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-62-generic N/A
 linux-backports-modules-3.13.0-62-generic  N/A
 linux-firmware 1.127.15
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug trusty

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

Title:
  Mono reliably crashes on certain multithreaded code in
  3.13.0-62-generic

Status in linux package in Ubuntu:
  New

Bug description:
  This bug appears to be due to a regression of the fix for:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584

  Specifically, the edit history for
  https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
  (one of the files that the parent mentioned needed patching for the
  fix) shows that the changes added for the fix were removed one month
  later.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-62-generic 3.13.0-62.102
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  droffel1829 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep  9 10:28:21 2015
  HibernationDevice: RESUME=UUID=c916917a-07a8-42ad-807a-b2f7c4ff9807
  InstallationDate: Installed on 2015-04-15 (146 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=51deb493-21fe-4016-9855-90d738549bff ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-62-generic N/A
   linux-backports-modules-3.13.0-62-generic  N/A
   linux-firmware 1.127.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications 

[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

[Douglas Roffel]

Specifically, the edit history for
https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
(one of the files that the parent mentioned needed patching for the fix)
shows that the changes added for the fix were removed one month later.

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

Title:
  mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  The addition of the commit:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  Causes SIGSEGVs when running certain workloads on multi-cpu VMs.

  [Test Case]

  Mono test case here that causes the SIGSEGV
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  [Fix]

  These two commits are required for fixing this issue:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27

  --

  Gradually since late March more and more users started to complain
  about frequent SIGSEGV crashes in our .net/mono application. Early
  April I started to investigate it actively.

  After eliminating possible native libraries, and testing various mono
  versions I discovered the crashes would occur more frequently on a
  vbox vm with multiple cpus configured. And discovered that the mono
  bug-18026.cs testcase would fairly consistently crash. At that point
  it was reported to the mono bug tracker.

  I finally got a break when we found a correlation with the kernel version. 
3.13.0-46 didn't crash while 3.13.0-48,49 did.
  More and more users upgrade to these newer kernel versions and start running 
into issues, which explains the gradual increase in reports.

  Early this week I performed a full git bisect on the kernel between 3.13.0-46 
and -48 and isolated the commit that seems to trigger the crashes.
  Namely 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  At this point I don't know if the commit messed up something, or that mono 
simply handles it incorrectly. However, a few commits for linux 4.x seem to fix 
it:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27
  I applied these commits myself on top of commit 11f4e033, compiled and ran 
the testcase... didn't crash in the 200x test runs I did.
  Although I don't know if those two patches have unknown side-effects.
  I'm not an expert on the kernel, not even remotely. But I thought it would be 
nice to be able to point at a possible solution.

  My current test vm is a virtualbox vm 64bit installed using the 14.04.2 
server iso running on an older i7 quad core Windows 7 64bit host.
  In the vm I've tested numerous mono and kernel combinations. Last test was 
with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still 
occurs.

  By now I've debugged the app using gdb several dozen times on various
  user setups, compiled mono half a dozen times, and then the 8x3h
  compile kernel bisect :) Speaking of down the rabbit-hole...

  So I'm pretty desperate for some expert to help me out here. :D

  Reference to mono bug report:
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-51-generic 3.13.0-51.84
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 30 18:53 seq
   crw-rw 1 root audio 116, 33 Apr 30 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Apr 30 19:45:43 2015
  HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30
  InstallationDate: Installed on 2015-04-22 (7 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH 

[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

[Douglas Roffel]

I believe that this issue has reappeared in 3.13.0-62-generic, i'm
getting an extremely similar problem on that kernel version.

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

Title:
  mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  The addition of the commit:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  Causes SIGSEGVs when running certain workloads on multi-cpu VMs.

  [Test Case]

  Mono test case here that causes the SIGSEGV
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  [Fix]

  These two commits are required for fixing this issue:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27

  --

  Gradually since late March more and more users started to complain
  about frequent SIGSEGV crashes in our .net/mono application. Early
  April I started to investigate it actively.

  After eliminating possible native libraries, and testing various mono
  versions I discovered the crashes would occur more frequently on a
  vbox vm with multiple cpus configured. And discovered that the mono
  bug-18026.cs testcase would fairly consistently crash. At that point
  it was reported to the mono bug tracker.

  I finally got a break when we found a correlation with the kernel version. 
3.13.0-46 didn't crash while 3.13.0-48,49 did.
  More and more users upgrade to these newer kernel versions and start running 
into issues, which explains the gradual increase in reports.

  Early this week I performed a full git bisect on the kernel between 3.13.0-46 
and -48 and isolated the commit that seems to trigger the crashes.
  Namely 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  At this point I don't know if the commit messed up something, or that mono 
simply handles it incorrectly. However, a few commits for linux 4.x seem to fix 
it:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27
  I applied these commits myself on top of commit 11f4e033, compiled and ran 
the testcase... didn't crash in the 200x test runs I did.
  Although I don't know if those two patches have unknown side-effects.
  I'm not an expert on the kernel, not even remotely. But I thought it would be 
nice to be able to point at a possible solution.

  My current test vm is a virtualbox vm 64bit installed using the 14.04.2 
server iso running on an older i7 quad core Windows 7 64bit host.
  In the vm I've tested numerous mono and kernel combinations. Last test was 
with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still 
occurs.

  By now I've debugged the app using gdb several dozen times on various
  user setups, compiled mono half a dozen times, and then the 8x3h
  compile kernel bisect :) Speaking of down the rabbit-hole...

  So I'm pretty desperate for some expert to help me out here. :D

  Reference to mono bug report:
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-51-generic 3.13.0-51.84
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 30 18:53 seq
   crw-rw 1 root audio 116, 33 Apr 30 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Apr 30 19:45:43 2015
  HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30
  InstallationDate: Installed on 2015-04-22 (7 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 

[Kernel-packages] [Bug 1471029] Re: ELF programs with R_386_RELATIVE blocks are badly mapped into memory

[Douglas Bagnall]

hi Colin,

I first met on a 3.19.0-20 build:

Linux samba-build-i386-32bit 3.19.0-20-generic #20-Ubuntu SMP Fri May 29
10:06:53 UTC 2015 i686 i686 i686 GNU/Linux

and as far as I can tell (taking into account Joseph's 3.16 and upstream
4.2rc3), that a87938b/b51621a commit is neither the cure or culprit.

It is interesting that it works for you on a VM -- it looks like the
specific VM peculiarities matter. I'll try to find out what my VM
actually is, beyond openstack.

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

Title:
  ELF programs with R_386_RELATIVE blocks are badly mapped into memory

Status in libxslt package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Running the Samba autobuild tests on a 15.04 openstack image results
  in a segfault in this command:

  /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5
  /home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl default
  /docs-xml/manpages/smb.conf.5.xml

  I reported this upstream as a bug in xsltproc, but it was found to be
  impossible to reproduce using upstream source on the openstack
  instance:

  https://bugzilla.gnome.org/show_bug.cgi?id=751764

  Comment 8 (https://bugzilla.gnome.org/show_bug.cgi?id=751764#c8) is
  particularly informative.

  The stack trace below shows the segfault actually occurs in libxml's
  xpath evaluation functions. I see no difference between xpath.c in
  upstream 2.9.2 and Ubuntu's version.

  (gdb) bt 12
  #0  0xb760f874 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc818) at 
../../xpath.c:13606
  #1  0xb760f82e in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc890) at 
../../xpath.c:13598
  #2  0xb7610244 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8b8) at 
../../xpath.c:13529
  #3  0xb760f9d6 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8e0) at 
../../xpath.c:13977
  #4  0xb7612735 in xmlXPathCompOpEval (op=optimized out, ctxt=0xba25d3e8) at 
../../xpath.c:14552
  #5  xmlXPathRunEval (ctxt=0xba25d3e8, toBool=optimized out) at 
../../xpath.c:14552
  #6  0xb76171ed in xmlXPathCompiledEvalInternal (toBool=0, resObj=synthetic 
pointer, ctxt=optimized out, comp=optimized out) at ../../xpath.c:14915
  #7  xmlXPathCompiledEval__internal_alias (comp=0xb866a948, ctx=0xb99bd308) at 
../../xpath.c:14978
  #8  0xb7787260 in xsltEvalVariable (ctxt=ctxt@entry=0xb9836560, 
variable=variable@entry=0xba25d3b0, castedComp=0xb86a4238) at 
../../../libxslt/variables.c:903
  #9  0xb778759a in xsltBuildVariable (ctxt=0xb9836560, castedComp=0xb86a4238, 
tree=0xb86a6978) at ../../../libxslt/variables.c:1759
  #10 0xb7788bfa in xsltParseStylesheetCallerParam (ctxt=0xb86a6978, 
inst=0xb86a6978) at ../../../libxslt/variables.c:1975
  #11 0xb779b9db in xsltCallTemplate (ctxt=0xb9836560, node=0xb85efed8, 
inst=0xb86a6880, castedComp=0xb86a4148) at ../../../libxslt/transform.c:4739
  (More stack frames follow...)

  (gdb) bt -5
  #3311 0xb779a7de in xsltProcessOneNode (ctxt=0xb9836560, 
contextNode=0xb97586a0, withParams=0x0) at ../../../libxslt/transform.c:2097
  #3312 0xb779d818 in xsltApplyStylesheetInternal (style=0xba25d3e8, 
style@entry=0xb85ee200, doc=0xb86bc7f0, doc@entry=0xb97586a0, params=0xb77ed340 
params, 
  output=0xb85e13e0 default/docs-xml/manpages/smb.conf.5, profile=0x0, 
userCtxt=0xb9836560) at ../../../libxslt/transform.c:6159
  #3313 0xb779df8d in xsltRunStylesheetUser (style=0xb85ee200, doc=0xb97586a0, 
params=0xb77ed340 params, output=0xb85e13e0 
default/docs-xml/manpages/smb.conf.5, SAX=0x0, IObuf=0x0, 
  profile=0x0, userCtxt=0xb9836560) at ../../../libxslt/transform.c:6449
  #3314 0xb77ea12c in xsltProcess (doc=0xb97586a0, cur=0xb85ee200, 
filename=0xbfd59812 default/docs-xml/manpages/smb.conf.5.xml) at 
../../../xsltproc/xsltproc.c:483
  #3315 0xb77e9298 in main (argc=6, argv=0xbfd58f94) at 
../../../xsltproc/xsltproc.c:903
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul  9 00:13 seq
   crw-rw 1 root audio 116, 33 Jul  9 00:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 15.04
  Ec2AMI: ami-012b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nz-por-1a
  Ec2InstanceType: c1.c4r4
  Ec2Kernel: aki-0005
  Ec2Ramdisk: ari-0005
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   

[Kernel-packages] [Bug 1471029] Re: ELF programs with R_386_RELATIVE blocks are badly mapped into memory

[Douglas Bagnall]

 I'll try to find out what my VM actually is, beyond openstack.

KVM 2.0.0+dfsg-2ubuntu1.11

The processor (per attached files above) is Intel Xeon E312xx (Sandy
Bridge).

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

Title:
  ELF programs with R_386_RELATIVE blocks are badly mapped into memory

Status in libxslt package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Running the Samba autobuild tests on a 15.04 openstack image results
  in a segfault in this command:

  /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5
  /home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl default
  /docs-xml/manpages/smb.conf.5.xml

  I reported this upstream as a bug in xsltproc, but it was found to be
  impossible to reproduce using upstream source on the openstack
  instance:

  https://bugzilla.gnome.org/show_bug.cgi?id=751764

  Comment 8 (https://bugzilla.gnome.org/show_bug.cgi?id=751764#c8) is
  particularly informative.

  The stack trace below shows the segfault actually occurs in libxml's
  xpath evaluation functions. I see no difference between xpath.c in
  upstream 2.9.2 and Ubuntu's version.

  (gdb) bt 12
  #0  0xb760f874 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc818) at 
../../xpath.c:13606
  #1  0xb760f82e in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc890) at 
../../xpath.c:13598
  #2  0xb7610244 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8b8) at 
../../xpath.c:13529
  #3  0xb760f9d6 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8e0) at 
../../xpath.c:13977
  #4  0xb7612735 in xmlXPathCompOpEval (op=optimized out, ctxt=0xba25d3e8) at 
../../xpath.c:14552
  #5  xmlXPathRunEval (ctxt=0xba25d3e8, toBool=optimized out) at 
../../xpath.c:14552
  #6  0xb76171ed in xmlXPathCompiledEvalInternal (toBool=0, resObj=synthetic 
pointer, ctxt=optimized out, comp=optimized out) at ../../xpath.c:14915
  #7  xmlXPathCompiledEval__internal_alias (comp=0xb866a948, ctx=0xb99bd308) at 
../../xpath.c:14978
  #8  0xb7787260 in xsltEvalVariable (ctxt=ctxt@entry=0xb9836560, 
variable=variable@entry=0xba25d3b0, castedComp=0xb86a4238) at 
../../../libxslt/variables.c:903
  #9  0xb778759a in xsltBuildVariable (ctxt=0xb9836560, castedComp=0xb86a4238, 
tree=0xb86a6978) at ../../../libxslt/variables.c:1759
  #10 0xb7788bfa in xsltParseStylesheetCallerParam (ctxt=0xb86a6978, 
inst=0xb86a6978) at ../../../libxslt/variables.c:1975
  #11 0xb779b9db in xsltCallTemplate (ctxt=0xb9836560, node=0xb85efed8, 
inst=0xb86a6880, castedComp=0xb86a4148) at ../../../libxslt/transform.c:4739
  (More stack frames follow...)

  (gdb) bt -5
  #3311 0xb779a7de in xsltProcessOneNode (ctxt=0xb9836560, 
contextNode=0xb97586a0, withParams=0x0) at ../../../libxslt/transform.c:2097
  #3312 0xb779d818 in xsltApplyStylesheetInternal (style=0xba25d3e8, 
style@entry=0xb85ee200, doc=0xb86bc7f0, doc@entry=0xb97586a0, params=0xb77ed340 
params, 
  output=0xb85e13e0 default/docs-xml/manpages/smb.conf.5, profile=0x0, 
userCtxt=0xb9836560) at ../../../libxslt/transform.c:6159
  #3313 0xb779df8d in xsltRunStylesheetUser (style=0xb85ee200, doc=0xb97586a0, 
params=0xb77ed340 params, output=0xb85e13e0 
default/docs-xml/manpages/smb.conf.5, SAX=0x0, IObuf=0x0, 
  profile=0x0, userCtxt=0xb9836560) at ../../../libxslt/transform.c:6449
  #3314 0xb77ea12c in xsltProcess (doc=0xb97586a0, cur=0xb85ee200, 
filename=0xbfd59812 default/docs-xml/manpages/smb.conf.5.xml) at 
../../../xsltproc/xsltproc.c:483
  #3315 0xb77e9298 in main (argc=6, argv=0xbfd58f94) at 
../../../xsltproc/xsltproc.c:903
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul  9 00:13 seq
   crw-rw 1 root audio 116, 33 Jul  9 00:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 15.04
  Ec2AMI: ami-012b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nz-por-1a
  Ec2InstanceType: c1.c4r4
  Ec2Kernel: aki-0005
  Ec2Ramdisk: ari-0005
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  ProcVersionSignature: User Name 3.19.0-20.20-generic 3.19.8
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1471029] Re: ELF programs with R_386_RELATIVE blocks are badly mapped into memory

[Douglas Bagnall]

Thanks Joseph!
It's no better with  3.16.0-44-generic #59~lp1471029. Perhaps even slightly 
worse -- in my sample of 2 I've seen the heap at b8d- and b94-, while I think 
stock Vivid 3.19 was most often in the b7's.

$ uname -a
Linux samba-build-i386-4-32bit 3.16.0-44-generic #59~lp1471029 SMP Wed Jul 22 
22:24:19 UTC 2015 i686 i686 i686 GNU/Linux

$ /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5 
/home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl 
default/docs-xml/manpages/smb.conf.5.xml  (set -e; for x in {1..200};  do cat 
/proc/$!/maps   proc-maps/$!-$x; sleep 0.2;done)
[1] 919
[1]+  Segmentation fault

$ head proc-maps/919-2
b5976000-b5979000 rw-p  00:00 0 
b5979000-b5995000 r-xp  fd:01 2095   
/lib/i386-linux-gnu/libgcc_s.so.1
b5995000-b5996000 rw-p 0001b000 fd:01 2095   
/lib/i386-linux-gnu/libgcc_s.so.1
b5996000-b5997000 rw-p  00:00 0 
b5997000-b5a8 r-xp  fd:01 56064  
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.20
b5a8-b5a84000 r--p 000e9000 fd:01 56064  
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.20
b5a84000-b5a85000 rw-p 000ed000 fd:01 56064  
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.20
b5a85000-b5a8c000 rw-p  00:00 0 
b5a8c000-b70f7000 r-xp  fd:01 55921  
/usr/lib/i386-linux-gnu/libicudata.so.52.1
b70f7000-b70f8000 r--p 0166a000 fd:01 55921  
/usr/lib/i386-linux-gnu/libicudata.so.52.1

$ tail proc-maps/919-2
b77c3000-b77c4000 r-xp  00:00 0  [vdso]
b77c4000-b77c6000 r--p  00:00 0  [vvar]
b77c6000-b77e8000 r-xp  fd:01 2083   /lib/i386-linux-gnu/ld-2.21.so
b77e8000-b77e9000 r--p 00021000 fd:01 2083   /lib/i386-linux-gnu/ld-2.21.so
b77e9000-b77ea000 rw-p 00022000 fd:01 2083   /lib/i386-linux-gnu/ld-2.21.so
b77ea000-b77ef000 r-xp  fd:01 58216  /usr/bin/xsltproc
b77ef000-b77f r--p 4000 fd:01 58216  /usr/bin/xsltproc
b77f-b77f1000 rw-p 5000 fd:01 58216  /usr/bin/xsltproc
b8db2000-b8f11000 rw-p  00:00 0  [heap]
bfbd8000-bfbf9000 rw-p  00:00 0  [stack]

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

Title:
  ELF programs with R_386_RELATIVE blocks are badly mapped into memory

Status in libxslt package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Running the Samba autobuild tests on a 15.04 openstack image results
  in a segfault in this command:

  /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5
  /home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl default
  /docs-xml/manpages/smb.conf.5.xml

  I reported this upstream as a bug in xsltproc, but it was found to be
  impossible to reproduce using upstream source on the openstack
  instance:

  https://bugzilla.gnome.org/show_bug.cgi?id=751764

  Comment 8 (https://bugzilla.gnome.org/show_bug.cgi?id=751764#c8) is
  particularly informative.

  The stack trace below shows the segfault actually occurs in libxml's
  xpath evaluation functions. I see no difference between xpath.c in
  upstream 2.9.2 and Ubuntu's version.

  (gdb) bt 12
  #0  0xb760f874 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc818) at 
../../xpath.c:13606
  #1  0xb760f82e in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc890) at 
../../xpath.c:13598
  #2  0xb7610244 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8b8) at 
../../xpath.c:13529
  #3  0xb760f9d6 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8e0) at 
../../xpath.c:13977
  #4  0xb7612735 in xmlXPathCompOpEval (op=optimized out, ctxt=0xba25d3e8) at 
../../xpath.c:14552
  #5  xmlXPathRunEval (ctxt=0xba25d3e8, toBool=optimized out) at 
../../xpath.c:14552
  #6  0xb76171ed in xmlXPathCompiledEvalInternal (toBool=0, resObj=synthetic 
pointer, ctxt=optimized out, comp=optimized out) at ../../xpath.c:14915
  #7  xmlXPathCompiledEval__internal_alias (comp=0xb866a948, ctx=0xb99bd308) at 
../../xpath.c:14978
  #8  0xb7787260 in xsltEvalVariable (ctxt=ctxt@entry=0xb9836560, 
variable=variable@entry=0xba25d3b0, castedComp=0xb86a4238) at 
../../../libxslt/variables.c:903
  #9  0xb778759a in xsltBuildVariable (ctxt=0xb9836560, castedComp=0xb86a4238, 
tree=0xb86a6978) at ../../../libxslt/variables.c:1759
  #10 0xb7788bfa in xsltParseStylesheetCallerParam (ctxt=0xb86a6978, 
inst=0xb86a6978) at ../../../libxslt/variables.c:1975
  #11 0xb779b9db in xsltCallTemplate (ctxt=0xb9836560, node=0xb85efed8, 
inst=0xb86a6880, castedComp=0xb86a4148) at ../../../libxslt/transform.c:4739
  (More stack frames follow...)

  (gdb) bt -5
  #3311 0xb779a7de in xsltProcessOneNode (ctxt=0xb9836560, 
contextNode=0xb97586a0, withParams=0x0) at ../../../libxslt/transform.c:2097
  #3312 0xb779d818 in xsltApplyStylesheetInternal (style=0xba25d3e8, 
style@entry=0xb85ee200, doc=0xb86bc7f0, doc@entry=0xb97586a0, params=0xb77ed340 
params, 
  

[Kernel-packages] [Bug 1471029] Re: ELF programs with R_386_RELATIVE blocks are badly mapped into memory

[Douglas Bagnall]

hi Joseph

Those packages don't want to install on the i386:

dpkg: error processing archive 
linux-tools-3.16.0-44-generic_3.16.0-44.59~lp1471029_amd64.deb (--install):
package architecture (amd64) does not match system (i386)

(In compiling the 4.2 upstream kernel for i386, I ended up using a whole
series of magic flags -- something like this:

   DEB_HOST_ARCH=i386 linux32 fakeroot make-kpkg –arch i386 –cross-compile – ...
)

BTW, the machine in question now has sufficient disk to compile a
kernel, so I could do it there if that is easier.

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

Title:
  ELF programs with R_386_RELATIVE blocks are badly mapped into memory

Status in libxslt package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Running the Samba autobuild tests on a 15.04 openstack image results
  in a segfault in this command:

  /usr/bin/xsltproc --nonet -o default/docs-xml/manpages/smb.conf.5
  /home/ubuntu/autobuild/b22271/samba/docs-xml/xslt/man.xsl default
  /docs-xml/manpages/smb.conf.5.xml

  I reported this upstream as a bug in xsltproc, but it was found to be
  impossible to reproduce using upstream source on the openstack
  instance:

  https://bugzilla.gnome.org/show_bug.cgi?id=751764

  Comment 8 (https://bugzilla.gnome.org/show_bug.cgi?id=751764#c8) is
  particularly informative.

  The stack trace below shows the segfault actually occurs in libxml's
  xpath evaluation functions. I see no difference between xpath.c in
  upstream 2.9.2 and Ubuntu's version.

  (gdb) bt 12
  #0  0xb760f874 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc818) at 
../../xpath.c:13606
  #1  0xb760f82e in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc890) at 
../../xpath.c:13598
  #2  0xb7610244 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8b8) at 
../../xpath.c:13529
  #3  0xb760f9d6 in xmlXPathCompOpEval (ctxt=0xba25d3e8, op=0xb86bc8e0) at 
../../xpath.c:13977
  #4  0xb7612735 in xmlXPathCompOpEval (op=optimized out, ctxt=0xba25d3e8) at 
../../xpath.c:14552
  #5  xmlXPathRunEval (ctxt=0xba25d3e8, toBool=optimized out) at 
../../xpath.c:14552
  #6  0xb76171ed in xmlXPathCompiledEvalInternal (toBool=0, resObj=synthetic 
pointer, ctxt=optimized out, comp=optimized out) at ../../xpath.c:14915
  #7  xmlXPathCompiledEval__internal_alias (comp=0xb866a948, ctx=0xb99bd308) at 
../../xpath.c:14978
  #8  0xb7787260 in xsltEvalVariable (ctxt=ctxt@entry=0xb9836560, 
variable=variable@entry=0xba25d3b0, castedComp=0xb86a4238) at 
../../../libxslt/variables.c:903
  #9  0xb778759a in xsltBuildVariable (ctxt=0xb9836560, castedComp=0xb86a4238, 
tree=0xb86a6978) at ../../../libxslt/variables.c:1759
  #10 0xb7788bfa in xsltParseStylesheetCallerParam (ctxt=0xb86a6978, 
inst=0xb86a6978) at ../../../libxslt/variables.c:1975
  #11 0xb779b9db in xsltCallTemplate (ctxt=0xb9836560, node=0xb85efed8, 
inst=0xb86a6880, castedComp=0xb86a4148) at ../../../libxslt/transform.c:4739
  (More stack frames follow...)

  (gdb) bt -5
  #3311 0xb779a7de in xsltProcessOneNode (ctxt=0xb9836560, 
contextNode=0xb97586a0, withParams=0x0) at ../../../libxslt/transform.c:2097
  #3312 0xb779d818 in xsltApplyStylesheetInternal (style=0xba25d3e8, 
style@entry=0xb85ee200, doc=0xb86bc7f0, doc@entry=0xb97586a0, params=0xb77ed340 
params, 
  output=0xb85e13e0 default/docs-xml/manpages/smb.conf.5, profile=0x0, 
userCtxt=0xb9836560) at ../../../libxslt/transform.c:6159
  #3313 0xb779df8d in xsltRunStylesheetUser (style=0xb85ee200, doc=0xb97586a0, 
params=0xb77ed340 params, output=0xb85e13e0 
default/docs-xml/manpages/smb.conf.5, SAX=0x0, IObuf=0x0, 
  profile=0x0, userCtxt=0xb9836560) at ../../../libxslt/transform.c:6449
  #3314 0xb77ea12c in xsltProcess (doc=0xb97586a0, cur=0xb85ee200, 
filename=0xbfd59812 default/docs-xml/manpages/smb.conf.5.xml) at 
../../../xsltproc/xsltproc.c:483
  #3315 0xb77e9298 in main (argc=6, argv=0xbfd58f94) at 
../../../xsltproc/xsltproc.c:903
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul  9 00:13 seq
   crw-rw 1 root audio 116, 33 Jul  9 00:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 15.04
  Ec2AMI: ami-012b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nz-por-1a
  Ec2InstanceType: c1.c4r4
  Ec2Kernel: aki-0005
  Ec2Ramdisk: ari-0005
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: