[Kernel-packages] [Bug 2024331] Re: Bluetooth fails to work after updating to linux-image-6.2.0-23-generic

2023-06-18 Thread Alex Murray
Hmm after rebooting a few more times I see Bluetooth is now working as
expected on linux-image-6.2.0-23-generic - setting this ticket to
Incomplete unless I can gather some more information.

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

Title:
  Bluetooth fails to work after updating to linux-image-6.2.0-23-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the latest kernel updates in Lunar, I can no longer
  enable Bluetooth in GNOME.

  Rebooting back into 6.2.0-20-generic allows it to work again.

  Looking at the journalctl log between the two, I see the following
  differences for hci0:

  
  $ diff <(journalctl -b-3 --grep hci0 --output short-monotonic | cut -c16-) 
<(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-)
  12c12
  < graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs
  ---
  > graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs
  14c14
  < graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs
  ---
  > graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs
  19c19,22
  < graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: 
fd(44) ready
  ---
  > graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
  > graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features 
(-110)
  > graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03
  > graphene kernel: Bluetooth: hci0: Intel version event size mismatch

  
  This looks similar to 
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 
but I am filing a separate bug since that doesn't appear to have any traction.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 19 10:31:38 2023
  InstallationDate: Installed on 2021-08-03 (684 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  MachineType: LENOVO 20XWCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-23-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-23-generic N/A
   linux-backports-modules-6.2.0-23-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-01-27 (142 days ago)
  dmi.bios.date: 04/05/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET84W (1.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET84W(1.60):bd04/05/2023:br1.60:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

2023-06-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  LG Gram hangs at black screen on suspend on Ubuntu 23.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop is an LG Gram, model number 15Z980-R.AAS9U1. I am running
  the latest BIOS.

  Ever since upgrading to Ubuntu 23.04, my computer frequently hangs
  upon suspending to RAM and I am not able to recover it. The hang
  occurs on suspend rather than resume. I have my configuration set to
  suspend upon closing my laptop's lid. The first time I suspend after
  boot, it almost always suspends properly and appears to resume with no
  issues. Starting on the second or third suspend attempt, my computer's
  screen goes black (backlight off) but it never actually enters suspend
  state, as indicated by the power LED, processor temperature, and
  battery drain, which indicate the computer is still on. I am not able
  to recover the computer to a working state from this point -- it does
  not respond to any keyboard or touchpad input I have tried, or further
  closings/openings of the lid, and I need to hold the power button for
  several seconds to force a hard restart. Once it restarts, the first
  one or two suspend cycles will work again, and then the pattern
  continues.

  I experienced very infrequent suspend hang problems on 22.10, which
  were rare enough that I did not troubleshoot them. This problem
  appeared immediately after upgrading to 23.04. I use the Wayland
  environment by default but have also tried X11 mode to troubleshoot
  and the problem seemed to occur there too. Let me know what further
  troubleshooting would be helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andy   2317 F wireplumber
   /dev/snd/seq:andy   2305 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 18 23:00:17 2023
  InstallationDate: Installed on 2018-12-01 (1660 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10a5:0007 FPC FPC Sensor Controller
   Bus 001 Device 003: ID 0bda:562e Realtek Semiconductor Corp. LG Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LG Electronics 15Z980-R.AAS9U1
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic 
root=UUID=f2bf5af7-5cc8-4a4f-83e3-1b60fd7b6da7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-23-generic N/A
   linux-backports-modules-6.2.0-23-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (58 days ago)
  dmi.bios.date: 04/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: K2ZC0254 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 15Z980
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 63.41
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrK2ZC0254X64:bd04/02/2018:br0.1:efr63.41:svnLGElectronics:pn15Z980-R.AAS9U1:pvr0.1:rvnLGElectronics:rn15Z980:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:sku:
  dmi.product.family: Z Series
  dmi.product.name: 15Z980-R.AAS9U1
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024336/+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 2024336] [NEW] LG Gram hangs at black screen on suspend on Ubuntu 23.04

2023-06-18 Thread Andy Pearson
Public bug reported:

My laptop is an LG Gram, model number 15Z980-R.AAS9U1. I am running the
latest BIOS.

Ever since upgrading to Ubuntu 23.04, my computer frequently hangs upon
suspending to RAM and I am not able to recover it. The hang occurs on
suspend rather than resume. I have my configuration set to suspend upon
closing my laptop's lid. The first time I suspend after boot, it almost
always suspends properly and appears to resume with no issues. Starting
on the second or third suspend attempt, my computer's screen goes black
(backlight off) but it never actually enters suspend state, as indicated
by the power LED, processor temperature, and battery drain, which
indicate the computer is still on. I am not able to recover the computer
to a working state from this point -- it does not respond to any
keyboard or touchpad input I have tried, or further closings/openings of
the lid, and I need to hold the power button for several seconds to
force a hard restart. Once it restarts, the first one or two suspend
cycles will work again, and then the pattern continues.

I experienced very infrequent suspend hang problems on 22.10, which were
rare enough that I did not troubleshoot them. This problem appeared
immediately after upgrading to 23.04. I use the Wayland environment by
default but have also tried X11 mode to troubleshoot and the problem
seemed to occur there too. Let me know what further troubleshooting
would be helpful.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-23-generic 6.2.0-23.23
ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
Uname: Linux 6.2.0-23-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andy   2317 F wireplumber
 /dev/snd/seq:andy   2305 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 18 23:00:17 2023
InstallationDate: Installed on 2018-12-01 (1660 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 10a5:0007 FPC FPC Sensor Controller
 Bus 001 Device 003: ID 0bda:562e Realtek Semiconductor Corp. LG Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LG Electronics 15Z980-R.AAS9U1
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic 
root=UUID=f2bf5af7-5cc8-4a4f-83e3-1b60fd7b6da7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-23-generic N/A
 linux-backports-modules-6.2.0-23-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
SourcePackage: linux
UpgradeStatus: Upgraded to lunar on 2023-04-21 (58 days ago)
dmi.bios.date: 04/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: K2ZC0254 X64
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 15Z980
dmi.board.vendor: LG Electronics
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LG Electronics
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 63.41
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrK2ZC0254X64:bd04/02/2018:br0.1:efr63.41:svnLGElectronics:pn15Z980-R.AAS9U1:pvr0.1:rvnLGElectronics:rn15Z980:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:sku:
dmi.product.family: Z Series
dmi.product.name: 15Z980-R.AAS9U1
dmi.product.version: 0.1
dmi.sys.vendor: LG Electronics

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


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

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

Title:
  LG Gram hangs at black screen on suspend on Ubuntu 23.04

Status in linux package in Ubuntu:
  New

Bug description:
  My laptop is an LG Gram, model number 15Z980-R.AAS9U1. I am running
  the latest BIOS.

  Ever since upgrading to Ubuntu 23.04, my computer frequently hangs
  upon suspending to RAM and I am not able to recover it. The hang
  occurs on suspend rather than resume. I have my configuration set to
  suspend upon closing my laptop's lid. The first time I suspend after
  boot, it almost always suspends properly and appears to resume with no
  issues. Starting on the second or third suspend attempt, my computer's
  screen goes black (backlight off) but it never actually enters suspend
  state, as indicated by the power LED, processor temperature, and
  battery drain, which indicate the computer is still on. I am not able
  to recover the computer to a working state from this point -- it does
  not respond to any keyboard or touchpad input I have 

[Kernel-packages] [Bug 2016826] Re: Plugging in Corsair K55 keyboard often doesnt work

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

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

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

Title:
  Plugging in Corsair K55 keyboard often doesnt work

Status in linux-raspi package in Ubuntu:
  Expired

Bug description:
  Often, plugging in my corsair K55 keyboard won't work. Sometimes, it
  works, but for the most part, like 80% of the time, it doesn't. I've
  had this issue for a while now across different versions.

  When I plug it in, the lights on the keyboard 'freeze' (keyboard
  firmware issue?), and no input is received from the keyboard. It seems
  the black USB 2 ports seem to have this occur less frequently than the
  blue USB 3 port.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-raspi 6.2.0.1004.6
  ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6
  Uname: Linux 6.2.0-1004-raspi aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jpeisach894 F wireplumber
   /dev/snd/controlC0:  jpeisach894 F wireplumber
   /dev/snd/seq:jpeisach891 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 17 20:35:32 2023
  ImageMediaBuild: 20230417
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 013: ID 1b1c:1b3d Corsair Corsair Corsair Gaming K55 RGB 
Keyboard
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 
snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:1600x900M@60 
smsc95xx.macaddr=DC:A6:32:C9:FA:05 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  zswap.enabled=1 zswap.zpool=z3fold 
zswap.compressor=zstd dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable 
rootfstype=ext4 rootwait fixrtc quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-1004-raspi N/A
   linux-backports-modules-6.2.0-1004-raspi  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux-raspi
  StagingDrivers: bcm2835_isp bcm2835_codec bcm2835_v4l2 snd_bcm2835 
bcm2835_mmal_vchiq vc_sm_cma rpivid_hevc
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2016826/+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 2016323] Re: NVIDIA kernel driver not built/installed

2023-06-18 Thread Daniel van Vugt
** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: Expired => New

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

Title:
  NVIDIA kernel driver not built/installed

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New

Bug description:
  Web pages display and app launch are VERY slow for a PC having this
  configuration. There is really a problem about display since I bougth
  this PC.

  And ...

  Since last big upgrade (including some Nvidia stuff) :

  No more gear on login to switch to Wayland/X11.
  Night mode in screen parameters doesn't work.
  Steam game (Northgard) launches very slowly and is unplayable

  I have uncommented the line #WaylandEnable=true in
  /etc/gdm3/custom.conf and restarted with no success.

  Thank you in advance for your help.

  Release Ubuntu 22.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14
  Uname: Linux 6.1.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 14 18:53:58 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.105.17: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] 
[1558:50f4]
  InstallationDate: Installed on 2023-01-27 (77 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Notebook NH5xVR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem 
root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2021
  dmi.bios.release: 7.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.07.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5xVR
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5xVR
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/nvidia-graphics-drivers-525/+bug/2016323/+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 2002601] Re: Wireless: Enable RTL8852BE wifi driver

2023-06-18 Thread koba
** Changed in: linux (Ubuntu Jammy)
   Status: Invalid => Won't Fix

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

Title:
  Wireless: Enable RTL8852BE wifi driver

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Justification]
  Enable Realtek RLT8852BE WIFI.

  [Test]
  1. put rtw8852b_fw.bin in /lib/firmware/rtw89/
  2. boot-up with kernel enabled RTL8852be.
  3. Connect to WIFI-AP and test with ping.

  * ping -I wlp2s0 8.8.8.8
  ~~~
  PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms
  64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms
  64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms
  64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms
  64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms
  ~~~
  * Connected to AP
  ~~~
  u@ubuntu:~$ nmcli dev
  DEVICE TYPE STATE CONNECTION
  enp3s0 ethernet connected Wired connection 1
  wlp2s0 wifi connected Canonical
  p2p-dev-wlp2s0 wifi-p2p disconnected --
  lo loopback unmanaged --
  ~~~
  * lsmod | grep 8852
  ~~~
  lsmod | grep 8852
  rtw89_8852be 16384 0
  rtw89_8852b 368640 1 rtw89_8852be
  rtw89_pci 61440 1 rtw89_8852be
  rtw89_core 442368 2 rtw89_8852b,rtw89_pci
  cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211
  ~~~

  4. cbd's built result,
  Lunar,
  ~~~
  remote: Resolving deltas: 100% (391/391), completed with 118 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-0e58018b43c1-ioeM
  remote: * 96/480 cores busy (1/5 hosts), 0 builds queued
  remote: 2023-01-12 03:16:35  kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK
  remote: 2023-01-12 03:17:47  kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK
  remote: 2023-01-12 03:11:36  kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK
  remote: 2023-01-12 03:16:30  kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK
  remote: 2023-01-12 03:10:24  kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK
  remote: 

  To cbd:lunar.git
  ~~~
  OEM-6.1,
  remote: Resolving deltas: 100% (399/399), completed with 121 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-c1002f30ccc3-m65z
  remote: * 0/192 cores busy (0/2 hosts), 0 builds queued
  remote: 2023-01-12 05:25:23  kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK
  remote: 

  To cbd:jammy.git

  [Where problems could occur]
  Medium, a new driver so the current driver may have some edge cases didn't 
