[Kernel-packages] [Bug 2018251] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess

2023-05-01 Thread Christopher Mann
Public bug reported:

Upgrading from Ubuntu 23.04 low latency.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-1023.24-lowlatency 5.19.17
Uname: Linux 5.19.0-1023-lowlatency x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chris  1044 F wireplumber
 /dev/snd/controlC0:  chris  1044 F wireplumber
 /dev/snd/seq:chris  1040 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon May  1 14:53:29 2023
ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-08-29 (244 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1023-lowlatency 
root=UUID=22d8ea0c-ecec-4194-ba2f-85730cc87037 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.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
RfKill:
 
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago)
dmi.bios.date: 10/12/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd10/12/2013:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrading from Ubuntu 23.04 low latency.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-1023.24-lowlatency 5.19.17
  Uname: Linux 5.19.0-1023-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1044 F wireplumber
   /dev/snd/controlC0:  chris  1044 F wireplumber
   /dev/snd/seq:chris  1040 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon May  1 14:53:29 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-08-29 (244 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-1023-lowlatency 
root=UUID=22d8ea0c-ecec-4194-ba2f-85730cc87037 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.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago)
  dmi.bios.date: 10/12/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  

[Kernel-packages] [Bug 2018250] [NEW] package linux-headers-6.2.0-1003-lowlatency 6.2.0-1003.3 failed to install/upgrade: installed linux-headers-6.2.0-1003-lowlatency package post-installation script

2023-05-01 Thread Christopher Mann
Public bug reported:

Upgrading from Ubuntu 23.04 low latency.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-1003-lowlatency 6.2.0-1003.3
ProcVersionSignature: Ubuntu 5.19.0-1023.24-lowlatency 5.19.17
Uname: Linux 5.19.0-1023-lowlatency x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon May  1 14:53:46 2023
ErrorMessage: installed linux-headers-6.2.0-1003-lowlatency package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-08-29 (244 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: linux-lowlatency
Title: package linux-headers-6.2.0-1003-lowlatency 6.2.0-1003.3 failed to 
install/upgrade: installed linux-headers-6.2.0-1003-lowlatency package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago)

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-1003-lowlatency 6.2.0-1003.3 failed to
  install/upgrade: installed linux-headers-6.2.0-1003-lowlatency package
  post-installation script subprocess returned error exit status 1

Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  Upgrading from Ubuntu 23.04 low latency.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-1003-lowlatency 6.2.0-1003.3
  ProcVersionSignature: Ubuntu 5.19.0-1023.24-lowlatency 5.19.17
  Uname: Linux 5.19.0-1023-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon May  1 14:53:46 2023
  ErrorMessage: installed linux-headers-6.2.0-1003-lowlatency package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-08-29 (244 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: linux-lowlatency
  Title: package linux-headers-6.2.0-1003-lowlatency 6.2.0-1003.3 failed to 
install/upgrade: installed linux-headers-6.2.0-1003-lowlatency package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2018250/+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 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs

2023-03-05 Thread Christopher Townsend
I'm also experiencing this on my Lenovo Gen 3 T14s w/ Ryzen CPU :(

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

Title:
  HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs

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

Bug description:
  After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32
  (from 5.15.0.60) suspend/wake up is broken on my laptop.

  The system refuses to wake up in about 50% of the cases, seemingly
  random. The only "solution" is a forced system power down.

  Reverting back to 5.15.0.60 resolves this issue immediately.

  I suspect some patch was not re-applied to 5.19, since there are many
  postings on Reddit (for instance) about sleep problems with newer AMD
  CPUs, but 5.15 was running beautifully.

  My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU.

  UPDATE:

  See attached log. This may not be a case of the laptop failing to
  resume, but a case of the laptop not suspending properly!

  What happened was the following. When packing in my things,  I closed
  the laptop and put it in my bag. At home I picked it up again, and
  immediately noticed how unusually hot it was. The laptop didn't resume
  properly on opening the lid, but was frozen as before.

  So this might actually be a case of the laptop FAILING TO SUSPEND
  properly, instead of failing to wake up.

  UPDATE:

  I just noticed the battery was down to the low 40% from at least 80%.
  Given the temperature on opening the laption I suspect the CPU has
  been working hard during "sleep time".

  EDIT:

  Changed title after confirmation for earlier Ryzen 5000 CPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+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 1973434] Re: massive performance issues since 22.04 upgrade

2022-08-24 Thread Christopher Hamer
I am getting this issue on two machines. One Dell 7530 Precision laptop,
I have upgraded 18.04 - 20.04 and 22.04. It is really quite noticeable;
after a few hours I start to notice it. After leaving it for a few days
it gets worse and worse. Even typing this I suddenly get 15 of the same
letter typed and stuttering.

This machines got 6 core Intel i7, 42GB RAM, NVMe SSD. It does have a
Radeon GPU but currently booted into the Intel GPU with switchable
graphics. Might be worth trying it booted via the Radeon. Might be worth
noting it is powered by a Dell Dock which says it doesn't deliver enough
power when booting (but it does for my use).

@Urban

I installed 21.10 on a Dell XPS 9365 2 in 1 and upgraded to 22.04. It is
happening on that too. Its not anywhere near as noticeable but
definitely got some mouse stuttering which 21.10 didn't have.

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

Title:
  massive performance issues since 22.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrading to 22.04 i had to fight with massive performance issues.

  Browsers appeared to hang every other minute, youtube videos being
  laggy and hang in between, applications in a virtualbox VM where slow
  and also hanging every other minute to a level of not being useable.
  On a pretty recent and powerful system just 2 years old.

  I noticed CPU jumps in top, but also somehow thought it could be a graphics 
issue so invested some time installing nvidia drivers properly.
  Also I wondered if it might be the lowlatency kernel I normally use because I 
do audio stuff, and switched to generic. But nothing helped.

  ThenI had the idea it could be a kernel/scheduler issue because the
  system wasn't always slow, but it appeared certain things kept hanging
  when other processed had a lot of cpu for a few seconds.

  So I got a recent mainline kernel, configured it with my last running
  config from 21.10 before the update, made the debs and installed them,
  and now can tell that a mainline kernel 5.17.7 with all the dkms
  modules that i had before which got compiled automatically at
  installation brings back a "normal" performance.

  I can browse the web, run multiple youtube vids at once, even in
  another browser, have thunderbird running, and a virtualbox machine
  open with another browser for some web app testing and everything runs
  fine and smooth, no lagging.

  Not sure yet what the real reason is - either the kernel version, or a
  patch in the ubuntu version, or the 22.04 kernel config so far, or
  some configuration made in 21.10 that isn't good with 22.04 and it's
  kernel anymore.

  I will go ahead tomorrow and see if I can build a vanilla kernel with
  the config from the ubuntu 22.04 kernel and "make oldconfig", then I
  will be able to tell if only the config is making the difference.

  Please let me know of there is anything I should test to further
  analyze this issue, or any ideas I can try to solve it without having
  to run a mainline manually installed kernel.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.30.33
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  henning6198 F pulseaudio
   /dev/snd/controlC1:  henning6198 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 23:02:38 2022
  InstallationDate: Installed on 2020-04-12 (761 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=/dev/mapper/vgubuntu-root ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: 

[Kernel-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly

2022-06-13 Thread Christopher Barrington-Leigh
Wow, I think this line  (comment #10 from @vanvugt)

xrandr --output NAME --set "max bpc" 8

works 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/1929209

Title:
  [i915] external monitor goes black for several seconds at a time,
  randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


Re: [Kernel-packages] [Bug 1974261] Re: After updating to Ubuntu 22.04 I could not boot.

2022-05-20 Thread Christopher Zhang
Sorry, removing that line was the fix.

On Thu, May 19, 2022 at 10:50 PM Daniel van Vugt <1974...@bugs.launchpad.net>
wrote:

> Thanks for the bug report. It sounds like "acpi_backlight=vendor
> acpi_osi=linux" is the main issue here but I can't tell if adding it was
> the fix, or removing it was the fix. Which was it?
>
> ** Tags added: amdgpu nouveau
>
> ** Tags added: hybrid
>
> ** Summary changed:
>
> - After updating to Ubuntu 22.04 I could not boot.
> + [Lenovo IdeaPad Gaming 3 15ACH6] After updating to Ubuntu 22.04 system
> boots to a black screen
>
> ** Package changed: xorg (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1974261
>
> Title:
>   [Lenovo IdeaPad Gaming 3 15ACH6] After updating to Ubuntu 22.04 system
>   boots to a black screen
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Booting the laptop resulted in the splash screen. Then some text
>   flashed very quickly but I couldn't read it. Then, the screen went
>   black. The back light was on. I went to the TTY recovery mode and
>   tried to fix the issue.
>
>   I tried to fix the issue by deleting my nvidia drivers.
>   `apt remove --purge nvidia-*`
>   Still would not boot.
>
>   I ended up fixing the issue by going into recovery mode and changing
>   the following line of `/etc/default/grub`:
>
>   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor
>   acpi_osi=linux"
>
>   was changed to
>
>   GRUB_CMDLINE_LINUX_DEFAULT=""
>
>   I forgot to update the grub. After rebooting the issue was fixed.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: xorg 1:7.7+23ubuntu2
>   ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
>   Uname: Linux 5.15.0-30-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.1
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: unknown
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu May 19 19:24:34 2022
>   DistUpgraded: 2022-05-19 18:29:07,954 DEBUG Running PostInstallScript:
> '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
>   DistroCodename: jammy
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3a5d]
>Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6)
> (prog-if 00 [VGA controller])
>  Subsystem: Lenovo Cezanne [17aa:3a5d]
>   InstallationDate: Installed on 2021-10-28 (203 days ago)
>   InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
> (20210819)
>   MachineType: LENOVO 82K2
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic
> root=UUID=3b1b44c9-cba0-4972-9d72-b1c58fe2f6f8 ro quiet splash
> acpi_backlight=vendor acpi_osi=linux vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to jammy on 2022-05-20 (0 days ago)
>   XorgLog:
>
>   dmi.bios.date: 06/28/2021
>   dmi.bios.release: 1.30
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: H3CN30WW(V2.00)
>   dmi.board.asset.tag: NO Asset Tag
>   dmi.board.name: LNVNB161216
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J40700 WIN
>   dmi.chassis.asset.tag: NO Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: IdeaPad Gaming 3 15ACH6
>   dmi.ec.firmware.release: 1.30
>   dmi.modalias:
> dmi:bvnLENOVO:bvrH3CN30WW(V2.00):bd06/28/2021:br1.30:efr1.30:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6:
>   dmi.product.family: IdeaPad Gaming 3 15ACH6
>   dmi.product.name: 82K2
>   dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6
>   dmi.product.version: IdeaPad Gaming 3 15ACH6
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.110-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
>   version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
>   version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20210115-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.17-2build1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974261/+subscriptions
>
>

-- 
You 

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-04-25 Thread Christopher Gual
I wrote to Ricardo Diaz & Eric Dumazet to ask if the patch for this bug
would be backported and it looks like the fix was made for the Linux
stable kernels very recently: https://www.spinics.net/lists/stable-
commits/msg244651.html

Eric Dumazet also mentioned that:
"the bug only happens if networking configuration is not optimal. (We never hit 
the bug at Google) Normally, all packets for a given 4-tuple should be handled 
by the same cpu. On multi-queues NIC, RSS ensures this, if only one cpu is 
servicing interrupts for any receive queue. Otherwise, cpus compete over the 
same spinlocks, and could hit the race that Ricardo fixed. I suggest you also 
work on networking configuration, as this could help even without this race, 
but once flows are established."

He suggested looking at `Documentation/networking/scaling.rst` as a
starting point for tackling the network configuration.

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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/linux/+bug/1924298/+subscriptions


-- 

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-04-25 Thread Christopher Gual
I wrote to Ricardo Diaz & Eric Dumazet to ask if the patch for this bug
would be backported and it looks like the fix was made for the Linux
stable kernels very recently: https://www.spinics.net/lists/stable-
commits/msg244651.html

Eric Dumazet also mentioned that:
"the bug only happens if networking configuration is not optimal. (We never hit 
the bug at Google) Normally, all packets for a given 4-tuple should be handled 
by the same cpu. On multi-queues NIC, RSS ensures this, if only one cpu is 
servicing interrupts for any receive queue. Otherwise, cpus compete over the 
same spinlocks, and could hit the race that Ricardo fixed. I suggest you also 
work on networking configuration, as this could help even without this race, 
but once flows are established."

He suggested looking at `Documentation/networking/scaling.rst` as a
starting point for tackling the network configuration.

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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/linux/+bug/1924298/+subscriptions


-- 

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-04-25 Thread Christopher Gual
Hi Mark,

Thanks for the reply and confirmation.

I was talking to a co-worker today about this bug and they pointed out
that even though it is fixed in the newer Linux kernel versions, Ubuntu
20.04 and 16.04 are under LTS until April 2025 and April 2023
respectively.

It might be good to leave this bug open to see if there is a way that
Ubuntu can backport the fix for this issue to those versions.

I think there is a good case to argue that they should consider doing
this as the bug affects the reliability of TCP networking under load,
however I don't know about the process for how Ubuntu bugs are triaged.

Chris

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  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.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  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/linux/+bug/1924298/+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 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly

2022-04-22 Thread Christopher Barrington-Leigh
No one else has joined this bug, but it has continued to make life with
my expensive monitor extremely annoying.

And despite suggestions above, I am certain this is not a hardware
problem.

Here is new proof:
 yesterday, I initiated an upgrade (do-release-upgrade) to 22.04 from 21.10 
from  the command line.
By chance, I tried full-screening a video while the upgrade was in progress. 
Amazingly, it worked flawlessly the entire duration of the upgrade! ! ! 
 As soon as it was done and rebooted, I tried playing that video again and it 
did the black-screen / device searching every 3 seconds or so, as it always has.

So, how can I reproduce the thing that the upgrade did?! It said
something at the beginning about disabling screen lock or something like
that, but I have tried turning off all such things in my settings
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/1929209

Title:
  [i915] external monitor goes black for several seconds at a time,
  randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1924298] Re: accept returns duplicate endpoints under load

2022-04-22 Thread Christopher Gual
After spending some time I think I have narrowed down the bug fix to
Linux kernel 5.10-rc6.

The bug reproed on Ubuntu with kernel 5.10-rc4 but not on 5.10-rc6.

Here is a diff of the kernel sources between those two versions:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/?id=v5.10-rc6=v5.10-rc4=2

Of note are some changes to `net/ipv4/inet_hashtables.c`

Using `git blame` I think the most likely source of the bug fix was this
commit by Ricardo Dias:
https://github.com/torvalds/linux/commit/01770a166165738a6e05c3d911fb4609cc4eb416

The description for the commit describes a race condition which looks
like it could cause the bug:

"When such event happens, the TCP stack code has a race condition that
occurs between the momement a lookup is done to the established
connections hashtable to check for the existence of a connection for the
same client, and the moment that the child socket is added to the
established connections hashtable. As a consequence, this race condition
can lead to a situation where we add two child sockets to the
established connections hashtable and deliver two sockets to the
userspace program to the same client."

So for anyone who comes across this bug, the likely solution is to
update your OS to a version which uses kernel 5.10 or greater.

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  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: 

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-04-21 Thread Christopher Gual
We have been hitting this bug quite often while running Tomcat 8.5 on
Amazon AWS Linux 2 with a kernel of 4.14.268-205.500.amzn2.x86_64

I wanted to see if the bug could be reproduced using an updated kernel
so I attempted to repro it using the server code and methodology
provided by Mark Thomas on Ubuntu Server 21.10 (running on a Raspberry
Pi 4 with 4GB RAM) and was NOT able to repro the bug (kernel
5.13.0-1008-raspi). I then installed Ubuntu Server 20.04 LTS on the same
machine and WAS able to repro the bug (kernel 5.4.0-1052-raspi).  The
bug was fairly easy to repro and did not take multiple times to repro.

Since then I have been able to repro the bug using the server code on
AWS Linux 2 with the 4.14.268-205.500.amzn2.x86_64 kernel, but not on
AWS Linux 2 with a 5.10.109-104.500.amzn2.x86_64 kernel.

I think there is a slight problem with the server code used in the
repro, as it is calling `pthread_create` with no thread attributes,
which will create joinable threads instead of detached threads. The
documentation for `pthread_create` says that "Only when a terminated
joinable thread has been joined are the last of its resources released
back to the system." Because the server code never joins the threads I
think this is preventing the OS from releasing the thread resources.
This results in the server eventually running out of memory and the
server program returning a "pthread_create: Cannot allocate memory" as
mentioned by Brooke Hedrick in their comment.  I was also not able to
repro the bug on WSL (kernel 4.4.0-19041-Microsoft), but perhaps their
underlying network drivers are different?

I also was running into this issue when running the server code. I made
a slight modification to the server code to set the pthread attribute to
create the new threads in a detached state. This seemed to solve the
memory issue and I was able to repro the bug with this server.  I've
attached the code.

Additionally, I found it useful to use `prlimit` to update the maximum
number of open files for the server process, once it was running. This
made the server less likely to run into an EMFILE error when calling
`accept`.


** Attachment added: "Updated server to demonstrate bug"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298/+attachment/5582247/+files/server.c

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless 

[Kernel-packages] [Bug 1948504] [NEW] [Lenovo P52s] Unable to WiFi connect to Inseego Wavemaker 5G FX2000

