[Kernel-packages] [Bug 1995196] Re: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1

2022-12-31 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso
  instalado, do pacote bluez, o script post-installation retornou erro
  do status de saída 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  From a release upgrade from 22.04 to 22.10

  (many moons ago) I had previously enabled pipewire on the 22.04
  install with the following:

  sudo apt install pipewire-audio-client-libraries libspa-0.2-bluetooth 
libspa-0.2-jack
  sudo apt install wireplumber pipewire-media-session-
  sudo apt remove pulseaudio-module-bluetooth
  systemctl --user --now enable wireplumber.service

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Oct 28 07:09:19 2022
  ErrorMessage: o subprocesso instalado, do pacote bluez, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2022-10-19 (9 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20V9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: bluez
  Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso 
instalado, do pacote bluez, o script post-installation retornou erro do status 
de saída 1
  UpgradeStatus: Upgraded to kinetic on 2022-10-28 (0 days ago)
  dmi.bios.date: 05/10/2022
  dmi.bios.release: 1.50
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F9CN50WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G2 ITL
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrF9CN50WW:bd05/10/2022:br1.50:efr1.44:svnLENOVO:pn20V9:pvrThinkBook13sG2ITL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG2ITL:skuLENOVO_MT_20V9_BU_idea_FM_ThinkBook13sG2ITL:
  dmi.product.family: ThinkBook 13s G2 ITL
  dmi.product.name: 20V9
  dmi.product.sku: LENOVO_MT_20V9_BU_idea_FM_ThinkBook 13s G2 ITL
  dmi.product.version: ThinkBook 13s G2 ITL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 64:79:F0:9D:09:A8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:21280 acl:17 sco:0 events:3348 errors:0
TX bytes:816597 acl:17 sco:0 commands:3319 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1995196/+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 2000822] [NEW] package libnvidia-compute-418-server (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui ap

2022-12-31 Thread Boukary
Public bug reported:

My nvidia version is 340 but a face issue with version 418 while
installing cuda

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-compute-418-server (not installed)
ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
Uname: Linux 5.4.0-135-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Dec 31 19:43:49 2022
ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.108-0ubuntu5.20.04.2
InstallationDate: Installed on 2022-12-31 (0 days ago)
InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: nvidia-graphics-drivers-418-server
Title: package libnvidia-compute-418-server (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.108-0ubuntu5.20.04.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-418-server (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-418-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2000822

Title:
  package libnvidia-compute-418-server (not installed) failed to
  install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-
  gnu/libnvidia-ml.so », qui appartient aussi au paquet nvidia-340
  340.108-0ubuntu5.20.04.2

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

Bug description:
  My nvidia version is 340 but a face issue with version 418 while
  installing cuda

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-418-server (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-135.152-generic 5.4.212
  Uname: Linux 5.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Dec 31 19:43:49 2022
  ErrorMessage: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.108-0ubuntu5.20.04.2
  InstallationDate: Installed on 2022-12-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: nvidia-graphics-drivers-418-server
  Title: package libnvidia-compute-418-server (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so », qui appartient aussi au paquet 
nvidia-340 340.108-0ubuntu5.20.04.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/2000822/+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 1994126] Re: NULL pointer dereference in power_supply_get_property

2022-12-31 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+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 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach

2022-12-31 Thread Peter Dedecker
Hi Daniel et al,

Happy new year if you're already in the new year!

Yesterday, I got the same issue: poor resolution with the (new) DP
cable. Unplugging and reconnection without success.

However, just unplugging and inserting the cable in another port did
some magic and brought the full resolution back. Reconnecting in the
right port again caused a restart of Wayland, but again in full
resolution.

After a recovery from suspend later today, I got no mousse functioning,
neither the external USB one, neither the internal mousepad. Pressing
the windows key caused only the main display to show both workspaces,
whilst all open windows at the external display stayed in place.
Reconnecting the USB made no difference. However, unplugging and
reconnecting the external monitor (USB-C - DP cable) made the mousse
work again.

What could be wrong or debugged in this weird situation? Thanks!

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

Title:
  [i915] Maximum resolution not available after suspend / screen detach

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my 
laptop which is used at two locations:
  - at work I have my primary built-in 4K display and 2 additional 1920x1080 
monitor connected to a HP DisplayLink docking station using DP, connected to my 
laptop using USB-C
  - at home, I have my primary built-in 4K display and an additional 4x monitor 
directly connected using the mini-DP

  After boot, everything works perfect. However, after working at work,
  putting the laptop into suspend (by closing the lid), attaching to my
  monitor at home and opening the lid again, I get my external display
  at a poor resolution which I cannot change to 4K in the settings menu:
  the 4K resolution is not available. Also in xrandr, the 4K resolution
  is not available. The resolution is however correctly provided by the
  monitor at all times:

  $ sudo get-edid -b 8 | parse-edid
  8
  This is read-edid version 3.0.2. Prepare for some fun.
  Attempting to use i2c interface
  Only trying 8 as per your request.
  256-byte EDID successfully retrieved from i2c bus 8
  Looks like i2c was successful. Have a good day.
  Checksum Correct

  Section "Monitor"
Identifier "PHL 328P6V"
ModelName "PHL 328P6V"
VendorName "PHL"
# Monitor Manufactured week 30 of 2020
# EDID version 1.4
# Digital Display
DisplaySize 700 400
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-160
VertRefresh 23-80
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x960, 60Hz
#Not giving standard mode: 1440x900, 75Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1280x720, 60Hz

#Extension block found. Parsing...
Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 
2191 +hsync -vsync 
Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168  
+hsync -vsync 
Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 
1125 +hsync +vsync interlace
Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 
+hsync +vsync 
Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 
 +hsync -vsync 
Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 
 +hsync -vsync 
Option "PreferredMode" "Mode 12"
  EndSection

  
  Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which 
could easily be solved by unplugging the external monitor and plugging in back 
again, which worked most of the times, sometimes only after a few retries. Now, 
with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. 

[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend

2022-12-31 Thread Johannes Mayrhofer
Hi,
I am experiencing this exact same bug on Manjaro with Kernels 6.0.x and 6.1.x.
@Kai-Heng Feng, could you please provide the patch you used for `lp1988346-5` 
so I could test if this fixes in those kernels as well?
Thanks for your work!

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

Title:
  cm32181 module error blocking suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to 22.04.1 (from 20.04) suspend gets interrupted and
  the system returns after a few seconds.

  journalctl output
  ```
  Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep)
  Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds
  Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... 
(elapsed 0.002 seconds) done.
  Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled.
  Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... 
(elapsed 3.894 seconds) done.
  Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI 
cache
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): 
acpi_subsys_suspend+0x0/0x60 returns -121
  Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to 
suspend: error -121
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or 
early wake event detected
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk
  Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated 
(0x6)
  Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled.
  Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done.
  Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake 
event 0x0
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle)
  Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds
  Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... 
(elapsed 0.005 seconds) done.
  Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled.
  Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... 
  Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM 
TrackPoint firmware: 0x0e, buttons: 3/3
  Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as 
/devices/rmi4-00/rmi4-00.fn03/serio2/input/input196
  Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done.
  Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI 
cache
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): 
acpi_subsys_suspend+0x0/0x60 returns -121
  Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to 
suspend: error -121
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or 
early wake event detected
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk
  Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated 
(0x6)
  Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled.
  Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done.
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: 
Deactivated successfully.
  Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake 
event 0x0
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to 
sleep. System resumed again: Remote I/O error
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda:
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]:  setting Advanced Power 
Management level to 0xfe (254)
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]:  APM_level= 254
  Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]:   
[1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 
uid=0 result="success"
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main 
process exited, code=exited, status=1/FAILURE
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed 
with result 'exit-code'.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job 
suspend.target/start failed with result 'dependency'.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: 

[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property

2022-12-31 Thread lirel
Back in October I already mentioned what would fix this issue, but afaik
nobody did backport the needed change from 5.19.8 to any respin of the
installer iso. So for me there is no way to install ubuntu 22.10 by now.
Let's keep watching for duplicates of this bug that might get more
attention by the kernel-team until they apply the patch. Launchpad
doesn't give me any buttons to draw more attention to this issue or
provide changes to the package directly. But i can try to upload the
*SPECULATIVE* patch from kernel.org again ;)

** Patch added: "Speculative patch from T. Iwai: Revert "usb: typec: ucsi: add 
a common function  ucsi_unregister_connectors()""
   
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/patch/?id=3d4044c9e6d2e3f11f1f8b5e0ee8647d3eb1afad

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

Title:
  NULL pointer dereference in power_supply_get_property

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 
(containing nvidia gpu)
  reproducible kernel panic during boot

  backtrace via OCR from picture of kernel panic:

  Started Periodic ext4 Online Hetadata Check for All Filesystems. Started
  Discard unused blocks once a week.

  Started Refresh fuupd metadate regularly. Started Daily rotation
  of log files.

  Started Daily man-db regeneration.

  Started Message of the Day.

  Started Daily Cleanup of Temporary Directories.

  Started Ubuntu Advantage Timer for running repeated jobs.

  Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation
  Socket.

  1 Listening on CUPS Scheduler.

  1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation
  for snappy deeson...

  Listening on UUID deemon activation socket. 1 Listening on Socket 
activation
  for snappy daemon.

  Reached target Socket Units. 1 Reached target Basic System.

  20.300662) BUG: Kernel NULL pointer dereference, address:
  

  20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 
WPF:
  error code (0x0010) - not-present page

  20.302458) PGD O P40 0

  20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579)

  CPU: 4 PID: 1 Comm: systemd Tainted: P

  0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 
20L5000BGE/20L5000BGE,
  BIOS N24ET7ON (1.45) 07/22/2022

  20.304190)

  20.304774) RIP: 0010:0N0

  20.305376) Code: Unable to access opcode bytes at RIP Oxffd6.
  20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202

  20.3066231 RAX:  RBX: 95538288 RCX: 
8c43c1d89800
  20.307282) RDX: b17180087cdo RSI: 0004 RDI: 
8c43c1d89800

  20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09:
  0

  20.308627) R10:  R11:  R12:
  00

  20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15:
  9553a288

  20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000
  20.310762) CS: 0010 DS:  ES:  CRO: 80050033

  20.311491) CR2:  fffds CRS: 00011eida002 CR4:
  003706e0

  20.312241) Call Trace:

  20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+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 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee

2022-12-31 Thread Attila
I downloaded and installed Ubuntu 16.04 on Dell Latitude 7390 and with
this version of Ubuntu, the laptop seems to be running fine EVEN after
suspend. It goes into sleep and wakes up without ANY errors or
malfunction so far. I am looking forward to any suggestion or tips if
you have.

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

Title:
  Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-
  recoverable after screen lock and screen completely fades to black or
  after system goes into sleep

Status in linux-hwe-5.4 package in Ubuntu:
  Invalid

Bug description:
  This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390.

  The system is non-recoverable after it goes into sleep. Or after the
  screen is locked by the user and after it fades to complete black.
  System becomes unresponsive, no mouse or keypress will get the system
  back on to work.

  If the systemctl suspend is issued, the system will not wake up again.
  Hard reset is needed.

  If Ubuntu 18.04.6 is booted from live USB, the same is happening.

  Sometimes, when the system is rendered unresponsive as a result of any
  of the above, the power led is sending the message of "processor
  failure" (2 x amber blinks followed by 1 x white blink).

  Any help is greatly appreciated! I will keep the system as is, without
  applying any updates for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 27 01:13:12 2022
  InstallationDate: Installed on 2022-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  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-hwe-5.4/+bug/2000491/+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