consider.

  [Misc]
  * For generic Jammy, need more patches to enable RTL8852be so only SRU for 
OEM-6.1.
  * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on 
Lunar, so only SRU for Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 2002601] Re: Wireless: Enable RTL8852BE wifi driver

2023-06-18 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Wireless: Enable RTL8852BE wifi driver

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Justification]
  Enable Realtek RLT8852BE WIFI.

  [Test]
  1. put rtw8852b_fw.bin in /lib/firmware/rtw89/
  2. boot-up with kernel enabled RTL8852be.
  3. Connect to WIFI-AP and test with ping.

  * ping -I wlp2s0 8.8.8.8
  ~~~
  PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms
  64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms
  64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms
  64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms
  64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms
  ~~~
  * Connected to AP
  ~~~
  u@ubuntu:~$ nmcli dev
  DEVICE TYPE STATE CONNECTION
  enp3s0 ethernet connected Wired connection 1
  wlp2s0 wifi connected Canonical
  p2p-dev-wlp2s0 wifi-p2p disconnected --
  lo loopback unmanaged --
  ~~~
  * lsmod | grep 8852
  ~~~
  lsmod | grep 8852
  rtw89_8852be 16384 0
  rtw89_8852b 368640 1 rtw89_8852be
  rtw89_pci 61440 1 rtw89_8852be
  rtw89_core 442368 2 rtw89_8852b,rtw89_pci
  cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211
  ~~~

  4. cbd's built result,
  Lunar,
  ~~~
  remote: Resolving deltas: 100% (391/391), completed with 118 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-0e58018b43c1-ioeM
  remote: * 96/480 cores busy (1/5 hosts), 0 builds queued
  remote: 2023-01-12 03:16:35  kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK
  remote: 2023-01-12 03:17:47  kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK
  remote: 2023-01-12 03:11:36  kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK
  remote: 2023-01-12 03:16:30  kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK
  remote: 2023-01-12 03:10:24  kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK
  remote: 

  To cbd:lunar.git
  ~~~
  OEM-6.1,
  remote: Resolving deltas: 100% (399/399), completed with 121 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-c1002f30ccc3-m65z
  remote: * 0/192 cores busy (0/2 hosts), 0 builds queued
  remote: 2023-01-12 05:25:23  kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK
  remote: 

  To cbd:jammy.git

  [Where problems could occur]
  Medium, a new driver so the current driver may have some edge cases didn't 