2021-10-22 Thread Christopher M . Peñalver
Public bug reported:

1) lsb_release -rd
Description:Ubuntu 21.10
Release:21.10

2) uname -a
Linux worldpeacepc 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

3) What is expected to happen is when I click the top right hand side of
the GUI, choose the SSID associated with the Inseego Wavemaker 5G
FX2000, put in the known good password, it connects.

4) What happens instead is it fails to connect. Same problem in Ubuntu
21.04.

However, I'm able to connect to other SSIDs from other non-Inseego
devices. An iPhone 12 Mini and Windows 10 devices have no problems
connecting.

What I tried but it didn't change anything:
1) Disable ipv6 in Ubuntu.
2) In the Inseego GUI, change from:
5GHz 802.11acn/ax

to:
5GHz 802.11ac

WORKAROUND: In the Inseego GUI changing the WiFi security from:
WPA3/WPA2 Transition

to:
WPA2 Personal PSK (AES)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-21-generic 5.13.0-21.21
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  moniker1825 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 22 16:07:37 2021
InstallationDate: Installed on 2021-08-25 (58 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20LB001FUS
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-21-generic N/A
 linux-backports-modules-5.13.0-21-generic  N/A
 linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2021
dmi.bios.release: 1.29
dmi.bios.vendor: LENOVO
dmi.bios.version: N27ET43W (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LB001FUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrN27ET43W(1.29):bd08/13/2021:br1.29:efr1.15:svnLENOVO:pn20LB001FUS:pvrThinkPadP52s:rvnLENOVO:rn20LB001FUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20LB_BU_Think_FM_ThinkPadP52s:
dmi.product.family: ThinkPad P52s
dmi.product.name: 20LB001FUS
dmi.product.sku: LENOVO_MT_20LB_BU_Think_FM_ThinkPad P52s
dmi.product.version: ThinkPad P52s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug impish package-from-proposed

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

Title:
  [Lenovo P52s] Unable to  WiFi connect to Inseego Wavemaker 5G FX2000

Status in linux package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  2) uname -a
  Linux worldpeacepc 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

  3) What is expected to happen is when I click the top right hand side
  of the GUI, choose the SSID associated with the Inseego Wavemaker 5G
  FX2000, put in the known good password, it connects.

  4) What happens instead is it fails to connect. Same problem in Ubuntu
  21.04.

  However, I'm able to connect to other SSIDs from other non-Inseego
  devices. An iPhone 12 Mini and Windows 10 devices have no problems
  connecting.

  What I tried but it didn't change anything:
  1) Disable ipv6 in Ubuntu.
  2) In the Inseego GUI, change from:
  5GHz 802.11acn/ax

  to:
  5GHz 802.11ac

  WORKAROUND: In the Inseego GUI changing the WiFi security from:
  WPA3/WPA2 Transition

  to:
  WPA2 Personal PSK (AES)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moniker1825 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 22 16:07:37 2021
  InstallationDate: Installed on 2021-08-25 (58 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20LB001FUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Kernel-packages] [Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

2021-08-16 Thread Christopher Hall
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750

I'm having a similar issue on Ubuntu 20.04. Currently, every time that I
reboot I'm unable to login. I just get a black screen after logging in.
I have noticed that if I first delete the contents of .config and .local
I'm able to log in. However, obviously, all of my configurations and
customizations are then gone. My workaround lately has been to clear
those directories, login, logout, copy a backup of those directories to
the active directories and then log back in. It's a pain, but for some
reason it works. Otherwise, 100% of the time after a reboot I can't
access the desktop.

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have the reproducible effect with Ubuntu 20.04 beta that I'm able to login 
right after installation, but after a few reboots a black screen is displayed 
after login.
  I'm able to switch to a tty and tried to collect information with ubuntu-bug, 
but I am not sure if that help. I'm happy to provide further information if 
needed.
  I reinstalled Ubuntu 20.04 a couple of times, the behaviour is always the 
same. 19.10 works without any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr  4 14:05:01 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Dell GP106 [GeForce GTX 1060 6GB] [1028:11d7]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5675
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=3210a7fb-4a4d-4b22-ba85-60282726ebc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0477DV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/14/2018:svnDellInc.:pnInspiron5675:pvr1.3.7:rvnDellInc.:rn0477DV:rvrA00:cvnDellInc.:ct3:cvr1.3.7:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5675
  dmi.product.sku: 07EE
  dmi.product.version: 1.3.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1929209] Re: external monitor goes black for several seconds at a time, randomly

2021-07-11 Thread Christopher Barrington-Leigh
You mentioned "intermediate adapters". I'm using a Lenovo Ultradock between my 
laptop and the monitor.
 This causes no trouble on my Acer B326HK, which is just as high-res, but the 
new Samsung monitor continues to do the blackout thing. It's not strictly 
reproducible so far (fullscreening does not always cause any problem, and is 
not required to cause the problem).

Happily, I have two ultradocks.  It happens with both! And the brand new
HDMI cable looks fine.

I cannot try without the ultradock because my laptop does not have an
HDMI port.

No one else has reported this problem, though if it's a hardware fault
with the monitor (my interpretation) then it might be rare.  I have
recently upgraded to 21.04 and Wayland.

I am wondering:
Should I buy an adapter from HDMI to VGA, if such a thing exist?

You would be generous to give this any more attention. Thank you!

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

Title:
  external monitor goes black for several seconds at a time, randomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1929209] Re: external monitor goes black for several seconds at a time, randomly

2021-05-26 Thread Christopher Barrington-Leigh
Thank you so much, Daniel!
The Samsung is new. I'll try some swapping to isolate any hardware problem.

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

Title:
  external monitor goes black for several seconds at a time, randomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1929209] Re: external monitor goes black for several seconds at a time, randomly

2021-05-26 Thread Christopher Barrington-Leigh
(Recently,) it only happens when I make something full-screen on the external 
monitor. I do not think this is a hardware (which is brand new) problem.
Just now I made a browser full screen and it immediately strted happening every 
several seconds for a couple of seconds at a time. I've attached the journal

** Attachment added: "journalctl -b0"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+attachment/5500460/+files/journal.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/1929209

Title:
  external monitor goes black for several seconds at a time, randomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

  There are other related behaviours reported in the past, but I am running 
Ubuntu 20.10.
   I guess the attachments will show that I'm using Intel graphics hardware.  
The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+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 1926284] Re: `zfs send`dry-run estimation (`-n`) (perhaps more) broken

2021-04-27 Thread Christopher J. Ruwe
For reasons I do not understand, the kernel was not upgraded with the
`dist-upgrade` meant to lift me from groovy to hirsute. Neither my
shell-history nor the apt-logs contain any hint of a removal of the
"versionless" `linux-image-generic` package.

With proper 5.11 in place, `zfs send`s work again. The issue is
definitely not with the zfs packages. I do not have any idea how to
trace the root-cause further and suggest to close the issue.

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

Title:
  `zfs send`dry-run estimation (`-n`) (perhaps more) broken

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Calling `zfs send -v` is used for size estimation, it is expected to
  return (called on focal here)

  ```bash
  [cjr@hoare:/home/cjr]
  $ zfs send -n -v 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 
  full send of 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 estimated 
size is 126G
  total estimated size is 126G
  ```

  On hirsute, this feature is broken and returns
  ```bash
  [cjr@mccarthy:/home/cjr]
  $ /usr/sbin/zfs send -n -v rpool/USERDATA/<...>@zrepl-20210427_103846_000
  warning: cannot send 'rpool/USERDATA/<...>@zrepl-20210427_103846_000': 
Unknown error 103
  ```

  which breaks my backup. Considering that it worked fine with focal and
  groovy, I suspect the upgraded zfs packages to be at fault (although I
  am not sure which of these).

  Thanks for your consideration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1926284/+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 1926284] Re: `zfs send`dry-run estimation (`-n`) (perhaps more) broken

2021-04-27 Thread Christopher J. Ruwe
I have tried to reproduce the error on a vboxed fresh install of 21.04
and on a minimal install from 20.04, which I sequentially upgraded over
20.10 to 21.04. I could not reproduce the error on these minimal
installations.

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

Title:
  `zfs send`dry-run estimation (`-n`) (perhaps more) broken

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Calling `zfs send -v` is used for size estimation, it is expected to
  return (called on focal here)

  ```bash
  [cjr@hoare:/home/cjr]
  $ zfs send -n -v 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 
  full send of 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 estimated 
size is 126G
  total estimated size is 126G
  ```

  On hirsute, this feature is broken and returns
  ```bash
  [cjr@mccarthy:/home/cjr]
  $ /usr/sbin/zfs send -n -v rpool/USERDATA/<...>@zrepl-20210427_103846_000
  warning: cannot send 'rpool/USERDATA/<...>@zrepl-20210427_103846_000': 
Unknown error 103
  ```

  which breaks my backup. Considering that it worked fine with focal and
  groovy, I suspect the upgraded zfs packages to be at fault (although I
  am not sure which of these).

  Thanks for your consideration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1926284/+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 1926284] [NEW] `zfs send`dry-run estimation (`-n`) (perhaps more) broken

2021-04-27 Thread Christopher J. Ruwe
Public bug reported:

Calling `zfs send -v` is used for size estimation, it is expected to
return (called on focal here)

```bash
[cjr@hoare:/home/cjr]
$ zfs send -n -v 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 
full send of 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 estimated 
size is 126G
total estimated size is 126G
```

On hirsute, this feature is broken and returns
```bash
[cjr@mccarthy:/home/cjr]
$ /usr/sbin/zfs send -n -v rpool/USERDATA/<...>@zrepl-20210427_103846_000
warning: cannot send 'rpool/USERDATA/<...>@zrepl-20210427_103846_000': Unknown 
error 103
```

which breaks my backup. Considering that it worked fine with focal and
groovy, I suspect the upgraded zfs packages to be at fault (although I
am not sure which of these).

Thanks for your consideration.

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

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

Title:
  `zfs send`dry-run estimation (`-n`) (perhaps more) broken

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Calling `zfs send -v` is used for size estimation, it is expected to
  return (called on focal here)

  ```bash
  [cjr@hoare:/home/cjr]
  $ zfs send -n -v 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 
  full send of 
stank/backup/mccarthy/rpool/USERDATA/<...>@zrepl-20210426_094232_000 estimated 
size is 126G
  total estimated size is 126G
  ```

  On hirsute, this feature is broken and returns
  ```bash
  [cjr@mccarthy:/home/cjr]
  $ /usr/sbin/zfs send -n -v rpool/USERDATA/<...>@zrepl-20210427_103846_000
  warning: cannot send 'rpool/USERDATA/<...>@zrepl-20210427_103846_000': 
Unknown error 103
  ```

  which breaks my backup. Considering that it worked fine with focal and
  groovy, I suspect the upgraded zfs packages to be at fault (although I
  am not sure which of these).

  Thanks for your consideration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1926284/+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 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS

2021-04-21 Thread Christopher
Just an update, I still see this in the beta after a reboot. Workaround
still functions.

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

Title:
  Snaps appear broken on 21.04 Beta with ZFS

Status in snapd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  I've attempted to use two different userland snaps (qownnotes and
  keepassxc) neither function. When attempting to launch I get the
  following error:

  ```
  chalbersma@abdos:~$ qownnotes
  cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No 
such file or directory
  ```

  Additionally the snaps installed "by default" have a note of "broken"
  next to them :

  ```
  chalbersma@abdos:~$ sudo snap list
  Name   Version  RevTracking Publisher   Notes
  core18  1997   latest/stablecanonical✓  broken
  gnome-3-34-1804 66 latest/stable/…  canonical✓  broken
  gtk-common-themes   1514   latest/stable/…  canonical✓  broken
  qownnotes  21.3.9   8183   latest/stablepbek-
  snap-store  518latest/stable/…  canonical✓  broken
  snapd   11402  latest/stablecanonical✓  broken
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend

2021-04-07 Thread Christopher Barrington-Leigh
Can't tell if it's the same problem, but a recent (<1 month) update on a
Lenovo T450s running 20.10 has led me to these symptoms: closing the lid
or calling suspend leaves the machine dark and unusuable until I hold
down the power button for 10 seconds to reboot.

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  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/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable 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: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  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:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS

2021-04-06 Thread Christopher
> (as for Wayland issues, let's please not mix it in here, please open a
separate bug report if needed, possibly adding ubuntu-desktop to it).

@stolowski No worries. I'll open a new one for that.

@mvo Let me know when a new release is cut and I can pop it on the box
and test.

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

Title:
  Snaps appear broken on 21.04 Beta with ZFS

Status in snapd package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I've attempted to use two different userland snaps (qownnotes and
  keepassxc) neither function. When attempting to launch I get the
  following error:

  ```
  chalbersma@abdos:~$ qownnotes
  cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No 
such file or directory
  ```

  Additionally the snaps installed "by default" have a note of "broken"
  next to them :

  ```
  chalbersma@abdos:~$ sudo snap list
  Name   Version  RevTracking Publisher   Notes
  core18  1997   latest/stablecanonical✓  broken
  gnome-3-34-1804 66 latest/stable/…  canonical✓  broken
  gtk-common-themes   1514   latest/stable/…  canonical✓  broken
  qownnotes  21.3.9   8183   latest/stablepbek-
  snap-store  518latest/stable/…  canonical✓  broken
  snapd   11402  latest/stablecanonical✓  broken
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+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 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)

2021-04-01 Thread Christopher Trahey
Not sure if this will overlap with anyone else, but my experience was a
combination of 2 things:

1. Reboots were happening, caused by unattended-upgrade
2. The device causing trouble was a renamed device.

Turns out it was trying to get renamed twice: Once very early in boot
from eth1 to eno2, then again based on my neplan from eno2 to the name I
wanted. This was failing, and leaving the device down.


See my comment #117 on this issue for more details: 
https://bugs.launchpad.net/netplan/+bug/1770082

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

Title:
  Ubuntu 18.04 networking issue (connection drops after approx. 15
  minutes)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently troubleshooting some network issues on Ubuntu 18.04 LTS Bionic. 
After checking a few logs I noticed that the networkd-dispatcher is generating 
errors. I'm unsure if this is a bug but I'd like to report it over here just to 
be sure:
   
  ```
  Jun 04 18:14:21 [servername] systemd-networkd-wait-online[2079]: managing: br2
  Jun 04 18:14:22 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
7 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
8 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown 
interface index 8 seen even after reload
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
8 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown 
interface index 8 seen even after reload
  ```

  These issues occur consistently on several servers. The problem is
  that I lose the connection  specifically towards the internet after
  approx. 15 minutes. Internal facing interfaces (same hardware and
  driver) seem to behave differently and remain properly connected to
  the internal network. These network-dispatcher errors seem to occur
  simultanously when the connection on the external interface
  permanently drops.

  The physical network links still appears to be online when the
  connection is lost.

  I'm still also able to ping the default gateway from my provider to
  access the Internet. But all IP addresses beyond this gateway on the
  Internet seem to be unreachable.

  I have disabled TCP offloading and firewalls to eliminate any influences. But 
that didn't work.
  The ARP table shows that my gateway is a STALE record after the connection 
drops. So it seems related to the ARP-table or something likewise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775131/+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 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)

2021-04-01 Thread Christopher Trahey
Also observing this in 20.04.2 (kernel 5.4.0-70).
I will try swapping out physical transceivers on both ends of the link and a 
new switch port...

Of particular interest to me, netplan does not appear to re-run when
this happens. I have a device renaming rule that matches on name, sets
IP, and sets name. This device never comes back up unless I manually run
netplan apply (which is always successful, but obvs. untenable). The
root device (eno2) is not even listed in `ip link` output during the
incident.

Please advise what logging/information I can provide to help track down
culprit.

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

Title:
  Ubuntu 18.04 networking issue (connection drops after approx. 15
  minutes)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently troubleshooting some network issues on Ubuntu 18.04 LTS Bionic. 
After checking a few logs I noticed that the networkd-dispatcher is generating 
errors. I'm unsure if this is a bug but I'd like to report it over here just to 
be sure:
   
  ```
  Jun 04 18:14:21 [servername] systemd-networkd-wait-online[2079]: managing: br2
  Jun 04 18:14:22 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
7 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
8 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown 
interface index 8 seen even after reload
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
8 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown 
interface index 8 seen even after reload
  ```

  These issues occur consistently on several servers. The problem is
  that I lose the connection  specifically towards the internet after
  approx. 15 minutes. Internal facing interfaces (same hardware and
  driver) seem to behave differently and remain properly connected to
  the internal network. These network-dispatcher errors seem to occur
  simultanously when the connection on the external interface
  permanently drops.

  The physical network links still appears to be online when the
  connection is lost.

  I'm still also able to ping the default gateway from my provider to
  access the Internet. But all IP addresses beyond this gateway on the
  Internet seem to be unreachable.

  I have disabled TCP offloading and firewalls to eliminate any influences. But 
that didn't work.
  The ARP table shows that my gateway is a STALE record after the connection 
drops. So it seems related to the ARP-table or something likewise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775131/+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 1171582] Re: [highbank] hvc0 getty causes random hangs

2021-03-26 Thread christopher wayne hess
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [highbank] hvc0 getty causes random hangs

Status in finish-install package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in finish-install source package in Raring:
  Fix Released
Status in linux source package in Raring:
  Won't Fix
Status in finish-install source package in Saucy:
  Fix Released
Status in linux source package in Saucy:
  Won't Fix

