[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

2023-01-23 Thread Daniel van Vugt
Can you provide a kernel log proving it's this bug?

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
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 source package in Jammy:
  Fix Released
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 source package in Kinetic:
  Fix Released
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

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be 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-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:sv

Re: [Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

2023-01-23 Thread Abu Sayeed
Hi,

Please check the output of uname -r command,
*5.15.0-58-generic*


On Mon, Jan 23, 2023 at 9:40 AM Daniel van Vugt <1988...@bugs.launchpad.net>
wrote:

> > I am facing this problem on ubuntu 22.04, kernel version 5.15. I do not
> > understand which kernel version should I install to get rid of this
> > issue.
>
> Comment #17 says:
>
> > This bug was fixed in the package linux - 5.15.0-57.63
>
> so it should only require a system update:
>
>   sudo apt update
>   sudo apt full-upgrade
>
> and reboot.
>
> If the problem persists then please include the full kernel version
> affected (uname -r).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988797
>
> Title:
>   pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
>   Fatal), type=Transaction Layer, (Requester ID)
>
> Status in HWE Next:
>   Fix Committed
> Status in OEM Priority Project:
>   New
> Status in linux package in Ubuntu:
>   Confirmed
> 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 source package in Jammy:
>   Fix Released
> 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 source package in Kinetic:
>   Fix Released
> 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
>
> Bug description:
>   My kernel log periodically bursts with:
>
>   [10405.588287] pcieport :00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>   [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error
> status/mask=0010/4000
>   [10405.598564] pcieport :00:1b.0:[20] UnsupReq
>  (First)
>   [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400
> 0152  
>   [10405.609563] pcieport :00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>   [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error
> status/mask=0010/4000
>   [10405.620296] pcieport :00:1b.0:[20] UnsupReq
>  (First)
>   [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400
> 0152  
>   [10405.631180] pcieport :00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>   [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error
> status/mask=0010/4000
>   [10405.641867] pcieport :00:1b.0:[20] UnsupReq
>  (First)
>   [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400
> 0152  
>   [10405.652919] pcieport :00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>   [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error
> status/mask=0010/4000
>   [10405.663803] pcieport :00:1b.0:[20] UnsupReq
>  (First)
>   [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400
> 0152  
>   [10405.675130] pcieport :00:1b.0: PCIe Bus Error:
> severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
>   [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error
> status/mask=0010/4000
>   [10405.686267] pcieport :00:1b.0:[20] UnsupReq
>  (First)
>   [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400
> 0152  
>
>   This has happened even since I got the machine. It also happened with
>   5.15.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.10
>   Package: linux-image-5.19.0-15-generic 5.19.0-15.15
>   ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
>   Uname: Linux 5.19.0-15-generic x86_64
>   ApportVersion: 2.23.0-0ubuntu1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  dan2477 F wireplumber
>/dev/snd/seq:dan2474 F pipewire
>   CRDA: N/A
>   CasperMD5CheckResult: pass
>   Date: Tue Sep  6 13:52:35 2022
>   InstallationDate: Installed on 2022-07-20 (47 days ago)
>   InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
>   MachineType: Intel(R) Client Systems NUC12DCMi7
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic
> root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be 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-15-generic N/A
>linux-backports-modules

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

2023-01-23 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/2003768

Title:
  iwlwifi Stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [40234.924454] iwlwifi :00:14.3: Queue 5 is stuck 78 150
  [40234.924775] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [40234.924916] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [40234.924920] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6
  [40234.924924] iwlwifi :00:14.3: Loaded firmware version: 71.058653f6.0 
QuZ-a0-hr-b0-71.ucode
  [40234.924928] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN
  [40234.924933] iwlwifi :00:14.3: 0xA210 | trm_hw_status0
  [40234.924936] iwlwifi :00:14.3: 0x | trm_hw_status1
  [40234.924939] iwlwifi :00:14.3: 0x004CBE06 | branchlink2
  [40234.924942] iwlwifi :00:14.3: 0x004C257A | interruptlink1
  [40234.924945] iwlwifi :00:14.3: 0x004C257A | interruptlink2
  [40234.924948] iwlwifi :00:14.3: 0xB620 | data1
  [40234.924951] iwlwifi :00:14.3: 0x0100 | data2
  [40234.924953] iwlwifi :00:14.3: 0x | data3
  [40234.924956] iwlwifi :00:14.3: 0x6100C1E4 | beacon time
  [40234.924959] iwlwifi :00:14.3: 0x0033EE36 | tsf low
  [40234.924962] iwlwifi :00:14.3: 0x0039 | tsf hi
  [40234.924965] iwlwifi :00:14.3: 0x | time gp1
  [40234.924968] iwlwifi :00:14.3: 0x7F921B5F | time gp2
  [40234.924971] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [40234.924974] iwlwifi :00:14.3: 0x0047 | uCode version major
  [40234.924977] iwlwifi :00:14.3: 0x058653F6 | uCode version minor
  [40234.924979] iwlwifi :00:14.3: 0x0351 | hw version
  [40234.924982] iwlwifi :00:14.3: 0x00C89001 | board version
  [40234.924985] iwlwifi :00:14.3: 0x8007FC04 | hcmd
  [40234.924988] iwlwifi :00:14.3: 0x2402 | isr0
  [40234.924991] iwlwifi :00:14.3: 0x | isr1
  [40234.924994] iwlwifi :00:14.3: 0x08F2 | isr2
  [40234.924996] iwlwifi :00:14.3: 0x00C3028C | isr3
  [40234.924999] iwlwifi :00:14.3: 0x | isr4
  [40234.925002] iwlwifi :00:14.3: 0x054C001C | last cmd Id
  [40234.925005] iwlwifi :00:14.3: 0xB620 | wait_event
  [40234.925008] iwlwifi :00:14.3: 0x00D4 | l2p_control
  [40234.925010] iwlwifi :00:14.3: 0x00010034 | l2p_duration
  [40234.925013] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
  [40234.925016] iwlwifi :00:14.3: 0x | l2p_addr_match
  [40234.925019] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel
  [40234.925022] iwlwifi :00:14.3: 0x | timestamp
  [40234.925025] iwlwifi :00:14.3: 0x907C | flow_handler
  [40234.925470] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [40234.925473] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7
  [40234.925478] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST
  [40234.925482] iwlwifi :00:14.3: 0x | umac branchlink1
  [40234.925484] iwlwifi :00:14.3: 0x80455B7C | umac branchlink2
  [40234.925487] iwlwifi :00:14.3: 0x804721A2 | umac interruptlink1
  [40234.925490] iwlwifi :00:14.3: 0x804721A2 | umac interruptlink2
  [40234.925492] iwlwifi :00:14.3: 0x0100 | umac data1
  [40234.925495] iwlwifi :00:14.3: 0x804721A2 | umac data2
  [40234.925498] iwlwifi :00:14.3: 0x | umac data3
  [40234.925500] iwlwifi :00:14.3: 0x0047 | umac major
  [40234.925503] iwlwifi :00:14.3: 0x058653F6 | umac minor
  [40234.925507] iwlwifi :00:14.3: 0x7F921B5C | frame pointer
  [40234.925510] iwlwifi :00:14.3: 0xC0886264 | stack pointer
  [40234.925515] iwlwifi :00:14.3: 0x0051019C | last host cmd
  [40234.925519] iwlwifi :00:14.3: 0x | isr status reg
  [40234.925634] iwlwifi :00:14.3: IML/ROM dump:
  [40234.925638] iwlwifi :00:14.3: 0x0003 | IML/ROM error/state
  [40234.925706] iwlwifi :00:14.3: 0x5603 | IML/ROM data1
  [40234.925816] iwlwifi :00:14.3: 0x0080 | IML/ROM WFPM_AUTH_KEY_0
  [40234.925836] iwlwifi :00:14.3: Fseq Registers:
  [40234.925879] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE
  [40234.925922] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION
  [40234.925964] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION
  [40234.926006] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION
  [40234.926049] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION
  [40234.926091] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
  [40234.926134] iwlwifi :00:14.3: 0x2302 | FSEQ_CNVI_ID
  [40234.926177] iwlwifi :00:14.3: 0x01300504 | FSEQ_CNVR_ID
  [40234.926220] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP
  [40234.926264] iwlwifi :00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
  [4

[Kernel-packages] [Bug 2003768] [NEW] iwlwifi Stuck

2023-01-23 Thread Islam
Public bug reported:

[40234.924454] iwlwifi :00:14.3: Queue 5 is stuck 78 150
[40234.924775] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[40234.924916] iwlwifi :00:14.3: Start IWL Error Log Dump:
[40234.924920] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6
[40234.924924] iwlwifi :00:14.3: Loaded firmware version: 71.058653f6.0 
QuZ-a0-hr-b0-71.ucode
[40234.924928] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN
[40234.924933] iwlwifi :00:14.3: 0xA210 | trm_hw_status0
[40234.924936] iwlwifi :00:14.3: 0x | trm_hw_status1
[40234.924939] iwlwifi :00:14.3: 0x004CBE06 | branchlink2
[40234.924942] iwlwifi :00:14.3: 0x004C257A | interruptlink1
[40234.924945] iwlwifi :00:14.3: 0x004C257A | interruptlink2
[40234.924948] iwlwifi :00:14.3: 0xB620 | data1
[40234.924951] iwlwifi :00:14.3: 0x0100 | data2
[40234.924953] iwlwifi :00:14.3: 0x | data3
[40234.924956] iwlwifi :00:14.3: 0x6100C1E4 | beacon time
[40234.924959] iwlwifi :00:14.3: 0x0033EE36 | tsf low
[40234.924962] iwlwifi :00:14.3: 0x0039 | tsf hi
[40234.924965] iwlwifi :00:14.3: 0x | time gp1
[40234.924968] iwlwifi :00:14.3: 0x7F921B5F | time gp2
[40234.924971] iwlwifi :00:14.3: 0x0001 | uCode revision type
[40234.924974] iwlwifi :00:14.3: 0x0047 | uCode version major
[40234.924977] iwlwifi :00:14.3: 0x058653F6 | uCode version minor
[40234.924979] iwlwifi :00:14.3: 0x0351 | hw version
[40234.924982] iwlwifi :00:14.3: 0x00C89001 | board version
[40234.924985] iwlwifi :00:14.3: 0x8007FC04 | hcmd
[40234.924988] iwlwifi :00:14.3: 0x2402 | isr0
[40234.924991] iwlwifi :00:14.3: 0x | isr1
[40234.924994] iwlwifi :00:14.3: 0x08F2 | isr2
[40234.924996] iwlwifi :00:14.3: 0x00C3028C | isr3
[40234.924999] iwlwifi :00:14.3: 0x | isr4
[40234.925002] iwlwifi :00:14.3: 0x054C001C | last cmd Id
[40234.925005] iwlwifi :00:14.3: 0xB620 | wait_event
[40234.925008] iwlwifi :00:14.3: 0x00D4 | l2p_control
[40234.925010] iwlwifi :00:14.3: 0x00010034 | l2p_duration
[40234.925013] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
[40234.925016] iwlwifi :00:14.3: 0x | l2p_addr_match
[40234.925019] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel
[40234.925022] iwlwifi :00:14.3: 0x | timestamp
[40234.925025] iwlwifi :00:14.3: 0x907C | flow_handler
[40234.925470] iwlwifi :00:14.3: Start IWL Error Log Dump:
[40234.925473] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7
[40234.925478] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST
[40234.925482] iwlwifi :00:14.3: 0x | umac branchlink1
[40234.925484] iwlwifi :00:14.3: 0x80455B7C | umac branchlink2
[40234.925487] iwlwifi :00:14.3: 0x804721A2 | umac interruptlink1
[40234.925490] iwlwifi :00:14.3: 0x804721A2 | umac interruptlink2
[40234.925492] iwlwifi :00:14.3: 0x0100 | umac data1
[40234.925495] iwlwifi :00:14.3: 0x804721A2 | umac data2
[40234.925498] iwlwifi :00:14.3: 0x | umac data3
[40234.925500] iwlwifi :00:14.3: 0x0047 | umac major
[40234.925503] iwlwifi :00:14.3: 0x058653F6 | umac minor
[40234.925507] iwlwifi :00:14.3: 0x7F921B5C | frame pointer
[40234.925510] iwlwifi :00:14.3: 0xC0886264 | stack pointer
[40234.925515] iwlwifi :00:14.3: 0x0051019C | last host cmd
[40234.925519] iwlwifi :00:14.3: 0x | isr status reg
[40234.925634] iwlwifi :00:14.3: IML/ROM dump:
[40234.925638] iwlwifi :00:14.3: 0x0003 | IML/ROM error/state
[40234.925706] iwlwifi :00:14.3: 0x5603 | IML/ROM data1
[40234.925816] iwlwifi :00:14.3: 0x0080 | IML/ROM WFPM_AUTH_KEY_0
[40234.925836] iwlwifi :00:14.3: Fseq Registers:
[40234.925879] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE
[40234.925922] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION
[40234.925964] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION
[40234.926006] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION
[40234.926049] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION
[40234.926091] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[40234.926134] iwlwifi :00:14.3: 0x2302 | FSEQ_CNVI_ID
[40234.926177] iwlwifi :00:14.3: 0x01300504 | FSEQ_CNVR_ID
[40234.926220] iwlwifi :00:14.3: 0x2302 | CNVI_AUX_MISC_CHIP
[40234.926264] iwlwifi :00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
[40234.926310] iwlwifi :00:14.3: 0x05B0905B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[40234.926356] iwlwifi :00:14.3: 0x025B | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[40234.928144] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 4 fired 
(delay=0ms).
[40234.928151] ieee80211 phy0: Hardware restart was requested

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-29-generic 5.19.0-29.30
ProcVersionSignature: Ubuntu 5.19.

[Kernel-packages] [Bug 2003762] Re: [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

2023-01-23 Thread Daniel van Vugt
Oh no, you seem to have installed graphics packages from the 'oibaf'
PPA. That PPA is known to cause bugs like this and is unsupported.

Please remove the PPA from your system completely, and then report a new
bug if the flickering persists.


** Changed in: kwin (Ubuntu)
   Status: New => Invalid

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

Status in kwin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  alienware aw3423dwf flickers when set to 165hz. Doesn't at 100hz.
  Works fine under windows. GPU is Radeon 6950XT. If I change refresh
  rate down to 100hz it's fine.

  Happened on 22.04 LTS, and the amdgpu ppa made games not work, so I
  upgraded to 22.10 instead.

  Description:Ubuntu 22.10
  Release:22.10

  I expect the display not to flicker at 165hz. monitor doesn't lose
  sync, it's just like a few pixel wide bar that runs the width of the
  screen that shows up randomly for a fraction of a second. Happens when
  just using the desktop environment, not sure if it happens when
  playing a game.

  filename:   
/lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
  srcversion: BB7C61D4A8F6AFF924034AA

  99% sure I should be under X11, not wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-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
  CurrentDesktop: KDE
  Date: Mon Jan 23 18:38:03 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2022-10-23 (92 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-11-06 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2003762/+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 2003762] Re: alienware aw3423dwf flickers at 165hz under linux only.

2023-01-23 Thread Daniel van Vugt
This sounds like a bandwidth management issue, which I know Linux
doesn't do as well as Windows (on Intel graphics either).

Firstly you seem to have the wrong (old) kernel still installed. It
should be version 5.19 so please try fixing that with:

  sudo apt install linux-generic

or

  sudo apt install linux-generic-hwe-22.04

and reboot.

If the problem persists after that then please run:

  journalctl -b0 > journal.txt
  lspci -k > lspci.txt

and attach the resulting text files here.


** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu)

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

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

** Summary changed:

- alienware aw3423dwf flickers at 165hz under linux only.
+ [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

** Tags added: amdgpu

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

Title:
  [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

Status in kwin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  alienware aw3423dwf flickers when set to 165hz. Doesn't at 100hz.
  Works fine under windows. GPU is Radeon 6950XT. If I change refresh
  rate down to 100hz it's fine.

  Happened on 22.04 LTS, and the amdgpu ppa made games not work, so I
  upgraded to 22.10 instead.

  Description:Ubuntu 22.10
  Release:22.10

  I expect the display not to flicker at 165hz. monitor doesn't lose
  sync, it's just like a few pixel wide bar that runs the width of the
  screen that shows up randomly for a fraction of a second. Happens when
  just using the desktop environment, not sure if it happens when
  playing a game.

  filename:   
/lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
  srcversion: BB7C61D4A8F6AFF924034AA

  99% sure I should be under X11, not wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-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
  CurrentDesktop: KDE
  Date: Mon Jan 23 18:38:03 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2022-10-23 (92 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-11-06 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2003762/+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 1997910] Re: Undeclared btqca and btusb firmware

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

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

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

Title:
  Undeclared btqca and btusb firmware

Status in linux package in Ubuntu:
  Expired

Bug description:
  Undeclared btusb firmware

  btusb.ko can request snprintf(fwname, sizeof(fwname),
  "qca/rampatch_usb_%08x.bin", ver_rom); but doesn't declare it as
  MODULES_FIRMWARE.

  btqca can request lots of qca/ things

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997910/+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 1997914] Re: intel/sof firmware is undeclared

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

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

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

Title:
  intel/sof firmware is undeclared

Status in linux package in Ubuntu:
  Expired

Bug description:
  intel/sof firmware is undeclared by the modules that load it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997914/+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 2003757] [NEW] LLVM12 issue: clang: CommandLine Error: Option 'h' registered more than once!

2023-01-23 Thread Dongwon Kim
Public bug reported:

With following packages installed on top of Ubuntu 22.04LTS related to
OpenCL on intel GFX.

libllvm12:amd64  1:12.0.1-19ubuntu3
libclang-cpp12:amd64  1:12.0.1-19ubuntu3
libllvmspirvlib12:amd64  12.0.0-3
libopencl-clang12:amd64  12.0.0-3
libigc1:amd64  1.0.10840-1
libigc-tools:amd64  1.0.10840-1
libclang1-12:amd64  1:12.0.1-19ubuntu3
libigdgmm12:amd64  22.1.2+ds1-1
libigdfcl1:amd64  1.0.10840-1
ocl-icd-libopencl1:amd64  2.2.14-3
intel-opencl-icd:amd64  22.14.22890-1

Subtests from standard Khronos OpenCL-CTS at
https://github.com/KhronosGroup/OpenCL-CTS sporadically fails with an
error,

Executed command : "OpenCL-CTS/build/test_conformance/math_brute_force$
./test_bruteforce -w rint"

clang: CommandLine Error: Option 'h' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
Aborted (core dumped)

Chance of failure is about 5-10%.

Researched little bit and found this is related to the problem the
recently accepted LLVM patch addresses.

https://reviews.llvm.org/D129129

This fix however, is for the current version of LLVM. This might need to
be rebased for LLVM12.

** Affects: llvm-toolchain-12 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  LLVM12 issue: clang: CommandLine Error: Option 'h' registered more
  than once!

Status in llvm-toolchain-12 package in Ubuntu:
  New

Bug description:
  With following packages installed on top of Ubuntu 22.04LTS related to
  OpenCL on intel GFX.

  libllvm12:amd64  1:12.0.1-19ubuntu3
  libclang-cpp12:amd64  1:12.0.1-19ubuntu3
  libllvmspirvlib12:amd64  12.0.0-3
  libopencl-clang12:amd64  12.0.0-3
  libigc1:amd64  1.0.10840-1
  libigc-tools:amd64  1.0.10840-1
  libclang1-12:amd64  1:12.0.1-19ubuntu3
  libigdgmm12:amd64  22.1.2+ds1-1
  libigdfcl1:amd64  1.0.10840-1
  ocl-icd-libopencl1:amd64  2.2.14-3
  intel-opencl-icd:amd64  22.14.22890-1

  Subtests from standard Khronos OpenCL-CTS at
  https://github.com/KhronosGroup/OpenCL-CTS sporadically fails with an
  error,

  Executed command : "OpenCL-
  CTS/build/test_conformance/math_brute_force$ ./test_bruteforce -w
  rint"

  clang: CommandLine Error: Option 'h' registered more than once!
  LLVM ERROR: inconsistency in registered CommandLine options
  Aborted (core dumped)

  Chance of failure is about 5-10%.

  Researched little bit and found this is related to the problem the
  recently accepted LLVM patch addresses.

  https://reviews.llvm.org/D129129

  This fix however, is for the current version of LLVM. This might need
  to be rebased for LLVM12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/2003757/+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 2003753] [NEW] Kinetic update: upstream stable patchset 2023-01-23

2023-01-23 Thread Kamal Mostafa
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2023-01-23

Ported from the following upstream stable releases:
v5.15.80, v6.0.10

   from git://git.kernel.org/

ASoC: wm5102: Revert "ASoC: wm5102: Fix PM disable depth imbalance in 
wm5102_probe"
ASoC: wm5110: Revert "ASoC: wm5110: Fix PM disable depth imbalance in 
wm5110_probe"
ASoC: wm8997: Revert "ASoC: wm8997: Fix PM disable depth imbalance in 
wm8997_probe"
ASoC: mt6660: Keep the pm_runtime enables before component stuff in 
mt6660_i2c_probe
ASoC: rt1019: Fix the TDM settings
ASoC: wm8962: Add an event handler for TEMP_HP and TEMP_SPK
spi: intel: Fix the offset to get the 64K erase opcode
ASoC: codecs: jz4725b: add missed Line In power control bit
ASoC: codecs: jz4725b: fix reported volume for Master ctl
ASoC: codecs: jz4725b: use right control for Capture Volume
ASoC: codecs: jz4725b: fix capture selector naming
ASoC: Intel: sof_sdw: add quirk variant for LAPBC710 NUC15
selftests/futex: fix build for clang
selftests/intel_pstate: fix build for ARCH=x86_64
ASoC: rt1308-sdw: add the default value of some registers
drm/amd/display: Remove wrong pipe control lock
ACPI: scan: Add LATT2021 to acpi_ignore_dep_ids[]
RDMA/efa: Add EFA 0xefa2 PCI ID
btrfs: raid56: properly handle the error when unable to find the missing stripe
NFSv4: Retry LOCK on OLD_STATEID during delegation return
ACPI: x86: Add another system to quirk list for forcing StorageD3Enable
firmware: arm_scmi: Cleanup the core driver removal callback
i2c: tegra: Allocate DMA memory for DMA engine
i2c: i801: add lis3lv02d's I2C address for Vostro 5568
drm/imx: imx-tve: Fix return type of imx_tve_connector_mode_valid
btrfs: remove pointless and double ulist frees in error paths of qgroup tests
x86/cpu: Add several Intel server CPU model numbers
ASoC: codecs: jz4725b: Fix spelling mistake "Sourc" -> "Source", "Routee" -> 
"Route"
KVM: x86/pmu: Do not speculatively query Intel GP PMCs that don't exist yet
hugetlbfs: don't delete error page from pagecache
arm64: dts: qcom: sa8155p-adp: Specify which LDO modes are allowed
arm64: dts: qcom: sm8150-xperia-kumano: Specify which LDO modes are allowed
arm64: dts: qcom: sm8250-xperia-edo: Specify which LDO modes are allowed
arm64: dts: qcom: sm8350-hdk: Specify which LDO modes are allowed
spi: stm32: Print summary 'callbacks suppressed' message
ARM: dts: at91: sama7g5: fix signal name of pin PB2
ASoC: core: Fix use-after-free in snd_soc_exit()
ASoC: tas2770: Fix set_tdm_slot in case of single slot
ASoC: tas2764: Fix set_tdm_slot in case of single slot
ARM: at91: pm: avoid soft resetting AC DLL
serial: 8250: omap: Fix missing PM runtime calls for omap8250_set_mctrl()
serial: 8250_omap: remove wait loop from Errata i202 workaround
serial: 8250: omap: Fix unpaired pm_runtime_put_sync() in omap8250_remove()
serial: 8250: omap: Flush PM QOS work on remove
serial: imx: Add missing .thaw_noirq hook
tty: n_gsm: fix sleep-in-atomic-context bug in gsm_control_send
bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb()
ASoC: soc-utils: Remove __exit for snd_soc_util_exit()
pinctrl: rockchip: list all pins in a possible mux route for PX30
scsi: scsi_transport_sas: Fix error handling in sas_phy_add()
block: sed-opal: kmalloc the cmd/resp buffers
bpf: Fix memory leaks in __check_func_call
arm64: Fix bit-shifting UB in the MIDR_CPU_MODEL() macro
siox: fix possible memory leak in siox_device_add()
parport_pc: Avoid FIFO port location truncation
pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map
drm/vc4: kms: Fix IS_ERR() vs NULL check for vc4_kms
drm/panel: simple: set bpc field for logic technologies displays
drm/drv: Fix potential memory leak in drm_dev_init()
drm: Fix potential null-ptr-deref in drm_vblank_destroy_worker()
arm64: dts: imx8mm: Fix NAND controller size-cells
arm64: dts: imx8mn: Fix NAND controller size-cells
ata: libata-transport: fix double ata_host_put() in ata_tport_add()
ata: libata-transport: fix error handling in ata_tport_add()
ata: libata-transport: fix error handling in ata_tlink_add()
ata: libata-transport: fix error handling in ata_tdev_add()
nfp: change eeprom length to max length enumerators
MIPS: fix duplicate definitions for exported symbols
MIPS: Loongson64: Add WARN_ON on kexec related kmalloc failed
bpf: Initialize same number of free nodes for each pcpu_freelist
net: bgmac: Drop free_netdev() from bgmac_enet_remove()
mISDN: fix possible memory leak in mISDN_dsp_element_register()
net: hinic: Fix error handling in hini

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

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

apport-collect 2003624

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

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

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

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

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

Title:
  Realtek RTL8822CE Wi-Fi Adapter not Found Ubuntu 22.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A few days ago, the Wi-Fi adapter stopped working, resulting in the
  following message "No Wi-Fi Adapter Found". I am using Ubuntu 22.04
  (Jammy).

  Running the command `$ lshw -C network` shows that the device is UNCLAIMED.
  WARNING: you should run this program as super-user.
*-network UNCLAIMED   
 description: Network controller
 product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: cap_list
 configuration: latency=0
 resources: ioport:2000(size=256) memory:fc70-fc70

  My `uname -r` is 5.17.0-1016-oem.
  However, the command `uname -a` gives "Linux tmarwa-IdeaPad-Flex-5-14ARE05 
5.17.0-1016-oem #17-Ubuntu SMP PREEMPT Mon Aug 22 11:31:08 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux".

  My device is ideaPad Flex 5 14ARE05.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003624/+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 2003624] Re: Realtek RTL8822CE Wi-Fi Adapter not Found Ubuntu 22.04

2023-01-23 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Realtek RTL8822CE Wi-Fi Adapter not Found Ubuntu 22.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A few days ago, the Wi-Fi adapter stopped working, resulting in the
  following message "No Wi-Fi Adapter Found". I am using Ubuntu 22.04
  (Jammy).

  Running the command `$ lshw -C network` shows that the device is UNCLAIMED.
  WARNING: you should run this program as super-user.
*-network UNCLAIMED   
 description: Network controller
 product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: cap_list
 configuration: latency=0
 resources: ioport:2000(size=256) memory:fc70-fc70

  My `uname -r` is 5.17.0-1016-oem.
  However, the command `uname -a` gives "Linux tmarwa-IdeaPad-Flex-5-14ARE05 
5.17.0-1016-oem #17-Ubuntu SMP PREEMPT Mon Aug 22 11:31:08 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux".

  My device is ideaPad Flex 5 14ARE05.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003624/+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 2003624] [NEW] Realtek RTL8822CE Wi-Fi Adapter not Found Ubuntu 22.04

2023-01-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

A few days ago, the Wi-Fi adapter stopped working, resulting in the
following message "No Wi-Fi Adapter Found". I am using Ubuntu 22.04
(Jammy).

Running the command `$ lshw -C network` shows that the device is UNCLAIMED.
WARNING: you should run this program as super-user.
  *-network UNCLAIMED   
   description: Network controller
   product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: cap_list
   configuration: latency=0
   resources: ioport:2000(size=256) memory:fc70-fc70

My `uname -r` is 5.17.0-1016-oem.
However, the command `uname -a` gives "Linux tmarwa-IdeaPad-Flex-5-14ARE05 
5.17.0-1016-oem #17-Ubuntu SMP PREEMPT Mon Aug 22 11:31:08 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux".

My device is ideaPad Flex 5 14ARE05.

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


** Tags: bot-comment
-- 
Realtek RTL8822CE Wi-Fi Adapter not Found Ubuntu 22.04
https://bugs.launchpad.net/bugs/2003624
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 2003730] Re: Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52

2023-01-23 Thread Frank Heimes
** Summary changed:

- Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52
+ Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

** Changed in: ubuntu-z-systems
   Status: New => Triaged

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

Title:
  Ubuntu 22.04.1 LTS - kernel dbgsym packages missing after version
  5.15.0-52

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for 
the most recent 5.15.0 kernels they are missing.
  They are required for dump analysis. Please add them to the updates pool.

  Reported by: Thorsten Diehl 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003730/+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 2003730] Re: Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52

2023-01-23 Thread Frank Heimes
Hi Thorsten, yeah we discussed that (and at that time had the pull-lp-source 
workaround) - in parallel I requested to fix the broken generation (its 
actually more a broken sync) of the last recent dbg packages.
I think (thought) that it got solved meanwhile and that they are now already 
available here:
http://ddebs.ubuntu.com/pool/main/l/linux/
like:
http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-unsigned-5.15.0-52-generic-dbgsym_5.15.0-52.58_s390x.ddeb
Please can you check if that is the right package you are looking for?
And if you have the ddebs as source line in your apt sources.list files,
you may need to do an update to see them:
sudo apt update

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

Title:
  Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version
  5.15.0-52

Status in linux package in Ubuntu:
  New

Bug description:
  Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for 
the most recent 5.15.0 kernels they are missing.
  They are required for dump analysis. Please add them to the updates pool.

  Reported by: Thorsten Diehl 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003730/+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 2003730] [NEW] Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52

2023-01-23 Thread bugproxy
Public bug reported:

Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for the 
most recent 5.15.0 kernels they are missing.
They are required for dump analysis. Please add them to the updates pool.

Reported by: Thorsten Diehl 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-200899 severity-high 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-200899 severity-high
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version
  5.15.0-52

Status in linux package in Ubuntu:
  New

Bug description:
  Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for 
the most recent 5.15.0 kernels they are missing.
  They are required for dump analysis. Please add them to the updates pool.

  Reported by: Thorsten Diehl 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003730/+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 2003730] [NEW] Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52

2023-01-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Up to linux-image-5.15.0-52-generic the dbgsym packages are available, for the 
most recent 5.15.0 kernels they are missing.
They are required for dump analysis. Please add them to the updates pool.

Reported by: Thorsten Diehl 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-200899 severity-high 
targetmilestone-inin---
-- 
Ubuntu22.04.1 LTS - kernel dbgsym packages missing after version 5.15.0-52
https://bugs.launchpad.net/bugs/2003730
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 2003728] [NEW] Enable MGBE ethernet on Orin platforms

2023-01-23 Thread Brad Figg
Public bug reported:

 [Impact]
Adding these patches enables additional functionality and addresses bugs 
related to the Ubuntu kernel on Orin reference HW.

Specifically these 3 patches (2 cherry-picks and 1 backport) add the
MGBE driver.

 [Fix]
These patches do not constitute a single fix or a set of fixes for bugs but 
instead enable kernel functionality as well as fix kernel bugs related to 
Nvidia HW.

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

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

Title:
  Enable MGBE ethernet on Orin platforms

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
   [Impact]
  Adding these patches enables additional functionality and addresses bugs 
related to the Ubuntu kernel on Orin reference HW.

  Specifically these 3 patches (2 cherry-picks and 1 backport) add
  the MGBE driver.

   [Fix]
  These patches do not constitute a single fix or a set of fixes for bugs 
but instead enable kernel functionality as well as fix kernel bugs related to 
Nvidia HW.

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

2023-01-23 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/2003722

Title:
  my bluetooth not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello, i use DellLatitude E5400 which has in-built bluetooth but cant turn on 
and i cant search devices .
  when i open bluetooth manager it tells me the "connection to bluez failed"
  i have tried all commands but has failed .
  when i check bluetooth status it show inactive(dead)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  symore 2803 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Mon Jan 23 17:54:37 2023
  InstallationDate: Installed on 2022-04-29 (269 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Latitude E5400
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=fd18940b-5621-4b7f-93db-e35579f383eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2009
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0D695C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd08/11/2009:br1.3:efr1.3:svnDellInc.:pnLatitudeE5400:pvr:rvnDellInc.:rn0D695C:rvr:cvnDellInc.:ct8:cvr:sku:
  dmi.product.name: Latitude E5400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003722/+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 2003722] [NEW] my bluetooth not working

2023-01-23 Thread MUHWEZI SIMON
Public bug reported:

hello, i use DellLatitude E5400 which has in-built bluetooth but cant turn on 
and i cant search devices .
when i open bluetooth manager it tells me the "connection to bluez failed"
i have tried all commands but has failed .
when i check bluetooth status it show inactive(dead)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-58-generic 5.15.0-58.64
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  symore 2803 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Mon Jan 23 17:54:37 2023
InstallationDate: Installed on 2022-04-29 (269 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
MachineType: Dell Inc. Latitude E5400
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=fd18940b-5621-4b7f-93db-e35579f383eb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-58-generic N/A
 linux-backports-modules-5.15.0-58-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2009
dmi.bios.release: 1.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0D695C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd08/11/2009:br1.3:efr1.3:svnDellInc.:pnLatitudeE5400:pvr:rvnDellInc.:rn0D695C:rvr:cvnDellInc.:ct8:cvr:sku:
dmi.product.name: Latitude E5400
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy

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

Title:
  my bluetooth not working

Status in linux package in Ubuntu:
  New

Bug description:
  hello, i use DellLatitude E5400 which has in-built bluetooth but cant turn on 
and i cant search devices .
  when i open bluetooth manager it tells me the "connection to bluez failed"
  i have tried all commands but has failed .
  when i check bluetooth status it show inactive(dead)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  symore 2803 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Mon Jan 23 17:54:37 2023
  InstallationDate: Installed on 2022-04-29 (269 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Latitude E5400
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=fd18940b-5621-4b7f-93db-e35579f383eb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2009
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0D695C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd08/11/2009:br1.3:efr1.3:svnDellInc.:pnLatitudeE5400:pvr:rvnDellInc.:rn0D695C:rvr:cvnDellInc.:ct8:cvr:sku:
  dmi.product.name: Latitude E5400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003722/+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 2003718] [NEW] [Ubuntu 22.04] Duplicate link for NVMe device by-id

2023-01-23 Thread Sheik Ajith Ali Mohammed Farook
Private bug reported:

[Impact]

Users may choose wrong link and would not be able to work with it.

[Test Plan]

Connect to NVMe/TCP subsystem using nvme connect-all. This was tested
against Dell PowerStore, PowerFlex and PowerMax

Steps to Reproduce:
1. Use nvme connect-all to connect to an NVMe/TCP subsystems
2. Check /dev/disc/by-id

[Original report]

Description:
When working with NVMe/TCP host functionality, connecting to NVMe subsystem 
through multiple controllers can lead to an invalid device link created in 
/dev/disc/by-id/ being created.

Steps to reproduce:
Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

Expected Behavior:
No duplicate entries of NVMe subsystems should exist.

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

** Information type changed from Public to Private

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

Title:
  [Ubuntu 22.04] Duplicate link for NVMe device by-id

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  Users may choose wrong link and would not be able to work with it.

  [Test Plan]

  Connect to NVMe/TCP subsystem using nvme connect-all. This was tested
  against Dell PowerStore, PowerFlex and PowerMax

  Steps to Reproduce:
  1. Use nvme connect-all to connect to an NVMe/TCP subsystems
  2. Check /dev/disc/by-id

  [Original report]

  Description:
  When working with NVMe/TCP host functionality, connecting to NVMe subsystem 
through multiple controllers can lead to an invalid device link created in 
/dev/disc/by-id/ being created.

  Steps to reproduce:
  Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
  Step 2: Install nvme-cli package, currently installed version is nvme version 
1.16
  Step 3: In the os terminal, type any nvme connect-all to connect to NVMe 
subsystems and check the duplicate entries in /dev/disk/by-id/.

  Expected Behavior:
  No duplicate entries of NVMe subsystems should exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003718/+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 2003714] Re: Azure: TDX enabled hyper-visors cause segfault

2023-01-23 Thread Tim Gardner
** Description changed:

  SRU Justification
  
  [Impact]
  
  Microsoft TDX enabled hyper visors cause a segfault due to an upstream
  glibc bug. This can be worked around with a kernel patch.
  
  Issue Description:
  
  When I start an Intel TDX Ubuntu 22.04 (or RHEL 9.0) guest on Hyper-V,
  the guest always hits segfaults and can’t boot up. Here the kernel
  running in the guest is the upstream kernel + my TDX patchset, or the
  5.19.0-azure kernel + the same TDX patchset:
  
  [Fix]
  
  We confirmed the segfault also happens to TDX guests on the KVM
  hypervisor. After I checked with more Intel folks, it turns out this is
  indeed a glibc bug
  (https://sourceware.org/bugzilla/show_bug.cgi?id=28784), which has been
  fixed in the upsteram glibc, but Ubuntu 22.04 and newer haven’t picked
  up the glibc fix yet.
  
- 
  I got a kernel side temporary workarouond from Intel:
  https://github.com/dcui/tdx/commit/16218cf73491e867fd39c16c9e4b8aa926cbda68,
  which is on the same existing branch “decui/upstream-
  kinetic-22.10/master-next/1209”.
  
- 
- 
  [   21.081453] Run /inits init process
  
  [   21.086896]   with arguments:
  
  [   21.095790] /init
  
  [   21.100982]   with environment:
  
  [   21.106611] HOME=/
  
  [   21.112463] TERM=linux
  
  [   21.119850] BOOT_IMAGE=/boot/vmlinuz-6.1.0-rc7-decui+
  
  Loading, please wait...
  
  Starting version 249.11-0ubuntu3.6
  
  [   21.253908] udevadm[144]: segfault at 56538d61e0c0 ip
  7f8f5899efeb sp 7ffd08fb7648 error 6 in
  libc.so.6[7f8f5882+195000] likely on CPU 0 (core 0, socket 0)
  
  [   21.316549] Code: 07 62 e1 7d 48 e7 4f 01 62 e1 7d 48 e7 67 40 62 e1
  7d 48 e7 6f 41 62 61 7d 48 e7 87 00 20 00 00 62 61 7d 48 e7 8f 40 20 00
  00 <62> 61 7d 48 e7 a7 00 30 00 00 62 61 7d 48 e7 af 40 30 00 00 48 83
  
  Segmentation fault
  
  [   22.499317] setfont[153]: segfault at 55ef3b91b000 ip
  7f5899899fa4 sp 7ffc8008f628 error 4 in
  libc.so.6[7f589971b000+195000] likely on CPU 0 (core 0, socket 0)
  
  [   22.602677] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1
  fe 48 6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00
  00 <62> 61 fe 48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83
  
  [   22.732413] loadkeys[156]: segfault at 563ffe292000 ip
  7fbff957afa4 sp 7ffe31453808 error 4 in
  libc.so.6[7fbff93fc000+195000] likely on CPU 0 (core 0, socket 0)
  
  [   22.833061] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1
  fe 48 6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00
  00 <62> 61 fe 48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83
- 
  
  The segfault only happens to recent glibc versions (e.g. v2.35 in Ubuntu
  22.04, and v2.34 in RHEL 9.0). It doesn’t happens to v2.31 in Ubuntu
  20.04, or v2.32 in Ubuntu 20.10. So something in glibc must have changed
  between v2.32 (good) and 2.34+ (not working for TDX). The oddity is:
  when I run the same Ubuntu 22.04/RHEL 9.0 image as a regular non-TDX
  guest, the segfault never happens.
  
- 
  If I boot up a Ubuntu 20.04 TDX guest (which works fine), mount a Ubuntu
  22.04 VHD image (“mount /dev/sdd1 /mnt”) and try to run “chroot /mnt”, I
  hit the same segfault:
  
- 
  [  109.478556] EXT4-fs (sdd1): mounted filesystem with ordered data
  mode. Quota mode: none.
  
  [  129.22] bash[2112]: segfault at 556987854000 ip 7f88468c4ea4
  sp 7ffc22ecf158 error 6 in libc.so.6[7f8846828000+195000] likely on
  CPU 48 (core 0, socket 48)
  
  [  129.242434] Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44
  0f e7 8f 10 20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00
  00 <66> 44 0f e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7
- 
  
  It looks like the application is referencing a memory location that
  somehow triggers a page fault, which is converted to a sigal SIGSEGV,
  which causes a segfault and terminates the application (I’m not sure
  where the below “movntdq” instructions come from):
  
- 
  root@decui-u2004-u28:/opt/linus-0824# echo 'Code: e7 bf 30 10 00 00 66
  44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20 00 00 66 44 0f e7 97 20 20
  00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f e7 a7 00 30 00 00 66 44 0f
  e7 af 10 30 00 00 66 44 0f e7' | scripts/decodecode
  
  Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20
  00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f
  e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7
  
  All code
  
  
  
-0:   e7 bf   out%eax,$0xbf
- 
-2:   30 10   xor%dl,(%rax)
- 
-4:   00 00   add%al,(%rax)
- 
-6:   66 44 0f e7 87 00 20movntdq %xmm8,0x2000(%rdi)
- 
-d:   00 00
- 
-f:   66 44 0f e7 8f 10 20movntdq %xmm9,0x2010(%rdi)
- 
-   16:   00 00
- 
-   18:   66 44 0f e7 97 20 20movntdq %xmm10,0x2020(%rdi)
- 
-   1f:   00 00
- 
-   21:   66 44 0f e7 9f 30 20movntdq 

[Kernel-packages] [Bug 2003714] [NEW] Azure: TDX enabled hyper-visors cause segfault

2023-01-23 Thread Tim Gardner
Public bug reported:

SRU Justification

[Impact]

Microsoft TDX enabled hyper visors cause a segfault due to an upstream
glibc bug. This can be worked around with a kernel patch.

Issue Description:

When I start an Intel TDX Ubuntu 22.04 (or RHEL 9.0) guest on Hyper-V,
the guest always hits segfaults and can’t boot up. Here the kernel
running in the guest is the upstream kernel + my TDX patchset, or the
5.19.0-azure kernel + the same TDX patchset:

[Fix]

We confirmed the segfault also happens to TDX guests on the KVM
hypervisor. After I checked with more Intel folks, it turns out this is
indeed a glibc bug
(https://sourceware.org/bugzilla/show_bug.cgi?id=28784), which has been
fixed in the upsteram glibc, but Ubuntu 22.04 and newer haven’t picked
up the glibc fix yet.

I got a kernel side temporary workarouond from Intel:
https://github.com/dcui/tdx/commit/16218cf73491e867fd39c16c9e4b8aa926cbda68,
which is on the same existing branch “decui/upstream-
kinetic-22.10/master-next/1209”.

[   21.081453] Run /inits init process

[   21.086896]   with arguments:

[   21.095790] /init

[   21.100982]   with environment:

[   21.106611] HOME=/

[   21.112463] TERM=linux

[   21.119850] BOOT_IMAGE=/boot/vmlinuz-6.1.0-rc7-decui+

Loading, please wait...

Starting version 249.11-0ubuntu3.6

[   21.253908] udevadm[144]: segfault at 56538d61e0c0 ip
7f8f5899efeb sp 7ffd08fb7648 error 6 in
libc.so.6[7f8f5882+195000] likely on CPU 0 (core 0, socket 0)

[   21.316549] Code: 07 62 e1 7d 48 e7 4f 01 62 e1 7d 48 e7 67 40 62 e1
7d 48 e7 6f 41 62 61 7d 48 e7 87 00 20 00 00 62 61 7d 48 e7 8f 40 20 00
00 <62> 61 7d 48 e7 a7 00 30 00 00 62 61 7d 48 e7 af 40 30 00 00 48 83

Segmentation fault

[   22.499317] setfont[153]: segfault at 55ef3b91b000 ip
7f5899899fa4 sp 7ffc8008f628 error 4 in
libc.so.6[7f589971b000+195000] likely on CPU 0 (core 0, socket 0)

[   22.602677] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1
fe 48 6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00
00 <62> 61 fe 48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83

[   22.732413] loadkeys[156]: segfault at 563ffe292000 ip
7fbff957afa4 sp 7ffe31453808 error 4 in
libc.so.6[7fbff93fc000+195000] likely on CPU 0 (core 0, socket 0)

[   22.833061] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1
fe 48 6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00
00 <62> 61 fe 48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83

The segfault only happens to recent glibc versions (e.g. v2.35 in Ubuntu
22.04, and v2.34 in RHEL 9.0). It doesn’t happens to v2.31 in Ubuntu
20.04, or v2.32 in Ubuntu 20.10. So something in glibc must have changed
between v2.32 (good) and 2.34+ (not working for TDX). The oddity is:
when I run the same Ubuntu 22.04/RHEL 9.0 image as a regular non-TDX
guest, the segfault never happens.

If I boot up a Ubuntu 20.04 TDX guest (which works fine), mount a Ubuntu
22.04 VHD image (“mount /dev/sdd1 /mnt”) and try to run “chroot /mnt”, I
hit the same segfault:

[  109.478556] EXT4-fs (sdd1): mounted filesystem with ordered data
mode. Quota mode: none.

[  129.22] bash[2112]: segfault at 556987854000 ip 7f88468c4ea4
sp 7ffc22ecf158 error 6 in libc.so.6[7f8846828000+195000] likely on
CPU 48 (core 0, socket 48)

[  129.242434] Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44
0f e7 8f 10 20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00
00 <66> 44 0f e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7

It looks like the application is referencing a memory location that
somehow triggers a page fault, which is converted to a sigal SIGSEGV,
which causes a segfault and terminates the application (I’m not sure
where the below “movntdq” instructions come from):

root@decui-u2004-u28:/opt/linus-0824# echo 'Code: e7 bf 30 10 00 00 66
44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20 00 00 66 44 0f e7 97 20 20
00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f e7 a7 00 30 00 00 66 44 0f
e7 af 10 30 00 00 66 44 0f e7' | scripts/decodecode

Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20
00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f
e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7

All code



   0:   e7 bf   out%eax,$0xbf

   2:   30 10   xor%dl,(%rax)

   4:   00 00   add%al,(%rax)

   6:   66 44 0f e7 87 00 20movntdq %xmm8,0x2000(%rdi)

   d:   00 00

   f:   66 44 0f e7 8f 10 20movntdq %xmm9,0x2010(%rdi)

  16:   00 00

  18:   66 44 0f e7 97 20 20movntdq %xmm10,0x2020(%rdi)

  1f:   00 00

  21:   66 44 0f e7 9f 30 20movntdq %xmm11,0x2030(%rdi)

  28:   00 00

  2a:*  66 44 0f e7 a7 00 30movntdq %xmm12,0x3000(%rdi)
<-- trapping instruction

  31:   00 00

  33:   66 44 0f e7 af 10 30movntdq %xmm13,0x3010(%rdi)

  3a:   00 00

  3c:   66  data16

  3d:   44  rex.

[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes

2023-01-23 Thread Łukasz Zemczak
Dimitri thank you for the upload! I'd like to accept it soonish, but
since this SRU bug is missing the usual Test Case, Impact and Regression
Potential, could you fill that up before I accept it? I'd like to know
more about the fix that you performed, what it changes and what could go
wrong with it.

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

Title:
  ZFS + Encryption installations of Ubuntu Desktop do not come up
  correctly on first boot, systemd unmounts many of the zfs volumes

Status in Ubuntu Manual Tests:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zsys package in Ubuntu:
  Invalid

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM,
  50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Install Ubuntu" and proceed with the installation process.
  3. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  4. Proceed with the rest of the installation as normal.
  5. Reboot into the newly installed system.
  6. Log in.
  7. Run "sudo apt update" in a terminal.

  Expected result: The package database should be updated normally.

  Actual result: You are presented with the following errors at the end
  of the apt output:

  Reading package lists... Error!
  E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or 
directory)
  E: Could not open file  - open (2: No such file or directory)
  E: Problem opening 
  E: The package lists or status file could not be parsed or opened.

  
  Notes: Switching to a TTY will print a crash error message related to the 
same missing /var/lib/dpkg/status file. Running "sudo touch 
/var/lib/dpkg/status" will allow "sudo apt update" to function and fix the 
crashed process in the TTY.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages was related to
  update-manager in my experience, and another one was from "check-new-
  release-gtk".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 09:55:27 2022
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19

2023-01-23 Thread Dimitri John Ledkov
zfs-linux SRUs, should follow the regular SRU testing process which
covers all bases.

In the past we have used these:

[Test Plan]

 * autopkgtest pass

 * kernel regression zfs testsuite pass

 * zsys integration test pass


The first two cover unit, functional, and integration tests. Whilst the last 
one covers full-end-to-end zfs-on-root systems with snapshotting.

More details guidelines are available internally in a google doc shared
with kernel team, on how to execute them.

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

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  In Progress

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

2023-01-23 Thread Dimitri John Ledkov
We should SRU these changes to Kinetic too, as they do fixup an issue
which can be hit on kinetic.

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

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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 2002636] Please test proposed package

2023-01-23 Thread Łukasz Zemczak
Hello Paolo, or anyone else affected,

Accepted broadcom-sta into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/broadcom-
sta/6.30.223.271-23~22.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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 2003174] Proposed package upload rejected

2023-01-23 Thread Łukasz Zemczak
An upload of zfs-linux to jammy-proposed has been rejected from the
upload queue for the following reason: "Please see
https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2003174/comments/3 for the rationale.".

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

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  In Progress

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19

2023-01-23 Thread Łukasz Zemczak
I don't feel comfortable accepting this SRU in the current form. I'm
happy to hear that there's 'no significant ABI changes' in this version,
but basically doing a new upstream release with a diff of 556 files
changed, 48365 insertions(+), 23626 deletions(-) with only "$ sudo apt
install zfs-dkms" as the test case is not acceptable.

This should ideally be a cherry-picked fix. Will reject it for now.

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

Title:
  zfs-dkms fails to build on jammy with linux 5.19

Status in zfs-linux package in Ubuntu:
  Invalid
Status in zfs-linux source package in Jammy:
  In Progress

Bug description:
  [Impact]

  zfs-dkms fails to build on jammy with the latest linux hwe 5.19:

  
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  The most reliable fix is probably to move to the same version that is
  available in kinetic, since there's no significant ABI change in this
  way we should be able to support both 5.15 and 5.19 kernels.

  [Regression potential]

  We may experience zfs regressions if there's a format/ABI
  incompatibility with volumes created with the previous version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+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 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

2023-01-23 Thread Łukasz Zemczak
Also: I assume there are no plans/needs to have this in kinetic? Only
asking because now jammy version > kinetic version, which is never
ideal.

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

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

2023-01-23 Thread Łukasz Zemczak
I'll accept this this time as the changes feel sane, but please be sure
not to include patches without any description in uploads that are later
pushed as SRUs to stable series.

** Changed in: broadcom-sta (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19

Status in broadcom-sta package in Ubuntu:
  Invalid
Status in broadcom-sta source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19.

  [Test case]

   $ sudo apt-get install broadcom-sta-dkms

  [Fix]

  The attached debdiff sync Jammy version to Lunar, minus the dh-dkms
  build-dep.

  [Regression potential]

  None, it's the same version we are already using in Lunar and it
  contains only fixes to the base version (that is the same among Jammy,
  Kinetic and Lunar).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+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 1995956] Re: amdgpu no-retry page fault in Kinetic Kudu

2023-01-23 Thread Daniel van Vugt
** Tags added: amdgpu fixed-upstream kinetic

** Tags added: fixed-in-linux-6.1

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

Title:
  amdgpu no-retry page fault in Kinetic Kudu

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
  Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin!
  Nov 03 16:35:55 laptop kernel: [drm] free PSP TMR buffer
  Nov 03 16:35:55 laptop kernel: CPU: 15 PID: 141579 Comm: kworker/u32:1 
Tainted: GW 

[Kernel-packages] [Bug 2003607] Re: Recurring graphics freezes (amdgpu 0000:06:00.0: amdgpu: [mmhub0] no-retry page fault)

2023-01-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1995956 ***
https://bugs.launchpad.net/bugs/1995956

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1995956, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- Freeze
+ Recurring graphics freezes (amdgpu :06:00.0: amdgpu: [mmhub0] no-retry 
page fault)

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

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

** This bug has been marked a duplicate of bug 1995956
   amdgpu no-retry page fault in Kinetic Kudu

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

Title:
  Recurring graphics freezes (amdgpu :06:00.0: amdgpu: [mmhub0] no-
  retry page fault)

Status in linux package in Ubuntu:
  New

Bug description:
  Freeze happens almost immediately with electron/chromium apps - the
  ones I am using are Spotify and Slack.

  I have two machines, both using the amdgpu driver. One identifies as
  CEZANNE d2 and the other as r9

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  Uname: Linux 5.19.0-28-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 21 09:41:11 2023
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5094]
  InstallationDate: Installed on 2022-11-10 (71 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 20XK00B1UK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=1abd05d4-b39c-4be7-9c66-33241c240265 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2022
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET51W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XK00B1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 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.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET51W(1.21):bd09/15/2022:br1.21:efr1.21:svnLENOVO:pn20XK00B1UK:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK00B1UK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a:
  dmi.product.family: ThinkPad T14 Gen 2a
  dmi.product.name: 20XK00B1UK
  dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a
  dmi.product.version: ThinkPad T14 Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003607/+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 2002088] Re: Ubuntu Desktop freezes

2023-01-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1995956 ***
https://bugs.launchpad.net/bugs/1995956

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1995956, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1995956
   amdgpu no-retry page fault in Kinetic Kudu

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

Title:
  Ubuntu Desktop freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While using desktop the machine suddenly freezes and computer has to be shut 
down
  from power button and restarted. However, I could log in from another machine 
by using ssh and saw that dmesg is showing lots of these messages:

  [ 6834.800344] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault 
(src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread 
slack:cs0 pid 5441)
  [ 6834.800351] amdgpu :08:00.0: amdgpu:   in page starting at address 
0x800106bf from IH client 0x12 (VMC)
  [ 6834.800355] amdgpu :08:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00240051
  [ 6834.800356] amdgpu :08:00.0: amdgpu:  Faulty UTCL2 client ID: MP1 
(0x0)
  [ 6834.800358] amdgpu :08:00.0: amdgpu:  MORE_FAULTS: 0x1
  [ 6834.800359] amdgpu :08:00.0: amdgpu:  WALKER_ERROR: 0x0
  [ 6834.800359] amdgpu :08:00.0: amdgpu:  PERMISSION_FAULTS: 0x5
  [ 6834.800360] amdgpu :08:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [ 6834.800361] amdgpu :08:00.0: amdgpu:  RW: 0x1
  [ 6834.800362] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault 
(src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread 
slack:cs0 pid 5441)
  [ 6834.800364] amdgpu :08:00.0: amdgpu:   in page starting at address 
0x800106bf1000 from IH client 0x12 (VMC)
  [ 6834.800373] amdgpu :08:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00240051
  [ 6834.800374] amdgpu :08:00.0: amdgpu:  Faulty UTCL2 client ID: MP1 
(0x0)
  [ 6834.800375] amdgpu :08:00.0: amdgpu:  MORE_FAULTS: 0x1
  [ 6834.800376] amdgpu :08:00.0: amdgpu:  WALKER_ERROR: 0x0
  [ 6834.800376] amdgpu :08:00.0: amdgpu:  PERMISSION_FAULTS: 0x5
  [ 6834.800377] amdgpu :08:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [ 6834.800378] amdgpu :08:00.0: amdgpu:  RW: 0x1
  [ 6834.800379] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault 
(src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread 
slack:cs0 pid 5441)
  [ 6834.800380] amdgpu :08:00.0: amdgpu:   in page starting at address 
0x800106bf2000 from IH client 0x12 (VMC)
  [ 6834.800382] amdgpu :08:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  [ 6834.800383] amdgpu :08:00.0: amdgpu:  Faulty UTCL2 client ID: MP1 
(0x0)
  [ 6834.800384] amdgpu :08:00.0: amdgpu:  MORE_FAULTS: 0x0
  [ 6834.800385] amdgpu :08:00.0: amdgpu:  WALKER_ERROR: 0x0
  [ 6834.800386] amdgpu :08:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [ 6834.800386] amdgpu :08:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [ 6834.800387] amdgpu :08:00.0: amdgpu:  RW: 0x0
  [ 6834.800388] amdgpu :08:00.0: amdgpu: [mmhub0] no-retry page fault 
(src_id:0 ring:40 vmid:2 pasid:32775, for process slack pid 5378 thread 
slack:cs0 pid 5441)
  [ 6834.800389] amdgpu :08:00.0: amdgpu:   in page starting at address 
0x800106bf3000 from IH client 0x12 (VMC)
  [ 6834.800391] amdgpu :08:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  [ 6834.800392] amdgpu :08:00.0: amdgpu:  Faulty UTCL2 client ID: MP1 
(0x0)
  [ 6834.800393] amdgpu :08:00.0: amdgpu:  MORE_FAULTS: 0x0
  [ 6834.800394] amdgpu :08:00.0: amdgpu:  WALKER_ERROR: 0x0
  [ 6834.800394] amdgpu :08:00.0: amdgpu:  PERMISSION_FAULTS: 0x0
  [ 6834.800395] amdgpu :08:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [ 6834.800396] amdgpu :08:00.0: amdgpu:  RW: 0x0
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sampie 3301 F wireplumber
   /dev/snd/controlC1:  sampie 3301 F wireplumber
   /dev/snd/controlC0:  sampie 3301 F wireplumber
   /dev/snd/seq:sampie 3295 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (458 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish In

[Kernel-packages] [Bug 1982833] Re: [UBUNTU 23.04] Bump (kernel) '-mtune' to z16 / arch14

2023-01-23 Thread Frank Heimes
** Summary changed:

- Bump (kernel) '-mtune' to z16 / arch14 with 23.04
+ [UBUNTU 23.04] Bump (kernel) '-mtune' to z16 / arch14

** Summary changed:

- [UBUNTU 23.04] Bump (kernel) '-mtune' to z16 / arch14
+ [23.04] Bump (kernel) '-mtune' to z16 / arch14

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

Title:
  [23.04] Bump (kernel) '-mtune' to z16 / arch14

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in gcc-12 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Consider to bump the kernel '-mtune' to z16 (equals arch14), starting
  with 23.04.

  Discuss with IBM Z team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982833/+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 2003607] [NEW] Recurring graphics freezes (amdgpu 0000:06:00.0: amdgpu: [mmhub0] no-retry page fault)

2023-01-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Freeze happens almost immediately with electron/chromium apps - the ones
I am using are Spotify and Slack.

I have two machines, both using the amdgpu driver. One identifies as
CEZANNE d2 and the other as r9

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
Uname: Linux 5.19.0-28-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 21 09:41:11 2023
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Cezanne [17aa:5094]
InstallationDate: Installed on 2022-11-10 (71 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: LENOVO 20XK00B1UK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=1abd05d4-b39c-4be7-9c66-33241c240265 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2022
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET51W (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XK00B1UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.21
dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET51W(1.21):bd09/15/2022:br1.21:efr1.21:svnLENOVO:pn20XK00B1UK:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK00B1UK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a:
dmi.product.family: ThinkPad T14 Gen 2a
dmi.product.name: 20XK00B1UK
dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a
dmi.product.version: ThinkPad T14 Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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

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


** Tags: amd64 amdgpu apport-bug freeze kinetic ubuntu wayland-session
-- 
Recurring graphics freezes (amdgpu :06:00.0: amdgpu: [mmhub0] no-retry page 
fault)
https://bugs.launchpad.net/bugs/2003607
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1995783] Re: Nightlight fails after suspend

2023-01-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1752680 ***
https://bugs.launchpad.net/bugs/1752680

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1752680, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1752680
   Night light does not work after resume from suspend or unlock.

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

Title:
  Nightlight fails after suspend

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Nightlight activates when turned on in settings but after closing the
  lid or otherwise suspending and then resuming power nightlight fails
  to change the color temperature.  Settings still indicates that
  nightlight is on.  If nightlight setting is cycled nightlight works
  again until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.154  Wed Jun 22 04:50:54 
UTC 2022
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  5 22:03:14 2022
  DistUpgraded: 2022-10-29 22:31:31,858 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/390.154, 5.15.0-52-generic, x86_64: installed
   nvidia/390.154, 5.19.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:212b]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:1247] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 635M [1043:212b]
  InstallationDate: Installed on 2019-01-15 (1390 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK Computer Inc. N55SL
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=47b67201-d4ee-44d7-adec-9d457d3c9b5c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (6 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SL.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SL.204:bd10/24/2012:br4.6:svnASUSTeKComputerInc.:pnN55SL:pvr1.0:rvnASUSTeKComputerInc.:rnN55SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.family: N
  dmi.product.name: N55SL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/mutter/+bug/1995783/+subscriptions


-- 
Mailing list: https://la

[Kernel-packages] [Bug 2003688] [NEW] Lunar update: v6.1.5 upstream stable release

2023-01-23 Thread Paolo Pisati
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.1.5 upstream stable release
   from git://git.kernel.org/


Linux 6.1.5
wifi: ath11k: Send PME message during wakeup from D3cold
efi: random: combine bootloader provided RNG seed with RNG protocol output
drm/i915/dsi: fix MIPI_BKLT_EN_1 native GPIO index
drm/i915/dsi: add support for ICL+ native MIPI GPIO sequence
ksmbd: check nt_len to be at least CIFS_ENCPWD_SIZE in 
ksmbd_decode_ntlmssp_auth_blob
ksmbd: send proper error response in smb2_tree_connect()
ksmbd: fix infinite loop in ksmbd_conn_handler_loop()
btrfs: handle case when repair happens with dev-replace
drm/amd/display: Uninitialized variables causing 4k60 UCLK to stay at DPM1 and 
not DPM0
drm/amd/display: Add check for DET fetch latency hiding for dcn32
virtio_blk: Fix signedness bug in virtblk_prep_rq()
virtio-blk: use a helper to handle request queuing errors
drm/i915/gvt: fix vgpu debugfs clean in remove
drm/i915/gvt: fix gvt debugfs destroy
drm/amdkfd: Fix kernel warning during topology setup
drm/plane-helper: Add the missing declaration of drm_atomic_state
of/fdt: run soc memory setup when early_init_dt_scan_memory fails
riscv, kprobes: Stricter c.jr/c.jalr decoding
riscv: uaccess: fix type of 0 variable on error in get_user()
thermal: int340x: Add missing attribute for data rate base
vhost_vdpa: fix the crash in unmap a large memory
tpm: Allow system suspend to continue when TPM suspend fails
io_uring: fix CQ waiting timeout handling
io_uring: pin context while queueing deferred tw
block: don't allow splitting of a REQ_NOWAIT bio
net: dsa: tag_qca: fix wrong MGMT_DATA2 size
net: dsa: qca8k: fix wrong length value for mgmt eth packet
Revert "net: dsa: qca8k: cache lo and hi for mdio write"
Revert "drm/amd/display: Enable Freesync Video Mode by default"
bpf: Fix panic due to wrong pageattr of im->image
fbdev: matroxfb: G200eW: Increase max memory from 1 MB to 16 MB
nfsd: fix handling of readdir in v4root vs. mount upcall timeout
x86/bugs: Flush IBP in ib_prctl_set()
x86/kexec: Fix double-free of elf header buffer
ASoC: SOF: Intel: pci-tgl: unblock S5 entry if DMA stop has failed"
nvme: also return I/O command effects from nvme_command_effects
nvmet: use NVME_CMD_EFFECTS_CSUPP instead of open coding it
kunit: alloc_string_stream_fragment error handling bug fix
io_uring: check for valid register opcode earlier
ACPI: video: Don't enable fallback path for creating ACPI backlight by default
drm/amd/display: Report to ACPI video if no panels were found
ACPI: video: Allow GPU drivers to report no panels
nvme: fix multipath crash caused by flush request when blktrace is enabled
io_uring/cancel: re-grab ctx mutex after finishing wait
drm/amdkfd: Fix double release compute pasid
drm/amdkfd: Fix kfd_process_device_init_vm error handling
drm/amdgpu: Fix size validation for non-exclusive domains (v4)
ASoC: SOF: mediatek: initialize panic_info to zero
ASoC: Intel: bytcr_rt5640: Add quirk for the Advantech MICA-071 tablet
9p/client: fix data race on req->status
ASoC: SOF: Revert: "core: unregister clients and machine drivers in .shutdown"
hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
usb: dwc3: xilinx: include linux/gpio/consumer.h
udf: Fix extension of the last extent in the file
caif: fix memory leak in cfctrl_linkup_request()
net/ulp: prevent ULP without clone op from entering the LISTEN status
qed: allow sleep in qed_mcp_trace_dump()
ublk: honor IO_URING_F_NONBLOCK for handling control command
drm/i915/gvt: fix double free bug in split_2MB_gtt_entry
drm/i915: unpin on error in intel_vgpu_shadow_mm_pin()
perf stat: Fix handling of --for-each-cgroup with --bpf-counters to match non 
BPF mode
perf stat: Fix handling of unsupported cgroup events when using BPF counters
perf lock contention: Fix core dump related to not finding the 
"__sched_text_end" symbol on s/390
usb: rndis_host: Secure rndis_query check against int overflow
octeontx2-pf: Fix lmtst ID used in aura free
drivers/net/bonding/bond_3ad: return when there's no aggregator
fs/ntfs3: don't hold ni_lock when calling truncate_setsize()
drm/imx: ipuv3-plane: Fix overlay plane width
perf tools: Fix resources leak in perf_data__open_dir()
drm/virtio: Fix memory leak in virtio_gpu_object_create()
netfilter: ipset: Rework long task execution when adding/deleting entries
netfilter: ipset: fix hash:net,port,net hang with /0 subnet
net: sparx5: Fix reading of the MAC address
vxlan: Fix memory leaks in error path
net: sched: cbq: dont intepret cls results when asked to drop
net: sched: at

[Kernel-packages] [Bug 2003686] [NEW] Lunar update: v6.1.3 upstream stable release

2023-01-23 Thread Paolo Pisati
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.1.3 upstream stable release
   from git://git.kernel.org/


Linux 6.1.3
kcsan: Instrument memcpy/memset/memmove with newer Clang
SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails
tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak
tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak
tpm: acpi: Call acpi_put_table() to fix memory leak
mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING
block: Do not reread partition table on exclusively open device
f2fs: allow to read node block after shutdown
f2fs: should put a page when checking the summary info
mm, compaction: fix fast_isolate_around() to stay within boundaries
md: fix a crash in mempool_free
mfd: mt6360: Add bounds checking in Regmap read/write call-backs
pnode: terminate at peers of source
ALSA: hda/hdmi: Static PCM mapping again with AMD HDMI codecs
ALSA: line6: fix stack overflow in line6_midi_transmit
ALSA: line6: correct midi status byte when receiving data from podxt
ovl: update ->f_iocb_flags when ovl_change_flags() modifies ->f_flags
ovl: Use ovl mounter's fsuid and fsgid in ovl_link()
binfmt: Fix error return code in load_elf_fdpic_binary()
ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+
ACPI: x86: s2idle: Force AMD GUID/_REV 2 on HP Elitebook 865
hfsplus: fix bug causing custom uid and gid being unable to be assigned with 
mount
pstore/zone: Use GFP_ATOMIC to allocate zone buffer
pstore: Properly assign mem_type property
kmsan: include linux/vmalloc.h
kmsan: export kmsan_handle_urb
mm/mempolicy: fix memory leak in set_mempolicy_home_node system call
mm, mremap: fix mremap() expanding vma with addr inside vma
rtmutex: Add acquire semantics for rtmutex lock acquisition slow path
futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error
HID: plantronics: Additional PIDs for double volume key presses quirk
HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint
kprobes: kretprobe events missing on 2-core KVM guest
NFSD: fix use-after-free in __nfs42_ssc_open()
rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe()
powerpc/rtas: avoid scheduling in rtas_os_term()
powerpc/rtas: avoid device tree lookups in rtas_os_term()
iommu/mediatek: Fix crash on isr after kexec()
objtool: Fix SEGFAULT
fs/ntfs3: Fix slab-out-of-bounds in r_page
fs/ntfs3: Delete duplicate condition in ntfs_read_mft()
fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super()
fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init()
fs/ntfs3: Validate index root when initialize NTFS security
phy: sun4i-usb: Add support for the H616 USB PHY
phy: sun4i-usb: Introduce port2 SIDDQ quirk
soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15
fs/ntfs3: Fix slab-out-of-bounds read in run_unpack
fs/ntfs3: Validate resident attribute name
fs/ntfs3: Validate buffer length while parsing index
fs/ntfs3: Validate attribute name offset
fs/ntfs3: Add null pointer check for inode operations
fs/ntfs3: Fix memory leak on ntfs_fill_super() error path
fs/ntfs3: Add null pointer check to attr_load_runs_vcn
fs/ntfs3: Validate data run offset
fs/ntfs3: Add overflow check for attribute size
fs/ntfs3: Validate BOOT record_size
nvmet: don't defer passthrough commands with trivial effects to the workqueue
nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition
ata: ahci: Fix PCS quirk application for suspend
block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
ACPI: video: Fix Apple GMUX backlight detection
ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks
ACPI: resource: do IRQ override on Lenovo 14ALC7
ACPI: resource: do IRQ override on XMG Core 15
nvme-pci: fix page size checks
nvme-pci: fix mempool alloc size
nvme-pci: fix doorbell buffer value endianness
io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups
eventfd: provide a eventfd_signal_mask() helper
eventpoll: add EPOLL_URING_WAKE poll wakeup flag

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: 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/2003686

Title:
  Lunar update: v6.1.3 upstream

[Kernel-packages] [Bug 2003687] [NEW] Lunar update: v6.1.4 upstream stable release

2023-01-23 Thread Paolo Pisati
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.1.4 upstream stable release
   from git://git.kernel.org/


Linux 6.1.4
drm/amd/pm: correct the fan speed retrieving in PWM for some SMU13 asics
drm/amd/pm: bump SMU13.0.0 driver_if header to version 0x34
drm/amd/pm: add missing SMU13.0.7 mm_dpm feature mapping
drm/amd/pm: add missing SMU13.0.0 mm_dpm feature mapping
drm/i915/migrate: Account for the reserved_space
drm/i915: improve the catch-all evict to handle lock contention
drm/amdgpu: make display pinning more flexible (v2)
drm/amdgpu: handle polaris10/11 overlap asics (v2)
drm/amd/display: Add DCN314 display SG Support
drm/i915/ttm: consider CCS for backup objects
ext4: allocate extended attribute value in vmalloc area
ext4: avoid unaccounted block allocation when expanding inode
ext4: initialize quota before expanding inode in setproject ioctl
ext4: fix inode leak in ext4_xattr_inode_create() on an error path
ext4: fix kernel BUG in 'ext4_write_inline_data_end()'
ext4: fix deadlock due to mbcache entry corruption
ext4: avoid BUG_ON when creating xattrs
ext4: fix corrupt backup group descriptors after online resize
ext4: dont return EINVAL from GETFSUUID when reporting UUID length
ext4: fix bad checksum after online resize
ext4: fix error code return to user-space in ext4_get_branch()
ext4: fix corruption when online resizing a 1K bigalloc fs
ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline
ext4: don't fail GETFSUUID when the caller provides a long buffer
ext4: init quota for 'old.inode' in 'ext4_rename'
ext4: fix uninititialized value in 'ext4_evict_inode'
ext4: fix off-by-one errors in fast-commit block filling
ext4: fix unaligned memory access in ext4_fc_reserve_space()
ext4: add missing validation of fast-commit record lengths
ext4: don't set up encryption key during jbd2 transaction
ext4: fix leaking uninitialized memory in fast-commit journal
ext4: disable fast-commit of encrypted dir operations
ext4: don't allow journal inode to have encrypt flag
ext4: fix bug_on in __es_tree_search caused by bad boot loader inode
ext4: check and assert if marking an no_delete evicting inode dirty
ext4: journal_path mount options should follow links
ext4: fix reserved cluster accounting in __es_remove_extent()
ext4: fix bug_on in __es_tree_search caused by bad quota inode
ext4: add helper to check quota inums
ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
ext4: fix undefined behavior in bit shift for ext4_check_flag_values
ext4: fix use-after-free in ext4_orphan_cleanup
fs: ext4: initialize fsdata in pagecache_write()
ext4: correct inconsistent error msg in nojournal mode
ext4: remove trailing newline from ext4_msg() message
ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite 
loop
ext4: silence the warning when evicting inode with dioread_nolock
drm/etnaviv: reap idle mapping if it doesn't match the softpin address
drm/ingenic: Fix missing platform_driver_unregister() call in ingenic_drm_init()
drm/i915/dsi: fix VBT send packet port selection for dual link DSI
drm/etnaviv: move idle mapping reaping into separate function
drm/mgag200: Fix PLL setup for G200_SE_A rev >=4
drm/vmwgfx: Validate the box size for the snooped cursor
drm/connector: send hotplug uevent on connector cleanup
device_cgroup: Roll back to original exceptions after copy failure
parisc: Drop PMD_SHIFT from calculation in pgtable.h
parisc: Drop duplicate kgdb_pdc console
parisc: Add missing FORCE prerequisites in Makefile
parisc: Fix locking in pdc_iodc_print() firmware call
parisc: Drop locking in pdc console code
parisc: led: Fix potential null-ptr-deref in start_task()
remoteproc: imx_rproc: Correct i.MX93 DRAM mapping
remoteproc: core: Do pm_relax when in RPROC_OFFLINE state
remoteproc: imx_dsp_rproc: Add mutex protection for workqueue
hugetlb: really allocate vma lock for all sharable vmas
test_kprobes: Fix implicit declaration error of test_kprobes
iommu/amd: Fix ill-formed ivrs_ioapic, ivrs_hpet and ivrs_acpihid options
iommu/amd: Fix ivrs_acpihid cmdline parsing code
phy: qcom-qmp-combo: fix sc8180x reset
phy: qcom-qmp-combo: fix sdm845 reset
bus: mhi: host: Fix race between channel preparation and M0 event
driver core: Fix bus_type.match() error handling in __driver_attach()
crypto: ccp - Add support for TEE for PCI ID 0x14CA
crypto: n2 - add missing hash statesize
riscv: mm: notify remote harts about mmu cache updates
riscv: stacktrace: Fixup ftrace_graph_ret_addr retp argument
RISC-V: kexec: Fix memory leak of elf header buffer

[Kernel-packages] [Bug 2003689] [NEW] Lunar update: v6.1.6 upstream stable release

2023-01-23 Thread Paolo Pisati
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.1.6 upstream stable release
   from git://git.kernel.org/


Linux 6.1.6
ALSA: hda: cs35l41: Check runtime suspend capability at runtime_idle
ALSA: hda - Enable headset mic on another Dell laptop with ALC3254
ALSA: hda: cs35l41: Don't return -EINVAL from system suspend/resume
ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform
ALSA: hda/hdmi: Add a HP device 0x8715 to force connect list
ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
net: sched: disallow noqueue for qdisc classes
gcc: disable -Warray-bounds for gcc-11 too
Revert "SUNRPC: Use RMW bitops in single-threaded hot paths"
selftests/vm/pkeys: Add a regression test for setting PKRU through ptrace
x86/fpu: Emulate XRSTOR's behavior if the xfeatures PKRU bit is not set
x86/fpu: Allow PKRU to be (once again) written by ptrace.
x86/fpu: Add a pkru argument to copy_uabi_to_xstate()
x86/fpu: Add a pkru argument to copy_uabi_from_kernel_to_xstate().
x86/fpu: Take task_struct* in copy_sigframe_from_user_to_xstate()
parisc: Align parisc MADV_XXX constants with all other architectures

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: 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/2003689

Title:
  Lunar update: v6.1.6 upstream stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v6.1.6 upstream stable release
 from git://git.kernel.org/

  
  Linux 6.1.6
  ALSA: hda: cs35l41: Check runtime suspend capability at runtime_idle
  ALSA: hda - Enable headset mic on another Dell laptop with ALC3254
  ALSA: hda: cs35l41: Don't return -EINVAL from system suspend/resume
  ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform
  ALSA: hda/hdmi: Add a HP device 0x8715 to force connect list
  ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
  net: sched: disallow noqueue for qdisc classes
  gcc: disable -Warray-bounds for gcc-11 too
  Revert "SUNRPC: Use RMW bitops in single-threaded hot paths"
  selftests/vm/pkeys: Add a regression test for setting PKRU through ptrace
  x86/fpu: Emulate XRSTOR's behavior if the xfeatures PKRU bit is not set
  x86/fpu: Allow PKRU to be (once again) written by ptrace.
  x86/fpu: Add a pkru argument to copy_uabi_to_xstate()
  x86/fpu: Add a pkru argument to copy_uabi_from_kernel_to_xstate().
  x86/fpu: Take task_struct* in copy_sigframe_from_user_to_xstate()
  parisc: Align parisc MADV_XXX constants with all other architectures

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