consider.

  [Misc]
  * For generic Jammy, need more patches to enable RTL8852be so only SRU for 
OEM-6.1.
  * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on 
Lunar, so only SRU for Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 2002601] Re: Wireless: Enable RTL8852BE wifi driver

2023-06-18 Thread koba
** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
 Assignee: koba (kobako)
   Status: In Progress

** Also affects: linux-firmware (Ubuntu Mantic)
   Importance: Undecided
   Status: Fix Released

** Also affects: linux-oem-6.1 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu Lunar)
   Status: In Progress => Fix Released

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

Title:
  Wireless: Enable RTL8852BE wifi driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Justification]
  Enable Realtek RLT8852BE WIFI.

  [Test]
  1. put rtw8852b_fw.bin in /lib/firmware/rtw89/
  2. boot-up with kernel enabled RTL8852be.
  3. Connect to WIFI-AP and test with ping.

  * ping -I wlp2s0 8.8.8.8
  ~~~
  PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms
  64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms
  64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms
  64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms
  64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms
  ~~~
  * Connected to AP
  ~~~
  u@ubuntu:~$ nmcli dev
  DEVICE TYPE STATE CONNECTION
  enp3s0 ethernet connected Wired connection 1
  wlp2s0 wifi connected Canonical
  p2p-dev-wlp2s0 wifi-p2p disconnected --
  lo loopback unmanaged --
  ~~~
  * lsmod | grep 8852
  ~~~
  lsmod | grep 8852
  rtw89_8852be 16384 0
  rtw89_8852b 368640 1 rtw89_8852be
  rtw89_pci 61440 1 rtw89_8852be
  rtw89_core 442368 2 rtw89_8852b,rtw89_pci
  cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211
  ~~~

  4. cbd's built result,
  Lunar,
  ~~~
  remote: Resolving deltas: 100% (391/391), completed with 118 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-0e58018b43c1-ioeM
  remote: * 96/480 cores busy (1/5 hosts), 0 builds queued
  remote: 2023-01-12 03:16:35  kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK
  remote: 2023-01-12 03:17:47  kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK
  remote: 2023-01-12 03:11:36  kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK
  remote: 2023-01-12 03:16:30  kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK
  remote: 2023-01-12 03:10:24  kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK
  remote: 

  To cbd:lunar.git
  ~~~
  OEM-6.1,
  remote: Resolving deltas: 100% (399/399), completed with 121 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-c1002f30ccc3-m65z
  remote: * 0/192 cores busy (0/2 hosts), 0 builds queued
  remote: 2023-01-12 05:25:23  kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK
  remote: 

  To cbd:jammy.git

  [Where problems could occur]
  Medium, a new driver so the current driver may have some edge cases didn't 