Bug description:
  After doing a fresh install of raring, I've observed several issues
  across multiple systems, and they all seem to be correlated with the
  hvc0 upstart job (hvc0 getty) running.

  One symptom I've seen on both machines is that the network goes
  unresponsive for several seconds before recovering. If I run a ping, I
  see a pattern of 84-85s of responses, followed by about 41s of
  failures.

  The khvcd process consumes a lot of CPU - often 100% of a processor.

  Processes seem to randomly hang and are seemingly unrecoverable. I ran
  an apt-get install that never emitted any output, but remained hung
  until I rebooted the system.

  When I try to kill the hvc0 upstart job (sudo stop hvc0 - or a kill
  -9), the process does not die.

  One one of the two hosts, I observed the console getty (ttyAMA0)
  successfully starting, but never providing a login prompt to the
  console. Restarting this process didn't help solve the problem.

  Disabling the hvc0 upstart job and rebooting reliably makes these
  problems go away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/finish-install/+bug/1171582/+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 1063895] Re: arm64 support to generate linux-source for crosstool bulds

2021-03-26 Thread christopher wayne hess
** Changed in: linux (Ubuntu Linaro Evaluation Build)
   Status: New => Fix Released

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

Title:
  arm64 support to generate linux-source for crosstool bulds

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu Linaro Evaluation Build:
  Fix Released

Bug description:
  [Not sure If I've filed this aginst the right package. It should be
  linux-3.5.0, but that doesn't exist according to launchpad. ]

  Attached is a first-cut patch adding arm64 support to the linux-3.5.0
  package so that it builds linux-source packages which can be used to
  build cross tools against. The arm64 support is just the core stuff so
  isn't much use for making binaries. It's also an unholy backport of
  3.6/3.7 vintage stuff to 3.5 so it probably bust in important ways.
  However that's not relevant for the primiary purpose here of building
  cross-tools, which just needs a correct set of headers in linux-libc-
  dev, and arch/package machinery in linux-source.

  I'm not expecting this to be uploaded but wanted to put it somewhere
  public for anyone else to build with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063895/+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 1063895] Re: arm64 support to generate linux-source for crosstool bulds

2021-03-26 Thread christopher wayne hess
** Changed in: linux (Ubuntu Linaro Evaluation Build)
 Assignee: (unassigned) => christopher wayne hess (hess8519)

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

Title:
  arm64 support to generate linux-source for crosstool bulds

Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu Linaro Evaluation Build:
  Fix Released

Bug description:
  [Not sure If I've filed this aginst the right package. It should be
  linux-3.5.0, but that doesn't exist according to launchpad. ]

  Attached is a first-cut patch adding arm64 support to the linux-3.5.0
  package so that it builds linux-source packages which can be used to
  build cross tools against. The arm64 support is just the core stuff so
  isn't much use for making binaries. It's also an unholy backport of
  3.6/3.7 vintage stuff to 3.5 so it probably bust in important ways.
  However that's not relevant for the primiary purpose here of building
  cross-tools, which just needs a correct set of headers in linux-libc-
  dev, and arch/package machinery in linux-source.

  I'm not expecting this to be uploaded but wanted to put it somewhere
  public for anyone else to build with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063895/+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 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)

2021-02-08 Thread Christopher Hill
I've also had this issue - twice - caused by leaving my desktop in
standby for > 24hrs (can't say the exact duration). Cold booting after
ensuring residual current has been expelled from the system has fixed it
on both occasions.

It sounds like #1905214. My hardware is also

Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi 

I will try the kernel parameter `btusb.enable_autosuspend=0` but (touch
wood) won't be able to replicate for another week as this system is my
daily-driver.

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

Title:
  Bluetooth unavailable after updates - Reading Intel version
  information failed (-110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After 10 days of uptime with automatic updates, I rebooted. Bluetooth,
  which I use every day, is no longer available.

  $ dmesg | grep -i bluetooth
  [4.846072] Bluetooth: Core ver 2.22
  [4.846088] Bluetooth: HCI device and connection manager initialized
  [4.846092] Bluetooth: HCI socket layer initialized
  [4.846094] Bluetooth: L2CAP socket layer initialized
  [4.846096] Bluetooth: SCO socket layer initialized
  [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [5.434082] Bluetooth: BNEP filters: protocol multicast
  [5.434086] Bluetooth: BNEP socket layer initialized
  [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout
  [6.874129] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  $ uname -a
  Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04
  LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+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 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2021-01-21 Thread Christopher Yates
+1 -- I'm stuck on an ancient version of the Pi OS because of this
issue...

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed
Status in linux-raspi source package in Groovy:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  

[Kernel-packages] [Bug 1908175] [NEW] Touchpad and Keyboard

2020-12-14 Thread Christopher John Gonzales
Public bug reported:

Built in touchpad and keyboard on laptop do not work on Ubuntu.
Installed Ubuntu on USB.  Opened Ubuntu and touchpad and keyboard were
not responsive.  External mouse and keyboard work fine, but want to use
built in touchpad/keyboard.  Computer is a Microsoft Surface Laptop with
Windows 10.  Attempting to install latest Ubuntu.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu11446 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 15 03:27:16 2020
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Microsoft Corporation Surface Laptop 3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/23/2020
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: 7.124.140
dmi.board.name: Surface Laptop 3
dmi.board.vendor: Microsoft Corporation
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr7.124.140:bd06/23/2020:svnMicrosoftCorporation:pnSurfaceLaptop3:pvr124I00036T000M030D0B07F1C05P48S01E0Y0K0U02:rvnMicrosoftCorporation:rnSurfaceLaptop3:rvr:cvnMicrosoftCorporation:ct9:cvr:
dmi.product.family: Surface
dmi.product.name: Surface Laptop 3
dmi.product.sku: Surface_Laptop_3_1867:1868
dmi.product.version: 124I:00036T:000M:030D:0B:07F:1C:05P:48S:01E:0Y:0K:0U:02
dmi.sys.vendor: Microsoft Corporation

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


** Tags: amd64 apport-bug focal

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

Title:
  Touchpad and Keyboard

Status in linux package in Ubuntu:
  New

Bug description:
  Built in touchpad and keyboard on laptop do not work on Ubuntu.
  Installed Ubuntu on USB.  Opened Ubuntu and touchpad and keyboard were
  not responsive.  External mouse and keyboard work fine, but want to
  use built in touchpad/keyboard.  Computer is a Microsoft Surface
  Laptop with Windows 10.  Attempting to install latest Ubuntu.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu11446 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 15 03:27:16 2020
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Microsoft Corporation Surface Laptop 3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2020
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 7.124.140
  dmi.board.name: Surface Laptop 3
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr7.124.140:bd06/23/2020:svnMicrosoftCorporation:pnSurfaceLaptop3:pvr124I00036T000M030D0B07F1C05P48S01E0Y0K0U02:rvnMicrosoftCorporation:rnSurfaceLaptop3:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Laptop 3
  dmi.product.sku: Surface_Laptop_3_1867:1868
  dmi.product.version: 
124I:00036T:000M:030D:0B:07F:1C:05P:48S:01E:0Y:0K:0U:02
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target

2020-12-11 Thread Christopher Hill
Adding this bug as that seems to be the exact issue here -
https://github.com/openzfs/zfs/issues/10140

Solution is "Use zfs-mount-generator instead of zfs-mount.service" ...

** Bug watch added: github.com/openzfs/zfs/issues #10140
   https://github.com/openzfs/zfs/issues/10140

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

Title:
  failed boot mount, and systemd ordering cycle on zfs-import.target

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I
  see these errors:

  [   11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
  [   11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
  [   11.354267] systemd[1]: Failed to mount /boot.
  [   11.354307] systemd[1]: Dependency failed for /boot/efi.
  [   11.354327] systemd[1]: Dependency failed for /boot/grub.
  [   11.354344] systemd[1]: Dependency failed for Local File Systems.
  [   11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed 
with result 'dependency'.
  [   11.354367] systemd[1]: local-fs.target: Triggering OnFailure= 
dependencies.
  [   11.355088] systemd[1]: var-lib.mount: Found ordering cycle on 
zfs-import.target/start
  [   11.355090] systemd[1]: var-lib.mount: Found dependency on 
zfs-import-cache.service/start
  [   11.355091] systemd[1]: var-lib.mount: Found dependency on 
zfs-load-module.service/start
  [   11.355093] systemd[1]: var-lib.mount: Found dependency on 
cryptsetup.target/start
  [   11.355094] systemd[1]: var-lib.mount: Found dependency on 
systemd-cryptsetup@cryptoswap.service/start
  [   11.355096] systemd[1]: var-lib.mount: Found dependency on 
systemd-random-seed.service/start
  [   11.355097] systemd[1]: var-lib.mount: Found dependency on 
var-lib.mount/start
  [   11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted 
to break ordering cycle starting with var-lib.mount/start
  [   11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed 
with result 'dependency'.
  [   11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed 
with result 'dependency'.

  Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be
  mounted, unable to open the dataset" for boot.mount

  I can manually start boot.mount from the console, which then lets the
  boot process complete.

  N.B. "zfs list" is

  NAME   USED  AVAIL REFER  
MOUNTPOINT
  bpool  402M  1.36G   96K  
/boot
  bpool/BOOT 401M  1.36G   96K  none
  bpool/BOOT/ubuntu_o9gk00   401M  1.36G  201M  
/boot
  rpool  171G   720G  192K  /
  rpool/ROOT9.26G   720G  192K  none
  rpool/ROOT/ubuntu_1.57G   720G 5.16G  /
  rpool/ROOT/ubuntu_o9gk00  7.69G   720G 4.24G  /
  rpool/ROOT/ubuntu_o9gk00/srv   192K   720G  192K  /srv
  rpool/ROOT/ubuntu_o9gk00/usr  1.02M   720G  192K  /usr
  rpool/ROOT/ubuntu_o9gk00/usr/local 852K   720G  388K  
/usr/local
  rpool/ROOT/ubuntu_o9gk00/var  2.09G   720G  192K  /var
  rpool/ROOT/ubuntu_o9gk00/var/games 192K   720G  192K  
/var/games
  rpool/ROOT/ubuntu_o9gk00/var/lib  1.85G   720G 1.42G  
/var/lib
  rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService  1.39M   720G  496K  
/var/lib/AccountsService
  rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager   3.39M   720G  292K  
/var/lib/NetworkManager
  rpool/ROOT/ubuntu_o9gk00/var/lib/apt  87.2M   720G 78.0M  
/var/lib/apt
  rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg  148M   720G 63.6M  
/var/lib/dpkg
  rpool/ROOT/ubuntu_o9gk00/var/log   223M   720G 94.2M  
/var/log
  rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M   720G  224K  
/var/mail
  rpool/ROOT/ubuntu_o9gk00/var/snap  940K   720G  500K  
/var/snap
  rpool/ROOT/ubuntu_o9gk00/var/spool26.7M   720G 5.52M  
/var/spool
  rpool/ROOT/ubuntu_o9gk00/var/www   192K   720G  192K  
/var/www
  rpool/USERDATA 162G   720G  192K  /
  rpool/USERDATA/chris_hwz0bd162G   720G  156G  
/home/chris
  rpool/USERDATA/root_hwz0bd2.91M   720G  804K  
/root
  rpool/keystore 518M   720G 48.1M  -

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target

2020-11-20 Thread Christopher Hill
So, long story short, I believe I have run into this issue
https://github.com/zfsonlinux/pkg-zfs/issues/205

** Bug watch added: github.com/zfsonlinux/pkg-zfs/issues #205
   https://github.com/zfsonlinux/pkg-zfs/issues/205

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

Title:
  failed boot mount, and systemd ordering cycle on zfs-import.target

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I
  see these errors:

  [   11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
  [   11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
  [   11.354267] systemd[1]: Failed to mount /boot.
  [   11.354307] systemd[1]: Dependency failed for /boot/efi.
  [   11.354327] systemd[1]: Dependency failed for /boot/grub.
  [   11.354344] systemd[1]: Dependency failed for Local File Systems.
  [   11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed 
with result 'dependency'.
  [   11.354367] systemd[1]: local-fs.target: Triggering OnFailure= 
dependencies.
  [   11.355088] systemd[1]: var-lib.mount: Found ordering cycle on 
zfs-import.target/start
  [   11.355090] systemd[1]: var-lib.mount: Found dependency on 
zfs-import-cache.service/start
  [   11.355091] systemd[1]: var-lib.mount: Found dependency on 
zfs-load-module.service/start
  [   11.355093] systemd[1]: var-lib.mount: Found dependency on 
cryptsetup.target/start
  [   11.355094] systemd[1]: var-lib.mount: Found dependency on 
systemd-cryptsetup@cryptoswap.service/start
  [   11.355096] systemd[1]: var-lib.mount: Found dependency on 
systemd-random-seed.service/start
  [   11.355097] systemd[1]: var-lib.mount: Found dependency on 
var-lib.mount/start
  [   11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted 
to break ordering cycle starting with var-lib.mount/start
  [   11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed 
with result 'dependency'.
  [   11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed 
with result 'dependency'.

  Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be
  mounted, unable to open the dataset" for boot.mount

  I can manually start boot.mount from the console, which then lets the
  boot process complete.

  N.B. "zfs list" is

  NAME   USED  AVAIL REFER  
MOUNTPOINT
  bpool  402M  1.36G   96K  
/boot
  bpool/BOOT 401M  1.36G   96K  none
  bpool/BOOT/ubuntu_o9gk00   401M  1.36G  201M  
/boot
  rpool  171G   720G  192K  /
  rpool/ROOT9.26G   720G  192K  none
  rpool/ROOT/ubuntu_1.57G   720G 5.16G  /
  rpool/ROOT/ubuntu_o9gk00  7.69G   720G 4.24G  /
  rpool/ROOT/ubuntu_o9gk00/srv   192K   720G  192K  /srv
  rpool/ROOT/ubuntu_o9gk00/usr  1.02M   720G  192K  /usr
  rpool/ROOT/ubuntu_o9gk00/usr/local 852K   720G  388K  
/usr/local
  rpool/ROOT/ubuntu_o9gk00/var  2.09G   720G  192K  /var
  rpool/ROOT/ubuntu_o9gk00/var/games 192K   720G  192K  
/var/games
  rpool/ROOT/ubuntu_o9gk00/var/lib  1.85G   720G 1.42G  
/var/lib
  rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService  1.39M   720G  496K  
/var/lib/AccountsService
  rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager   3.39M   720G  292K  
/var/lib/NetworkManager
  rpool/ROOT/ubuntu_o9gk00/var/lib/apt  87.2M   720G 78.0M  
/var/lib/apt
  rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg  148M   720G 63.6M  
/var/lib/dpkg
  rpool/ROOT/ubuntu_o9gk00/var/log   223M   720G 94.2M  
/var/log
  rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M   720G  224K  
/var/mail
  rpool/ROOT/ubuntu_o9gk00/var/snap  940K   720G  500K  
/var/snap
  rpool/ROOT/ubuntu_o9gk00/var/spool26.7M   720G 5.52M  
/var/spool
  rpool/ROOT/ubuntu_o9gk00/var/www   192K   720G  192K  
/var/www
  rpool/USERDATA 162G   720G  192K  /
  rpool/USERDATA/chris_hwz0bd162G   720G  156G  
/home/chris
  rpool/USERDATA/root_hwz0bd2.91M   720G  804K  
/root
  rpool/keystore 518M   720G 48.1M  -

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target

2020-11-20 Thread Christopher Hill
Hmm, issue still happens, and I'm now suspicious of the dependencies in
systemd.


$ systemctl list-dependencies boot.mount
boot.mount
● ├─-.mount
● ├─system.slice
● └─zfs-import.target
●   └─zfs-import-cache.service


I see "boot.mount" depends on "zfs-import-cache.service", however the 
timestamps show otherwise


$ journalctl -f -u boot.mount
-- Logs begin at Sat 2020-11-14 20:41:30 EST. --
Nov 19 22:20:45 test systemd[1]: Mounting /boot...
Nov 19 22:20:45 test systemd[1]: Mounted /boot.
-- Reboot --
Nov 19 22:21:34 test systemd[1]: Mounting /boot...
Nov 19 22:21:35 test systemd[1]: Mounted /boot.
-- Reboot --
Nov 20 16:19:07 test mount[1265]: filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot 
be mounted, unable to open the dataset
Nov 20 16:19:07 test systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
Nov 20 16:19:07 test systemd[1]: boot.mount: Failed with result 'exit-code'.
Nov 20 16:19:07 test systemd[1]: Failed to mount /boot.
Nov 20 16:19:52 test systemd[1]: Mounting /boot...
Nov 20 16:19:52 test systemd[1]: Mounted /boot.

$ systemctl status zfs-import-cache.service 
● zfs-import-cache.service - Import ZFS pools by cache file
 Loaded: loaded (/lib/systemd/system/zfs-import-cache.service; enabled; 
vendor preset: enabled)
 Active: active (exited) since Fri 2020-11-20 16:19:08 EST; 16min ago
   Docs: man:zpool(8)
   Main PID: 2084 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 18936)
 Memory: 0B
 CGroup: /system.slice/zfs-import-cache.service

Nov 20 16:19:08 test systemd[1]: Starting Import ZFS pools by cache file...
Nov 20 16:19:08 test systemd[1]: Finished Import ZFS pools by cache file.


So mount ran at 16:19:07 (and failed) yet zfs-import-cache didn't complete 
until 16:19:08. That's rather odd...


$ journalctl -f -u zfs-import-cache.service 
-- Logs begin at Sat 2020-11-14 20:41:30 EST. --
Nov 19 22:21:34 test systemd[1]: Finished Import ZFS pools by cache file.
-- Reboot --
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found ordering cycle on 
zfs-import.target/start
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on 
zfs-import-cache.service/start
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on 
cryptsetup.target/start
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on 
systemd-cryptsetup@cryptoswap.service/start
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on 
systemd-random-seed.service/start
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Found dependency on 
var-lib.mount/start
Nov 20 16:19:07 test systemd[1]: var-lib.mount: Job zfs-import.target/start 
deleted to break ordering cycle starting with var-lib.mount/start
Nov 20 16:19:08 test systemd[1]: Starting Import ZFS pools by cache file...
Nov 20 16:19:08 test systemd[1]: Finished Import ZFS pools by cache file.


Now I see zfs-import-cache was "deleted" by systemd at 16:19:07 to break an 
ordering cycle, which I think explains the above - but this seems wrong?

If I then look at the prior zfs-import-cache log, I can see
cryptsetup@cryptoswap.service was "deleted", thus enabling /boot to
mount correctly:


Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found ordering cycle on 
systemd-cryptsetup@cryptoswap.service/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
systemd-random-seed.service/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
var-lib.mount/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
zfs-load-key-rpool.service/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
zfs-import.target/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
zfs-import-cache.service/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
zfs-load-module.service/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Found dependency on 
cryptsetup.target/start
Nov 19 22:21:34 test systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@cryptoswap.service/start deleted to break ordering cycle 
starting with cryptsetup.target/start
Nov 19 22:21:34 test systemd[1]: Starting Import ZFS pools by cache file...
Nov 19 22:21:34 test systemd[1]: Finished Import ZFS pools by cache file.

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

Title:
  failed boot mount, and systemd ordering cycle on zfs-import.target

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I
  see these errors:

  [   11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
  [   11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
  [   11.354267] systemd[1]: Failed to mount /boot.
  [   11.354307] systemd[1]: Dependency failed for /boot/efi.
  [ 

[Kernel-packages] [Bug 1904764] Re: failed boot mount, and systemd ordering cycle on zfs-import.target

2020-11-19 Thread Christopher Hill
BTW, I ran the following and that seems to have solved the missing
bpool.

zpool set cachefile=/etc/zfs/zpool.cache bpool
zpool set cachefile=/etc/zfs/zpool.cache rpool
update-initramfs -u -k all

I have a hunch the zpool.cache file is getting out of sync with the
initramfs one..?

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

Title:
  failed boot mount, and systemd ordering cycle on zfs-import.target

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I
  see these errors:

  [   11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
  [   11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
  [   11.354267] systemd[1]: Failed to mount /boot.
  [   11.354307] systemd[1]: Dependency failed for /boot/efi.
  [   11.354327] systemd[1]: Dependency failed for /boot/grub.
  [   11.354344] systemd[1]: Dependency failed for Local File Systems.
  [   11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed 
with result 'dependency'.
  [   11.354367] systemd[1]: local-fs.target: Triggering OnFailure= 
dependencies.
  [   11.355088] systemd[1]: var-lib.mount: Found ordering cycle on 
zfs-import.target/start
  [   11.355090] systemd[1]: var-lib.mount: Found dependency on 
zfs-import-cache.service/start
  [   11.355091] systemd[1]: var-lib.mount: Found dependency on 
zfs-load-module.service/start
  [   11.355093] systemd[1]: var-lib.mount: Found dependency on 
cryptsetup.target/start
  [   11.355094] systemd[1]: var-lib.mount: Found dependency on 
systemd-cryptsetup@cryptoswap.service/start
  [   11.355096] systemd[1]: var-lib.mount: Found dependency on 
systemd-random-seed.service/start
  [   11.355097] systemd[1]: var-lib.mount: Found dependency on 
var-lib.mount/start
  [   11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted 
to break ordering cycle starting with var-lib.mount/start
  [   11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed 
with result 'dependency'.
  [   11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed 
with result 'dependency'.

  Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be
  mounted, unable to open the dataset" for boot.mount

  I can manually start boot.mount from the console, which then lets the
  boot process complete.

  N.B. "zfs list" is

  NAME   USED  AVAIL REFER  
MOUNTPOINT
  bpool  402M  1.36G   96K  
/boot
  bpool/BOOT 401M  1.36G   96K  none
  bpool/BOOT/ubuntu_o9gk00   401M  1.36G  201M  
/boot
  rpool  171G   720G  192K  /
  rpool/ROOT9.26G   720G  192K  none
  rpool/ROOT/ubuntu_1.57G   720G 5.16G  /
  rpool/ROOT/ubuntu_o9gk00  7.69G   720G 4.24G  /
  rpool/ROOT/ubuntu_o9gk00/srv   192K   720G  192K  /srv
  rpool/ROOT/ubuntu_o9gk00/usr  1.02M   720G  192K  /usr
  rpool/ROOT/ubuntu_o9gk00/usr/local 852K   720G  388K  
/usr/local
  rpool/ROOT/ubuntu_o9gk00/var  2.09G   720G  192K  /var
  rpool/ROOT/ubuntu_o9gk00/var/games 192K   720G  192K  
/var/games
  rpool/ROOT/ubuntu_o9gk00/var/lib  1.85G   720G 1.42G  
/var/lib
  rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService  1.39M   720G  496K  
/var/lib/AccountsService
  rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager   3.39M   720G  292K  
/var/lib/NetworkManager
  rpool/ROOT/ubuntu_o9gk00/var/lib/apt  87.2M   720G 78.0M  
/var/lib/apt
  rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg  148M   720G 63.6M  
/var/lib/dpkg
  rpool/ROOT/ubuntu_o9gk00/var/log   223M   720G 94.2M  
/var/log
  rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M   720G  224K  
/var/mail
  rpool/ROOT/ubuntu_o9gk00/var/snap  940K   720G  500K  
/var/snap
  rpool/ROOT/ubuntu_o9gk00/var/spool26.7M   720G 5.52M  
/var/spool
  rpool/ROOT/ubuntu_o9gk00/var/www   192K   720G  192K  
/var/www
  rpool/USERDATA 162G   720G  192K  /
  rpool/USERDATA/chris_hwz0bd162G   720G  156G  
/home/chris
  rpool/USERDATA/root_hwz0bd2.91M   720G  804K  
/root
  rpool/keystore 518M   720G 48.1M  -

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1904764] [NEW] failed boot mount, and systemd ordering cycle on zfs-import.target

2020-11-18 Thread Christopher Hill
Public bug reported:

On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I see
these errors:

[   11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
[   11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
[   11.354267] systemd[1]: Failed to mount /boot.
[   11.354307] systemd[1]: Dependency failed for /boot/efi.
[   11.354327] systemd[1]: Dependency failed for /boot/grub.
[   11.354344] systemd[1]: Dependency failed for Local File Systems.
[   11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed 
with result 'dependency'.
[   11.354367] systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
[   11.355088] systemd[1]: var-lib.mount: Found ordering cycle on 
zfs-import.target/start
[   11.355090] systemd[1]: var-lib.mount: Found dependency on 
zfs-import-cache.service/start
[   11.355091] systemd[1]: var-lib.mount: Found dependency on 
zfs-load-module.service/start
[   11.355093] systemd[1]: var-lib.mount: Found dependency on 
cryptsetup.target/start
[   11.355094] systemd[1]: var-lib.mount: Found dependency on 
systemd-cryptsetup@cryptoswap.service/start
[   11.355096] systemd[1]: var-lib.mount: Found dependency on 
systemd-random-seed.service/start
[   11.355097] systemd[1]: var-lib.mount: Found dependency on 
var-lib.mount/start
[   11.355099] systemd[1]: var-lib.mount: Job zfs-import.target/start deleted 
to break ordering cycle starting with var-lib.mount/start
[   11.355819] systemd[1]: boot-grub.mount: Job boot-grub.mount/start failed 
with result 'dependency'.
[   11.355823] systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with 
result 'dependency'.

Journalctl shows "filesystem 'bpool/BOOT/ubuntu_o9gk00' cannot be
mounted, unable to open the dataset" for boot.mount

I can manually start boot.mount from the console, which then lets the
boot process complete.

N.B. "zfs list" is

NAME   USED  AVAIL REFER  
MOUNTPOINT
bpool  402M  1.36G   96K  /boot
bpool/BOOT 401M  1.36G   96K  none
bpool/BOOT/ubuntu_o9gk00   401M  1.36G  201M  /boot
rpool  171G   720G  192K  /
rpool/ROOT9.26G   720G  192K  none
rpool/ROOT/ubuntu_1.57G   720G 5.16G  /
rpool/ROOT/ubuntu_o9gk00  7.69G   720G 4.24G  /
rpool/ROOT/ubuntu_o9gk00/srv   192K   720G  192K  /srv
rpool/ROOT/ubuntu_o9gk00/usr  1.02M   720G  192K  /usr
rpool/ROOT/ubuntu_o9gk00/usr/local 852K   720G  388K  
/usr/local
rpool/ROOT/ubuntu_o9gk00/var  2.09G   720G  192K  /var
rpool/ROOT/ubuntu_o9gk00/var/games 192K   720G  192K  
/var/games
rpool/ROOT/ubuntu_o9gk00/var/lib  1.85G   720G 1.42G  
/var/lib
rpool/ROOT/ubuntu_o9gk00/var/lib/AccountsService  1.39M   720G  496K  
/var/lib/AccountsService
rpool/ROOT/ubuntu_o9gk00/var/lib/NetworkManager   3.39M   720G  292K  
/var/lib/NetworkManager
rpool/ROOT/ubuntu_o9gk00/var/lib/apt  87.2M   720G 78.0M  
/var/lib/apt
rpool/ROOT/ubuntu_o9gk00/var/lib/dpkg  148M   720G 63.6M  
/var/lib/dpkg
rpool/ROOT/ubuntu_o9gk00/var/log   223M   720G 94.2M  
/var/log
rpool/ROOT/ubuntu_o9gk00/var/mail 1.19M   720G  224K  
/var/mail
rpool/ROOT/ubuntu_o9gk00/var/snap  940K   720G  500K  
/var/snap
rpool/ROOT/ubuntu_o9gk00/var/spool26.7M   720G 5.52M  
/var/spool
rpool/ROOT/ubuntu_o9gk00/var/www   192K   720G  192K  
/var/www
rpool/USERDATA 162G   720G  192K  /
rpool/USERDATA/chris_hwz0bd162G   720G  156G  
/home/chris
rpool/USERDATA/root_hwz0bd2.91M   720G  804K  /root
rpool/keystore 518M   720G 48.1M  -

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

** Description changed:

  On a new Ubuntu 20.10 ZoL root I frequently get boot failures, and I see
  these errors:
  
+ [   11.353930] systemd[1]: boot.mount: Mount process exited, code=exited, 
status=1/FAILURE
+ [   11.353934] systemd[1]: boot.mount: Failed with result 'exit-code'.
+ [   11.354267] systemd[1]: Failed to mount /boot.
+ [   11.354307] systemd[1]: Dependency failed for /boot/efi.
+ [   11.354327] systemd[1]: Dependency failed for /boot/grub.
+ [   11.354344] systemd[1]: Dependency failed for Local File Systems.
+ [   11.354365] systemd[1]: local-fs.target: Job local-fs.target/start failed 
with result 'dependency'.
+ [   11.354367] systemd[1]: local-fs.target: Triggering OnFailure= 
dependencies.
+ [   11.355088] 

[Kernel-packages] [Bug 1902435] Re: Touchpad of Lenovo Ideapad 3 15IIL not detected after fresh install of Ubuntu 20.04 LTS

2020-11-05 Thread Jomel Christopher Villar
step: update kernel to Linux 5.10.0-051000rc1-generic
result: touchpad still not detected as input device (/proc/bus/input/devices)

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

Title:
  Touchpad of Lenovo Ideapad 3 15IIL not detected after fresh install of
  Ubuntu 20.04 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu: Ubuntu 20.04.1 LTS
  2) The version of the package you are using: N/A
  3) What you expected to happen: touchpad is working
  4) What happened instead: no response from touchpad, also not found in input 
devices (see attachment)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jomel  1513 F pulseaudio
   /dev/snd/controlC0:  jomel  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 21:10:24 2020
  InstallationDate: Installed on 2020-10-27 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 81WE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=27f982f1-8efc-4179-b643-3f8783d0c3bb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EMCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05:
  dmi.product.family: IdeaPad 3 15IIL05
  dmi.product.name: 81WE
  dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05
  dmi.product.version: IdeaPad 3 15IIL05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902435/+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 1902435] [NEW] Touchpad of Lenovo Ideapad 3 15IIL not detected after fresh install of Ubuntu 20.04 LTS

2020-11-01 Thread Jomel Christopher Villar
Public bug reported:

1) The release of Ubuntu: Ubuntu 20.04.1 LTS
2) The version of the package you are using: N/A
3) What you expected to happen: touchpad is working
4) What happened instead: no response from touchpad, also not found in input 
devices (see attachment)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-52-generic 5.4.0-52.57
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jomel  1513 F pulseaudio
 /dev/snd/controlC0:  jomel  1513 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  1 21:10:24 2020
InstallationDate: Installed on 2020-10-27 (5 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 81WE
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=27f982f1-8efc-4179-b643-3f8783d0c3bb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-52-generic N/A
 linux-backports-modules-5.4.0-52-generic  N/A
 linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: EMCN40WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 15IIL05
dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05:
dmi.product.family: IdeaPad 3 15IIL05
dmi.product.name: 81WE
dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05
dmi.product.version: IdeaPad 3 15IIL05
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Attachment added: "/proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1902435/+attachment/5430015/+files/devices

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

Title:
  Touchpad of Lenovo Ideapad 3 15IIL not detected after fresh install of
  Ubuntu 20.04 LTS

Status in linux package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu: Ubuntu 20.04.1 LTS
  2) The version of the package you are using: N/A
  3) What you expected to happen: touchpad is working
  4) What happened instead: no response from touchpad, also not found in input 
devices (see attachment)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jomel  1513 F pulseaudio
   /dev/snd/controlC0:  jomel  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  1 21:10:24 2020
  InstallationDate: Installed on 2020-10-27 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 81WE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=27f982f1-8efc-4179-b643-3f8783d0c3bb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EMCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05:
  dmi.product.family: IdeaPad 3 15IIL05
  dmi.product.name: 81WE
  dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05
  dmi.product.version: IdeaPad 3 15IIL05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902435/+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 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

2020-10-22 Thread Christopher M . Peñalver
Henry Wertz, a hardware failure causing collatoral logging wouldn't be
considered something for a developer to change here, but I'll mark this
Confirmed for now should a bug exist. Feel free to mark this Status
Invalid if you like.

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

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell Inspiron 1545 dmesg, I get:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This will be like 2-10 seconds apart, then it could be 5 minutes or
  more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kernel.

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+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 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-10-22 Thread Christopher Yates
Ahhh.  I do have 3 tunnels up as well.  Good find!

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

2020-10-22 Thread Christopher M . Peñalver
Henry Wertz, please answer all of the following:

1) Do you actually have superflous key strokes, along with that which is
logged in dmesg?

2) Could you please test the latest mainline kernel (now 5.9.1) and
advise to the results?

3) Did you personally test this with your Inspiron 1545 in a prior
version of Ubuntu (not someone else, somewhere else)? If so, what is the
earliest version and what were the results?

** Tags added: latest-bios-a14

** Description changed:

- I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) 
 In dmesg, I get a pair like:
+ On my Dell Inspiron 1545 dmesg, I get:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  
- This pair will be like 2-10 seconds apart, then it could be 5 minutes or
- more between pairs.
+ This will be like 2-10 seconds apart, then it could be 5 minutes or more
+ between pairs.
  
  I've been running 5.7.19 kernel (installed via mainline), but did boot
- 5.4.0-52-generic to file this since it's a supported kerenl (I seriously
- doubted it would make a difference since this has apparently been logged
- since at least the 2.6.x kernel series, and it didn't.)
- 
- I consider this bug pretty minor to possibly invalid; these keystroke
- messages spam up the kernel log a little but not too badly (since I'm
- not getting them every second like the original poster in #549741, but
- rather getting one, getting another a few seconds later, then it may be
- 5 minutes or more before I get another pair of them a few seconds
- apart.).
+ 5.4.0-52-generic to file this since it's a supported kernel.
  
  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
- (near network manager, volume, etc.) I think it sends this 0x8d each
- time the battery status changes.  Not sure what the point of the 0x8d
- is, but it's harmless for Linux to ignore, it's well aware of the status
- changes via ACPI anyway.
+ (near network manager, volume, etc.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
  
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  hwertz 3637 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  hwertz 3637 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:
-  
+ 
  MachineType: Dell Inc. Inspiron 1545
  Package: linux (not installed)
  ProcEnviron:
-  TERM=screen.xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen.xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup 
mitigations=off
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-52-generic N/A
-  linux-backports-modules-5.4.0-52-generic  N/A
-  linux-firmware1.173.19
+  linux-restricted-modules-5.4.0-52-generic N/A
+  linux-backports-modules-5.4.0-52-generic  N/A
+  linux-firmware1.173.19
  StagingDrivers: ashmem_linux
  Tags:  bionic staging
  Uname: Linux 5.4.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra
  _MarkForUpload: True
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell 

[Kernel-packages] [Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)

2020-10-22 Thread Christopher M . Peñalver
Henry Wertz, thank you for reporting this and helping make Ubuntu
better.

Could you please boot into a Ubuntu kernel (not third party kernel) and execute 
the following command only once, as it will automatically gather debugging 
information, in a terminal:
apport-collect 1901083

** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Inpsiron 1545 -- superflous key stroke logs (translated set 2, code
  0x8d)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted some information on bug #549741 stating that I was getting similar 
logs to what people were seeing in there, and was advised to go ahead and file 
a bug.  In dmesg, I get a pair like:
  [  529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.
  [  536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d 
on isa0060/serio0).
  [  536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it 
known.

  This pair will be like 2-10 seconds apart, then it could be 5 minutes
  or more between pairs.

  I've been running 5.7.19 kernel (installed via mainline), but did boot
  5.4.0-52-generic to file this since it's a supported kerenl (I
  seriously doubted it would make a difference since this has apparently
  been logged since at least the 2.6.x kernel series, and it didn't.)

  I consider this bug pretty minor to possibly invalid; these keystroke
  messages spam up the kernel log a little but not too badly (since I'm
  not getting them every second like the original poster in #549741, but
  rather getting one, getting another a few seconds later, then it may
  be 5 minutes or more before I get another pair of them a few seconds
  apart.).

  My battery packed up quite a while ago and shows 0% charge.. it has
  begun every so often "dropping off" and back on a few seconds later,
  both in gkrellm, and whatever app shows the battery icon in top right
  (near network manager, volume, etc.) I think it sends this 0x8d each
  time the battery status changes.  Not sure what the point of the 0x8d
  is, but it's harmless for Linux to ignore, it's well aware of the
  status changes via ACPI anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Thu Oct 22 15:13:25 2020
  InstallationDate: Installed on 2018-09-09 (774 days ago)
  InstallationMedia:

  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-22 Thread Christopher M . Peñalver
Philippe Coval, one thing that would be helpful is if you could make a
short video from a cell phone of the computer screen right before the
problem begins, as it starts ,and little bit as it is happening. This
helps developers root cause the issue better.

** Tags added: eoan

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

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

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1900854/+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 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages

2020-10-22 Thread Christopher M . Peñalver
Henry Wertz (hwertz10), as this report is closed, it will help immensely if you 
use Ubuntu with the computer the problem is reproducible with and file a new 
report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/549741

Title:
  [Dell Latitude 131L] keyboard not recognized properly; logs fill up
  with messages

Status in linux package in Ubuntu:
  Invalid

Bug description:
  hi

  Running Ubuntu Lucid amd64 on a Dell Latitude 131L (AMD chips),
  updated twice a day at the moment.

  Linux seems not to recognize the keyboard in my laptop well. Starting early 
in the boot process (well before X kicks in) I see error messages on the 
screen. The same messages then swamp the logs. A sample:
  =
  [19667.508573] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19667.508580] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19668.588701] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on 
isa0060/serio0).
  [19668.588712] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19668.600223] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19668.600230] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19669.717801] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on 
isa0060/serio0).
  [19669.717811] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19669.729365] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19669.729373] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19670.825302] atkbd.c: Unknown key pressed (translated set 2, code 0x8d on 
isa0060/serio0).
  [19670.825313] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  [19670.835700] atkbd.c: Unknown key released (translated set 2, code 0x8d on 
isa0060/serio0).
  [19670.835707] atkbd.c: Use 'setkeycodes e00d ' to make it known.
  =
  This goes on every second until shut down.

  It's been there for a while now, but I haven't made -or found- a bug report 
about it yet. I did some googling and it seems related to not-so-standard 
handling of hotkeys (which you would find on a laptop) by the bios. However, I 
have not found a solution.
  It is possible to 'shut up' the messages by assigning e00d to an unused 
keycode, but that is just hiding the symptom. Also that kills the screen saver 
/ blackout and it breaks my repeating keys, so not an option really.

  WORKAROUND: - shutdown the pc
  - Remove both battery and AC
  - push the 'on' switch several times
  - Plug the battery and AC back in

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1529 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16'
     Mixer name : 'SigmaTel STAC9200'
     Components : 'HDA:14f12bfa,14f100c3,0009 
HDA:83847690,102801f6,00102201'
     Controls  : 6
     Simple ctrls  : 4
  CheckboxSubmission: 41a9dc4bbc2c91d7f7445d204c57c74b
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  DistroRelease: Ubuntu 10.04
  HibernationDevice: RESUME=UUID=f83c27ce-b7e6-4250-967c-1920bb543ba0
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  MachineType: Dell Inc. Latitude 131L
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic 
root=UUID=46062d1f-f00c-4276-9ff1-541279640a93 ro single nomodeset
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Regression: No
  RelatedPackageVersions: linux-firmware 1.33
  Reproducible: Yes
  Tags: lucid
  TestedUpstream: Yes
  Uname: Linux 2.6.32-17-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 05/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.1
  dmi.board.name: 0PM607??
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.1:bd05/30/2006:svnDellInc.:pnLatitude131L:pvrNotSpecified:rvnDellInc.:rn0PM607??:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Latitude 131L
  dmi.product.version: Not Specified
  

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-22 Thread Christopher M . Peñalver
** Attachment added: "pinball-table-gnu-pincab-2020-rzr-9J5CHTFWnTc.mp4"
   
https://bugs.launchpad.net/linux/+bug/1900854/+attachment/5425486/+files/pinball-table-gnu-pincab-2020-rzr-9J5CHTFWnTc.mp4

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

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

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1900854/+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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-22 Thread Christopher M . Peñalver
Philippe Coval, could you please address all of the following:

1) In order for upstream to help you, could you please make a net new
bug report (not link a report you didn't make) via
https://gitlab.freedesktop.org/xorg/driver/xf86-video-
ati/-/issues/new?issue%5Bassignee_id%5D=%5Bmilestone_id%5D= ? Once
done, please advise on the URL.

2) To confirm, did this issue not occur in Ubuntu 19.10 before you
upgraded?

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

** Changed in: linux
   Importance: Unknown => Undecided

** Changed in: linux
   Status: Unknown => New

** Changed in: linux
 Remote watch: gitlab.freedesktop.org/drm/amd/-/issues #630 => None

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

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

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1900854/+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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-22 Thread Christopher M . Peñalver
** Description changed:

- Hi,
+ To reproduce type at a terminal or open with same file locally:
+ mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4
  
- I suspect there is an issue with radeon driver for video acceleration,
- I haven't investigated yet but I would investigate resources releases of VPU 
driver.
+ Stop the video by clicking Esc. Run again and the process will be stuck
+ on creating window frame for a while, then the video will start to show,
+ but the video's first frame looks like blinking in this triangle mess.
+ The system is still usable, and audio is still playing.
  
+ Log when issue occurred:
+ https://launchpadlibrarian.net/502954026/CurrentDmesg.txt
  
- As suggested on other (obsolete) bug:
- 
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all
- 
- 
- I thought it was a VLC bug but actually it's also replicated using mpv:
- 
- Just run
- 
- mpv
- 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4
- 
- It appears to work as expected
- 
- Stop with Esc
- 
- and run again
- 
- Process will be stuck on creating window frame 
- and then once windows is starting to show the video,
- desktop's frame buffer will become garbage:
- 
- video's first frame looks like blicking in this triangle mess.
- 
- 
- system is still usable,
- audio is still playing.
- 
- I logged using ssh and reported details using:
- 
- ubuntu-bug linux
- 
- 
- I hope collected data is not mixed with my client's host.
- 
- I can give more details or test patches.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 20.10
- Package: linux-image-5.8.0-25-generic 5.8.0-25.26
- ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
- Uname: Linux 5.8.0-25-generic x86_64
- ApportVersion: 2.20.11-0ubuntu50
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDmesg:
-  Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
-  Error executing command as another user: Not authorized
-  
-  This incident has been reported.
- Date: Wed Oct 21 16:02:27 2020
- IwConfig:
-  lono wireless extensions.
-  
-  enp2s0no wireless extensions.
-  
-  docker0   no wireless extensions.
- MachineType: Dell Inc. Precision T1500
- ProcEnviron:
-  TERM=screen.xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- ProcFB: 0 radeondrmfb
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
- RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-25-generic N/A
-  linux-backports-modules-5.8.0-25-generic  N/A
-  linux-firmware1.190
- RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
- SourcePackage: linux
- UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
- acpidump:
-  Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: pam_authenticate failed: 
Authentication failure
-  Error executing command as another user: Not authorized
-  
-  This incident has been reported.
- dmi.bios.date: 01/13/2011
- dmi.bios.release: 8.15
- dmi.bios.vendor: Dell Inc.
- dmi.bios.version: 2.4.0
- dmi.board.name: 0XC7MM
- dmi.board.vendor: Dell Inc.
- dmi.board.version: A00
- dmi.chassis.type: 3
- dmi.chassis.vendor: Dell Inc.
- dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
- dmi.product.family: 0
- dmi.product.name: Precision T1500
- dmi.product.sku: 0
- dmi.product.version: 00
- dmi.sys.vendor: Dell Inc.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rzr4431 F pulseaudio
-  /dev/snd/controlC1:  rzr4431 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rzr4431 F pulseaudio
+  /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
+  /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
-  lono wireless extensions.
-  
-  enp2s0no wireless extensions.
-  
-  docker0   no wireless extensions.
+  lono wireless extensions.
+ 
+  enp2s0no wireless extensions.
+ 
+  docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
-  

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-22 Thread Christopher M . Peñalver
** Tags removed: needs-upstream-testing
** Tags added: focal

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

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

Bug description:
  To reproduce type at a terminal or open with same file locally:
  mpv 
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  Stop the video by clicking Esc. Run again and the process will be
  stuck on creating window frame for a while, then the video will start
  to show, but the video's first frame looks like blinking in this
  triangle mess. The system is still usable, and audio is still playing.

  Log when issue occurred:
  https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/pcmC0D0p:   rzr4431 F...m pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin netdev plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1900854/+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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-21 Thread Christopher M . Peñalver
Philippe Coval, please advise to all of the following:

1) Did this issue not occur in a prior release of Ubuntu?

2) Is this still reproducible if the file is local versus streamed from
a website?

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I suspect there is an issue with radeon driver for video acceleration,
  I haven't investigated yet but I would investigate resources releases of VPU 
driver.

  
  As suggested on other (obsolete) bug:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all

  
  I thought it was a VLC bug but actually it's also replicated using mpv:

  Just run

  mpv
  
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  It appears to work as expected

  Stop with Esc

  and run again

  Process will be stuck on creating window frame 
  and then once windows is starting to show the video,
  desktop's frame buffer will become garbage:

  video's first frame looks like blicking in this triangle mess.

  
  system is still usable,
  audio is still playing.

  I logged using ssh and reported details using:

  ubuntu-bug linux

  
  I hope collected data is not mixed with my client's host.

  I can give more details or test patches.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Date: Wed Oct 21 16:02:27 2020
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: pam_authenticate failed: 
Authentication failure
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rzr4431 F pulseaudio
   /dev/snd/controlC1:  rzr4431 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RebootRequiredPkgs:
   linux-image-unsigned-5.9.1-050901-generic
   linux-base
   linux-image-unsigned-5.9.1-050901-lowlatency
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: 

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-21 Thread Christopher M . Peñalver
** Tags added: regression-potential

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I suspect there is an issue with radeon driver for video acceleration,
  I haven't investigated yet but I would investigate resources releases of VPU 
driver.

  
  As suggested on other (obsolete) bug:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all

  
  I thought it was a VLC bug but actually it's also replicated using mpv:

  Just run

  mpv
  
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  It appears to work as expected

  Stop with Esc

  and run again

  Process will be stuck on creating window frame 
  and then once windows is starting to show the video,
  desktop's frame buffer will become garbage:

  video's first frame looks like blicking in this triangle mess.

  
  system is still usable,
  audio is still playing.

  I logged using ssh and reported details using:

  ubuntu-bug linux

  
  I hope collected data is not mixed with my client's host.

  I can give more details or test patches.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Date: Wed Oct 21 16:02:27 2020
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: pam_authenticate failed: 
Authentication failure
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900854/+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 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-21 Thread Christopher M . Peñalver
Philippe Coval, in order to allow additional upstream mainline kernel 
developers to examine the issue, at your earliest convenience, could you please 
test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I suspect there is an issue with radeon driver for video acceleration,
  I haven't investigated yet but I would investigate resources releases of VPU 
driver.

  
  As suggested on other (obsolete) bug:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all

  
  I thought it was a VLC bug but actually it's also replicated using mpv:

  Just run

  mpv
  
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  It appears to work as expected

  Stop with Esc

  and run again

  Process will be stuck on creating window frame 
  and then once windows is starting to show the video,
  desktop's frame buffer will become garbage:

  video's first frame looks like blicking in this triangle mess.

  
  system is still usable,
  audio is still playing.

  I logged using ssh and reported details using:

  ubuntu-bug linux

  
  I hope collected data is not mixed with my client's host.

  I can give more details or test patches.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Date: Wed Oct 21 16:02:27 2020
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: 

[Kernel-packages] [Bug 1900854] Re: radeon: GPU lockup when restarting a video on RV730

2020-10-21 Thread Christopher M . Peñalver
** Tags added: apport-collected latest-bios-2.4.0

** Tags added: needs-upstream-testing

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

Title:
  radeon:  GPU lockup when restarting a video on RV730

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I suspect there is an issue with radeon driver for video acceleration,
  I haven't investigated yet but I would investigate resources releases of VPU 
driver.

  
  As suggested on other (obsolete) bug:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574130?comments=all

  
  I thought it was a VLC bug but actually it's also replicated using mpv:

  Just run

  mpv
  
https://conf.tube/download/videos/ea60f030-90c1-4e8e-9782-bef14dd3b1d1-1080.mp4

  It appears to work as expected

  Stop with Esc

  and run again

  Process will be stuck on creating window frame 
  and then once windows is starting to show the video,
  desktop's frame buffer will become garbage:

  video's first frame looks like blicking in this triangle mess.

  
  system is still usable,
  audio is still playing.

  I logged using ssh and reported details using:

  ubuntu-bug linux

  
  I hope collected data is not mixed with my client's host.

  I can give more details or test patches.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Date: Wed Oct 21 16:02:27 2020
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T1500
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=036d3d8c-98d4-48ec-a18b-dce21dcf0bb5 ro initrd=initrd.gz splash quiet 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-13 (8 days ago)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: pam_authenticate failed: 
Authentication failure
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 01/13/2011
  dmi.bios.release: 8.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0XC7MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:br8.15:svnDellInc.:pnPrecisionT1500:pvr00:rvnDellInc.:rn0XC7MM:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Precision T1500
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900854/+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 1481442] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot

2020-10-20 Thread Christopher M . Peñalver
** Description changed:

  When booting HP Pavilion dv6-6145eo with Ubuntu 15.04 the laptop monitor
  turns off in the middle of the boot.
  
- If I suspend and resume the computer (close and open the lid) when I
- hear the login sound the monitor turns back on and the computers works
- just fine.
+ 
+ WORKAROUND: Changing in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT from:
+ quiet splash
+ 
+ to:
+ quiet
+ 
+ WORKAROUND: If I suspend and resume the computer (close and open the
+ lid) when I hear the login sound the monitor turns back on and the
+ computers works just fine.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  markus 1653 F pulseaudio
-  /dev/snd/controlC0:  markus 1653 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  markus 1653 F pulseaudio
+  /dev/snd/controlC0:  markus 1653 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  4 21:24:03 2015
  HibernationDevice: RESUME=UUID=1496baa6-25ad-490c-8be1-371b62216282
  InstallationDate: Installed on 2015-08-04 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
-  0 radeondrmfb
-  1 radeondrmfb
+  0 radeondrmfb
+  1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=36500a23-b99a-4df0-9cd8-24126399d9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.19.0-25-generic N/A
-  linux-backports-modules-3.19.0-25-generic  N/A
-  linux-firmware 1.143.2
+  linux-restricted-modules-3.19.0-25-generic N/A
+  linux-backports-modules-3.19.0-25-generic  N/A
+  linux-firmware 1.143.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 358D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124461620100
  dmi.sys.vendor: Hewlett-Packard

** Tags added: focal

** Changed in: linux (Ubuntu)
   Importance: High => Low

** Changed in: linux (Ubuntu)
   Status: Won't Fix => Triaged

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

Title:
  [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor
  turns off during boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When booting HP Pavilion dv6-6145eo with Ubuntu 15.04 the laptop
  monitor turns off in the middle of the boot.

  
  WORKAROUND: Changing in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT from:
  quiet splash

  to:
  quiet

  WORKAROUND: If I suspend and resume the computer (close and open the
  lid) when I hear the login sound the monitor turns back on and the
  computers works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 1653 F pulseaudio
   /dev/snd/controlC0:  markus 1653 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  4 21:24:03 2015
  HibernationDevice: RESUME=UUID=1496baa6-25ad-490c-8be1-371b62216282
  InstallationDate: Installed on 2015-08-04 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=36500a23-b99a-4df0-9cd8-24126399d9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.2
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  

[Kernel-packages] [Bug 1513914] Re: Dell E7440 touchpad jumps position

2020-10-17 Thread Christopher M . Peñalver
Pawel Por (porparek), it is most helpful to provide necessary debugging 
information via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: latest-bios-a18
** Tags added: bios-outdated-a28

** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing

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

Title:
  Dell E7440 touchpad jumps position

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 15.10 - Dell E7440 touchpad works correctly when freshly started each 
time; but after some time running the mouse pointer starts to randomly jumps 
position when I try to use the touchpad.
  If I shut down Ubuntu and re-start after about 10 seconds, the problem is 
temporarily resolved.
  Both the USB Mouse and keyboard blue joy-button continue to work correctly 
while having "jumpy touchpad problem.
  Running Ubuntu 15.10 installed version (updated from 15.04 new installation)
  I have previously seen the same same problem with Ubuntu 14.04 and 15.04, 
both live CD and installed versions.
  I am new to Linux & forums, so please excuse my lack of knowledge.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martyn 1217 F pulseaudio
   /dev/snd/controlC0:  martyn 1217 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov  6 17:33:42 2015
  HibernationDevice: RESUME=UUID=d0cf60ae-c48f-4267-bb58-af4193cc2e5c
  InstallationDate: Installed on 2015-09-23 (44 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=42d901b2-6e43-4fbf-a79f-c6329d47548a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (14 days ago)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 03M26R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03M26R:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  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/1513914/+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 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2020-10-17 Thread Christopher M . Peñalver
** Description changed:

  On initial boot, sound on internal speakers is working. After standby it
  doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.
  
  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.
  
  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785
+ 
+ WORKAROUND: Use suspend to disk.
  
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  WORKAROUND: Use suspend to disk.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 1575071] Re: Graphics corruption (framebuffer offset) in i915 on 4.4.0

2020-10-17 Thread Christopher M . Peñalver
DooMMasteR (winrootkit-w), in order to provide necessary debugging information 
please file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Changed in: linux (Ubuntu)
   Importance: Medium => Low

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

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

Title:
  Graphics corruption (framebuffer offset) in i915 on 4.4.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Appeared after upgrading to 16.04 LTS. Mostly happens with switching
  channels in a full-screen irssi window by using Alt and the number
  keys (or the top row of the keyboard).

  Entire screen flickers between normal view, and a semi-arbitary offset
  view (with the entire screen offset by about 50-100 pixel, wrapping to
  the other side). Minor irritation to begin with.

  Eventually lead to the entire screen blanking save for a solid
  yellow/green line (about 5-10 px wide) on the left, occasionally (~1s)
  flicking back to the correct contents.

  Rebooting into 4.2.0 (left over from before the upgrade) appears to
  have fixed the issue.

  
  Hardware: Toshiba Portege z20t
  - "VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated 
Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller])"

  Relevant packages (assuming that they weren't captured):
  - linux-image-4.4.0-21-generic
  - linux-image-extra-4.4.0-21-generic
  - (working version is 4.2.0-35)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tpg2401 F pulseaudio
   /dev/snd/controlC0:  tpg2401 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 17:08:04 2016
  HibernationDevice: RESUME=UUID=ab95a533-52f3-4458-96dc-9119684b0ed6
  InstallationDate: Installed on 2015-06-19 (312 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: TOSHIBA PORTEGE Z20t-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=b6cc139d-95e4-48f1-a3a8-284dbdb3b6fa ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-35-generic N/A
   linux-backports-modules-4.2.0-35-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (1 days ago)
  dmi.bios.date: 01/06/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.60:bd01/06/2015:svnTOSHIBA:pnPORTEGEZ20t-B:pvrPT15BA-00500Y:rvnTOSHIBA:rnPORTEGEZ20t-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-B
  dmi.product.version: PT15BA-00500Y
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575071/+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 1574130] Re: radeon GPU lockup when using VLC and Firefox

2020-10-17 Thread Christopher M . Peñalver
Philippe Coval (rzr), to provide the necessary debugging information for an 
investigation please file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to 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/1574130

Title:
  radeon GPU lockup when using VLC and Firefox

Status in linux package in Ubuntu:
  Expired

Bug description:
  When playing a video with VLC and running Firefox at the same time,
  the radeon driver consistently (reproducibly) locks up and crashes on
  my machine since upgrading to 16.04. I'm using a Radeon HD 6870.

  This does not happen with other video players (totem, mpv). Tested
  with different video codecs and different window managers (gnome-
  shell, metacity).

  When VLC starts, the following message is printed to dmesg:

  [  102.379520] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
  rv770_restrict_performance_levels_before_switch failed

  This is not the case with Totem.
  When Firefox is started, or if Firefox had been running in the first place, a 
few seconds later it locks up:

  [  157.157196] radeon :01:00.0: ring 5 stalled for more than 10104msec
  [  157.157212] radeon :01:00.0: GPU lockup (current fence id 
0x03b7 last fence id 0x03bb on ring 5)
  [  157.506657] radeon :01:00.0: couldn't schedule ib
  [  157.506746] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!
  [  157.507820] radeon :01:00.0: Saved 535 dwords of commands on ring 0.
  [  157.507840] radeon :01:00.0: GPU softreset: 0x0088
  [  157.507846] radeon :01:00.0:   GRBM_STATUS   = 0xA0003828
  [  157.507852] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
  [  157.507858] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
  [  157.507863] radeon :01:00.0:   SRBM_STATUS   = 0x200040C0
  [  157.507868] radeon :01:00.0:   SRBM_STATUS2  = 0x
  [  157.507874] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
  [  157.507879] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x0001
  [  157.507884] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x0002
  [  157.507890] radeon :01:00.0:   R_008680_CP_STAT  = 0x80010243
  [  157.507895] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
  [  157.520474] radeon :01:00.0: GRBM_SOFT_RESET=0x4001
  [  157.520532] radeon :01:00.0: SRBM_SOFT_RESET=0x8100
  [  157.521682] radeon :01:00.0:   GRBM_STATUS   = 0x3828
  [  157.521687] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
  [  157.521692] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
  [  157.521698] radeon :01:00.0:   SRBM_STATUS   = 0x20C0
  [  157.521703] radeon :01:00.0:   SRBM_STATUS2  = 0x
  [  157.521708] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
  [  157.521714] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x
  [  157.521719] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x
  [  157.521724] radeon :01:00.0:   R_008680_CP_STAT  = 0x
  [  157.521730] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
  [  157.521750] radeon :01:00.0: GPU reset succeeded, trying to resume
  [  157.544993] [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
  [  157.547598] [drm] PCIE GART of 1024M enabled (table at 0x00274000).
  [  157.547689] radeon :01:00.0: WB enabled
  [  157.547692] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x8800cf551c00
  [  157.547694] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x8800cf551c0c
  [  157.549250] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00072118 and cpu addr 0xc90002032118
  [  157.771955] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test 
failed (scratch(0x8504)=0xCAFEDEAD)
  [  157.771978] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup 
failed on resume

  
  Software version information:

  % cat /proc/version
  Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 
(Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016

  % dpkg -l firefox vlc
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   VersionArchitecture   
Description
  
+++-==-==-==-=
  ii  firefox45.0.2+build1-0ubu amd64  Safe and 
easy web browser from 

[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep

2020-10-17 Thread Christopher M . Peñalver
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/+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 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

2020-10-17 Thread Christopher M . Peñalver
Ian! D. Allen (idallen)), it most helpful if you use the computer the problem 
is reproducible with, and provide necessary debugging logs by filing a new 
report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: apport-collected bionic

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327748/+files/AlsaInfo.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327749/+files/CRDA.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327750/+files/CurrentDmesg.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327751/+files/IwConfig.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327752/+files/Lspci.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327753/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327754/+files/ProcCpuinfo.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327755/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327756/+files/ProcEnviron.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327757/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327758/+files/ProcModules.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327759/+files/PulseList.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586195/+attachment/5327760/+files/UdevDb.txt

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

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Expired

Bug description:
  Continued in Bug #1622322.

  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [  296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  [  300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
  [  302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
  [  302.832697] .
  [  302.833086] usb 4-3: USB disconnect, device number 4

  Mainline version fyi:
  [0.00] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc 
version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 
23:32:59 UTC 2016

  I also get a similar message about 'Failed to disable LTM' if I just
  unplug the device before the breakage occurs.

  I've attached lsusb before the breakage occurs (so you can see the
  device) from the mainline kernel.

  Interestingly it appears the drivers on trusty and wily/mainline are
  different (r815x vs r8152) yet still exhibit similar troubles. I'm
  still digging around to try and figure out why this doesn't seem to be
  working, but I was wondering if you all had any idea what might 

[Kernel-packages] [Bug 1622322] Re: Realtek 8153-based ethernet adapter doesn't work

2020-10-17 Thread Christopher M . Peñalver
zwpwjwtz, could you please advise if this is still a problem in a supported 
release? If so, could you please boot into a x64 Ubuntu kernel (not third party 
kernel or i386 OS) and execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1622322

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

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

Title:
  Realtek 8153-based ethernet adapter doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar to Bug #1586195.

  Realtek 8153-based ethernet adapter doesn't work. No entry for the
  adapter appears in ifconfig.

  Adding "0bda:8152" to tlp blacklist(/etc/default/tlp) or triggering
  usb_modeswitch (by ejecting /dev/sr0) does not work either.

  
  dnesg output:
  
  [ 15.229468] usb 3-1.1: new SuperSpeed USB device number 4 using xhci_hcd
  [ 15.249257] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=8153
  [ 15.249260] usb 3-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [ 15.249262] usb 3-1.1: Product: USB 10/100/1000 LAN
  [ 15.249264] usb 3-1.1: Manufacturer: Realtek
  [ 15.249265] usb 3-1.1: SerialNumber: 
  [ 15.329605] usb 3-1.1: reset SuperSpeed USB device number 4 using xhci_hcd
  [ 15.372202] r8152 3-1.1:1.0 eth0: v1.08.2
  [ 16.413210] r8152 3-1.1:1.0 enx00e04c680bfb: renamed from eth0
  [ 16.454622] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680bfb: link is not ready
  [ 17.032871] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680bfb: link is not ready
  [ 17.038222] usb 3-1.1: Disable of device-initiated U1 failed.
  [ 17.038257] usb 3-1.1: Failed to set U2 timeout to 0x0,error code -71
  [ 17.042065] usb 3-1.1: Set SEL for device-initiated U1 failed.
  [ 17.045682] usb 3-1.1: Set SEL for device-initiated U2 failed.
  [ 17.045690] usb 3-1.1: usb_reset_and_verify_device Failed to disable LPM
 .
  [ 17.046906] usb 3-1.1: USB disconnect, device number 4
  [ 17.713462] usb 3-1.1: new SuperSpeed USB device number 5 using xhci_hcd
  [ 17.730139] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=8153
  [ 17.730147] usb 3-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [ 17.730151] usb 3-1.1: Product: USB 10/100/1000 LAN
  [ 17.730155] usb 3-1.1: Manufacturer: Realtek
  [ 17.730158] usb 3-1.1: SerialNumber: 
  [ 22.732882] usb 3-1.1: Disable of device-initiated U1 failed.
  [ 22.739551] usb 3-1.1: Disable of device-initiated U2 failed.
  [ 23.053009] usb 3-1.1: reset SuperSpeed USB device number 5 using xhci_hcd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1825 F pulseaudio
   /dev/snd/controlC1:  user   1825 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 11 19:01:59 2016
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 930X2K/931X2K
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=711b7dd0-0467-4bb6-85b4-bca68124c2cb ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06AEU.084.151026.MK
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930X2K-K07CN
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8656A04-C01-G001-S0001+10.0.10586
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06AEU.084.151026.MK:bd10/26/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn930X2K/931X2K:pvrP06AEU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930X2K-K07CN:rvrSGL8656A04-C01-G001-S0001+10.0.10586:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 930X2K/931X2K
  dmi.product.version: P06AEU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622322/+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 916677] Re: 1106:0415 Boot problem with VIA VT6415 PATA IDE Host Controller

2020-10-17 Thread Christopher M . Peñalver
biohazara, it would be most helpful if you provided necessary debugging 
information via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to 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/916677

Title:
  1106:0415 Boot problem with VIA VT6415 PATA IDE Host Controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kubuntu-32 11.10, Linux server 3.0.0-14-generic-pae #23-Ubuntu SMP Mon
  Nov 21 22:07:10 UTC 2011 i686 athlon i386 GNU/Linux.

  After the motherboard and CPU uograde I started to experience
  intermittent system frezes during the system boot process with

   udevd[101]: timeout: killing '/sbin/modprobe -bv
  pci:v1B4Bd91A0sv1849sd91A0bc01sc01i8f' [145]

  message dispayed on screen (white on black, 'thick' system textmode
  font, not 'thin' ubuntu console font).

  If system boots successfully (3 out of 8 attempts so far) it functions
  without futher problems.

  WORKAROUND: I disabled IDE controller system booted normally.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lvm2342 F pulseaudio
   /dev/snd/controlC0:  lvm2342 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe60 irq 16'
     Mixer name : 'Realtek ALC892'
     Components : 'HDA:10ec0892,18497892,00100302'
     Controls  : 35
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfe08 irq 25'
     Mixer name : 'Nvidia GPU 0d HDMI/DP'
     Components : 'HDA:10de000d,10de0101,00100100'
     Controls  : 17
     Simple ctrls  : 5
  DistroRelease: Ubuntu 11.10
  HibernationDevice: RESUME=UUID=d22ce633-8298-47af-bd3b-b2f2c011e08f
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  IwConfig:
   lono wireless extensions.

   eth2  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-14-generic-pae 
root=UUID=e5d4b20c-2274-4625-bff0-06fcc27e7755 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-14-generic-pae N/A
   linux-backports-modules-3.0.0-14-generic-pae  N/A
   linux-firmware1.60
  RfKill:

  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic-pae i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (95 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/13/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: 990FX Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/13/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916677/+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 1321421] Re: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97

2020-10-17 Thread Christopher M . Peñalver
José Santos Salvador (thejosess), as this bug report is closed, if you want 
your problem addressed please file a new report via a terminal:
ubuntu-bug -s audio

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

Title:
  8086:8ca0 Sound output distorted/unusable with Intel Z97/H97

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I get horribly cracking sound and distortion with my ne AS Rock
  Fatal1ty H97 Performance Mainboard. This MB is using PuritySound 2
  Engine powered by the Realtek ALC1150 Chipset. Here is some ALSA Info:
  http://www.alsa-
  project.org/db/?f=44b12e252a2cf7ebb75ab3e23d5cef072af6c328

  Following commit fixes this problem:
  
https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound/+/77f07800cb456bed6e5c345e6e4e83e8eda62437

  WORKAROUND: Create a modprobe.d file with command:
  echo "options snd-hda-intel vid=8086 pid=8ca0 snoop=0" | sudo tee 
/etc/modprobe.d/fix-sound-intel97.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 20 21:03:18 2014
  InstallationDate: Installed on 2014-05-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H97 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/28/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  ---
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ben1445 F pulseaudio
   /dev/snd/controlC0:  ben1445 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=f35e4cc7-52c2-4fe7-9e4b-405280ed487f
  InstallationDate: Installed on 2014-05-20 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H97 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/28/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421/+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 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04

2020-10-17 Thread Christopher M . Peñalver
Nikolaj Løbner Sheller (nikolaj-l), this report is closed as it was
reported resolved by the original reporter. Hence, it has nothing to do
with your problem.

However, if you would like your issue resolved, please use the computer the 
problem is reproducible with, and provide necessary debugging logs by filing a 
new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to 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/1767611

Title:
  ath10k_pci crash leading to unstable wifi on 18.04

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04.
  mitch@mitch-YOGA:~$ uname -a
  Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  Same laptop, device, working fine on 17.10. No crashes, stable wifi.

  Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: 
ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
  Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: 
failed to set 5g txpower 20: -11
  Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: 
failed to setup tx power 20: -11
  Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: 
failed to recalc tx power: -11
  Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: 
failed to set inactivity time for vdev 0: -11
  Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: 
failed to setup powersave: -11
  Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating 
from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING)
  Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: 
failed to set inactivity time for vdev 0: -11
  Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: 
failed to setup powersave: -11
  Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: 
failed to set PS Mode 0 for vdev 0: -11
  Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: 
failed to setup powersave: -11
  Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: 
failed to setup ps on vdev 0: -11
  Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: 
failed to flush transmit queue (skip 0 ar-state 1): 0
  Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: 
failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11
  Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove 
key (0, 54:a0:50:d8:ca:00) from hardware (-11)
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: 
failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: 
found sta peer 54:a0:50:d8:ca:00 (ptr  id 133) entry on vdev 0 
after it was supposedly removed
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at 
/build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 
__sta_info_destroy_part2+0x169/0x170 [mac80211]
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl 
hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als 
hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf 
videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio 
videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 
hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core 
kvm_intel
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566]  ath kvm mac80211 irqbypass 
snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 
ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device 
snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma 
soundcore mei_me mei processor_thermal_device shpchp int340x_thermal_zone 
intel_lpss_pci intel_pch_thermal intel_lpss intel_soc_dts_iosf ideapad_laptop 
sparse_keymap mac_hid int3400_thermal acpi_thermal_rel acpi_pad tpm_crb 
sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme 
drm nvme_core i2c_hid wmi hid video
  Apr 28 12:12:25 mitch-YOGA kernel: [12379.644694] CPU: 0 PID: 757 Comm: 
NetworkManager Tainted: G   

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-10-15 Thread Christopher Yates
@mlx -- dunno.  What I do know is reverting to prior firmware solves the
issue for me and at least @Tim.

I had the same issue in May as there was another release.  I reverted
and it became stable.

This summer, I tried to sudo apt upgrade and hit the problem again.  So
I reverted and am stable.

Would like to get back to the tip for sure, but instability is
instability.  And it seems it's a shared problem across ETH0 and WLAN1
based on this thread.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-10-15 Thread Christopher Yates
@Juerg:

My config for my network setup, which is an AP via wlan0, not bridged
and station via USB Wifi dongle:

-
#!/bin/bash

# Error management
set -o pipefail
set -o nounset
set -x

apt install -y hostapd dnsmasq
systemctl unmask hostapd
systemctl enable hostapd

systemctl stop hostapd
systemctl stop dnsmasq

echo -e "interface wlan0\n\tstatic ip_address=192.168.10.1/24\n\tnohook
wpa_supplicant\n" >> /etc/dhcpcd.conf

systemctl restart dhcpcd
cp /home/pi/hostapd.conf /etc/hostapd/
sed -i 's/^#DAEMON_CONF=.*$/DAEMON_CONF="\/etc\/hostapd\/hostapd.conf"/' 
/etc/default/hostapd

mv /etc/dnsmasq.conf /etc/dnsmasq.conf.orig
cp /home/pi/dnsmasq.conf /etc/

systemctl unmask hostapd
systemctl enable hostapd
systemctl start hostapd
service dnsmasq start

-

Unlike the top post, I'm not using IPV6 so that is not a factor.  However, the 
kernel
log --- CUT HERE --- ... NETDEV WATCHDOG occurs for me.

As I state above in my original post:

-
When I do connect, I am sending a lot of data. Hard to pin what actions are 
triggering the NETDEV WATCHDOG backtrace, but it leaves wlan1 in a state where 
it cannot come up again:

SIOCSIFFLAGS: No such device

ip address shows wlan1:  mtu 1500 qdisc mq state
DOWN group default qlen 1000

vcgencmd shows:
Aug 6 2020 16:24:09
version af3...d5b337 (clean) (release) (start)
---

Seems to me a driver issue when there is a flood of traffic.  The older version
of firmware I posted above solves the problem.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-10-06 Thread Christopher Yates
Bummers.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  571.879020]  __handle_domain_irq+0x70/0xc0
  Feb  4 23:42:59 rpi3 kernel: [  571.879028]  

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-09-12 Thread Christopher Yates
No idea.  I didn't march forward on the commits until it breaks, and I
don't know when the bug occurs or I'd scream about it.

What I do know is this old version is stable and I've had demonstrably
no problems with it.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-09-11 Thread Christopher Yates
4.19.75, https://github.com/Hexxeh/rpi-
firmware/commit/86b202d127ca3d413d0779d870cce2169afaacd7

Ancient.  And functional.  ;)

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 23:42:59 rpi3 kernel: [  

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-09-09 Thread Christopher Yates
@hamishbm -- I solved this by reverting to a prior fw release:

sudo rpi-update 86b202d127ca3d413d0779d870cce2169afaacd7

Zero issues since.  JFYI

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 :  x6 : 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878921] x5 :  x4 : 
0008
  Feb  4 23:42:59 rpi3 kernel: [  571.878929] x3 : 305e0ee15750 x2 : 