consider.

  [Misc]
  * For generic Jammy, need more patches to enable RTL8852be so only SRU for 
OEM-6.1.
  * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on 
Lunar, so only SRU for Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002601/+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 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169

2023-06-18 Thread koba
** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
 Assignee: koba (kobako)
   Status: In Progress

** Also affects: linux-oem-5.13 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-oem-5.14 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-oem-5.17 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-oem-6.0 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-oem-6.1 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Released

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

Title:
  Fix only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Triaged
Status in linux-oem-5.13 source package in Kinetic:
  Invalid
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-5.13 source package in Lunar:
  Invalid
Status in linux-oem-5.14 source package in Lunar:
  Invalid
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-5.13 source package in Mantic:
  Invalid
Status in linux-oem-5.14 source package in Mantic:
  Invalid
Status in linux-oem-5.17 source package in Mantic:
  Invalid
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  System only can reach PC3, and it affects power consumption alot.

  [Fix]
  Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state 
issue, but also fixes network speed issue.
  V7:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/
  V6:
  
https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/

  
  [Test]
  Verified on 2 different systems which has PC state issue and has network 
speed issue, these patches fix both issues.

  [Where problems could occur]
  It toggles ASPM on and off depends on the network traffic during runtime, I 
don't think it'll lead to any regressions. Some potential issues have been 
addressed during the patch submitting. It's v6 now and accepted by upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 2023927] Re: Screen flickering whe update images

2023-06-18 Thread Daniel van Vugt
Comment #7 shows the wrong driver in use - it's using software rendering
on the CPU instead of using the GPU. I cannot figure out why yet, but
generally recommend you use long term support release 22.04 instead:

https://ubuntu.com/download/desktop

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Screen flickering whe update images
+ [focal] Screen flickering in Xorg on i7-1165G7

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

Title:
  [focal] Screen flickering in Xorg on i7-1165G7

Status in linux-hwe-5.13 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Often, when there are small changes in image displayed, an horizontal 
flickering is observed. This happen for example on a mouse right button menu, 
or when a hyperlink description appears on the screen bottom when mouse pointer 
cross some field on a webpage, also when favorites menu appear.
  The flickering usually disappear in a few moments, sometimes (usually when a 
few pixels are updating) it can last for seconds.
  This flickering is caused by a late updating of some horizontal lines, so for 