0004
  Feb  4 23:42:59 rpi3 kernel: [  571.878937] x1 : 6abb42c67c954600 x0 : 

  Feb  4 23:42:59 rpi3 kernel: [  571.878946] Call trace:
  Feb  4 23:42:59 rpi3 kernel: [  571.878955]  dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878967]  call_timer_fn+0x3c/0x178
  Feb  4 23:42:59 rpi3 kernel: [  571.878977]  __run_timers.part.0+0x200/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878985]  run_timer_softirq+0x40/0x78
  Feb  4 23:42:59 rpi3 kernel: [  571.878995]  __do_softirq+0x168/0x384
  Feb  4 23:42:59 rpi3 kernel: [  571.879007]  irq_exit+0xb0/0xe8
  Feb  4 

[Kernel-packages] [Bug 1894793] Re: High load freezes ubuntu completely everytime (have to reboot)

2020-09-09 Thread Christopher M. Penalver
Alois Dirnaichner, thank you for reporting this and making Ubuntu
better.

Iin order to allow additional upstream mainline kernel developers to examine 
the issue, at your earliest convenience, could you please test the latest 
mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** This bug is no longer a duplicate of bug 1555351
   High load freezes ubuntu completely everytime (have to reboot)

** Tags added: latest-bios-1.18.0

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  High load freezes ubuntu completely everytime (have to reboot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Followed the suggestion to report the Bug in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351 by
  Christopher Penalver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-115-generic 4.15.0-115.116
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alois  3256 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 09:07:16 2020
  InstallationDate: Installed on 2018-05-15 (846 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude 7480
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=32418d9d-1b21-4d1f-91ed-be3fd7ad01cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-115-generic N/A
   linux-backports-modules-4.15.0-115-generic  N/A
   linux-firmware  1.173.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd06/05/2020:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894793/+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 1873809] Re: Make linux-kvm bootable in LXD VMs

2020-08-25 Thread Christopher Townsend
Both the 18.04 & 16.04 Ubuntu Minimal cloud images use the kvm kernel by
default, so we need this fix applied to those kernels as well.  Are
there plans for that so that we can use those Minimal images in LXD?

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

Title:
  Make linux-kvm bootable in LXD VMs

Status in cloud-images:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released

Bug description:
  The `disk-kvm.img` images which are to be preferred when run under
  virtualization, currently completely fail to boot under UEFI.

  A workaround was put in place such that LXD instead will pull generic-
  based images until this is resolved, this however does come with a
  much longer boot time (as the kernel panics, reboots and then boots)
  and also reduced functionality from cloud-init, so we'd still like
  this fixed in the near future.

  To get things behaving, it looks like we need the following config
  options to be enable in linux-kvm:

   - CONFIG_EFI_STUB
   - CONFIG_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS
   - CONFIG_VIRTIO_VSOCKETS_COMMON

  == Rationale ==
  We'd like to be able to use the linux-kvm based images for LXD, those will 
directly boot without needing the panic+reboot behavior of generic images and 
will be much lighter in general.

  We also need the LXD agent to work, which requires functional virtio
  vsock.

  == Test case ==
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz 
focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809
   - lxc launch bug1873809 v1
   - lxc console v1
   - 
   - 
   - lxc exec v1 bash

  To validate a new kernel, you'll need to manually repack the .img file
  and install the new kernel in there.

  == Regression potential ==
  I don't know who else is using those kvm images right now, but those changes 
will cause a change to the kernel binary such that it contains the EFI stub 
bits + a signature. This could cause some (horribly broken) systems to no 
longer be able to boot that kernel. Though considering that such a setup is 
common to our other kernels, this seems unlikely.

  Also, this will be introducing virtio vsock support which again, could
  maybe confused some horribly broken systems?

  
  In either case, the kernel conveniently is the only package which ships 
multiple versions concurently, so rebooting on the previous kernel is always an 
option, mitigating some of the risks.

  
  -- Details from original report --
  User report on the LXD side: https://github.com/lxc/lxd/issues/7224

  I've reproduced this issue with:
   - wget 
http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img
   - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda 
focal-server-cloudimg-amd64-disk-kvm.img -m 1G

  On the graphical console, you'll see EDK2 load (TianoCore) followed by basic 
boot messages and then a message from grub (error: can't find command 
`hwmatch`).
  Those also appear on successful boots of other images so I don't think 
there's anything concerning that. However it'll hang indefinitely and eat up 
all your CPU.

  Switching to the text console view (serial0), you'll see the same
  issue as that LXD report:

  BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found
  BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from 
PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0)
  error: can't find command `hwmatch'.
  e X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 
 
  ExceptionData - 
  RIP  - 3FF2DA12, CS  - 0038, RFLAGS - 00200202
  RAX  - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF
  RBX  - 0398, RSP - 3FF1C638, RBP - 3FF34360
  RSI  - 3FF343B8, RDI - 1000
  R8   - 3E80F108, R9  - 3E815B98, R10 - 0065
  R11  - 2501, R12 - 0004, R13 - 3E80F100
  R14  - , R15 - 
  DS   - 0030, ES  - 0030, FS  - 0030
  GS   - 0030, SS  - 0030
  CR0  - 80010033, CR2 - , CR3 - 3FC01000
  CR4  - 0668, CR8 - 
  DR0  - , DR1 - , DR2 - 
  DR3  - , DR6 - 0FF0, DR7 - 0400
  GDTR - 3FBEEA98 0047, LDTR 

[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)

2020-08-22 Thread Christopher Yates
RPI 3B+.  My configuration is as follows:
Raspian (buster)
5.4.51-v7+#1333 SMP Mon Aug 10 16:45:19 BST 2020

wlan0 AP, no bridge, fixed IP.
wlan1 USB Wifi adapter
ppp0 Hologram Nova Modem

My application is in the field, so Wifi HotSpots can be unreliable (I
can get an IP but can't connect).  So I watch to see if I can get to the
internet through wlan1 and if I cannot, I switch to cellular.  Once on
cellular, I look to see if I can get to the Internet via wlan1 (cheaper
/ faster) by ifconfig wlan1 up.

When I do connect, I am sending a lot of data.  Hard to pin what actions
are triggering the NETDEV WATCHDOG backtrace, but it leaves wlan1 in a
state where it cannot come up again:

SIOCSIFFLAGS:  No such device

ip address shows wlan1:  mtu 1500 qdisc mq state
DOWN group default qlen 1000

vcgencmd shows:
Aug 6 2020 16:24:09
version af3...d5b337 (clean) (release) (start)

Not clear this is the same issue, but I thought I'd report as a use
case.

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

Title:
  Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel
  network load ((lan78xx): transmit queue 0 timed out)

Status in linux-raspi2 package in Ubuntu:
  Incomplete
Status in linux-raspi2 source package in Eoan:
  Won't Fix
Status in linux-raspi2 source package in Focal:
  Confirmed

Bug description:
  Desciption changed:
  Raspberry Pi 3 network partially dies (transmission doesn't work, reception 
still does) shortly after a burst of network load over IPv6, when IPv6 
connectivity is provided by a tunnel from tunnelbroker.net. The triggering load 
is typically an HTTP(S) download, and replication can be done without actually 
saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 
GB, usually withinthe first 1 GB of traffic)
  Replication is 100% as long as _all_ of the following conditions are met 
  - 6in4 tunnel to HE.net set up with netplan
  - ipv6 rules applied (netfilter-persistent)
  - ipv6 forwarding enabled (edit /etc/sysctl.conf)

  
  kern.log message that appears after a while:

  Feb  4 23:42:59 rpi3 kernel: [  571.878359] [ cut here 
]
  Feb  4 23:42:59 rpi3 kernel: [  571.878420] NETDEV WATCHDOG: eth0 (lan78xx): 