awhile a few lines of previous image coexist with a majority of new ones

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 22:44:12 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.32, 5.13.0-40-generic, x86_64: installed
   virtualbox, 6.1.32, 5.13.0-41-generic, x86_64: installed
   virtualbox, 6.1.32, 5.4.0-126-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Device [1e39:a025]
  InstallationDate: Installed on 2022-01-01 (529 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb: Error: command ['lsusb'] failed with exit code 127: lsusb: symbol 
lookup error: lsusb: undefined symbol: libusb_error_name
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 127: lsusb: 
symbol lookup error: lsusb: undefined symbol: libusb_error_name
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 127: lsusb: 
symbol lookup error: lsusb: undefined symbol: libusb_error_name
  MachineType: MEDION S15449
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro quiet splash pci=noaer 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 212
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr212:bd04/09/2021:br5.19:svnMEDION:pnS15449:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:skuML-23000830031014:
  dmi.product.family: Akoya
  dmi.product.name: S15449
  dmi.product.sku: ML-230008 30031014
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~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 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-hwe-5.13/+bug/2023927/+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 2024331] Status changed to Confirmed

2023-06-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Bluetooth fails to work after updating to linux-image-6.2.0-23-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the latest kernel updates in Lunar, I can no longer
  enable Bluetooth in GNOME.

  Rebooting back into 6.2.0-20-generic allows it to work again.

  Looking at the journalctl log between the two, I see the following
  differences for hci0:

  
  $ diff <(journalctl -b-3 --grep hci0 --output short-monotonic | cut -c16-) 
<(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-)
  12c12
  < graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs
  ---
  > graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs
  14c14
  < graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs
  ---
  > graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs
  19c19,22
  < graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: 
fd(44) ready
  ---
  > graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
  > graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features 