transmit queue 0 timed out
  Feb  4 23:42:59 rpi3 kernel: [  571.878550] WARNING: CPU: 3 PID: 0 at 
net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878557] Modules linked in: sit tunnel4 
ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack 
nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil 
cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) 
v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 
raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel 
jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed 
aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64
  Feb  4 23:42:59 rpi3 kernel: [  571.878774] CPU: 3 PID: 0 Comm: swapper/3 
Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu
  Feb  4 23:42:59 rpi3 kernel: [  571.878781] Hardware name: Raspberry Pi 3 
Model B Plus Rev 1.3 (DT)
  Feb  4 23:42:59 rpi3 kernel: [  571.878789] pstate: 6045 (nZCv daif +PAN 
-UAO)
  Feb  4 23:42:59 rpi3 kernel: [  571.878800] pc : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878807] lr : dev_watchdog+0x324/0x330
  Feb  4 23:42:59 rpi3 kernel: [  571.878812] sp : 1001bd60
  Feb  4 23:42:59 rpi3 kernel: [  571.878817] x29: 1001bd60 x28: 
0140
  Feb  4 23:42:59 rpi3 kernel: [  571.878827] x27:  x26: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878836] x25: 8ecbefa4e000 x24: 
305e0f529018
  Feb  4 23:42:59 rpi3 kernel: [  571.878845] x23:  x22: 
0001
  Feb  4 23:42:59 rpi3 kernel: [  571.878853] x21: 8ecbefa4e480 x20: 
305e0f807000
  Feb  4 23:42:59 rpi3 kernel: [  571.878862] x19:  x18: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878871] x17: 10fd8218 x16: 
305e0e30efb8
  Feb  4 23:42:59 rpi3 kernel: [  571.878879] x15: 8ecbf922a290 x14: 

  Feb  4 23:42:59 rpi3 kernel: [  571.87] x13:  x12: 
305e0f944000
  Feb  4 23:42:59 rpi3 kernel: [  571.878897] x11: 305e0f82d000 x10: 

  Feb  4 23:42:59 rpi3 kernel: [  571.878905] x9 : 0004 x8 : 
017f
  Feb  4 23:42:59 rpi3 kernel: [  571.878913] x7 : 

[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU

2020-08-03 Thread Christopher Clapp
I had a similar issue with an existing Ubuntu 16.04 LTS install on my
Dell Precision 5820 tower that has booted without issue for 2 years.
After updating the BIOS via the Ubuntu Software Center (to 1.13.0), my
computer gave only a black screen.

After clearing the BIOS, CMOS and NVRAM by removing the CMOS battery, it
would only boot to BusyBox.  BusyBox gave me a "ALERT! UUID=*** does not
exist. Dropping to a shell" error.

My OS is installed on a NVMe PCIe SSD boot drive, and I have a single SATA file 
drive.  
   
Setting the SATA Operation from to "AHCI" and Disabling the "Intel VMD 
Technology" under System Configuration in the BIOS seems to have solved the 
issue for me as well.  (@kvasko - thank you!)

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

Title:
  Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell 
Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. 

  I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then
  starts throwing a bunch of error messages stating

  [33.192238] nouveau :05:00.0: DRM: base-0: timeout

  repeating over and over again. It never gets past this.

  I tried the suggestions of adding "nomodeset" in grub when I'm
  booting. It progresses a little further but hangs at "failed to start
  Ubuntu Installation Service, please run journalctl to see what
  failed". I can't see what failed as I can't get a prompt since nothing
  is installed. I don't know where to go debug from here.

  My computer boots to a black screen, what options do I have to fix it?

  Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA
  graphics

  Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes -
  Nouveau/Nvidia Driver issue 1080ti

  Ubuntu 16.04 installation blank screen

  Ubuntu 16.04 unable to boot with GTX 1080

  etc.

  However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with
  the video and was successfully able to install Ubuntu 16.04.1.
  Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM
  network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit
  the same behavior as 16.04.5 with the video.

  Just as a test, I installed 16.04.1, installed broadcom NIC (which was
  successfully detected), and upgraded from 16.04.1 --> 16.04.5 with
  apt-get and had no video issues after reboot (I didn't install the
  video drivers), in addition, after it was upgraded to 16.04.5 the
  Intel 219-LM drivers were added and would work. I have a workaround,
  but it's REALLY annoying.

  The kicker in this is that the Dell Precision 5810 worked 100%
  correctly. Put the USB boot drive in, select the drive in UEFI to boot
  and everything works out of the box.

  I'm working on gathering more logs of this issue and testing different
  kernel versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+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 1874010] Re: [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot in kernel 5.4, but 5.5.19 has no problem

2020-05-20 Thread Christopher Chafin
I just wanted to update that updating the bios for my laptop (Dell XPS
13 9300) fixed the issue without needing a different kernel.

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

Title:
  [Ice Lake] 2-second black screen blips when using Chrome or gnome-
  screenshot in kernel 5.4, but 5.5.19 has no problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Im using a HP 14s dq laptop with intel 630 graphics.

  I've tried both the mode setting and xserver-xorg-video-intel drivers,
  both result in the same 2-second black screen blips. The happens
  frequently using chrome, and always when using the gnome screenshot
  utility. Also, during boot teh screen flickers between black screen
  and boot splash a lot.

  setting nomodeset as a grub parameter stops the flickering, but is not
  a feasible solution as brightness can no longer be set.

  kind regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 08:15:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.4.0-21-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-24-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:86c8]
  InstallationDate: Installed on 2020-04-16 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP Laptop 14s-dq1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic 
root=UUID=54a7cc42-ac04-4466-b29f-16b1a7016ed0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86C8
  dmi.board.vendor: HP
  dmi.board.version: 56.31
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop14s-dq1xxx:pvr:rvnHP:rn86C8:rvr56.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14s-dq1xxx
  dmi.product.sku: 8BL04EA#ABH
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874010/+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 1874010] Re: [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot

2020-05-17 Thread Christopher Chafin
I have the same exact problem, on Kubuntu 20.04 with Dell XPS 13 9300,
using another kernel does fix it, but I have no wifi as a result and
couldn't seem to solve that myself.

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

Title:
  [Ice Lake] 2-second black screen blips when using Chrome or gnome-
  screenshot

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

Bug description:
  Hi,

  Im using a HP 14s dq laptop with intel 630 graphics.

  I've tried both the mode setting and xserver-xorg-video-intel drivers,
  both result in the same 2-second black screen blips. The happens
  frequently using chrome, and always when using the gnome screenshot
  utility. Also, during boot teh screen flickers between black screen
  and boot splash a lot.

  setting nomodeset as a grub parameter stops the flickering, but is not
  a feasible solution as brightness can no longer be set.

  kind regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 08:15:51 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.4.0-21-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-24-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:86c8]
  InstallationDate: Installed on 2020-04-16 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP Laptop 14s-dq1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic 
root=UUID=54a7cc42-ac04-4466-b29f-16b1a7016ed0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86C8
  dmi.board.vendor: HP
  dmi.board.version: 56.31
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop14s-dq1xxx:pvr:rvnHP:rn86C8:rvr56.31:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14s-dq1xxx
  dmi.product.sku: 8BL04EA#ABH
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874010/+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 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries

2020-05-08 Thread Christopher M. Rogers
Still an issue in the latest Ubuntu 20.04 release.
User winds up having to click the toggle over and over again while it 
stubbornly snaps back.
Replicated on Many different machines with different hardware.

Is there anyone who can not replicate this bug?


** Changed in: bluez (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Bluetooth "Connection switch" snaps back by itself until after many
  tries

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Attempting to slide the "Connection" switch in the gui to connect a
  bluetooth device fails initially -- the switch moves but "snaps back"
  by itself immediately.   Clicking on the switch flashes the "busy"
  indicator momentarily, but the switch does not move.   After a while,
  connecting succeeds.

  I don't know if the mouse input is not recognized until the "Nth"
  attempt, or else the connection was in-progress all along but the gui
  was not tracking that correctly.

  Please watch the attached video (use vlc).

  NOTE: This system is running a non-standard kernel 5.2 in order to
  circumvent other problems (see bug 1838180).

  Again, see the video; there is something wrong with how the GUI
  communicates with the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluez 5.50-0ubuntu2
  Uname: Linux 5.2.0-050200-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 22:46:28 2019
  InstallationDate: Installed on 2019-02-06 (173 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago)
  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.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   
  rfkill:
   
  syslog:
   Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]:   
[1564378931.7693] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so)
   Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted 
in Bluetooth service being skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+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 1876211] [NEW] Bluetooth connection to headset works for volume buttons but not tests

2020-04-30 Thread Christopher Barrington-Leigh
Public bug reported:

bluetooth worked fine under 19.10.
 Now, when bluetooth connects to my headset, I can hear noises from the 
increase/ decrease volume keys, but the "test" for Output Device in Sound 
settings makes sound on my laptop, not the headset.
 And all applications send sound to the laptop, not the headset.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 19:39:09 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-11-26 (156 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20BX001PUS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET66WW (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BX001PUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BX001PUS
dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: DC:53:60:42:C0:97  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:22321 acl:74 sco:0 events:1206 errors:0
TX bytes:257018 acl:319 sco:0 commands:403 errors:0
syslog:

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth connection to headset works for volume buttons but not tests

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth worked fine under 19.10.
   Now, when bluetooth connects to my headset, I can hear noises from the 
increase/ decrease volume keys, but the "test" for Output Device in Sound 
settings makes sound on my laptop, not the headset.
   And all applications send sound to the laptop, not the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 19:39:09 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-11-26 (156 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BX001PUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001PUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX001PUS
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:53:60:42:C0:97  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:22321 acl:74 sco:0 events:1206 errors:0
TX bytes:257018 acl:319 sco:0 commands:403 errors:0
  syslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1876211/+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 1876039] [NEW] package linux-image-5.4.0-28-generic 5.4.0-28.32 failed to install/upgrade: installed linux-image-5.4.0-28-generic package pre-removal script subprocess returned

2020-04-30 Thread Christopher King
Public bug reported:

The system software updater prompted me to update, hung at about 4/5
completion according to the progress bar.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-28-generic 5.4.0-28.32
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 30 02:13:04 2020
ErrorMessage: installed linux-image-5.4.0-28-generic package pre-removal script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-04-24 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IwConfig:
 lono wireless extensions.
 
 enp5s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=cfc208c4-6703-475e-9049-d91c4eb6f807 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
RfKill:
 
SourcePackage: linux
Title: package linux-image-5.4.0-28-generic 5.4.0-28.32 failed to 
install/upgrade: installed linux-image-5.4.0-28-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50a
dmi.board.asset.tag: Default string
dmi.board.name: AB350M-DS3H-CF
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.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350M-DS3H
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-package focal

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

Title:
  package linux-image-5.4.0-28-generic 5.4.0-28.32 failed to
  install/upgrade: installed linux-image-5.4.0-28-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system software updater prompted me to update, hung at about 4/5
  completion according to the progress bar.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-28-generic 5.4.0-28.32
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 30 02:13:04 2020
  ErrorMessage: installed linux-image-5.4.0-28-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=cfc208c4-6703-475e-9049-d91c4eb6f807 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.4.0-28-generic 5.4.0-28.32 failed to 
install/upgrade: installed linux-image-5.4.0-28-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350M-DS3H-CF
  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: 

[Kernel-packages] [Bug 1863479] [NEW] package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post-installation script subprocess returne

2020-02-16 Thread Christopher Golden
Public bug reported:

I tried to remove the package also

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-compute-utils-435 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Sun Feb 16 15:52:50 2020
ErrorMessage: installed nvidia-compute-utils-435 package post-installation 
script subprocess returned error exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.9
SourcePackage: nvidia-graphics-drivers-435
Title: package nvidia-compute-utils-435 (not installed) failed to 
install/upgrade: installed nvidia-compute-utils-435 package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-01-24 (23 days ago)

** Affects: nvidia-graphics-drivers-435 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-compute-utils-435 (not installed) failed to
  install/upgrade: installed nvidia-compute-utils-435 package post-
  installation script subprocess returned error exit status 1

Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  I tried to remove the package also

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-435 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Sun Feb 16 15:52:50 2020
  ErrorMessage: installed nvidia-compute-utils-435 package post-installation 
script subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.9
  SourcePackage: nvidia-graphics-drivers-435
  Title: package nvidia-compute-utils-435 (not installed) failed to 
install/upgrade: installed nvidia-compute-utils-435 package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-01-24 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1863479/+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 1799180] Re: Ubuntu 18.10 / Linux 4.19 -rc7/8/Final - System slows / stops

2020-02-11 Thread Christopher Patti
This is fixed across all environments in Ubuntu 20.04

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

Title:
  Ubuntu 18.10 / Linux 4.19 -rc7/8/Final - System slows / stops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there folks sorry if it's inappropriate to report a bug in an
  upstream release candidate kernel, but as a suggested test / fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743 I was
  told to install an upstream kernel, which I did.

  When I run with that kernel for any length of time, or do anything
  involving high CPU (like run Firefox for instance) the system fan
  begins to whine and the system slows down to the point where it
  finally hangs.

  I tried to run 'ubuntu-bug linux' from the terminal, but when I do I
  get the error seen in the screenshot (attached).

  I'll go back to running 4.18 for now because not being able to sleep
  the laptop isn't a show stopper, but it's definitely something I
  consider important for a fully fledged operating system / work
  environment :)

  Thanks and please let me know if there's anything I can do to provide more 
data / help with testing / etc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-07 (14 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-07 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799180/+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 1796743] Re: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep

2020-02-11 Thread Christopher Patti
Hi! This is definitely fixed in Ubuntu 20.04 - my laptop now sleeps like
a champ with no issues or crashes.

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

Title:
  Ubuntu 18.10 - Alienware 17 R5 crashes on sleep

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If the machine goes to sleep, either because I close the lid or
  because it idles too long, it ends up in a weird state when I try to
  resume. If I press the power/Alien button, the fan runs and the
  keyboard/trackpad light up but nothing happens.

  Ultimately I need to hard power off the laptop (by holding the power
  button in for three seconds) which causes it to boot from scratch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feoh   2895 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Oct  8 14:25:16 2018
  InstallationDate: Installed on 2018-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  MachineType: Alienware Alienware 17 R5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.5.0
  dmi.board.name: Alienware 17 R5
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 17 R5
  dmi.product.sku: 0877
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796743/+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 1860787] Re: Suspend not working on Lenovo Carbon X1 after upgrade to 20.04

2020-01-29 Thread Christopher Townsend
Hi @p-pisati,

Yes, that is the new version.  I should also add that closing the lid is
suspending the machine and opening the lid is resuming it like I would
expect.

This may be fixed by the newer kernel and/or (an)other package(s).  I'm
content with the behavior now and I'm fine closing this bug.

If you'd still like me to try out the other kernel, let me know.

Thanks so much!

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

Title:
  Suspend not working on Lenovo Carbon X1 after upgrade to 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Either closing the laptop lid (via the setting in Gnome Tweak Tool) or
  issuing `systemctl suspend` results in the same behavior.  The screen
  will go blank, yet the power will remain on and the battery will drain
  slowly when off of AC power.  The only way to recover is to hard power
  off the system and cold boot.

  I should also add that I was originally on 18.04+HWE kernel with no
  issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 07:52:22 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860787/+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 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

2020-01-28 Thread kent christopher
Update: a kernel upgrade solved the mic white noise for me. I had been
running a 5.0 kernel. Updating to a 5.4 kernel fixed 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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  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 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net

[Kernel-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

2020-01-28 Thread kent christopher
Tyler, did you ever find a solution to this? I'm having the same problem
with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The
only "solution" I've found is to turn off "internal mic boost" using
alsa-mixer (hit F5 to show all channels, cursor all the way to the
right) and keep the mic capture level below 20%. So it works, but far
from ideal since the mic is low (but better than making the person on
the other end of a call hearing a shitload of white noise that's
produced otherwise).

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  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 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  

[Kernel-packages] [Bug 1860787] Re: Suspend not working on Lenovo Carbon X1 after upgrade to 20.04

2020-01-27 Thread Christopher Townsend
I'm not sure exactly what has changed, but a new kernel did install
today and suspend/resume is working much better.

`systemctl suspend` is working as expected.  However, closing the laptop
lid is not quite working yet.  When I close the lid, the power stays on,
but when I open the lid, it suspends.  A subsequent lid close and open
will resume the machine.

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

Title:
  Suspend not working on Lenovo Carbon X1 after upgrade to 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Either closing the laptop lid (via the setting in Gnome Tweak Tool) or
  issuing `systemctl suspend` results in the same behavior.  The screen
  will go blank, yet the power will remain on and the battery will drain
  slowly when off of AC power.  The only way to recover is to hard power
  off the system and cold boot.

  I should also add that I was originally on 18.04+HWE kernel with no
  issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 07:52:22 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860787/+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 1860697] Re: Sound doesn't work on Lenovo X1 Carbon with 20.04

2020-01-27 Thread Christopher Townsend
Hi @hui.wang,

Thank you very much for this.  It now works using the module parameter
you said to use.

Will there be some way that I will be notified that the sof-hda-generic-
4ch.tplg firmware has been incorporated into Ubuntu so I can remove the
workaround?

Thanks 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/1860697

Title:
  Sound doesn't work on Lenovo X1 Carbon with 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
  output and input, does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 12:00:01 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+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 1860787] [NEW] Suspend not working on Lenovo Carbon X1 after upgrade to 20.04

2020-01-24 Thread Christopher Townsend
Public bug reported:

Either closing the laptop lid (via the setting in Gnome Tweak Tool) or
issuing `systemctl suspend` results in the same behavior.  The screen
will go blank, yet the power will remain on and the battery will drain
slowly when off of AC power.  The only way to recover is to hard power
off the system and cold boot.

I should also add that I was originally on 18.04+HWE kernel with no
issues.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-9-generic 5.4.0-9.12
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 07:52:22 2020
InstallationDate: Installed on 2019-09-06 (139 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20QDCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic  N/A
 linux-firmware   1.184
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
dmi.bios.date: 12/09/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET43W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug champagne focal

** Description changed:

  Either closing the laptop lid (via the setting in Gnome Tweak Tool) or
  issuing `systemctl suspend` results in the same behavior.  The screen
  will go blank, yet the power will remain on and the battery will drain
  slowly when off of AC power.  The only way to recover is to hard power
  off the system and cold boot.
+ 
+ I should also add that I was originally on 18.04+HWE kernel with no
+ issues.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 07:52:22 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-9-generic N/A
-  linux-backports-modules-5.4.0-9-generic  N/A
-  linux-firmware   1.184
+  linux-restricted-modules-5.4.0-9-generic N/A
+  linux-backports-modules-5.4.0-9-generic  N/A
+  linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

-- 
You received 

[Kernel-packages] [Bug 1860697] [NEW] Sound doesn't work on Lenovo X1 Carbon with 20.04

2020-01-23 Thread Christopher Townsend
Public bug reported:

I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
output and input, does not work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-9-generic 5.4.0-9.12
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 23 12:00:01 2020
InstallationDate: Installed on 2019-09-06 (139 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20QDCTO1WW
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic  N/A
 linux-firmware   1.184
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
dmi.bios.date: 12/09/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET43W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug champagne focal

** Tags added: champagne

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

Title:
  Sound doesn't work on Lenovo X1 Carbon with 20.04

Status in linux package in Ubuntu:
  New

Bug description:
  I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
  output and input, does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 12:00:01 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+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 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2019-11-24 Thread Christopher M. Penalver
apsaras, it's helpful for developers if folks report their own bug so logs may 
be obtained from the hardware, regardless of similarities, via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

To do otherwise risks issues being ignored as unconfirmable noise.

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2019-11-03 Thread Christopher M. Penalver
Ilgaz, could you please report this problem following the instructions
at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate
mailing list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?

Please provide a direct URL to your post to the mailing list (not
Bugzilla) when it becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2019-11-03 Thread Christopher M. Penalver
Ilgaz, to help developers debug a potential ACPI/BIOS bug, could you please 
install the package acpidump and attach to this report uncompressed and 
untarred the following via a terminal:
sudo acpidump -o acpidump.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/1848445

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2019-11-03 Thread Christopher M. Penalver
** Summary changed:

- Kernel needs a special workaround argument to boot 
+ [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= 
required to boot

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-11-03 Thread Christopher M. Penalver
whl2:

1) As noted in #32, one will want to keep testing the latest upstream
kernel (now 5.4-rc5) as it is released, or one risks developers not
paying attention to your problem.

2) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

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

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-11-03 Thread Christopher M. Penalver
** Tags added: eoan needs-upstream-testing

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

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

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+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 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-03 Thread Christopher M. Penalver
Ilgaz, to clarify, did you actually try to gather logs as per all
techniques noted in
https://help.ubuntu.com/community/DebuggingSystemCrash or are you making
assumptions of your not being 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/1848445

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
Ilgaz:

To advise, you have missed steps in two different comments, which are
vital to proceed. Please ensure you are responding to all items
requested.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/comments/10:
C) To further clarify, does removing the external HDD device (USB?) impact your 
ability to boot?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/comments/13:
2) Please review https://help.ubuntu.com/community/DebuggingSystemCrash and 
attempt all suggestions to see if something useful may be obtained.

** Tags removed: kernel-bug-exists-upstream-5.4-rc3 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.4-rc5

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
Ilgaz:

1) To keep this relevant to upstream, you will want to continue to test
the latest mainline kernel as it is released (now 5.4-rc5). Instructions
are available via https://wiki.ubuntu.com/Kernel/MainlineBuilds .

2) Please review https://help.ubuntu.com/community/DebuggingSystemCrash
and attempt all suggestions to see if something useful may be obtained.

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
Ilgaz:

A) I'm afraid providing logs from a working boot does nothing to help.

B) To clarify, you removed all of the following kernel parameters:
quiet
splash
vt.handoff=7
acpi_osi=
pci=biosirq

then changed:
gfxmode $linux_gfx_mode

to:

gfxmode text

and then got the bad boot? If so, please provide video evidence starting
from the computer being off all the way to it stopped booting (e.g. take
a video of the computer screen via phone, get logs, etc.). Please note,
stating it was a bad boot isn't helpful given this was already known.

C) To further clarify, does removing the external HDD device (USB?)
impact your ability to boot?

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1848445/+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 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
** Description changed:

- When booting my computer, it stops with just a non-blinking white cursor
- on screen in the top left, and the Caps Lock doesn't respond when
- pressed.
+ When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops with
+ just a non-blinking white cursor on screen in the top left, and the Caps
+ Lock doesn't respond when pressed.
  
  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.
  
  WORKAROUND: Boot with kernel parameter:
  acpi_osi=
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

** Tags added: latest-bios-f.41

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  

[Kernel-packages] [Bug 1847151] Re: Touchpad not detected

2019-11-01 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847151/comments/4
.

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 5.0.0-31.33-generic 5.0.21 (from 5.0.0-29),
  my laptop's touchpad is no longer detected as a device. This is a new
  problem.

  Contents of /proc/bus/input/devices attached.

  Following directions from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss3353 F pulseaudio
   /dev/snd/controlC0:  pss3353 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct  7 14:14:13 2019
  InstallationDate: Installed on 2019-04-24 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=76a404c8-db6d-4ab3-8614-86dbef6fdda8 ro "acpi_osi=!acpi_osi=Windows 
2009" quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-29 (161 days ago)
  dmi.bios.date: 10/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17B7IMS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17B7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17B7IMS.10F:bd10/03/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS73 Stealth 8RF
  dmi.product.sku: 17B7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-04-25T10:50:34.601584

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


  1   2   3   4   5   6   7   8   9   10   >