(-110)
  > graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03
  > graphene kernel: Bluetooth: hci0: Intel version event size mismatch

  
  This looks similar to 
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 
but I am filing a separate bug since that doesn't appear to have any traction.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 19 10:31:38 2023
  InstallationDate: Installed on 2021-08-03 (684 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  MachineType: LENOVO 20XWCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-23-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-23-generic N/A
   linux-backports-modules-6.2.0-23-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-01-27 (142 days ago)
  dmi.bios.date: 04/05/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET84W (1.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET84W(1.60):bd04/05/2023:br1.60:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024331/+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 2024331] [NEW] Bluetooth fails to work after updating to linux-image-6.2.0-23-generic

2023-06-18 Thread Alex Murray
Public bug reported:

After upgrading to the latest kernel updates in Lunar, I can no longer
enable Bluetooth in GNOME.

Rebooting back into 6.2.0-20-generic allows it to work again.

Looking at the journalctl log between the two, I see the following
differences for hci0:


$ diff <(journalctl -b-3 --grep hci0 --output short-monotonic | cut -c16-) 
<(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-)
12c12
< graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs
---
> graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs
14c14
< graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs
---
> graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs
19c19,22
< graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: 
fd(44) ready
---
> graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
> graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features 
> (-110)
> graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03
> graphene kernel: Bluetooth: hci0: Intel version event size mismatch


This looks similar to 
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 
but I am filing a separate bug since that doesn't appear to have any traction.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-23-generic 6.2.0-23.23
ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
Uname: Linux 6.2.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 19 10:31:38 2023
InstallationDate: Installed on 2021-08-03 (684 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
MachineType: LENOVO 20XWCTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-23-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-23-generic N/A
 linux-backports-modules-6.2.0-23-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
SourcePackage: linux
UpgradeStatus: Upgraded to lunar on 2023-01-27 (142 days ago)
dmi.bios.date: 04/05/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET84W (1.60 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XWCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 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.33
dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET84W(1.60):bd04/05/2023:br1.60:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XWCTO1WW
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO

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


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

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

Title:
  Bluetooth fails to work after updating to linux-image-6.2.0-23-generic

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to the latest kernel updates in Lunar, I can no longer
  enable Bluetooth in GNOME.

  Rebooting back into 6.2.0-20-generic allows it to work again.

  Looking at the journalctl log between the two, I see the following
  differences for hci0:

  
  $ diff <(journalctl -b-3 --grep hci0 --output short-monotonic | cut -c16-) 
<(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-)
  12c12
  < graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs
  ---
  > graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs
  14c14
  < graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs
  ---
  > graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs
  19c19,22
  < graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: 
fd(44) ready
  ---
  > graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
  > graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features 
(-110)
  > graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03
  > graphene kernel: Bluetooth: hci0: Intel version event size mismatch

  
  This looks similar to 
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 
but I am filing a separate bug since that doesn't appear to have any traction.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  

[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0

2023-06-18 Thread Ewen McNeill
Thanks to Steve Matos for pointing out that the relevant warning was
likely reverted in the Linux Kernel "Stable" release 5.4.234, which is
tracked in Ubuntu as:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017691

>From digging into the Linux kernel stable git history (below) I'm fairly
sure that the issue should have been fixed in Linux 5.4.0-151 (and thus
fixed in 5.4.0.152), by entirely removing the warning line that was
triggering.  It also seems like the (known) triggering cause was IPv6
traffic, which is at least consistent with my problematic server (and
explains why it wasn't seen often enough for Ubuntu / Canonical do
engage with this bug).

More details below.


The Linux Kernel mailing list announcement of Linux stable kernel 5.4.234 is:

https://lore.kernel.org/lkml/1677842623227...@kroah.com/T/

and a patch stream list:

https://lore.kernel.org/all/20230301180651.177668...@linuxfoundation.org/

which includes a diff from (Linux kernel upstream) 5.4.233 to 5.4.234.
And that diff removes the line:

WARN_ON(sk->sk_forward_alloc);

from net/core/stream.c.  (It's *not* a warn on once, so I've no idea why
the revert says that; it was a warn on every occurence, which explains
why we got a bunch of them.)

>From upstream Linux stable 5.4.234 that relevant warning does seem to be
explicitly removed:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-
rc.git/log/net/core/stream.c?h=v5.4.234

by the commit:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-
rc.git/commit/net/core/stream.c?h=v5.4.234=ee8cd3abe7228161be143702efa3d03a65a757c8

which gives the background:

"Christoph Paasch reported that commit b5fc29233d28 ("inet6: Remove
inet6_destroy_sock() in sk->sk_prot->destroy().") started triggering
WARN_ON_ONCE(sk->sk_forward_alloc) in sk_stream_kill_queues().  [0 - 2]
Also, we can reproduce it by a program in [3]."

So apparently a change in IPv6 handling started triggering this
particular problem in the cleanup phase elsewhere.  And they've now
removed the warning we were getting entirely (which it seems has been
there a while longer, but not triggerd until now, and wasn't needed at
all as there were other checks on that data elsewhere).

This seems to be the upstream Linux kernel bug report:

https://lore.kernel.org/netdev/39725ab4-88f1-41b3-b07f-949c5caef...@icloud.com/

and the relevant bug referenced from there:

https://github.com/multipath-tcp/mptcp_net-next/issues/341

both from February 2023, with the fix released March 2023
(https://gitlab.com/linux-
kernel/stable/-/commit/a103859aaa718cf13cb5f55c3a33512dbab613f7).  Yet
Ubuntu Linux released the buggy version in April 2023 :-/

Anyway I'm fairly confident that Ubuntu 5.4.0-152 should be okay.  I'll
update my server later this month, and if there are no more reports by
about mid July 2023 I'll close this issue.

Ewen

** Bug watch added: github.com/multipath-tcp/mptcp_net-next/issues #341
   https://github.com/multipath-tcp/mptcp_net-next/issues/341

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

Title:
  linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212
  sk_stream_kill_queues+0xcf/0xe0

Status in linux-signed package in Ubuntu:
  Confirmed
Status in linux-signed-kvm package in Ubuntu:
  Confirmed

Bug description:
  After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu
  Focal), I noticed that it was suddenly getting a bunch of kernel log
  (dmesg) reports like:

  WARNING: CPU: 4 PID: 0 at net/core/stream.c:212
  sk_stream_kill_queues+0xcf/0xe0

  while investigating I determined that it is currently running the
  focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns
  out was enabled for this server (clearly it seemed like a good idea at
  the time).

  I'm not expecting focal-proposed to be fixed as if it were a release
  package, but since I couldn't find any reports on Launchpad I figured
  I should let y'all know this focal-proposed package could do with some
  additional work before it's actually released :-)

  There have been at least 80 such reports in the last 5 hours since the
  server was rebooted, differing only by the CPU core and the process
  reported, although it seems the last one was a couple of hours ago, so
  I guess it's traffic dependent/timing dependent.

  ewen@naosr620:~$ uptime
   16:27:32 up  5:19,  1 user,  load average: 0.08, 0.14, 0.06
  ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: 
[0-9]*/PID: N/;' | uniq -c
   88 WARNING: CPU: N PID: N at net/core/stream.c:212 
sk_stream_kill_queues+0xcf/0xe0
  ewen@naosr620:~$ 

  Ubuntu Release:

  ewen@naosr620:~$ lsb_release -rd
  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04
  ewen@naosr620:~$ 

  
  Kernel/package version affected:

  ewen@naosr620:~$ uname -a
  Linux naosr620 5.4.0-149-generic 

[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

2023-06-18 Thread D
Observed with VS Code and VS Codium as well.

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

Title:
  Chrome crashes with FATAL:credentials.cc(127)] Check failed: . :
  Permission denied (13)

Status in linux-meta-nvidia-5.19 package in Ubuntu:
  Confirmed

Bug description:
  With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I 
experience that google-chrome crashes.
  It shows

  ```shell
  [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap (core dumped)".
  ```

  To be honest I don't think it has anything to do with google-chrome at all.
  When google-chrome starts it (normally) request the system key-manager 
(KWallet in my case) for access to the users keys before it actually shows 
anything from chrome. Not even that part (the KWallet password box) shows up.

  I can only reproduce this problem with this specific kernel. It should
  be possible to take google-chrome out of the equation by using another
  application that starts by request the desktop key manager for access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-nvidia-5.19 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
  Uname: Linux 5.15.0-1023-nvidia x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr 28 11:23:23 2023
  InstallationDate: Installed on 2016-01-08 (2666 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: linux-meta-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2024306] Re: Blank screen on 5.4.0-152.169

2023-06-18 Thread Brian E Carpenter
** 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/2024306

Title:
  Blank screen on 5.4.0-152.169

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run Linux Mint on a pretty old HP laptop. Today I updated Ubuntu
  from 5.4.0-150 to -152.169 and the screen is _completely blank_ after
  reboot. Starting in recovery mode, the screen works but I get an
  infinite loop trying to update some (unspecified) video driver. I went
  through the whole process twice using different mirrors. I have
  reverted to -150 and everything is fine. For obvious reasons I cannot
  give you any output from the failing kernel. Were any drivers removed
  from -152?

  FYI on the working kernel:

  ~$ sudo lshw  -c video
  [sudo] password for brian: 
*-display 
 description: VGA compatible controller
 product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 0e
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:94 memory:9000-903f memory:8000-8fff 
ioport:2050(size=8) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brian  1011 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.2
  InstallationDate: Installed on 2021-10-07 (619 days ago)
  InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703
  Lsusb:
   Bus 001 Device 004: ID 064e:9302 Suyin Corp. 
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 4: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 4: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: Hewlett-Packard HP 14 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-150-generic 
root=UUID=24cf6e45-1f74-4c8e-a756-8f4a81d4cb45 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-150.167-generic 5.4.233
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-150-generic N/A
   linux-backports-modules-5.4.0-150-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  uma
  Uname: Linux 5.4.0-150-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 220F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn220F:rvr57.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 14 Notebook PC
  dmi.product.sku: G8D08PA#ABG
  dmi.product.version: 097610405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

2023-06-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  WiFi stops working several minutes after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kernel image version linux-image-5.15.0-75-generic
  my WiFi adaptor stops working after 5 or 10 minutes. I can get it to
  work again temporarily (another 5 or 10 mins) by stop Turning Off the
  WiFi on the desktop UI and Turning it On again. After booting back in
  to the previous kernel (5.15.0-73) everything is working as expected
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-75-generic 5.15.0-75.82
  ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 18 22:30:59 2023
  InstallationDate: Installed on 2019-08-07 (1411 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=62808064 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-73-generic N/A
   linux-backports-modules-5.15.0-73-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-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.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024327/+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 2024327] Re: WiFi stops working several minutes after boot

2023-06-18 Thread bsdz
The automatically attached dmesg would be from my previous kernel which
I booted into from grub. Here's the dmesg output from boot where bug
manifested, i.e. journalctl -o short-precise -k -b -1 > /tmp/dmesg.txt

** Attachment added: "dmesg log from problematic kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024327/+attachment/5680549/+files/dmesg.txt

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

Title:
  WiFi stops working several minutes after boot

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to kernel image version linux-image-5.15.0-75-generic
  my WiFi adaptor stops working after 5 or 10 minutes. I can get it to
  work again temporarily (another 5 or 10 mins) by stop Turning Off the
  WiFi on the desktop UI and Turning it On again. After booting back in
  to the previous kernel (5.15.0-73) everything is working as expected
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-75-generic 5.15.0-75.82
  ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 18 22:30:59 2023
  InstallationDate: Installed on 2019-08-07 (1411 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=62808064 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-73-generic N/A
   linux-backports-modules-5.15.0-73-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-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.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024327/+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 2024327] [NEW] WiFi stops working several minutes after boot

2023-06-18 Thread bsdz
Public bug reported:

After upgrading to kernel image version linux-image-5.15.0-75-generic my
WiFi adaptor stops working after 5 or 10 minutes. I can get it to work
again temporarily (another 5 or 10 mins) by stop Turning Off the WiFi on
the desktop UI and Turning it On again. After booting back in to the
previous kernel (5.15.0-73) everything is working as expected again.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-75-generic 5.15.0-75.82
ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
Uname: Linux 5.15.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 18 22:30:59 2023
InstallationDate: Installed on 2019-08-07 (1411 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=62808064 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-73-generic N/A
 linux-backports-modules-5.15.0-73-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.13
SourcePackage: linux
StagingDrivers: ashmem_linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: X399 AORUS XTREME-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.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: X399 AORUS XTREME
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug jammy staging

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

Title:
  WiFi stops working several minutes after boot

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to kernel image version linux-image-5.15.0-75-generic
  my WiFi adaptor stops working after 5 or 10 minutes. I can get it to
  work again temporarily (another 5 or 10 mins) by stop Turning Off the
  WiFi on the desktop UI and Turning it On again. After booting back in
  to the previous kernel (5.15.0-73) everything is working as expected
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-75-generic 5.15.0-75.82
  ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 18 22:30:59 2023
  InstallationDate: Installed on 2019-08-07 (1411 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=62808064 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-73-generic N/A
   linux-backports-modules-5.15.0-73-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux
  StagingDrivers: ashmem_linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-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.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  

[Kernel-packages] [Bug 2012019] Re: Fix E-star testing failure with RTK 8852BE

2023-06-18 Thread Kiwinote
Just for completeness, please note that someone else reported an
identical sounding issue at
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2017277
which is dated a few days after this change was released to linux-
oem-6.1/jammy.

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

Title:
  Fix E-star testing failure with RTK 8852BE

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  New

Bug description:
  [Impact]
  E-star testing failure on machine with RTK 8852BE configuration.

  [Fix]
  1. Enable CLKREQ to reduce power consumption.
  2. release RX standby timer of beamformee to save power

  [Test Case]
  1. Prepare one system with RTK 8852BE WLAN/BT.
  2. Run E-star testing.
  3. The result must meet PASS criteria.

  [Where problems could occur]
  Low, may face the performance issue during throughput verification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2012019/+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 2023446] Re: Excessive Power drain in sleep mode on XPS 9315

2023-06-18 Thread Nick
Should I regenerate the logs for the OEM 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/2023446

Title:
  Excessive Power drain in sleep mode on XPS 9315

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 9315, with Ubuntu 22.04 installed (from vanilla
  image, downloaded from the Ubuntu site). The machine was sold with an
  OEM 20.04 image which I am no longer using.

  From a full charge, I close the lid and the machine enters sleep. Over
  the course of 8Hrs, the battery drops from 100% to 80%.

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17

  See attached log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noutram2273 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-06-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Dell Inc. XPS 9315
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  Tags:  jammy
  Uname: Linux 5.19.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 02GGG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd04/12/2023:br1.11:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023446/+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 1998722] Re: kernel update 5.19.0-1013-oracle breaks my system

2023-06-18 Thread Chris Martin
It was installed automatically when I installed Ubuntu

Cheers


Chris Martin
m: +61 419 812 371
e: ch...@martin.cc



On Fri, 16 Jun 2023 at 23:41, Alberto Milone <1998...@bugs.launchpad.net>
wrote:

> How did you originally install the nvidia driver?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1998722
>
> Title:
>   kernel update 5.19.0-1013-oracle breaks my system
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This update over the weekend caused by stsem to fail to boot
>   In recovery mode my networking, and video configuration was broken
>   Booting the alternate(backup) kernel image worked fine
>
>   I was able to recover by removing the new oracle kernel
>   sudo apt purge linux-image-5.19.0-1013-oracle
>
>   After rebooting I then ran
>   sudo apt autoremove
>   to remove the other compoments that where installed with the oracle
> kernel
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.10
>   Package: linux-image-5.19.0-26-generic 5.19.0-26.27
>   ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
>   Uname: Linux 5.19.0-26-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.23.1-0ubuntu3
>   Architecture: amd64
>   CRDA: N/A
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Dec  5 10:06:52 2022
>   InstallationDate: Installed on 2022-04-05 (243 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
> (20220329.1)
>   MachineType: Dell Inc. Precision T1700
>   ProcEnviron:
>LANGUAGE=en_AU:en
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_AU.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 VESA VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic
> root=UUID=896ec6e0-7230-417f-a041-5588c627727c ro quiet splash vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-5.19.0-26-generic N/A
>linux-backports-modules-5.19.0-26-generic  N/A
>linux-firmware 20220923.gitf09bebf3-0ubuntu1
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to kinetic on 2022-10-20 (45 days ago)
>   dmi.bios.date: 05/30/2019
>   dmi.bios.release: 65.28
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A28
>   dmi.board.name: 04JGCK
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A01
>   dmi.chassis.type: 15
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr:sku05A6:
>   dmi.product.name: Precision T1700
>   dmi.product.sku: 05A6
>   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/1998722/+subscriptions
>
>

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

Title:
  kernel update 5.19.0-1013-oracle breaks my system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This update over the weekend caused by stsem to fail to boot
  In recovery mode my networking, and video configuration was broken
  Booting the alternate(backup) kernel image worked fine 

  I was able to recover by removing the new oracle kernel
  sudo apt purge linux-image-5.19.0-1013-oracle

  After rebooting I then ran
  sudo apt autoremove
  to remove the other compoments that where installed with the oracle kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-26-generic 5.19.0-26.27
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  5 10:06:52 2022
  InstallationDate: Installed on 2022-04-05 (243 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Dell Inc. Precision T1700
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=896ec6e0-7230-417f-a041-5588c627727c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-26-generic N/A
   linux-backports-modules-5.19.0-26-generic  N/A
   linux-firmware   

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

2023-06-18 Thread Igor Andrianov
Hello colleagues. I confirm the successful solution of this problem also
for camera model 0408:4033 (Acer Acer Aspire A515-57, Ubuntu 22.04,
kernel 5.19.0-45-generic) by simply changing in one place 4035 to 4033
in uvc_driver.c before compiling.

I have no problems with sound. Everything works great. 
Thank you for your attention, have a nice day everyone!

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

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


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


  -kindly ASK

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

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

  
  BR
  Giuliano

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

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