[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

[Kai-Heng Feng]

Please give this kernel a try:
https://people.canonical.com/~khfeng/lp1970074/

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

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

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Something wrong with ata driver in dmesg found:

  [1.980693] kernel: 

  [1.980699] kernel: fbcon: Taking over console
  [1.980703] kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
  [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
  [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 
5.15.0-25-generic #25-Ubuntu
  [1.980716] kernel: Hardware name: System manufacturer System Product 
Name/P5Q3, BIOS 110206/11/2010
  [1.980718] kernel: Call Trace:
  [1.980721] kernel:  
  [1.980723] kernel:  show_stack+0x52/0x58
  [1.980729] kernel:  dump_stack_lvl+0x4a/0x5f
  [1.980734] kernel:  dump_stack+0x10/0x12
  [1.980736] kernel:  ubsan_epilogue+0x9/0x45
  [1.980739] kernel:  __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [1.980742] kernel:  ahci_qc_issue+0x166/0x170 [libahci]
  [1.980748] kernel:  ata_qc_issue+0x135/0x240
  [1.980752] kernel:  ata_exec_internal_sg+0x2c4/0x580
  [1.980754] kernel:  ? vprintk_default+0x1d/0x20
  [1.980759] kernel:  ata_exec_internal+0x67/0xa0
  [1.980762] kernel:  sata_pmp_read+0x8d/0xc0
  [1.980765] kernel:  sata_pmp_read_gscr+0x3c/0x90
  [1.980768] kernel:  sata_pmp_attach+0x8b/0x310
  [1.980771] kernel:  ata_eh_revalidate_and_attach+0x28c/0x4b0
  [1.980775] kernel:  ata_eh_recover+0x6b6/0xb30
  [1.980778] kernel:  ? ahci_do_hardreset+0x180/0x180 [libahci]
  [1.980783] kernel:  ? ahci_stop_engine+0xb0/0xb0 [libahci]
  [1.980787] kernel:  ? ahci_do_softreset+0x290/0x290 [libahci]
  [1.980792] kernel:  ? 
trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
  [1.980795] kernel:  sata_pmp_eh_recover.isra.0+0x214/0x560
  [1.980799] kernel:  sata_pmp_error_handler+0x23/0x40
  [1.980802] kernel:  ahci_error_handler+0x43/0x80 [libahci]
  [1.980806] kernel:  ata_scsi_port_error_handler+0x2b1/0x600
  [1.980810] kernel:  ata_scsi_error+0x9c/0xd0
  [1.980813] kernel:  scsi_error_handler+0xa1/0x180
  [1.980817] kernel:  ? scsi_unjam_host+0x1c0/0x1c0
  [1.980820] kernel:  kthread+0x12a/0x150
  [1.980823] kernel:  ? set_kthread_struct+0x50/0x50
  [1.980826] kernel:  ret_from_fork+0x22/0x30
  [1.980831] kernel:  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene16798 F pulseaudio
   /dev/snd/pcmC0D0p:   eugene16798 F...m pulseaudio
   /dev/snd/controlC1:  eugene16798 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Apr 24 05:13:34 2022
  HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
  InstallationDate: Installed on 2019-04-13 (1106 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   virbr0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic 
root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComput

[Kernel-packages] [Bug 1923284] Re: vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test / vmx_hlt_with_rvi_test fails with timeout on Bionic

[Po-Hsu Lin]

With test suite updated to d8a4f9e5e8 ci: Update the list of tests that
we run in the Fedora Cirrus-CI

This issue still exist on Bionic, even with 10 mins timeout on these 4
tests.

It's worth noting that the vmx_host_state_area test will generate these 
messages in dmesg:
[ 4219.010606] kvm [17175]: vcpu0, guest rIP: 0x4085e4 kvm_set_msr_common: 
MSR_IA32_DEBUGCTLMSR 0x1, nop
[ 4219.059166] kvm [17175]: vcpu0, guest rIP: 0x40b099 kvm_set_msr_common: 
MSR_IA32_DEBUGCTLMSR 0x3, nop
[ 4219.109307] kvm [17175]: vcpu0, guest rIP: 0x410453 kvm_set_msr_common: 
MSR_IA32_DEBUGCTLMSR 0x1, nop
[ 4219.153933] kvm [17175]: vcpu0, guest rIP: 0x40b13a kvm_set_msr_common: 
MSR_IA32_DEBUGCTLMSR 0x3, nop
[ 5014.736843] *** Guest State ***
[ 5014.753543] CR0: actual=0x80010031, shadow=0x80010031, 
gh_mask=fff7
[ 5014.798851] CR4: actual=0x2060, shadow=0x2020, 
gh_mask=e871
[ 5014.839351] CR3 = 0x01007000
[ 5014.856094] RSP = 0x0053a2f8  RIP = 0x004079a5
[ 5014.883133] RFLAGS=0x0002 DR7 = 0x0400
[ 5014.910111] Sysenter RSP= CS:RIP=0008:004001e4
[ 5014.940072] CS:   sel=0x0008, attr=0x0a09b, limit=0x, 
base=0x
[ 5014.977109] DS:   sel=0x0010, attr=0x0c093, limit=0x, 
base=0x
[ 5015.012935] SS:   sel=0x0010, attr=0x0c093, limit=0x, 
base=0x
[ 5015.048569] ES:   sel=0x0010, attr=0x0c093, limit=0x, 
base=0x
[ 5015.084293] FS:   sel=0x0010, attr=0x0c093, limit=0x, 
base=0x
[ 5015.120186] GS:   sel=0x0010, attr=0x0c093, limit=0x, 
base=0x00539590
[ 5015.155731] GDTR:   limit=0x, 
base=0x0042af80
[ 5015.191524] LDTR: sel=0x, attr=0x1, limit=0x, 
base=0x
[ 5015.227181] IDTR:   limit=0x, 
base=0x0054af00
[ 5015.263048] TR:   sel=0x0080, attr=0x0008b, limit=0x0067, 
base=0x00544760
[ 5015.303739] EFER = 0x0500  PAT = 0x0007040600070406
[ 5015.332411] DebugCtl = 0x  DebugExceptions = 
0x
[ 5015.366642] Interruptibility =   ActivityState = 
[ 5015.394930] InterruptStatus = 
[ 5015.410633] *** Host State ***
[ 5015.424791] RIP = 0xc07b454c  RSP = 0xbfc98a3c7c98
[ 5015.451433] CS=0010 SS=0018 DS= ES= FS= GS= TR=0040
[ 5015.480408] FSBase=7f571eaa4700 GSBase=9c02df48 
TRBase=fe1ed000
[ 5015.515285] GDTBase=fe1eb000 IDTBase=fe00
[ 5015.541569] CR0=80050033 CR3=00084e7d2002 CR4=003626e0
[ 5015.572969] Sysenter RSP=fe1ed000 CS:RIP=0010:b9a01b00
[ 5015.602954] EFER = 0x0d01  PAT = 0x0407050600070106
[ 5015.630027] *** Control State ***
[ 5015.645470] PinBased=00bf CPUBased=96a069fe SecondaryExec=000277eb
[ 5015.675481] EntryControls=d3ff ExitControls=002fefff
[ 5015.699919] ExceptionBitmap=00060042 PFECmask= PFECmatch=
[ 5015.731131] VMEntry: intr_info= errcode= ilen=
[ 5015.761253] VMExit: intr_info= errcode= ilen=0003
[ 5015.793758] reason=8021 qualification=
[ 5015.824873] IDTVectoring: info= errcode=
[ 5015.849472] TSC Offset = 0xf3dd6e735c09
[ 5015.868763] TPR Threshold = 0x00
[ 5015.883732] PostedIntrVec = 0xf2
[ 5015.898665] EPT pointer = 0x000852b0c05e
[ 5015.917916] PLE Gap=0080 Window=1000
[ 5015.937563] Virtual processor ID = 0x0001


** Tags added: sru-20220919

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

Title:
  vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test /
  vmx_hlt_with_rvi_test  fails with timeout on Bionic

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  vmx_host_state_area / vmx_intr_window_test / vmx_nmi_window_test
  fails with timeout on Bionic 4.15.0-141.145  host rizzo

  this failed on the previous version of bionic   4.15.0-140.144 as
  well, so not a regression.

  
  vmx_host_state_area has an error before giving timeout:

  04/10 01:29:18 DEBUG| utils:0153| [stderr] KVM: entry failed, hardware 
error 0x8021
  04/10 01:29:18 DEBUG| utils:0153| [stderr] 
  04/10 01:29:18 DEBUG| utils:0153| [stderr] If you're running a guest on 
an Intel machine without unrestricted mode
  04/10 01:29:18 DEBUG| utils:0153| [stderr] support, the failure can be 
most likely due to the guest entering an invalid
  04/10 01:29:18 DEBUG| utils:0153| [stderr] state for Intel VT. For 
example, the guest maybe running in big real mode
  04/10 01:29:18 DEBUG| utils:0153

[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen

[Daniel van Vugt]

I see the same crash as comment #7, at least on the i7-12700.

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th
  gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1991774] Re: Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes

[ChengEn, Du]

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => ChengEn, Du (chengendu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => ChengEn, Du (chengendu)

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Tags added: bionic sts

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

Title:
  Memory leak while using NFQUEUE to delegate the decision on TCP
  packets to userspace processes

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]

  Environment: v4.15.0-177-generic Xenial ESM

  Using NFQUEUE to delegate the decision on TCP packets to userspace processes 
will cause memory leak.
  The symptom is that TCP slab objects will accumulate and eventually cause OOM.

  [Fix]

  There is a discrepancy between backport and upstream commit.

  [Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 9eed51e920e8..980daa6e1e3a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct 
nf_queue_handler *qh);
   void nf_unregister_queue_handler(void);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_free(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 5ab0680db445..e39549c55945 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct 
nf_queue_entry *entry)
   }

   /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
   {
    struct nf_hook_state *state = &entry->state;

  + if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
  + return false;
  +
    dev_hold(state->in);
    dev_hold(state->out);
  - if (state->sk)
  - sock_hold(state->sk);

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
    dev_hold(entry->physin);
    dev_hold(entry->physout);
   #endif
  + return true;
   }
   EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);

  @@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
  struct nf_hook_state *state,

    __nf_queue_entry_init_physdevs(entry);

  - nf_queue_entry_get_refs(entry);
  + if (!nf_queue_entry_get_refs(entry)) {
  + kfree(entry);
  + return -ENOTCONN;
  + }

    switch (entry->state.pf) {
    case AF_INET:
  diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
  index ea2d9c2a44cf..64a6acb6aeae 100644
  --- a/net/netfilter/nfnetlink_queue.c
  +++ b/net/netfilter/nfnetlink_queue.c
  @@ -710,9 +710,15 @@ static struct nf_queue_entry *
   nf_queue_entry_dup(struct nf_queue_entry *e)
   {
    struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
  - if (entry)
  - nf_queue_entry_get_refs(entry);
  - return entry;
  +
  + if (!entry)
  + return NULL;
  +
  + if (nf_queue_entry_get_refs(entry))
  + return entry;
  +
  + kfree(entry);
  + return NULL;
   }

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)

  [Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 814058d0f167..f38cc6092c5a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const 
struct nf_queue_handler *q
   void nf_unregister_queue_handler(struct net *net);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_release_refs(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 59340b3ef7ef..dbc45165c533 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -80,10 +80,13 @@ void nf_queue_entry_release_refs(struct nf_queue_entry 
*entry)
   EXPORT_SYMBOL_GPL(nf_queue_entry_release_refs);

   /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_e

[Kernel-packages] [Bug 1991774] Re: Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes

[ChengEn, Du]

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

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

Title:
  Memory leak while using NFQUEUE to delegate the decision on TCP
  packets to userspace processes

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New

Bug description:
  [Impact]

  Environment: v4.15.0-177-generic Xenial ESM

  Using NFQUEUE to delegate the decision on TCP packets to userspace processes 
will cause memory leak.
  The symptom is that TCP slab objects will accumulate and eventually cause OOM.

  [Fix]

  There is a discrepancy between backport and upstream commit.

  [Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 9eed51e920e8..980daa6e1e3a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct 
nf_queue_handler *qh);
   void nf_unregister_queue_handler(void);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_free(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 5ab0680db445..e39549c55945 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct 
nf_queue_entry *entry)
   }

   /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
   {
    struct nf_hook_state *state = &entry->state;

  + if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
  + return false;
  +
    dev_hold(state->in);
    dev_hold(state->out);
  - if (state->sk)
  - sock_hold(state->sk);

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
    dev_hold(entry->physin);
    dev_hold(entry->physout);
   #endif
  + return true;
   }
   EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);

  @@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
  struct nf_hook_state *state,

    __nf_queue_entry_init_physdevs(entry);

  - nf_queue_entry_get_refs(entry);
  + if (!nf_queue_entry_get_refs(entry)) {
  + kfree(entry);
  + return -ENOTCONN;
  + }

    switch (entry->state.pf) {
    case AF_INET:
  diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
  index ea2d9c2a44cf..64a6acb6aeae 100644
  --- a/net/netfilter/nfnetlink_queue.c
  +++ b/net/netfilter/nfnetlink_queue.c
  @@ -710,9 +710,15 @@ static struct nf_queue_entry *
   nf_queue_entry_dup(struct nf_queue_entry *e)
   {
    struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
  - if (entry)
  - nf_queue_entry_get_refs(entry);
  - return entry;
  +
  + if (!entry)
  + return NULL;
  +
  + if (nf_queue_entry_get_refs(entry))
  + return entry;
  +
  + kfree(entry);
  + return NULL;
   }

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)

  [Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 814058d0f167..f38cc6092c5a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const 
struct nf_queue_handler *q
   void nf_unregister_queue_handler(struct net *net);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_release_refs(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 59340b3ef7ef..dbc45165c533 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -80,10 +80,13 @@ void nf_queue_entry_release_refs(struct nf_queue_entry 
*entry)
   EXPORT_SYMBOL_GPL(nf_queue_entry_release_refs);

   /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
   {
    struct nf_hook_state *state = &entry->state;

  + if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
  + return false;
  +
    if (state->in)
     dev_hold(state->in);
    if (state->out)
  @@ -102,6 +105,7 @@ void nf_queue_

[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Dan Bungert]

** Tags added: foundations-todo

** Changed in: grub2-signed (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: grub2-signed (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  New

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+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 1988838] Re: No console output on kinetic pi server images

[William Wilson]

Marking as Fix Released. During ubuntu-image testing I noticed this is
resolved with the latest kernel.

** Changed in: linux-raspi (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  No console output on kinetic pi server images

Status in Release Notes for Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released

Bug description:
  On kinetic pi server daily images with the 5.19 linux-raspi kernel
  (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/current/) there is no console output over HDMI. The
  "rainbow" boot screen appears as usual, but then remains while the
  system continues to boot and never switches to display the console.

  The system does still boot successfully, I can SSH into it, and
  console over serial still works but not over HDMI (testing on a Pi 3,
  and two revisions of the Pi 4). Adding either kms overlay
  (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this.
  Is it simply the case that future kernels are going to require a KMS
  overlay of some flavour or other to operate the console?

  If so, that's probably a good thing to some degree (it'll remove
  another difference between the pi server and desktop images), but
  ubuntu-release-upgrader will need to work to enforce that in the boot
  configuration for upgraders (and I'll need to tweak the gadget to
  ensure it's always included from now on).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988838/+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 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

[Jeffrey Baker]

This seems to be the relevant utterance of the kernel that fails to
boot:

i915 :00:02.0: vgaarb: deactivate vga console
BUG: kernel NULL pointer dereference, address: 002e
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 0 P4D 0 
Oops: 0002 [#1] PREEMPT SMP NOPTI
CPU: 14 PID: 547 Comm: systemd-udevd Not tainted 5.19.0-18-generic #18-Ubuntu
Hardware name: ASUS System Product Name/PRIME Z690-P WIFI D4, BIOS 1203 
03/04/2022
RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915]
Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d 
b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff  46 2e 00 66 41 89 85 
e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08
RSP: 0018:b11d815df7a0 EFLAGS: 00010206
RAX: 0301 RBX: 0003 RCX: 0001
RDX:  RSI:  RDI: 0001
RBP: b11d815df890 R08:  R09: 
R10: 0002 R11: 0001 R12: 0100
R13: 94894d8b00f0 R14: 0005 R15: 94894d8b
FS:  7f631e7628c0() GS:94909f58() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 002e CR3: 000108d5c004 CR4: 00770ee0
PKRU: 5554
Call Trace:
 
 ? __intel_wait_for_register_fw+0xf5/0x200 [i915]
Bluetooth: hci0: Found device firmware: intel/ibt-1040-4150.sfi
 intel_bw_init_hw+0xe5/0x140 [i915]
Bluetooth: hci0: Boot Address: 0x100800
Bluetooth: hci0: Firmware Version: 129-28.22
 i915_driver_hw_probe+0x2cc/0x370 [i915]
 i915_driver_probe+0x19b/0x490 [i915]
 ? drm_privacy_screen_get+0x16d/0x190 [drm]
 ? acpi_dev_found+0x64/0x80
 i915_pci_probe+0x56/0x150 [i915]
 local_pci_probe+0x44/0x90
 pci_call_probe+0x55/0x190
 pci_device_probe+0x84/0x120
 really_probe+0x1dc/0x3b0
 __driver_probe_device+0x12c/0x1b0
 driver_probe_device+0x24/0xd0
 __driver_attach+0xe0/0x210
 ? __device_attach_driver+0x130/0x130
 bus_for_each_dev+0x8d/0xe0
 driver_attach+0x1e/0x30
 bus_add_driver+0x187/0x230
 driver_register+0x8f/0x100
 __pci_register_driver+0x62/0x70
 i915_pci_register_driver+0x23/0x30 [i915]
 i915_init+0x3b/0xf2 [i915]
 ? 0xc2b93000
 do_one_initcall+0x5b/0x240
 do_init_module+0x50/0x210
 load_module+0xb7d/0xcd0
 __do_sys_finit_module+0xc4/0x140
 ? __do_sys_finit_module+0xc4/0x140
 __x64_sys_finit_module+0x18/0x30
 do_syscall_64+0x58/0x90
 ? exit_to_user_mode_prepare+0x30/0xb0
 ? syscall_exit_to_user_mode+0x26/0x50
 ? __x64_sys_newfstatat+0x1c/0x30
 ? do_syscall_64+0x67/0x90
 ? exit_to_user_mode_prepare+0x30/0xb0
 ? syscall_exit_to_user_mode+0x26/0x50
 ? __x64_sys_newfstatat+0x1c/0x30
 ? do_syscall_64+0x67/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f631e916a1d
Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 
c3 48 8b 0d b3 f3 0d 00 f7 d8 64 89 01 48
RSP: 002b:7fff877ffce8 EFLAGS: 0246 ORIG_RAX: 0139
RAX: ffda RBX: 55b85b1c15c0 RCX: 7f631e916a1d
RDX:  RSI: 7f631eb75458 RDI: 0017
RBP: 7f631eb75458 R08:  R09: 7fff877ffe10
R10: 0017 R11: 0246 R12: 0002
R13: 55b85b1cbb30 R14:  R15: 55b85b1c7ef0
 
Modules linked in: snd_seq_midi_event btusb fjes(+) btrtl i915(+) snd_rawmidi 
libarc4 kvm btbcm crct10dif_pclmul snd_seq ghash_clmulni_intel btintel 
drm_buddy aesni_intel ttm crypto_simd btmtk snd_seq
1 ecdh_generic soundcore ecc mei drm_kms_helper intel_vsec fb_sys_fops 
syscopyarea sysfillrect sysimgblt acpi_pad mac_hid acpi_tad sch_fq nct6775 
nct6775_core hwmon_vid coretemp msr parport_pc ppdev l
l i2c_algo_bit spi_intel_pci nvme i2c_i801 intel_lpss_pci dca spi_intel ahci 
i2c_smbus xhci_pci intel_lpss nvme_core libahci
 idma64 vmd xhci_pci_renesas wmi video pinctrl_alderlake
CR2: 002e
---[ end trace  ]---
RIP: 0010:tgl_get_bw_info.isra.0+0x473/0x6c0 [i915]
Code: fa 0b 0f 86 e7 00 00 00 41 39 c2 0f 8e 77 fc ff ff e9 3a 5c 0f 00 49 8d 
b5 e4 21 00 00 0f b7 85 30 ff ff ff 8b 8d 4c ff ff ff  46 2e 00 66 41 89 85 
e0 21 00 00 85 c9 0f 85 f2 fd ff ff e9 08
RSP: 0018:b11d815df7a0 EFLAGS: 00010206
RAX: 0301 RBX: 0003 RCX: 0001
RDX:  RSI:  RDI: 0001
RBP: b11d815df890 R08:  R09: 
R10: 0002 R11: 0001 R12: 0100
R13: 94894d8b00f0 R14: 0005 R15: 94894d8b
FS:  7f631e7628c0() GS:94909f58() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 002e CR3: 000108d5c004 CR4: 00770ee0
PKRU: 5554

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
h

[Kernel-packages] [Bug 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

[Jose Ogando Justo]

Proposed fix sent to the mailing list:

https://lists.ubuntu.com/archives/kernel-team/2022-October/133711.html


** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Description changed:

  Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu
  
  This is a new test case from bug 1988809
  
  Test failed with:
   Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
     INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: fib_nexthop_nongw.sh
   # Object "nexthop" is unknown, try "ip help".
   # Error: either "to" is duplicate, or "nhid" is a garbage.
   # TEST: nexthop: get route with nexthop without gw[FAIL]
   # TEST: nexthop: ping through nexthop without gw  [FAIL]
   not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1
+ 
+ --
+ 
+ [Impact]
+ 
+ When running kselftests on Bionic with a 5.4 kernel, it would
+ fail because of no nexthop capability.
+ 
+ [Fix]
+ 
+ We query the ip command help to know whether it is implemented
+ or not, and we skip or execute the test accordingly
+ 
+ [Test Plan]
+ 
+ Running the test script directly in Bionic will throw a Skip,
+ while running it in Focal will throw the test result.
+ 
+ [Where problems could ocurr]
+ 
+ The regression potential for this is low.
+ 
+ [Other Info]
+ 
+ None

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

Title:
  fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu

  This is a new test case from bug 1988809

  Test failed with:
   Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
     INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: fib_nexthop_nongw.sh
   # Object "nexthop" is unknown, try "ip help".
   # Error: either "to" is duplicate, or "nhid" is a garbage.
   # TEST: nexthop: get route with nexthop without gw[FAIL]
   # TEST: nexthop: ping through nexthop without gw  [FAIL]
   not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1

  --

  [Impact]

  When running kselftests on Bionic with a 5.4 kernel, it would
  fail because of no nexthop capability.

  [Fix]

  We query the ip command help to know whether it is implemented
  or not, and we skip or execute the test accordingly

  [Test Plan]

  Running the test script directly in Bionic will throw a Skip,
  while running it in Focal will throw the test result.

  [Where problems could ocurr]

  The regression potential for this is low.

  [Other Info]

  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+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 1991841] [NEW] Jammy update: v5.15.67 upstream stable release

[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:

   v5.15.67 upstream stable release
   from git://git.kernel.org/

kbuild: fix up permissions on scripts/pahole-flags.sh
Linux 5.15.67
UBUNTU: Upstream stable to v5.15.67

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

** Description changed:

+ SRU Justification
  
- 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:
  
- 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:
+    v5.15.67 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.67 upstream stable release
-from git://git.kernel.org/
+ kbuild: fix up permissions on scripts/pahole-flags.sh
+ Linux 5.15.67
+ UBUNTU: Upstream stable to v5.15.67

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Jammy update: v5.15.67 upstream stable release

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

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:

     v5.15.67 upstream stable release
     from git://git.kernel.org/

  kbuild: fix up permissions on scripts/pahole-flags.sh
  Linux 5.15.67
  UBUNTU: Upstream stable to v5.15.67

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991841/+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 1991840] [NEW] Jammy update: v5.15.66 upstream stable release

[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:

   v5.15.66 upstream stable release
   from git://git.kernel.org/

drm/msm/dsi: fix the inconsistent indenting
drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
drm/msm/dsi: Fix number of regulators for SDM660
platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
iio: adc: mcp3911: make use of the sign bit
skmsg: Fix wrong last sg check in sk_msg_recvmsg()
bpf: Restrict bpf_sys_bpf to CAP_PERFMON
bpf, cgroup: Fix kernel BUG in purge_effective_progs
ieee802154/adf7242: defer destroy_workqueue call
drm/i915/backlight: extract backlight code to a separate file
drm/i915/display: avoid warnings when registering dual panel backlight
ALSA: hda: intel-nhlt: remove use of __func__ in dev_dbg
ALSA: hda: intel-nhlt: Correct the handling of fmt_config flexible array
wifi: cfg80211: debugfs: fix return type in ht40allow_map_read()
Revert "xhci: turn off port power in shutdown"
net: sparx5: fix handling uneven length packets in manual extraction
net: smsc911x: Stop and start PHY during suspend and resume
openvswitch: fix memory leak at failed datapath creation
net: dsa: xrs700x: Use irqsave variant for u64 stats update
net: sched: tbf: don't call qdisc_put() while holding tree lock
net/sched: fix netdevice reference leaks in attach_default_qdiscs()
ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler
mlxbf_gige: compute MDIO period based on i1clk
kcm: fix strp_init() order and cleanup
sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
tcp: annotate data-race around challenge_timestamp
Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb"
net/smc: Remove redundant refcount increase
soundwire: qcom: fix device status array range
serial: fsl_lpuart: RS485 RTS polariy is inverse
staging: rtl8712: fix use after free bugs
staging: r8188eu: add firmware dependency
powerpc: align syscall table for ppc32
vt: Clear selection before changing the font
musb: fix USB_MUSB_TUSB6010 dependency
tty: serial: lpuart: disable flow control while waiting for the transmit engine 
to complete
Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
iio: ad7292: Prevent regulator double disable
iio: adc: mcp3911: use correct formula for AD conversion
misc: fastrpc: fix memory corruption on probe
misc: fastrpc: fix memory corruption on open
USB: serial: ftdi_sio: add Omron CS1W-CIF31 device id
mmc: core: Fix UHS-I SD 1.8V workaround branch
mmc: core: Fix inconsistent sd3_bus_mode at UHS-I SD voltage switch failure
binder: fix UAF of ref->proc caused by race condition
binder: fix alloc->vma_vm_mm null-ptr dereference
cifs: fix small mempool leak in SMB2_negotiate()
KVM: VMX: Heed the 'msr' argument in msr_write_intercepted()
drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops
Revert "clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops"
clk: core: Fix runtime PM sequence in clk_core_unprepare()
Input: rk805-pwrkey - fix module autoloading
clk: bcm: rpi: Fix error handling of raspberrypi_fw_get_rate
clk: bcm: rpi: Use correct order for the parameters of devm_kcalloc()
clk: bcm: rpi: Prevent out-of-bounds access
clk: bcm: rpi: Add missing newline
hwmon: (gpio-fan) Fix array out of bounds access
gpio: pca953x: Add mutex_lock for regcache sync in PM
KVM: x86: Mask off unsupported and unknown bits of IA32_ARCH_CAPABILITIES
xen/grants: prevent integer overflow in gnttab_dma_alloc_pages()
mm: pagewalk: Fix race between unmap and page walker
xen-blkback: Advertise feature-persistent as user requested
xen-blkfront: Advertise feature-persistent as user requested
xen-blkfront: Cache feature_persistent value before advertisement
thunderbolt: Use the actual buffer in tb_async_error()
usb: dwc3: pci: Add support for Intel Raptor Lake
media: mceusb: Use new usb_control_msg_*() routines
xhci: Add grace period after xHC start to prevent premature runtime suspend.
USB: serial: cp210x: add Decagon UCA device id
USB: serial: option: add support for OPPO R11 diag port
USB: serial: option: add Quectel EM060K modem
USB: serial: option: add support for Cinterion MV32-WA/WB RmNet mode
usb: typec: altmodes/displayport: correct pin assignment for UFP receptacles
usb: typec: intel_pmc_mux: Add new ACPI ID for Meteor Lake IOM device
usb: typec: tcpm: Return ENOTSUPP for power supply prop writes
usb: dwc2: fix wrong order of phy_power_on and phy_init
usb: cdns3: fix issue with rearming ISO OUT endpoint
usb: cdns3: fix inc

[Kernel-packages] [Bug 1991833] Re: VRF Kernel Module Does Not Exist

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  VRF Kernel Module Does Not Exist

Status in linux-aws package in Ubuntu:
  New

Bug description:
  On a standard Ubuntu 22.04 LTS image, the vrf module exists and can be
  loaded. The AMI image ami-08c40ec9ead489470 in AWS us-east-1 (and all
  other regions that I have tested) does not have this kernel module
  built therefore I cannot create vrf network devices.

  Usually I could run `ip link add vrf-mgmt type vrf table 10` and
  create the VRF device, but instead get an error `Error: Unknown device
  type.`.

  
  Trying to load the module:

  # modprobe vrf
  modprobe: FATAL: Module vrf not found in directory 
/lib/modules/5.15.0-1020-aws

  
  # Boot config
  # grep VRF /boot/config-5.15.0-1020-aws 
  CONFIG_NET_VRF=m

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-aws-headers-5.15.0-1020 5.15.0-1020.24
  ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Oct  5 18:41:11 2022
  Ec2AMI: ami-08c40ec9ead489470
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1a
  Ec2InstanceType: t3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1991833/+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 1991833] [NEW] VRF Kernel Module Does Not Exist

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On a standard Ubuntu 22.04 LTS image, the vrf module exists and can be
loaded. The AMI image ami-08c40ec9ead489470 in AWS us-east-1 (and all
other regions that I have tested) does not have this kernel module built
therefore I cannot create vrf network devices.

Usually I could run `ip link add vrf-mgmt type vrf table 10` and create
the VRF device, but instead get an error `Error: Unknown device type.`.


Trying to load the module:

# modprobe vrf
modprobe: FATAL: Module vrf not found in directory /lib/modules/5.15.0-1020-aws


# Boot config
# grep VRF /boot/config-5.15.0-1020-aws 
CONFIG_NET_VRF=m

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-aws-headers-5.15.0-1020 5.15.0-1020.24
ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53
Uname: Linux 5.15.0-1020-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Oct  5 18:41:11 2022
Ec2AMI: ami-08c40ec9ead489470
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: t3.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images jammy
-- 
VRF Kernel Module Does Not Exist
https://bugs.launchpad.net/bugs/1991833
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-aws 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 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

[Jeffrey Baker]

I'm also seeing failure to boot with -18 (-15 works) and I do not have
nvidia graphics, I have i915.

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

Title:
  Failure to boot with linux-image-5.19.0-18-generic

Status in linux-signed package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  Since the last kernel update today my system stops in the middle of the boot 
process and does not reach KDE.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-05-26 (495 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm 
nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G 
hugepages=4
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  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 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic uec-images
  Uname: Linux 5.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/24/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4204
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1991703/+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 1991831] [NEW] Jammy update: v5.15.65 upstream stable release

[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:

   v5.15.65 upstream stable release
   from git://git.kernel.org/

mm: Force TLB flush for PFNMAP mappings before unlink_file_vma()
drm/bridge: Add stubs for devm_drm_of_get_bridge when OF is disabled
ACPI: thermal: drop an always true check
drm/vc4: hdmi: Rework power up
drm/vc4: hdmi: Depends on CONFIG_PM
firmware: tegra: bpmp: Do only aligned access to IPC memory area
crypto: lib - remove unneeded selection of XOR_BLOCKS
Drivers: hv: balloon: Support status report for larger page sizes
mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2441009
arm64: errata: Add Cortex-A510 to the repeat tlbi list
io_uring: Remove unused function req_ref_put
kbuild: Fix include path in scripts/Makefile.modpost
Bluetooth: L2CAP: Fix build errors in some archs
HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
udmabuf: Set the DMA mask for the udmabuf device (v2)
media: pvrusb2: fix memory leak in pvr_probe
HID: hidraw: fix memory leak in hidraw_release()
net: fix refcount bug in sk_psock_get (2)
fbdev: fb_pm2fb: Avoid potential divide by zero error
ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead
bpf: Don't redirect packets with invalid pkt_len
mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
ALSA: usb-audio: Add quirk for LH Labs Geek Out HD Audio 1V5
HID: add Lenovo Yoga C630 battery quirk
HID: AMD_SFH: Add a DMI quirk entry for Chromebooks
HID: asus: ROG NKey: Ignore portion of 0x5a report
HID: thrustmaster: Add sparco wheel and fix array length
drm/i915/gt: Skip TLB invalidations once wedged
mmc: mtk-sd: Clear interrupts when cqe off/disable
mmc: sdhci-of-dwcmshc: add reset call back for rockchip Socs
mmc: sdhci-of-dwcmshc: rename rk3568 to rk35xx
mmc: sdhci-of-dwcmshc: Re-enable support for the BlueField-3 SoC
btrfs: remove root argument from btrfs_unlink_inode()
btrfs: remove no longer needed logic for replaying directory deletes
btrfs: add and use helper for unlinking inode during log replay
btrfs: fix warning during log replay when bumping inode link count
fs/ntfs3: Fix work with fragmented xattr
ASoC: sh: rz-ssi: Improve error handling in rz_ssi_probe() error path
drm/amd/display: Avoid MPC infinite loop
drm/amd/display: Fix HDMI VSIF V3 incorrect issue
drm/amd/display: For stereo keep "FLIP_ANY_FRAME"
drm/amd/display: clear optc underflow before turn off odm clock
ksmbd: return STATUS_BAD_NETWORK_NAME error status if share is not configured
neigh: fix possible DoS due to net iface start/stop loop
s390/hypfs: avoid error message under KVM
ksmbd: don't remove dos attribute xattr on O_TRUNC open
drm/amd/pm: add missing ->fini_microcode interface for Sienna Cichlid
drm/amd/display: Fix pixel clock programming
drm/amdgpu: Increase tlb flush timeout for sriov
drm/amd/display: avoid doing vm_init multiple time
netfilter: conntrack: NF_CONNTRACK_PROCFS should no longer default to y
testing: selftests: nft_flowtable.sh: use random netns names
btrfs: move lockdep class helpers to locking.c
btrfs: fix lockdep splat with reloc root extent buffers
btrfs: tree-checker: check for overlapping extent items
kprobes: don't call disarm_kprobe() for disabled kprobes
btrfs: fix space cache corruption and potential double allocations
android: binder: fix lockdep check on clearing vma
net/af_packet: check len when min_header_len equals to 0
net: neigh: don't call kfree_skb() under spin_lock_irqsave()
Linux 5.15.65
UBUNTU: Upstream stable to v5.15.65

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process fo

[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

[Jeff Lane ]

** Description changed:

  [IMPACT/Justification]
- There are numerous bug fixes included in the more recent version of lpfc that 
Broadcom has asked to pull into Jammy and Kinetic.  These all are limited to 
the lpfc driver itself, no patches to core code are requested.
+ There are numerous bug fixes included in the more recent version of lpfc That 
Broadcom has asked to pull into Jammy and Kinetic to better support customers 
in the field who are using the GA kernel and cant or wont move to the HWE 
kernels.  These all are limited to the lpfc driver itself, no patches to core 
code are requested.
  
  [FIX]
- 
- A few of these were already landed in Jammy, and all but 6 (ones landed
- in 6.0 upstream) were already in Kinetic.
+ A few of these were already landed in Jammy, and all but 6 (ones landed in 
6.0 upstream) were already in Kinetic.
  
  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
  c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
  92bd903da12b scsi: lpfc: Fix additional reference counting in 
lpfc_bsg_rport_els()
  db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
  646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
  3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in 
lpfc_sli_prep_wqe()
  a346f28ad231 scsi: lpfc: Remove unneeded variable
  66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
  4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
  fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
  f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
  ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
  d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
  1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post 
RSCN completion
  6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in 
Fabric topology
  6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
  c364c453d30a scsi: lpfc: Revise FDMI reporting of supported port speed for 
trunk groups
  d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O 

[Kernel-packages] [Bug 1990945] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.6 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 linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1990945

Title:
  i915: Add GuC v70.1.1 for all platforms

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]  
 

 
  Intel Quake N i915 for kernel 5.19+ will need v70.1.1 firmware files. 
 

 
  [Fix] 
 

 
  Upstream commit ab0d8c137d42 ("i915: Add GuC v70.1.1 for all platforms"). 
 

 
  [Test Case]   
 

 
  With v69 firmware, kernel prints: 
 

 
kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin  
 
is recommended, but only i915/adlp_guc_69.0.3.bin was found

 
  New firmware would silence this line. 
 

 
  [Where problems could occur]  
 

 
  Firmware update, little knowledge to what was actually fixed, and the 
 
  actual revision being used is guarded by kernel.   

 
  [Other Info]  
 

 
  This update already exists in Kinetic, so only Jammy is nominated.

  == original bug report ==

  Quake N i915 for kernel 5.19+ will need the firmware files listed in the 
following mail post:
  https://www.spinics.net/lists/intel-gfx/msg295995.html

  We are targeting Quake N to release with 6.0-oem kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990945/+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 1989144] Re: unprivileged users may trigger page cache invalidation WARN

[Luke Nowakowski-Krijger]

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

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

Title:
  unprivileged users may trigger page cache invalidation WARN

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Unprivileged users may trigger a page cache invalidation failure when doing 
parallel direct I/O and buffered I/O. On some kernels, that may lead to a WARN.

  [   22.415082] WARNING: CPU: 3 PID: 3404 at 
/build/linux-GtMq7R/linux-4.15.0/fs/iomap.c:903 iomap_dio_actor+0xbd/0x460
  [   22.415083] Modules linked in: xfs isofs kvm_intel kvm irqbypass joydev 
input_leds serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
psmouse ahci libahci virtio_blk virtio_net
  [   22.415099] CPU: 3 PID: 3404 Comm: xfs_io Not tainted 4.15.0-192-generic 
#203-Ubuntu
  [   22.415100] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.15.0-1 04/01/2014
  [   22.415103] RIP: 0010:iomap_dio_actor+0xbd/0x460
  [   22.415104] RSP: 0018:b7c782fe7bf0 EFLAGS: 00010202
  [   22.415104] RAX: 0002 RBX:  RCX: 
0009
  [   22.415105] RDX: 01ff RSI:  RDI: 
b7c782fe7e20
  [   22.415105] RBP: b7c782fe7c68 R08: b7c782fe7c88 R09: 
9bbc9f48fba0
  [   22.415106] R10: 0001 R11:  R12: 
0009
  [   22.415106] R13: 9bbc9f48fba0 R14: b7c782fe7c88 R15: 
1000
  [   22.415107] FS:  7f2b802ed700() GS:9bbcbfd8() 
knlGS:
  [   22.415107] CS:  0010 DS:  ES:  CR0: 80050033
  [   22.415108] CR2: 01639000 CR3: 1e6b0003 CR4: 
00760ee0
  [   22.415110] PKRU: 5554
  [   22.415110] Call Trace:
  [   22.415122]  ? iomap_dio_zero+0x130/0x130
  [   22.415123]  iomap_apply+0xa5/0x120
  [   22.415124]  ? iomap_dio_zero+0x130/0x130
  [   22.415125]  iomap_dio_rw+0x2f3/0x430
  [   22.415126]  ? iomap_dio_zero+0x130/0x130
  [   22.415148]  xfs_file_dio_aio_read+0x68/0xf0 [xfs]
  [   22.415157]  ? xfs_file_dio_aio_read+0x68/0xf0 [xfs]
  [   22.415165]  xfs_file_read_iter+0xbf/0xe0 [xfs]
  [   22.415170]  new_sync_read+0xe4/0x130
  [   22.415171]  __vfs_read+0x29/0x40
  [   22.415172]  vfs_read+0x8e/0x130
  [   22.415173]  SyS_pread64+0x95/0xb0
  [   22.415176]  do_syscall_64+0x73/0x130
  [   22.415183]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
  [   22.415184] RIP: 0033:0x7f2b7fbc0b73
  [   22.415185] RSP: 002b:7ffc134e1a58 EFLAGS: 0246 ORIG_RAX: 
0011
  [   22.415186] RAX: ffda RBX:  RCX: 
7f2b7fbc0b73
  [   22.415186] RDX: 1000 RSI: 01639000 RDI: 
0003
  [   22.415186] RBP:  R08:  R09: 

  [   22.415187] R10:  R11: 0246 R12: 
7ffc134e1b00
  [   22.415187] R13: 0002 R14:  R15: 

  [   22.415188] Code: 21 d0 48 89 45 a0 0f 85 aa 03 00 00 41 0f b7 46 18 66 83 
f8 03 0f 84 7e 02 00 00 66 83 f8 04 74 52 66 83 f8 01 0f 84 c8 02 00 00 <0f> 0b 
48 c7 45 a0 fb ff ff ff 48 8b 5d d0 65 48 33 1c 25 28 00 

  [Test case]
  Run xfstests generic/446 test.

  [Potential regressions]
  Data corruption could be caused, though it is expected to be caused in such 
scenarions anyway. That should affecte direct I/O.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989144/+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 1990434] Re: Bionic update: upstream stable patchset 2022-09-21

[Luke Nowakowski-Krijger]

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

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

Title:
  Bionic update: upstream stable patchset 2022-09-21

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

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:

     upstream stable patchset 2022-09-21

  Ported from the following upstream stable releases:
  v4.14.290, v4.19.254
 v4.19.255

     from git://git.kernel.org/

  xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE
  xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in 
xfrm_bundle_lookup()
  power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe
  perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()
  ip: Fix a data-race around sysctl_fwmark_reflect.
  tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.
  tcp: Fix a data-race around sysctl_tcp_probe_threshold.
  tcp: Fix a data-race around sysctl_tcp_probe_interval.
  i2c: cadence: Change large transfer count reset logic to be unconditional
  net: stmmac: fix dma queue left shift overflow issue
  igmp: Fix data-races around sysctl_igmp_llm_reports.
  igmp: Fix a data-race around sysctl_igmp_max_memberships.
  tcp: Fix a data-race around sysctl_tcp_notsent_lowat.
  be2net: Fix buffer overflow in be_get_module_eeprom
  Revert "Revert "char/random: silence a lockdep splat with printk()""
  mm/mempolicy: fix uninit-value in mpol_rebind_policy()
  bpf: Make sure mac_header was set before using it
  drm/tilcdc: Remove obsolete crtc_mode_valid() hack
  tilcdc: tilcdc_external: fix an incorrect NULL check on list iterator
  ALSA: memalloc: Align buffer allocations in page size
  Bluetooth: Add bt_skb_sendmsg helper
  Bluetooth: Add bt_skb_sendmmsg helper
  Bluetooth: SCO: Replace use of memcpy_from_msg with bt_skb_sendmsg
  Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg
  Bluetooth: Fix passing NULL to PTR_ERR
  Bluetooth: SCO: Fix sco_send_frame returning skb->len
  Bluetooth: Fix bt_skb_sendmmsg not allocating partial chunks
  tty: drivers/tty/, stop using tty_schedule_flip()
  tty: the rest, stop using tty_schedule_flip()
  tty: drop tty_schedule_flip()
  tty: extract tty_flip_buffer_commit() from tty_flip_buffer_push()
  tty: use new tty_insert_flip_string_and_push_buffer() in pty_write()
  PCI: hv: Fix multi-MSI to allow more than one MSI vector
  PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI
  PCI: hv: Reuse existing IRTE allocation in compose_msi_msg()
  PCI: hv: Fix interrupt mapping for multi-MSI
  ip: Fix data-races around sysctl_ip_fwd_use_pmtu.
  ip: Fix data-races around sysctl_ip_nonlocal_bind.
  tcp: Fix data-races around sysctl_tcp_mtu_probing.
  tcp: Fix data-races around sysctl_tcp_reordering.
  tcp: Fix data-races around some timeout sysctl knobs.
  tcp: Fix a data-race around sysctl_tcp_tw_reuse.
  tcp: Fix data-races around sysctl_tcp_fastopen.
  tcp: Fix a data-race around sysctl_tcp_early_retrans.
  tcp: Fix data-races around sysctl_tcp_recovery.
  tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.
  tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.
  tcp: Fix a data-race around sysctl_tcp_retrans_collapse.
  tcp: Fix a data-race around sysctl_tcp_stdurg.
  tcp: Fix a data-race around sysctl_tcp_rfc1337.
  tcp: Fix data-races around sysctl_tcp_max_reordering.
  ima: remove the IMA_TEMPLATE Kconfig option
  UBUNTU: [Config] updateconfigs for IMA_TEMPLATE
  UBUNTU: Upstream stable to v4.14.290, v4.19.254
  s390/archrandom: prevent CPACF trng invocations in interrupt context
  tcp: Fix data-races around sysctl_tcp_dsack.
  tcp: Fix a data-race around sysctl_tcp_app_win.
  tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
  tcp: Fix a data-race around sysctl_tcp_frto.
  tcp: Fix a data-race around sysctl_tcp_nometrics_save.
  scsi: ufs: host: Hold reference returned by of_parse_phandle()
  tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit.
  net: ping6: Fix memleak in ipv6_renew_options().
  igmp: Fix data-races around sysctl_igmp_qrv.
  net: sungem_phy: Add of_node_put() for reference returned by of_get_parent()
  tcp: Fix a data-race around sysctl_tcp_min_tso_segs.
  tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen.
  tcp: Fix a data-race around sysctl_tcp_aut

[Kernel-packages] [Bug 1990698] Re: Bionic update: upstream stable patchset 2022-09-23

[Luke Nowakowski-Krijger]

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

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

Title:
  Bionic update: upstream stable patchset 2022-09-23

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

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:

     upstream stable patchset 2022-09-23

  Ported from the following upstream stable releases:
  v4.14.291, v4.19.256

     from git://git.kernel.org/

  Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
  ntfs: fix use-after-free in ntfs_ucsncmp()
  ARM: crypto: comment out gcc warning that breaks clang builds
  mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle.
  ACPI: video: Force backlight native for some TongFang devices
  macintosh/adb: fix oob read in do_adb_query() function
  Makefile: link with -z noexecstack --no-warn-rwx-segments
  x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
  ALSA: bcd2000: Fix a UAF bug on the error path of probing
  add barriers to buffer_uptodate and set_buffer_uptodate
  HID: wacom: Don't register pad_input for touch switch
  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
  KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
  KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
  ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
  ALSA: hda/cirrus - support for iMac 12,1 model
  vfs: Check the truncate maximum size in inode_newsize_ok()
  fs: Add missing umask strip in vfs_tmpfile
  usbnet: Fix linkwatch use-after-free on disconnect
  parisc: Fix device names in /proc/iomem
  drm/nouveau: fix another off-by-one in nvbios_addr
  drm/amdgpu: Check BO's requested pinning domains against its preferred_domains
  iio: light: isl29028: Fix the warning in isl29028_remove()
  fuse: limit nsec
  md-raid10: fix KASAN warning
  ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr()
  PCI: Add defines for normal and subtractive PCI bridges
  powerpc/fsl-pci: Fix Class Code of PCIe Root Port
  powerpc/powernv: Avoid crashing if rng is NULL
  MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
  USB: HCD: Fix URB giveback issue in tasklet function
  netfilter: nf_tables: fix null deref due to zeroed list head
  arm64: Do not forget syscall when starting a new thread.
  arm64: fix oops in concurrently setting insn_emulation sysctls
  ext2: Add more validity checks for inode counts
  ARM: dts: imx6ul: add missing properties for sram
  ARM: dts: imx6ul: fix qspi node compatible
  ARM: OMAP2+: display: Fix refcount leak bug
  ACPI: PM: save NVS memory for Lenovo G40-45
  ACPI: LPSS: Fix missing check in register_device_clock()
  PM: hibernate: defer device probing when resuming from hibernation
  selinux: Add boundary check in put_entry()
  ARM: findbit: fix overflowing offset
  ARM: bcm: Fix refcount leak in bcm_kona_smc_init
  x86/pmem: Fix platform-device leak in error path
  ARM: dts: ast2500-evb: fix board compatible
  soc: fsl: guts: machine variable might be unset
  cpufreq: zynq: Fix refcount leak in zynq_get_revision
  ARM: dts: qcom: pm8841: add required thermal-sensor-cells
  arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node
  regulator: of: Fix refcount leak bug in of_get_regulation_constraints()
  thermal/tools/tmon: Include pthread and time headers in tmon.h
  dm: return early from dm_pr_call() if DM device is suspended
  drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers()
  drm/mediatek: Add pull-down MIPI operation in mtk_dsi_poweroff function
  i2c: Fix a potential use after free
  wifi: iwlegacy: 4965: fix potential off-by-one overflow in 
il4965_rs_fill_link_cmd()
  drm: bridge: adv7511: Add check for mipi_dsi_driver_register
  media: hdpvr: fix error value returns in hdpvr_read
  drm/vc4: dsi: Correct DSI divider calculations
  drm/rockchip: vop: Don't crash for invalid duplicate_state()
  drm/mediatek: dpi: Remove output format of YUV
  drm: bridge: sii8620: fix possible off-by-one
  media: platform: mtk-mdp: Fix mdp_ipi_comm structure alignment
  tcp: make retransmitted SKB fit into the send window
  selftests: timers: valid-adjtimex: build fix for newer toolchains
  selftests: timers: clocksource-switch: fix passing errors from child
  fs: check FMODE_LSEEK to control intern

[Kernel-packages] [Bug 1975444] Re: mt7921e wifi fails to resume after suspend

[Deyl]

Hello. I got the same issue, 6.0.0-0.rc7 doesn't solve the issue. By the
way I tried Fedora 36 and recent Manjaro, the same problem everywhere.
On older 5.15 kernel wifi doesn't appear to work but suspension
functions well.

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

Title:
  mt7921e wifi fails to resume after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After resuming my suspended PC, the wifi becomes unresponsive. The
  only way to get it working again is to do a full reboot. I'm using
  Ubuntu 22.04 LTS Jammy and my wifi card is:

  MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver.

  This is what I can see in the logs:

  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: chip reset
  kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: chip reset failed
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
  kernel: mt7921e :02:00.0: chip reset failed
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: mt7921e :02:00.0: Failed to get patch semaphore
  kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout
  kernel:  mt7921_start+0x25/0x70 [mt7921e]
  kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x0020]
  kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] 
returns -110
  kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout
  kernel:  mt7921_poll_rx+0x4f/0xe0 [mt7921e]
  kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0
  NetworkManager:   [1653237444.7259] rfkill1: found Wi-Fi radio 
killswitch (at 
/sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) 
(driver mt7921e)
  kernel: mt7921e :02:00.0: Firmware init done
  kernel:  mt7921_pci_driver_init+0x23/0x1000 [mt7921e]
  kernel: mt7921e :02:00.0: ASIC revision: 79610010

  I really appreciate someone's help to fix this behaviour.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsoles 1932 F pulseaudio
   /dev/snd/controlC0:  dsoles 1932 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-07 (16 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: AZW SER
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/21/2022
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: SER_V1.08_P3C6M43_B_Link
  dmi.board.asset.tag: Default string
  dmi.board.name: SER
  dmi.board.vendor: AZW
  dmi.board.version: V01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: AZW
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:
  dmi.product.family: SER
  dmi.product.nam

[Kernel-packages] [Bug 1990690] Re: Users belonging to video group may trigger a deadlock WARN

[Luke Nowakowski-Krijger]

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

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

Title:
  Users belonging to video group may trigger a deadlock WARN

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
  ("fbcon: Prevent that screen size is smaller than font size") introduced
  an extraneous lock_fb_info line into the ioctl flow in fbmem.c.

  This line only exists in bionic tree.

  Users belonging to video group may trigger a deadlock and potentially
  lock the system.

  
  WARNING: possible recursive locking detected
  4.15.0-195-generic #206 Not tainted
  
  refresh/1248 is trying to acquire lock:
    (&fb_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40

  but task is already holding lock:
    (&fb_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40

  other info that might help us debug this:
    Possible unsafe locking scenario:
  CPU0
  
     lock(&fb_info->lock);
     lock(&fb_info->lock);

  *** DEADLOCK ***
    May be due to missing lock nesting notation
   2 locks held by refresh/1248:
    #0:  (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
    #1:  (&fb_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40

  stack backtrace:
   CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
   Call Trace:
    dump_stack+0x98/0xd2
    __lock_acquire+0x736/0x1480
    ? sched_clock_local+0x17/0x90
    ? sched_clock+0x9/0x10
    ? sched_clock_local+0x17/0x90
    lock_acquire+0xa3/0x1e0
    ? lock_acquire+0xa3/0x1e0
    ? lock_fb_info+0x1d/0x40
    ? lock_fb_info+0x1d/0x40
    __mutex_lock+0x65/0x970
    ? lock_fb_info+0x1d/0x40
    ? sched_clock_local+0x17/0x90
    ? lock_acquire+0xa3/0x1e0
    mutex_lock_nested+0x1b/0x20
    ? mutex_lock_nested+0x1b/0x20
    lock_fb_info+0x1d/0x40
    do_fb_ioctl+0x57a/0x5e0
    ? __fd_install+0x5/0x250
    fb_ioctl+0x33/0x40
    ? fb_ioctl+0x33/0x40
    do_vfs_ioctl+0xa9/0x6d0
    ? putname+0x4c/0x60
    ? do_sys_open+0x13d/0x370
    SyS_ioctl+0x79/0x90
    do_syscall_64+0x7b/0x1e0
    entry_SYSCALL_64_after_hwframe+0x46/0xbb
   RIP: 0033:0x7f22acca7217
   RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
   RAX: ffda RBX:  RCX: 7f22acca7217
   RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
   RBP: 7ffe2a930d40 R08:  R09: 
   R10:  R11: 0213 R12: 5624ac8fc7c0
   R13: 7ffe2a930e20 R14:  R15: 

  [Test case]
  Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
  and verified with LOCKDEP.

  [Potential regressions]
  There are no new potential regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990690/+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 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

[Jose Ogando Justo]

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

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

Title:
  fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu

  This is a new test case from bug 1988809

  Test failed with:
   Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
     INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: fib_nexthop_nongw.sh
   # Object "nexthop" is unknown, try "ip help".
   # Error: either "to" is duplicate, or "nhid" is a garbage.
   # TEST: nexthop: get route with nexthop without gw[FAIL]
   # TEST: nexthop: ping through nexthop without gw  [FAIL]
   not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+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 1989521] Re: Ubuntu 22.04.1 CPU soft lockup occurs repeatedly

[Marcus Yanello]

For me it started after installing gnome on my Ubuntu server. Suspicion
is that the desktop sets up suspend mode, though since it is used as a
server it causes issues for any server programs that need to not be
suspended

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

Title:
  Ubuntu 22.04.1 CPU soft lockup occurs repeatedly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  Ubuntu server 22.04.1 is having issues freezing repeatedly with CPU
  softlocking. The issue seems to have started in the last week, all
  packages are up to date. I've updated to hwe kernel, rebooted several
  times, and it still happens. Hw info: 32G RAM, AMD 3600x CPU, Quadro
  RTX 4000 GPU.

  I caught the following in syslog :

  
  Sep 13 04:17:55 marcus-server kernel: [33687.436241] watchdog: BUG: soft 
lockup - CPU#2 stuck for 26s! [kworker/u64:17:154214]
  Sep 13 04:17:55 marcus-server kernel: [33687.436243] Modules linked in: tls 
xt_nat veth nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
nft_counter nf_tables nfnetlink overlay bridge stp llc nvidia_drm(PO) 
snd_hda_codec_realtek intel_rapl_msr intel_rapl_common nvidia_modeset(PO) 
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event zfs(PO) edac_mce_amd nls_iso8859_1 
snd_rawmidi kvm_amd zunicode(PO) nvidia(PO) snd_seq kvm zzstd(O) zlua(O) 
zavl(PO) snd_seq_device icp(PO) rapl wmi_bmof snd_timer zcommon(PO) k10temp ccp 
ucsi_ccg znvpair(PO) snd typec_ucsi typec spl(O) soundcore apex(OE) gasket(OE) 
mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nct6775 
hwmon_vid ipmi_devi
 ntf ipmi_msghandler msr parport_pc ppdev lp
  Sep 13 04:17:55 marcus-server kernel: [33687.436279]  parport ramoops 
reed_solomon pstore_blk pstore_zone mtd efi_pstore ip_tables x_tables autofs4 
btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear nouveau mxm_wmi drm_ttm_helper ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops cec rc_core crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel drm aesni_intel video crypto_simd igb cryptd xhci_pci ahci 
dca i2c_piix4 i2c_nvidia_gpu arcmsr libahci xhci_pci_renesas i2c_algo_bit wmi
  Sep 13 04:17:55 marcus-server kernel: [33687.436302] CPU: 2 PID: 154214 Comm: 
kworker/u64:17 Tainted: P   OE 5.15.0-47-generic #51-Ubuntu
  Sep 13 04:17:55 marcus-server kernel: [33687.436303] Hardware name: To Be 
Filled By O.E.M. To Be Filled By O.E.M./X570 Phantom Gaming 4, BIOS P4.20 
08/02/2021
  Sep 13 04:17:55 marcus-server kernel: [33687.436305] Workqueue: 
events_unbound async_run_entry_fn
  Sep 13 04:17:55 marcus-server kernel: [33687.436308] RIP: 
0010:arcmsr_wait_firmware_ready+0xc1/0x140 [arcmsr]
  Sep 13 04:17:55 marcus-server kernel: [33687.436312] Code: e3 49 8b 94 24 48 
08 00 00 b8 10 00 00 00 89 02 5b 41 5c 5d e9 b0 7b db e8 48 8b 47 50 4c 8d a0 
bc 00 00 00 eb 0c 41 8b 04 24 <85> c0 0f 88 64 ff ff ff f6 83 81 00 00 00 01 75 
eb bf 14 00 00 00
  Sep 13 04:17:55 marcus-server kernel: [33687.436313] RSP: 
0018:ade8d136fd10 EFLAGS: 0202
  Sep 13 04:17:55 marcus-server kernel: [33687.436314] RAX:  
RBX: 96720a460870 RCX: ade8c12b0034
  Sep 13 04:17:55 marcus-server kernel: [33687.436315] RDX: 000d 
RSI: 96721b53ef80 RDI: 96720a460870
  Sep 13 04:17:55 marcus-server kernel: [33687.436315] RBP: ade8d136fd20 
R08:  R09: 
  Sep 13 04:17:55 marcus-server kernel: [33687.436316] R10: 0284 
R11:  R12: ade8c12b00bc
  Sep 13 04:17:55 marcus-server kernel: [33687.436317] R13: 000d 
R14: 96720a46 R15: 96720a460870
  Sep 13 04:17:55 marcus-server kernel: [33687.436318] FS:  
() GS:96791ea8() knlGS:
  Sep 13 04:17:55 marcus-server kernel: [33687.436319] CS:  0010 DS:  ES: 
 CR0: 80050033
  Sep 13 04:17:55 marcus-server kernel: [33687.436320] CR2:  
CR3: 0007c8c1 CR4: 00350ee0

  
  It happens pretty often too, but the system isn't overloaded, so I'm not sure 
what is causing it. 

  Message from syslogd@marcus-server at Sep 14 02:16:11 ...
   kernel:[ 1276.914096] watchdog: BUG: soft lockup - CPU#8 stuck for 26s! 
[kworker/u64:28:252938]

  Message from syslogd@marcus-server at Sep 14 02:16:11 ...
   kernel:[ 1304.913956] watchdog: BUG: soft lockup - CPU#8 stuck for 52s! 
[kworker/u64:28:252938]

  Message from syslogd@marcus-server at Sep 14 0

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Stefan Bader]

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

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

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

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged

[Stefan Bader]

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

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

Title:
  Fix resume on AMD platforms when TBT monitor is plugged

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  When TBT monitor is connected to AMD platform, system resume will hit
  stack corruption or BUG_ON() macro.

  [Fix]
  Revert the offending commit and handle MST properly.

  [Test]
  The system can resume normally and no more kernel splat.
   
  [Where problems could occur]
  The new logic is restriced to MST hub, so normal DP/HDMI usage should be
  unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990920/+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 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

[Alexandru Bolboaca]

I tried a workaround until the issue is resolved: switch to Nvidia
performance profile. I find it weird that freezes still happen - less
than when running AMDGPU but still happen. I also tried to blacklist
AMDGPU but the login screen was not loading anymore.

Is there a way to run Ubuntu completely on Nvidia GPU?

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

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

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1980831/+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 1918583] Re: Switch to libgpiod and disable CONFIG_GPIO_SYSFS

[Launchpad Bug Tracker]

This bug was fixed in the package linux-raspi - 5.19.0-1002.6

---
linux-raspi (5.19.0-1002.6) kinetic; urgency=medium

  * kinetic/linux-raspi: 5.19.0-1002.6 -proposed tracker (LP: #1991077)

  * VM fails to boot in ScalingStack (LP: #1990995)
- [Packaging] raspi: Include virtio drivers in linux-modules

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/master)

  * kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-09-14)
(LP: #1989958)
- Revert "ext4: make mb_optimize_scan performance mount option work with
  extents"
- dtoverlays: Add nohdmi options to vc4-kms-v3d overlays
- configs: Enable IIO software trigger modules
- configs: Enable IP_VS_IPV6 (for loadbalancing)
- configs: Enable CEPH_FS=m
- overlays: Make more overlays runtime-capable
- overlays: Mark more overlays as Pi4-specific
- configs: Add CONFIG_MT7921U=m
- overlays:Adds HiFiBerry AMP3
- rpi-simple-soundcard: adds definitions for the HiFiBerry AMP3 card
- media: bcm2835-unicam: Correctly handle FS + FE ISR condtion
- bcm2708-dmaengine: Use platform_get_irq
- media: i2c: imx290: Add compatible strings for IMX327 and IMX462
- dtoverlays: Add overlays for Sony IMX327 and IMX462 image sensors
- defconfigs: Add VIDEO_MUX to all defconfigs
- dtoverlays: Reshuffle image sensor overlays to allow use with muxes
- bcm2835-v4l2-codec: support H.264 5.0 and 5.1 levels
- configs: Add support for Cilium on 2711 64-bit
- overlays: gpio-fan: Add hyst (hysteresis) param
- overlays: gpio-fan: Document the hyst parameter
- sound: soc: bcm: Added Sound card driver for Dacberry400 Audio card for
  Raspberry Pi 400
- overlays: Add dacberry400
- configs: Enable DACBERRY400
- overlays: merus-amp: Set GPIO 8 as input np
- rpi-simple-soundcard: limits sample rate of Merus Amp board
- drm/vc4: Add async update support for cursor planes
- media: video-mux: Read CSI2 config from FW, and pass to receiver
- defconfigs: Add CONFIG_MUX_GPIO.
- media: i2c: arducam-pivariety: Add custom controls
- configs: Add LAN7430 driver on BCM2711
- [Config] raspi: updateconfigs after update to rpi-5.19.y (2022-08-31)
- overlays: Add a pull (up/down) parameter to pps-gpio
- drm/vc4: Configure the HVS COB allocations
- drm/vc4: Set AXI panic modes for the HVS
- drm/vc4: SCALER_DISPBKGND_AUTOHS is only valid on HVS4
- drm/vc4: Correct interrupt masking bit assignment for HVS5
- media: bcm2835-unicam: Fix for possible dummy buffer overrun
- ASoC:ma120x0p: Extend the volume range to -144dB (mute)
- media: i2c: imx290: Updating VBLANK should update exposure in all states
- Revert "media: i2c: imx290: Explicitly set v&h blank on mode change"
- media: i2c: imx290: Drop incorrect comment about pixelrate
- media: i2c: imx290: Do not reset exposure time from set_fmt
- overlays: Add the Raspberry Pi sound cards
- overlays: Rename unofficial "rpi-" overlays
- drm/mipi-dsi: Detach devices when removing the host
- drm/crtc: Introduce drmm_crtc_init_with_planes
- drm/encoder: Introduce drmm_encoder_init
- drm/connector: Reorder headers
- drm/connector: Mention the cleanup after drm_connector_init
- drm/connector: Clarify when drm_connector_unregister is needed
- drm/connector: Consolidate Connector Initialization
- drm/connector: Check for destroy implementation
- drm/connector: Introduce drmm_connector_init
- drm/bridge: panel: Introduce drmm_panel_bridge_add
- drm/bridge: panel: Introduce drmm_of_get_bridge
- drm/vc4: Add module dependency on hdmi-codec
- drm/vc4: drv: Call component_unbind_all()
- drm/vc4: drv: Use drm_dev_unplug
- drm/vc4: crtc: Create vblank reporting function
- drm/vc4: hvs: Protect device resources after removal
- drm/vc4: hvs: Remove planes currently allocated before taking down
- drm/vc4: plane: Take possible_crtcs as an argument
- drm/vc4: crtc: Remove manual plane removal on error
- drm/vc4: plane: Switch to drmm_universal_plane_alloc()
- drm/vc4: crtc: Move debugfs_name to crtc_data
- drm/vc4: crtc: Switch to drmm_kzalloc
- drm/vc4: crtc: Switch to DRM-managed CRTC initialization
- drm/vc4: dpi: Remove vc4_dev dpi pointer
- drm/vc4: dpi: Embed DRM structures into the private structure
- drm/vc4: dpi: Switch to drmm_kzalloc
- drm/vc4: dpi: Return an error if we can't enable our clock
- drm/vc4: dpi: Remove unnecessary drm_of_panel_bridge_remove call
- drm/vc4: dpi: Add action to disable the clock
- drm/vc4: dpi: Switch to DRM-managed encoder initialization
- drm/vc4: dpi: Switch to drmm_of_get_bridge
- drm/vc4: dpi: Protect device resources
- drm/vc4: dsi: Embed DRM structures into the private structure
- drm/vc4: dsi: Switch to DRM-managed encoder initialization
- drm

[Kernel-packages] [Bug 1987998] Re: LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot

[Stefan Bader]

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

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

Title:
  LSM: Configuring Too Many LSMs Causes Kernel Panic on Boot

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1987998

  [Impact]

  The Ubuntu kernel carries an out of tree patchet, known as "LSM:
  Module stacking for AppArmor" upstream, to enable stackable LSMs for
  containers. The revision the Ubuntu kernel carries is an older one,
  from 2020, and has some slight divergences from the latest revision in
  development.

  One such divergence, is support for Landlock as a stackable LSM. When
  the stackable LSM patchset was applied, Landlock was still in
  development and not mainlined yet, and wasn't present in the earlier
  revision of the "LSM: Module stacking for AppArmor" patchset. Support
  for this was added by us.

  There was a minor omission made during enabling support for Landlock.
  The LSM slot type was marked as LSMBLOB_NEEDED, when it should have
  been LSMBLOB_NOT_NEEDED.

  Landlock itself does not provide any of the hooks that use a struct
  lsmblob, such as secid_to_secctx, secctx_to_secid, inode_getsecid,
  cred_getsecid, kernel_act_as task_getsecid_subj task_getsecid_obj and
  ipc_getsecid.

  When we set .slot = LSMBLOB_NEEDED, this indicates that we need an
  entry in struct lsmblob, and we need to increment LSMBLOB_ENTRIES by
  one to fit the entry into the secid array:

  #define LSMBLOB_ENTRIES ( \
     (IS_ENABLED(CONFIG_SECURITY_SELINUX) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_SECURITY_SMACK) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_SECURITY_APPARMOR) ? 1 : 0) + \
     (IS_ENABLED(CONFIG_BPF_LSM) ? 1 : 0))

  struct lsmblob {
     u32 secid[LSMBLOB_ENTRIES];
  };

  Currently, we don't increment LSMBLOB_ENTRIES by one to make an entry
  for Landlock, so for the Ubuntu kernel, we can fit a maximum of two
  entries, one for Apparmor and one for bpf.

  If you try and configure three LSMs like so and reboot:

  GRUB_CMDLINE_LINUX_DEFAULT="lsm=landlock,bpf,apparmor"

  You will receive the following panic:

  LSM: Security Framework initializing
  landlock: Up and running.
  LSM support for eBPF active
  Kernel panic - not syncing: security_add_hooks Too many LSMs registered.
  CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
  Call Trace:
   
   show_stack+0x52/0x5c
   dump_stack_lvl+0x4a/0x63
   dump_stack+0x10/0x16
   panic+0x149/0x321
   security_add_hooks+0x45/0x13a
   apparmor_init+0x189/0x1ef
   initialize_lsm+0x54/0x74
   ordered_lsm_init+0x379/0x392
   security_init+0x40/0x49
   start_kernel+0x466/0x4dc
   x86_64_start_reservations+0x24/0x2a
   x86_64_start_kernel+0xe4/0xef
   secondary_startup_64_no_verify+0xc2/0xcb
   
  ---[ end Kernel panic - not syncing: security_add_hooks Too many LSMs 
registered. ]---

  There is a check added in security_add_hooks() that makes sure that
  you cannot configure too many LSMs:

  if (lsmid->slot == LSMBLOB_NEEDED) {
   if (lsm_slot >= LSMBLOB_ENTRIES)
    panic("%s Too many LSMs registered.\n", __func__);
   lsmid->slot = lsm_slot++;
   init_debug("%s assigned lsmblob slot %d\n", lsmid->lsm,
   lsmid->slot);
  }

  A workaround is to enable no more than 2 LSMs until this is fixed.

  [Fix]

  If you read the following mailing list thread on linux-security-
  modules from May 2021:

  https://lore.kernel.org/selinux/202105141224.942DE93@keescook/T/

  It is explained that Landlock does not provide any of the hooks that
  use a struct lsmblob, such as secid_to_secctx, secctx_to_secid,
  inode_getsecid, cred_getsecid, kernel_act_as task_getsecid_subj
  task_getsecid_obj and ipc_getsecid.

  I verified this with:

  ubuntu-jammy$ grep -Rin "secid_to_secctx" security/landlock/
  ubuntu-jammy$ grep -Rin "secctx_to_secid" security/landlock/
  ubuntu-jammy$ grep -Rin "inode_getsecid" security/landlock/
  ubuntu-jammy$ grep -Rin "cred_getsecid" security/landlock/
  ubuntu-jammy$ grep -Rin "kernel_act_as" security/landlock/
  ubuntu-jammy$ grep -Rin "task_getsecid_subj" security/landlock/
  ubuntu-jammy$ grep -Rin "task_getsecid_obj" security/landlock/
  ubuntu-jammy$ grep -Rin "ipc_getsecid" security/landlock/

  The fix is to change Landlock from LSMBLOB_NEEDED to
  LSMBLOB_NOT_NEEDED.

  Due to the "LSM: Module stacking for AppArmor" patchset being 25
  patches long, it was impractical to revert just the below patch and
  reapply with the fix, due to a large amount of conflicts:

  commit f17b27a2790e72198d2aaf45242453e5a9043049
  Author: Casey Schaufler 
  Date:   Mon Aug 17 16:02:56 2020 -07

[Kernel-packages] [Bug 1990995] Re: VM fails to boot in ScalingStack

[Launchpad Bug Tracker]

This bug was fixed in the package linux-raspi - 5.19.0-1002.6

---
linux-raspi (5.19.0-1002.6) kinetic; urgency=medium

  * kinetic/linux-raspi: 5.19.0-1002.6 -proposed tracker (LP: #1991077)

  * VM fails to boot in ScalingStack (LP: #1990995)
- [Packaging] raspi: Include virtio drivers in linux-modules

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/master)

  * kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-09-14)
(LP: #1989958)
- Revert "ext4: make mb_optimize_scan performance mount option work with
  extents"
- dtoverlays: Add nohdmi options to vc4-kms-v3d overlays
- configs: Enable IIO software trigger modules
- configs: Enable IP_VS_IPV6 (for loadbalancing)
- configs: Enable CEPH_FS=m
- overlays: Make more overlays runtime-capable
- overlays: Mark more overlays as Pi4-specific
- configs: Add CONFIG_MT7921U=m
- overlays:Adds HiFiBerry AMP3
- rpi-simple-soundcard: adds definitions for the HiFiBerry AMP3 card
- media: bcm2835-unicam: Correctly handle FS + FE ISR condtion
- bcm2708-dmaengine: Use platform_get_irq
- media: i2c: imx290: Add compatible strings for IMX327 and IMX462
- dtoverlays: Add overlays for Sony IMX327 and IMX462 image sensors
- defconfigs: Add VIDEO_MUX to all defconfigs
- dtoverlays: Reshuffle image sensor overlays to allow use with muxes
- bcm2835-v4l2-codec: support H.264 5.0 and 5.1 levels
- configs: Add support for Cilium on 2711 64-bit
- overlays: gpio-fan: Add hyst (hysteresis) param
- overlays: gpio-fan: Document the hyst parameter
- sound: soc: bcm: Added Sound card driver for Dacberry400 Audio card for
  Raspberry Pi 400
- overlays: Add dacberry400
- configs: Enable DACBERRY400
- overlays: merus-amp: Set GPIO 8 as input np
- rpi-simple-soundcard: limits sample rate of Merus Amp board
- drm/vc4: Add async update support for cursor planes
- media: video-mux: Read CSI2 config from FW, and pass to receiver
- defconfigs: Add CONFIG_MUX_GPIO.
- media: i2c: arducam-pivariety: Add custom controls
- configs: Add LAN7430 driver on BCM2711
- [Config] raspi: updateconfigs after update to rpi-5.19.y (2022-08-31)
- overlays: Add a pull (up/down) parameter to pps-gpio
- drm/vc4: Configure the HVS COB allocations
- drm/vc4: Set AXI panic modes for the HVS
- drm/vc4: SCALER_DISPBKGND_AUTOHS is only valid on HVS4
- drm/vc4: Correct interrupt masking bit assignment for HVS5
- media: bcm2835-unicam: Fix for possible dummy buffer overrun
- ASoC:ma120x0p: Extend the volume range to -144dB (mute)
- media: i2c: imx290: Updating VBLANK should update exposure in all states
- Revert "media: i2c: imx290: Explicitly set v&h blank on mode change"
- media: i2c: imx290: Drop incorrect comment about pixelrate
- media: i2c: imx290: Do not reset exposure time from set_fmt
- overlays: Add the Raspberry Pi sound cards
- overlays: Rename unofficial "rpi-" overlays
- drm/mipi-dsi: Detach devices when removing the host
- drm/crtc: Introduce drmm_crtc_init_with_planes
- drm/encoder: Introduce drmm_encoder_init
- drm/connector: Reorder headers
- drm/connector: Mention the cleanup after drm_connector_init
- drm/connector: Clarify when drm_connector_unregister is needed
- drm/connector: Consolidate Connector Initialization
- drm/connector: Check for destroy implementation
- drm/connector: Introduce drmm_connector_init
- drm/bridge: panel: Introduce drmm_panel_bridge_add
- drm/bridge: panel: Introduce drmm_of_get_bridge
- drm/vc4: Add module dependency on hdmi-codec
- drm/vc4: drv: Call component_unbind_all()
- drm/vc4: drv: Use drm_dev_unplug
- drm/vc4: crtc: Create vblank reporting function
- drm/vc4: hvs: Protect device resources after removal
- drm/vc4: hvs: Remove planes currently allocated before taking down
- drm/vc4: plane: Take possible_crtcs as an argument
- drm/vc4: crtc: Remove manual plane removal on error
- drm/vc4: plane: Switch to drmm_universal_plane_alloc()
- drm/vc4: crtc: Move debugfs_name to crtc_data
- drm/vc4: crtc: Switch to drmm_kzalloc
- drm/vc4: crtc: Switch to DRM-managed CRTC initialization
- drm/vc4: dpi: Remove vc4_dev dpi pointer
- drm/vc4: dpi: Embed DRM structures into the private structure
- drm/vc4: dpi: Switch to drmm_kzalloc
- drm/vc4: dpi: Return an error if we can't enable our clock
- drm/vc4: dpi: Remove unnecessary drm_of_panel_bridge_remove call
- drm/vc4: dpi: Add action to disable the clock
- drm/vc4: dpi: Switch to DRM-managed encoder initialization
- drm/vc4: dpi: Switch to drmm_of_get_bridge
- drm/vc4: dpi: Protect device resources
- drm/vc4: dsi: Embed DRM structures into the private structure
- drm/vc4: dsi: Switch to DRM-managed encoder initialization
- drm

[Kernel-packages] [Bug 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

[Kleber Sacilotto de Souza]

We had a similar issue in the past with bug 1896448. We can likely do
something similar, check if 'nexthop' is available and skip the test if
not.

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

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

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

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

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

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

Title:
  fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu

  This is a new test case from bug 1988809

  Test failed with:
   Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
     INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: fib_nexthop_nongw.sh
   # Object "nexthop" is unknown, try "ip help".
   # Error: either "to" is duplicate, or "nhid" is a garbage.
   # TEST: nexthop: get route with nexthop without gw[FAIL]
   # TEST: nexthop: ping through nexthop without gw  [FAIL]
   not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+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 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]

[Stefan Bader]

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

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

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

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

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

Title:
  To support Intel Maple Ridge Thunderbolt [8086:1134]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
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 Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The TBT ID[8086:1134] the new project uses is not listed in the driver.

  [Fix]
  Intel submits this as we requested which is still in linux-next
  https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/

  [Where problems could occur]
  Adding only one ID, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990240/+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 1990242] Re: Intel graphic driver is not probing[8086:468b]

[Stefan Bader]

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

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

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

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

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

Title:
  Intel graphic driver is not probing[8086:468b]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
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 Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Got blank screen after entered desktop

  [Fix]
  Below commit in linux-next fixes the issue.
  6215a7c8f552 drm/i915: Add new ADL-S pci id

  [Test]
  Verified on the target machine.

  [Where problems could occur]
  It only adds an ID to the list, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990242/+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 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen

[Daniel van Vugt]

We should also clarify "won't boot" is just an illusion. The OS boots
and runs but you don't get any working graphics.

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th
  gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot

[Daniel van Vugt]

No bug on Intel 10th gen either. So it's only 11th gen and later that's
a problem.

** Tags added: i915

** Summary changed:

- New Kinetic kernel (5.19.0-18-generic) won't boot
+ New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th gen

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th
  gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1989578] Re: Add HDMI codec ID for Intel Raptor Lake

[Stefan Bader]

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

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

Title:
  Add HDMI codec ID for Intel Raptor Lake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  The HDAudio is not functional on some RaptorLake machines. The audio codec is 
failed to be probed so no PCM stream available for audio functions.

  [Fix]
  Backport the patch from upstream which adds the support for the HDMI codec ID 
on RaptorLake.

  [Test]
  Power on the machine and check if the audio function's working with alsa 
utilities.

  [Where problems could occur]
  The change only applies to the new RaptorLake Intel HDA controller and HDMI 
codec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989578/+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 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='

[Stefan Bader]

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

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

Title:
  cgroup: all controllers mounted when using 'cgroup_no_v1='

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  When mounting a cgroup hierarchy with disabled controller in cgroup v1,
  all available controllers will be attached.
  For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
  mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
  enabled controllers will be attached except cpu.

  This exists since linux v5.1 and fixed in linux v5.11 with this commit:
  61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

  [Test Case]

  root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
  root@dut-vm:~# systemctl kexec
  root@dut-vm:~# mount | grep cgroup
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)

  
  => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
  Note that several reboots may be needed to reproduce the problem (it fails 
only when systemd tries to mount 'net_cls,net_prio' first, but the order is 
random).

  [Regression Potential]

  The patch is located in cgroup1_parse_param(), the potential
  regressions are low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988584/+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 1991156] Re: Focal update: v5.4.212 upstream stable release

[Stefan Bader]

Skipped af_key: "Do not call xfrm_probe_algs in parallel" as it already
was applied for security (CVE-2022-3028).

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3028

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

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

Title:
  Focal update: v5.4.212 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

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:

     v5.4.212 upstream stable release
     from git://git.kernel.org/

  audit: fix potential double free on error path from fsnotify_add_inode_mark
  parisc: Fix exception handler for fldw and fstw instructions
  kernel/sys_ni: add compat entry for fadvise64_64
  usb: cdns3: Fix issue for clear halt endpoint
  pinctrl: amd: Don't save/restore interrupt status and wake status bits
  sched/deadline: Unthrottle PI boosted threads while enqueuing
  sched/deadline: Fix stale throttling on de-/boosted tasks
  sched/deadline: Fix priority inheritance with multiple scheduling classes
  kernel/sched: Remove dl_boosted flag comment
  xfrm: fix refcount leak in __xfrm_policy_check()
  af_key: Do not call xfrm_probe_algs in parallel
  SUNRPC: RPC level errors should set task->tk_rpc_status
  rose: check NULL rose_loopback_neigh->loopback
  net/mlx5e: Properly disable vlan strip on non-UL reps
  net: moxa: get rid of asymmetry in DMA mapping/unmapping
  bonding: 802.3ad: fix no transmission of LACPDUs
  net: ipvtap - add __init/__exit annotations to module init/exit funcs
  netfilter: ebtables: reject blobs that don't provide all entry points
  bnxt_en: fix NQ resource accounting during vf creation on 57500 chips
  netfilter: nft_payload: report ERANGE for too long offset and length
  netfilter: nft_payload: do not truncate csum_offset and csum_type
  netfilter: nft_osf: restrict osf to ipv4, ipv6 and inet families
  netfilter: nft_tunnel: restrict it to netdev family
  net: Fix data-races around weight_p and dev_weight_[rt]x_bias.
  net: Fix data-races around netdev_tstamp_prequeue.
  ratelimit: Fix data-races in ___ratelimit().
  net: Fix a data-race around sysctl_tstamp_allow_data.
  net: Fix a data-race around sysctl_net_busy_poll.
  net: Fix a data-race around sysctl_net_busy_read.
  net: Fix a data-race around netdev_budget.
  net: Fix a data-race around netdev_budget_usecs.
  net: Fix a data-race around sysctl_somaxconn.
  ixgbe: stop resetting SYSTIME in ixgbe_ptp_start_cyclecounter
  btrfs: fix silent failure when deleting root reference
  btrfs: replace: drop assert for suspended replace
  btrfs: add info when mount fails due to stale replace target
  btrfs: check if root is readonly while setting security xattr
  x86/unwind/orc: Unwind ftrace trampolines with correct ORC entry
  loop: Check for overflow while configuring loop
  asm-generic: sections: refactor memory_intersects
  s390: fix double free of GS and RI CBs on fork() failure
  ACPI: processor: Remove freq Qos request for all CPUs
  mm/hugetlb: fix hugetlb not supporting softdirty tracking
  md: call __md_stop_writes in md_stop
  perf/x86/intel/uncore: Fix broken read_counter() for SNB IMC PMU
  scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq
  mm: Force TLB flush for PFNMAP mappings before unlink_file_vma()
  s390/mm: do not trigger write fault when vma does not allow VM_WRITE
  x86/bugs: Add "unknown" reporting for MMIO Stale Data
  kbuild: Fix include path in scripts/Makefile.modpost
  Bluetooth: L2CAP: Fix build errors in some archs
  HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
  udmabuf: Set the DMA mask for the udmabuf device (v2)
  media: pvrusb2: fix memory leak in pvr_probe
  HID: hidraw: fix memory leak in hidraw_release()
  fbdev: fb_pm2fb: Avoid potential divide by zero error
  ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is 
dead
  bpf: Don't redirect packets with invalid pkt_len
  mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
  btrfs: introduce btrfs_lookup_match_dir
  btrfs: do not pin logs too early during renames
  btrfs: unify lookup return value when dir entry is missing
  drm/amd/display: Avoid MPC infinite loop
  drm/amd/display: clear optc underflow before turn off odm clock
  neigh: fix possible DoS due to net iface start/stop loop
  s390/hypfs: avoid error message under KVM
  drm/

[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot

[Mariusz Dykierek]

i7-1165G7 has Iris X graphics like mine. If you checked dmesg.log.0 from
failed boot, you should see same i915 failure.

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1991790] [NEW] Disable sv57 as the userspace is not ready

[Alexandre Ghiti]

Public bug reported:

[ Impact ]

sv57 breaks Go since Go uses the upper bits of a pointer to store data,
and it is not ready for sv57 yet. It probably breaks other type of
software using this "pointer tagging" technic. The following patch fixes
this: at the moment, there is no way to indicate to the kernel to
downgrade to sv48, so we must patch the kernel.

diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
index 2c4a64e97aec..18a0c70ed313 100644
--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/init.c
@@ -775,6 +775,10 @@ static __init void set_satp_mode(void)
disable_pgtable_l4();
}
 
+   /* UBUNTU: Force disable sv57 and fallback to sv48 */
+   if (pgtable_l5_enabled)
+   disable_pgtable_l5();
+
memset(early_pg_dir, 0, PAGE_SIZE);
memset(early_p4d, 0, PAGE_SIZE);
memset(early_pud, 0, PAGE_SIZE);

[ Test Plan ]

Build an image with the new kernel and make sure snapd started
correctly, or that you can compile a simple helloworld written in Go.

[ Where problems could occur ]

The patch could be wrong, but I already built a kernel with it and it
worked fine.

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

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

Title:
  Disable sv57 as the userspace is not ready

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  [ Impact ]

  sv57 breaks Go since Go uses the upper bits of a pointer to store
  data, and it is not ready for sv57 yet. It probably breaks other type
  of software using this "pointer tagging" technic. The following patch
  fixes this: at the moment, there is no way to indicate to the kernel
  to downgrade to sv48, so we must patch the kernel.

  diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
  index 2c4a64e97aec..18a0c70ed313 100644
  --- a/arch/riscv/mm/init.c
  +++ b/arch/riscv/mm/init.c
  @@ -775,6 +775,10 @@ static __init void set_satp_mode(void)
  disable_pgtable_l4();
  }
   
  +   /* UBUNTU: Force disable sv57 and fallback to sv48 */
  +   if (pgtable_l5_enabled)
  +   disable_pgtable_l5();
  +
  memset(early_pg_dir, 0, PAGE_SIZE);
  memset(early_p4d, 0, PAGE_SIZE);
  memset(early_pud, 0, PAGE_SIZE);

  [ Test Plan ]

  Build an image with the new kernel and make sure snapd started
  correctly, or that you can compile a simple helloworld written in Go.

  [ Where problems could occur ]

  The patch could be wrong, but I already built a kernel with it and it
  worked fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1991790/+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 1990190] Re: Focal update: v5.4.211 upstream stable release

[Stefan Bader]

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

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

Title:
  Focal update: v5.4.211 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

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:

     v5.4.211 upstream stable release
     from git://git.kernel.org/

  Makefile: link with -z noexecstack --no-warn-rwx-segments
  x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
  scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover"
  ALSA: bcd2000: Fix a UAF bug on the error path of probing
  igc: Remove _I_PHY_ID checking
  wifi: mac80211_hwsim: fix race condition in pending packet
  wifi: mac80211_hwsim: add back erroneously removed cast
  wifi: mac80211_hwsim: use 32-bit skb cookie
  add barriers to buffer_uptodate and set_buffer_uptodate
  HID: wacom: Only report rotation for art pen
  HID: wacom: Don't register pad_input for touch switch
  KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case
  KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case
  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
  KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value
  KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
  KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
  mm/mremap: hold the rmap lock in write mode when moving page table entries.
  ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
  ALSA: hda/cirrus - support for iMac 12,1 model
  ALSA: hda/realtek: Add quirk for another Asus K42JZ model
  tty: vt: initialize unicode screen buffer
  vfs: Check the truncate maximum size in inode_newsize_ok()
  fs: Add missing umask strip in vfs_tmpfile
  thermal: sysfs: Fix cooling_device_stats_setup() error code path
  fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters
  usbnet: Fix linkwatch use-after-free on disconnect
  ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh()
  parisc: Fix device names in /proc/iomem
  parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode
  drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error
  drm/nouveau: fix another off-by-one in nvbios_addr
  drm/amdgpu: Check BO's requested pinning domains against its preferred_domains
  iio: light: isl29028: Fix the warning in isl29028_remove()
  fuse: limit nsec
  serial: mvebu-uart: uart2 error bits clearing
  md-raid10: fix KASAN warning
  ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr()
  PCI: Add defines for normal and subtractive PCI bridges
  powerpc/fsl-pci: Fix Class Code of PCIe Root Port
  powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E
  powerpc/powernv: Avoid crashing if rng is NULL
  MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
  coresight: Clear the connection field properly
  USB: HCD: Fix URB giveback issue in tasklet function
  ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC
  arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC
  netfilter: nf_tables: fix null deref due to zeroed list head
  epoll: autoremove wakers even more aggressively
  x86: Handle idle=nomwait cmdline properly for x86_idle
  arm64: Do not forget syscall when starting a new thread.
  arm64: fix oops in concurrently setting insn_emulation sysctls
  ext2: Add more validity checks for inode counts
  genirq: Don't return error on missing optional irq_request_resources()
  wait: Fix __wait_event_hrtimeout for RT/DL tasks
  ARM: dts: imx6ul: add missing properties for sram
  ARM: dts: imx6ul: change operating-points to uint32-matrix
  ARM: dts: imx6ul: fix csi node compatible
  ARM: dts: imx6ul: fix lcdif node compatible
  ARM: dts: imx6ul: fix qspi node compatible
  spi: synquacer: Add missing clk_disable_unprepare()
  ARM: OMAP2+: display: Fix refcount leak bug
  ACPI: EC: Remove duplicate ThinkPad X1 Carbon 6th entry from DMI quirks
  ACPI: PM: save NVS memory for Lenovo G40-45
  ACPI: LPSS: Fix missing check in register_device_clock()
  arm64: dts: qcom: ipq8074: fix NAND node name
  arm64: dts: allwinner: a64: orangepi-win: Fix LED node name
  ARM: shmobile: rcar-gen2: Increase refcount for new reference
  PM: hibernate: defer device probing when resuming from hibernation
  selinux: Add boundary check in put_entry()
  spi: spi-rspi: Fix PIO fa

[Kernel-packages] [Bug 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot

[Balint Kozma]

Intel i9-9900K on Z390 with TPM2.0 module boots.
Asus UX425EA Intel i7-1165G7 doesn't boot.

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1991717] Re: Jammy update: v5.15.64 upstream stable release

[Stefan Bader]

Skipped:
- "af_key: Do not call xfrm_probe_algs in parallel"
  already applied for security (CVE-2022-3028)


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3028

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

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

Title:
  Jammy update: v5.15.64 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

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:

     v5.15.64 upstream stable release
     from git://git.kernel.org/

  wifi: rtlwifi: remove always-true condition pointed out by GCC 12
  eth: sun: cassini: remove dead code
  audit: fix potential double free on error path from fsnotify_add_inode_mark
  cgroup: Fix race condition at rebind_subsystems()
  parisc: Make CONFIG_64BIT available for ARCH=parisc64 only
  parisc: Fix exception handler for fldw and fstw instructions
  kernel/sys_ni: add compat entry for fadvise64_64
  x86/entry: Move CLD to the start of the idtentry macro
  block: add a bdev_max_zone_append_sectors helper
  block: add bdev_max_segments() helper
  btrfs: zoned: revive max_zone_append_bytes
  btrfs: replace BTRFS_MAX_EXTENT_SIZE with fs_info->max_extent_size
  btrfs: convert count_max_extents() to use fs_info->max_extent_size
  Input: i8042 - move __initconst to fix code styling warning
  Input: i8042 - merge quirk tables
  Input: i8042 - add TUXEDO devices to i8042 quirk tables
  Input: i8042 - add additional TUXEDO devices to i8042 quirk tables
  drivers/base: fix userspace break from using bin_attributes for cpumap and 
cpulist
  scsi: qla2xxx: Fix response queue handler reading stale packets
  scsi: qla2xxx: edif: Fix dropped IKE message
  btrfs: put initial index value of a directory in a constant
  btrfs: pass the dentry to btrfs_log_new_name() instead of the inode
  btrfs: remove unnecessary parameter delalloc_start for writepage_delalloc()
  riscv: lib: uaccess: fold fixups into body
  riscv: lib: uaccess: fix CSR_STATUS SR_SUM bit
  xfrm: fix refcount leak in __xfrm_policy_check()
  xfrm: clone missing x->lastused in xfrm_do_migrate
  af_key: Do not call xfrm_probe_algs in parallel
  xfrm: policy: fix metadata dst->dev xmit null pointer dereference
  fs: require CAP_SYS_ADMIN in target namespace for idmapped mounts
  net: use eth_hw_addr_set() instead of ether_addr_copy()
  Revert "net: macsec: update SCI upon MAC address change."
  NFS: Don't allocate nfs_fattr on the stack in __nfs42_ssc_open()
  NFSv4.2 fix problems with __nfs42_ssc_open
  SUNRPC: RPC level errors should set task->tk_rpc_status
  mm/smaps: don't access young/dirty bit if pte unpresent
  ntfs: fix acl handling
  rose: check NULL rose_loopback_neigh->loopback
  r8152: fix the units of some registers for RTL8156A
  r8152: fix the RX FIFO settings when suspending
  nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout
  ice: xsk: Force rings to be sized to power of 2
  ice: xsk: prohibit usage of non-balanced queue id
  net/mlx5e: Properly disable vlan strip on non-UL reps
  net/mlx5: Avoid false positive lockdep warning by adding lock_class_key
  net/mlx5e: Fix wrong application of the LRO state
  net/mlx5e: Fix wrong tc flag used when set hw-tc-offload off
  net: ipa: don't assume SMEM is page-aligned
  net: phy: Don't WARN for PHY_READY state in mdio_bus_phy_resume()
  net: moxa: get rid of asymmetry in DMA mapping/unmapping
  bonding: 802.3ad: fix no transmission of LACPDUs
  net: ipvtap - add __init/__exit annotations to module init/exit funcs
  netfilter: ebtables: reject blobs that don't provide all entry points
  bnxt_en: fix NQ resource accounting during vf creation on 57500 chips
  netfilter: nf_tables: disallow updates of implicit chain
  netfilter: nf_tables: make table handle allocation per-netns friendly
  netfilter: nft_payload: report ERANGE for too long offset and length
  netfilter: nft_payload: do not truncate csum_offset and csum_type
  netfilter: nf_tables: do not leave chain stats enabled on error
  netfilter: nft_osf: restrict osf to ipv4, ipv6 and inet families
  netfilter: nft_tunnel: restrict it to netdev family
  netfilter: nf_tables: consolidate rule verdict trace call
  netfilter: nft_cmp: optimize comparison for 16-bytes
  netfilter: bitwise: improve error goto labels
  netfilter: nf_tables: upfront validation of data via nft_data_init()
  netfilter: nf_tables: 

[Kernel-packages] [Bug 1990554] Re: Jammy update: v5.15.62 upstream stable release

[Stefan Bader]

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

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

Title:
  Jammy update: v5.15.62 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

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:

     v5.15.62 upstream stable release
     from git://git.kernel.org/

  io_uring: use original request task for inflight tracking
  tee: add overflow check in register_shm_helper()
  net_sched: cls_route: disallow handle of 0
  ksmbd: prevent out of bound read for SMB2_WRITE
  ksmbd: fix heap-based overflow in set_ntacl_dacl()
  btrfs: only write the sectors in the vertical stripe which has data stripes
  btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()
  Linux 5.15.62
  UBUNTU: Upstream stable to v5.15.62

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990554/+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 1990564] Re: Jammy update: v5.15.63 upstream stable release

[Stefan Bader]

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

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

Title:
  Jammy update: v5.15.63 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

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:

     v5.15.63 upstream stable release
     from git://git.kernel.org/

  ALSA: info: Fix llseek return value when using callback
  ALSA: hda/realtek: Add quirk for Clevo NS50PU, NS70PU
  KVM: Unconditionally get a ref to /dev/kvm module when creating a VM
  x86/mm: Use proper mask when setting PUD mapping
  rds: add missing barrier to release_refill
  locking/atomic: Make test_and_*_bit() ordered on failure
  drm/nouveau: recognise GA103
  drm/ttm: Fix dummy res NULL ptr deref bug
  drm/amd/display: Check correct bounds for stream encoder instances for DCN303
  ata: libata-eh: Add missing command name
  mmc: pxamci: Fix another error handling path in pxamci_probe()
  mmc: pxamci: Fix an error handling path in pxamci_probe()
  mmc: meson-gx: Fix an error handling path in meson_mmc_probe()
  btrfs: unset reloc control if transaction commit fails in 
prepare_to_relocate()
  btrfs: reset RO counter on block group if we fail to relocate
  btrfs: fix lost error handling when looking up extended ref on log replay
  cifs: Fix memory leak on the deferred close
  x86/kprobes: Fix JNG/JNLE emulation
  tracing/eprobes: Do not allow eprobes to use $stack, or % for regs
  tracing/eprobes: Do not hardcode $comm as a string
  tracing/eprobes: Have event probes be consistent with kprobes and uprobes
  tracing/probes: Have kprobes and uprobes use $COMM too
  tracing: Have filter accept "common_cpu" to be consistent
  ALSA: usb-audio: More comprehensive mixer map for ASUS ROG Zenith II
  dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be optional
  can: ems_usb: fix clang's -Wunaligned-access warning
  apparmor: fix quiet_denied for file rules
  Revert "UBUNTU: SAUCE: apparmor: drop prefixing abs root labels with '='"
  apparmor: fix absroot causing audited secids to begin with =
  apparmor: Fix failed mount permission check error message
  apparmor: fix aa_label_asxprint return check
  apparmor: fix setting unconfined mode on a loaded profile
  apparmor: fix overlapping attachment computation
  apparmor: fix reference count leak in aa_pivotroot()
  apparmor: Fix memleak in aa_simple_write_to_buffer()
  Documentation: ACPI: EINJ: Fix obsolete example
  NFSv4.1: Don't decrease the value of seq_nr_highest_sent
  NFSv4.1: Handle NFS4ERR_DELAY replies to OP_SEQUENCE correctly
  NFSv4: Fix races in the legacy idmapper upcall
  NFSv4.1: RECLAIM_COMPLETE must handle EACCES
  NFSv4/pnfs: Fix a use-after-free bug in open
  BPF: Fix potential bad pointer dereference in bpf_sys_bpf()
  bpf: Don't reinit map value in prealloc_lru_pop
  bpf: Acquire map uref in .init_seq_private for array map iterator
  bpf: Acquire map uref in .init_seq_private for hash map iterator
  bpf: Acquire map uref in .init_seq_private for sock local storage map iterator
  bpf: Acquire map uref in .init_seq_private for sock{map,hash} iterator
  bpf: Check the validity of max_rdwr_access for sock local storage map iterator
  can: mcp251x: Fix race condition on receive interrupt
  can: j1939: j1939_session_destroy(): fix memory leak of skbs
  net: atlantic: fix aq_vec index out of range error
  m68k: coldfire/device.c: protect FLEXCAN blocks
  sunrpc: fix expiry of auth creds
  SUNRPC: Fix xdr_encode_bool()
  SUNRPC: Reinitialise the backchannel request buffers before reuse
  virtio_net: fix memory leak inside XPD_TX with mergeable
  devlink: Fix use-after-free after a failed reload
  net: phy: Warn about incorrect mdio_bus_phy_resume() state
  net: bcmgenet: Indicate MAC is in charge of PHY PM
  net: bgmac: Fix a BUG triggered by wrong bytes_compl
  selftests: forwarding: Fix failing tests with old libnet
  dt-bindings: arm: qcom: fix Alcatel OneTouch Idol 3 compatibles
  pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map
  pinctrl: qcom: msm8916: Allow CAMSS GP clocks to be muxed
  pinctrl: amd: Don't save/restore interrupt status and wake status bits
  pinctrl: sunxi: Add I/O bias setting for H6 R-PIO
  pinctrl: qcom: sm8250: Fix PDC map
  Input: exc3000 - fix return value check of wait_for_completion_timeout
  octeontx2-pf: Fix NIX_AF_TL3_TL2X_LINKX_CFG 

[Kernel-packages] [Bug 1990162] Re: Jammy update: v5.15.61 upstream stable release

[Stefan Bader]

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

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

Title:
  Jammy update: v5.15.61 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

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:

     v5.15.61 upstream stable release
     from git://git.kernel.org/

  Makefile: link with -z noexecstack --no-warn-rwx-segments
  x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
  Revert "pNFS: nfs3_set_ds_client should set NFS_CS_NOPING"
  scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover"
  pNFS/flexfiles: Report RDMA connection errors to the server
  NFSD: Clean up the show_nf_flags() macro
  nfsd: eliminate the NFSD_FILE_BREAK_* flags
  ALSA: usb-audio: Add quirk for Behringer UMC202HD
  ALSA: bcd2000: Fix a UAF bug on the error path of probing
  ALSA: hda/realtek: Add quirk for Clevo NV45PZ
  ALSA: hda/realtek: Add quirk for HP Spectre x360 15-eb0xxx
  wifi: mac80211_hwsim: fix race condition in pending packet
  wifi: mac80211_hwsim: add back erroneously removed cast
  wifi: mac80211_hwsim: use 32-bit skb cookie
  add barriers to buffer_uptodate and set_buffer_uptodate
  lockd: detect and reject lock arguments that overflow
  HID: hid-input: add Surface Go battery quirk
  HID: wacom: Only report rotation for art pen
  HID: wacom: Don't register pad_input for touch switch
  KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case
  KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case
  KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
  KVM: s390: pv: don't present the ecall interrupt twice
  KVM: x86: Split kvm_is_valid_cr4() and export only the non-vendor bits
  KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value
  KVM: nVMX: Account for KVM reserved CR4 bits in consistency checks
  KVM: nVMX: Inject #UD if VMXON is attempted with incompatible CR0/CR4
  KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
  KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
  KVM: nVMX: Always enable TSC scaling for L2 when it was enabled for L1
  KVM: x86: Tag kvm_mmu_x86_module_init() with __init
  KVM: x86: do not report preemption if the steal time cache is stale
  KVM: x86: revalidate steal time cache if MSR value changes
  riscv: set default pm_power_off to NULL
  ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
  ALSA: hda/cirrus - support for iMac 12,1 model
  ALSA: hda/realtek: Add quirk for another Asus K42JZ model
  ALSA: hda/realtek: Add a quirk for HP OMEN 15 (8786) mute LED
  tty: vt: initialize unicode screen buffer
  vfs: Check the truncate maximum size in inode_newsize_ok()
  fs: Add missing umask strip in vfs_tmpfile
  thermal: sysfs: Fix cooling_device_stats_setup() error code path
  fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters
  fbcon: Fix accelerated fbdev scrolling while logo is still shown
  usbnet: Fix linkwatch use-after-free on disconnect
  fix short copy handling in copy_mc_pipe_to_iter()
  crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory 
leak
  ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh()
  parisc: Fix device names in /proc/iomem
  parisc: Drop pa_swapper_pg_lock spinlock
  parisc: Check the return value of ioremap() in lba_driver_probe()
  parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode
  riscv:uprobe fix SR_SPIE set/clear handling
  dt-bindings: riscv: fix SiFive l2-cache's cache-sets
  RISC-V: kexec: Fixup use of smp_processor_id() in preemptible context
  RISC-V: Fixup get incorrect user mode PC for kernel mode regs
  RISC-V: Fixup schedule out issue in machine_crash_shutdown()
  RISC-V: Add modules to virtual kernel memory layout dump
  rtc: rx8025: fix 12/24 hour mode detection on RX-8035
  drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error
  drm/shmem-helper: Add missing vunmap on error
  drm/vc4: hdmi: Disable audio if dmas property is present but empty
  drm/hyperv-drm: Include framebuffer and EDID headers
  drm/nouveau: fix another off-by-one in nvbios_addr
  drm/nouveau: Don't pm_runtime_put_sync(), only pm_runtime_put_autosuspend()
  drm/nouveau/acpi: Don't print error when we get -EINPROGRESS from pm_runtime
  drm/nouveau/kms: Fix failure path for creating D

[Kernel-packages] [Bug 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

[Daniel Swarbrick]

I'm also seeing failure to boot with linux-image-5.19.0-18-generic, on a
Dell XPS 15 9510 (with NVIDIA RTX 3050 Ti). It was the only update that
I installed yesterday. Prior to that, kinetic has been remarkably
reliable for a pre-release.

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

Title:
  Failure to boot with linux-image-5.19.0-18-generic

Status in linux-signed package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  Since the last kernel update today my system stops in the middle of the boot 
process and does not reach KDE.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-05-26 (495 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm 
nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G 
hugepages=4
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  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 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic uec-images
  Uname: Linux 5.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/24/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4204
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1991703/+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 1991703] Re: Failure to boot with linux-image-5.19.0-18-generic

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failure to boot with linux-image-5.19.0-18-generic

Status in linux-signed package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  Since the last kernel update today my system stops in the middle of the boot 
process and does not reach KDE.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-05-26 (495 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_drm 
nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgkubuntu-root ro default_hugepagesz=1G hugepagesz=1G 
hugepages=4
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  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 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic uec-images
  Uname: Linux 5.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/24/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4204
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4204:bd02/24/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[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/1991779

Title:
  Touchpad not being detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Details as mentioned here - https://wiki.ubuntu.com/DebuggingTouchpadDetection
  Laptop model - HP ProBook 450 G3
  Touchpad manufacturer - Synaptics
  Seeing issue since - Not sure, a few months

  My touchpad started malfunctioning (pointer moving by itself). To be
  able to finish my work, I had disabled my touchpad temporarily using
  "xinput disable https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991779/+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 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot

[Mariusz Dykierek]

It is i915 that fails. recovery boot works.
[1.671342] kernel: Call Trace:
[1.671344] kernel:  
[1.671346] kernel:  ? __intel_wait_for_register_fw+0xf5/0x200 [i915]
[1.671406] kernel:  intel_bw_init_hw+0x120/0x140 [i915]
[1.671470] kernel:  i915_driver_hw_probe+0x2cc/0x370 [i915]
[1.671525] kernel:  i915_driver_probe+0x19b/0x490 [i915]
[1.671574] kernel:  ? drm_privacy_screen_get+0x16d/0x190 [drm]
[1.671604] kernel:  ? acpi_dev_found+0x64/0x80
[1.671609] kernel:  i915_pci_probe+0x56/0x150 [i915]
[1.671664] kernel:  local_pci_probe+0x44/0x90
[1.671667] kernel:  pci_call_probe+0x55/0x190
[1.671669] kernel:  pci_device_probe+0x84/0x120
[1.671672] kernel:  really_probe+0x1dc/0x3b0
[1.671675] kernel:  __driver_probe_device+0x12c/0x1b0
[1.671677] kernel:  driver_probe_device+0x24/0xd0
[1.671679] kernel:  __driver_attach+0xe0/0x210
[1.671681] kernel:  ? __device_attach_driver+0x130/0x130
[1.671683] kernel:  bus_for_each_dev+0x8d/0xe0
[1.671686] kernel:  driver_attach+0x1e/0x30
[1.671687] kernel:  bus_add_driver+0x187/0x230
[1.671689] kernel:  driver_register+0x8f/0x100
[1.671691] kernel:  __pci_register_driver+0x62/0x70
[1.671694] kernel:  i915_pci_register_driver+0x23/0x30 [i915]
[1.671744] kernel:  i915_init+0x3b/0xf2 [i915]
[1.671804] kernel:  ? 0xc08b
[1.671806] kernel:  do_one_initcall+0x5b/0x240
[1.671810] kernel:  do_init_module+0x50/0x210
[1.671813] kernel:  load_module+0xb7d/0xcd0
[1.671815] kernel:  __do_sys_finit_module+0xc4/0x140
[1.671818] kernel:  ? __do_sys_finit_module+0xc4/0x140
[1.671820] kernel:  __x64_sys_finit_module+0x18/0x30
[1.671822] kernel:  do_syscall_64+0x58/0x90
[1.671826] kernel:  ? do_syscall_64+0x67/0x90
[1.671828] kernel:  ? __do_sys_newfstatat+0x53/0x90
[1.671831] kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
[1.671834] kernel:  ? syscall_exit_to_user_mode+0x26/0x50
[1.671837] kernel:  ? __x64_sys_newfstatat+0x1c/0x30
[1.671839] kernel:  ? do_syscall_64+0x67/0x90
[1.671841] kernel:  ? do_syscall_64+0x67/0x90
[1.671843] kernel:  ? sysvec_call_function+0x4b/0xd0
[1.671845] kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: 

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

The above hda-verb command didn't get the speaker working.
No sound yet.
Here I have attached my dmesg output. Hope that gets us somewhere useful.
Thanks!

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+attachment/5621391/+files/dmesg.txt

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1991779] [NEW] Touchpad not being detected

[Palash Aggrawal]

Public bug reported:

Details as mentioned here - https://wiki.ubuntu.com/DebuggingTouchpadDetection
Laptop model - HP ProBook 450 G3
Touchpad manufacturer - Synaptics
Seeing issue since - Not sure, a few months

My touchpad started malfunctioning (pointer moving by itself). To be
able to finish my work, I had disabled my touchpad temporarily using
"xinput disable https://bugs.launchpad.net/bugs/1991779/+attachment/5621374/+files/devices

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

Title:
  Touchpad not being detected

Status in linux package in Ubuntu:
  New

Bug description:
  Details as mentioned here - https://wiki.ubuntu.com/DebuggingTouchpadDetection
  Laptop model - HP ProBook 450 G3
  Touchpad manufacturer - Synaptics
  Seeing issue since - Not sure, a few months

  My touchpad started malfunctioning (pointer moving by itself). To be
  able to finish my work, I had disabled my touchpad temporarily using
  "xinput disable https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991779/+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 1991774] Missing required logs.

[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 1991774

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

Title:
  Memory leak while using NFQUEUE to delegate the decision on TCP
  packets to userspace processes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  Environment: v4.15.0-177-generic Xenial ESM

  Using NFQUEUE to delegate the decision on TCP packets to userspace processes 
will cause memory leak.
  The symptom is that TCP slab objects will accumulate and eventually cause OOM.

  [Fix]

  There is a discrepancy between backport and upstream commit.

  [Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 9eed51e920e8..980daa6e1e3a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct 
nf_queue_handler *qh);
   void nf_unregister_queue_handler(void);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_free(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 5ab0680db445..e39549c55945 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct 
nf_queue_entry *entry)
   }

   /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
   {
    struct nf_hook_state *state = &entry->state;

  + if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
  + return false;
  +
    dev_hold(state->in);
    dev_hold(state->out);
  - if (state->sk)
  - sock_hold(state->sk);

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
    dev_hold(entry->physin);
    dev_hold(entry->physout);
   #endif
  + return true;
   }
   EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);

  @@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
  struct nf_hook_state *state,

    __nf_queue_entry_init_physdevs(entry);

  - nf_queue_entry_get_refs(entry);
  + if (!nf_queue_entry_get_refs(entry)) {
  + kfree(entry);
  + return -ENOTCONN;
  + }

    switch (entry->state.pf) {
    case AF_INET:
  diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
  index ea2d9c2a44cf..64a6acb6aeae 100644
  --- a/net/netfilter/nfnetlink_queue.c
  +++ b/net/netfilter/nfnetlink_queue.c
  @@ -710,9 +710,15 @@ static struct nf_queue_entry *
   nf_queue_entry_dup(struct nf_queue_entry *e)
   {
    struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
  - if (entry)
  - nf_queue_entry_get_refs(entry);
  - return entry;
  +
  + if (!entry)
  + return NULL;
  +
  + if (nf_queue_entry_get_refs(entry))
  + return entry;
  +
  + kfree(entry);
  + return NULL;
   }

   #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)

  [Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 814058d0f167..f38cc6092c5a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const 
struct nf_queue_handler *q
   void nf_unregister_queue_handler(struct net *net);
   void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
   void nf_queue_entry_release_refs(struct nf_queue_entry *entry);

   static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 59340b3ef7ef..dbc45165c533 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -80,10 +80,13 @@ void nf_queue_entry_release_refs(struct nf_queue_entry 
*entry)
   EXPORT_SYMBOL_GPL(nf_queu

[Kernel-packages] [Bug 1991774] Re: Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes

[ChengEn, Du]

** Description changed:

  [Impact]
  
  Environment: v4.15.0-177-generic Xenial ESM
  
  Using NFQUEUE to delegate the decision on TCP packets to userspace processes 
will cause memory leak.
  The symptom is that TCP slab objects will accumulate and eventually cause OOM.
  
  [Fix]
  
  There is a discrepancy between backport and upstream commit.
  
  [Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 9eed51e920e8..980daa6e1e3a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct 
nf_queue_handler *qh);
-  void nf_unregister_queue_handler(void);
-  void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
-  
+  void nf_unregister_queue_handler(void);
+  void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
+ 
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
-  void nf_queue_entry_free(struct nf_queue_entry *entry);
-  
-  static inline void init_hashrandom(u32 *jhash_initval)
+  void nf_queue_entry_free(struct nf_queue_entry *entry);
+ 
+  static inline void init_hashrandom(u32 *jhash_initval)
  diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
  index 5ab0680db445..e39549c55945 100644
  --- a/net/netfilter/nf_queue.c
  +++ b/net/netfilter/nf_queue.c
  @@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct 
nf_queue_entry *entry)
-  }
-  
-  /* Bump dev refs so they don't vanish while packet is out */
+  }
+ 
+  /* Bump dev refs so they don't vanish while packet is out */
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
-  {
-   struct nf_hook_state *state = &entry->state;
-  
+  {
+   struct nf_hook_state *state = &entry->state;
+ 
  + if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
  + return false;
  +
-   dev_hold(state->in);
-   dev_hold(state->out);
+   dev_hold(state->in);
+   dev_hold(state->out);
  - if (state->sk)
  - sock_hold(state->sk);
-  
-  #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
-   dev_hold(entry->physin);
-   dev_hold(entry->physout);
-  #endif
+ 
+  #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
+   dev_hold(entry->physin);
+   dev_hold(entry->physout);
+  #endif
  + return true;
-  }
-  EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);
-  
- @@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const struct 
nf_hook_state *state,
-  
-   __nf_queue_entry_init_physdevs(entry);
-  
+  }
+  EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);
+ 
+ @@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
+ struct nf_hook_state *state,
+ 
+   __nf_queue_entry_init_physdevs(entry);
+ 
  - nf_queue_entry_get_refs(entry);
  + if (!nf_queue_entry_get_refs(entry)) {
  + kfree(entry);
  + return -ENOTCONN;
  + }
-  
-   switch (entry->state.pf) {
-   case AF_INET:
+ 
+   switch (entry->state.pf) {
+   case AF_INET:
  diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
  index ea2d9c2a44cf..64a6acb6aeae 100644
  --- a/net/netfilter/nfnetlink_queue.c
  +++ b/net/netfilter/nfnetlink_queue.c
  @@ -710,9 +710,15 @@ static struct nf_queue_entry *
-  nf_queue_entry_dup(struct nf_queue_entry *e)
-  {
-   struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
+  nf_queue_entry_dup(struct nf_queue_entry *e)
+  {
+   struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
  - if (entry)
  - nf_queue_entry_get_refs(entry);
  - return entry;
  +
  + if (!entry)
  + return NULL;
  +
  + if (nf_queue_entry_get_refs(entry))
  + return entry;
  +
  + kfree(entry);
  + return NULL;
-  }
-  
-  #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
-  
+  }
+ 
+  #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
+ 
  [Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
  diff --git a/include/net/netfilter/nf_queue.h 
b/include/net/netfilter/nf_queue.h
  index 814058d0f167..f38cc6092c5a 100644
  --- a/include/net/netfilter/nf_queue.h
  +++ b/include/net/netfilter/nf_queue.h
  @@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const 
struct nf_queue_handler *q
-  void nf_unregister_queue_handler(struct net *net);
-  void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
-  
+  void nf_unregister_queue_handler(struct net *net);
+  void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
+ 
  -void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
  +bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
-  void nf_queue_entry_release_refs(struct nf_queue_entry *entry);
-  
-  static inline void init_hashrandom(u32 *jhash_initval)
+  void nf_queue_entry_rel

[Kernel-packages] [Bug 1991774] [NEW] Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes

[ChengEn, Du]

Public bug reported:

[Impact]

Environment: v4.15.0-177-generic Xenial ESM

Using NFQUEUE to delegate the decision on TCP packets to userspace processes 
will cause memory leak.
The symptom is that TCP slab objects will accumulate and eventually cause OOM.

[Fix]

There is a discrepancy between backport and upstream commit.

[Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
diff --git a/include/net/netfilter/nf_queue.h b/include/net/netfilter/nf_queue.h
index 9eed51e920e8..980daa6e1e3a 100644
--- a/include/net/netfilter/nf_queue.h
+++ b/include/net/netfilter/nf_queue.h
@@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct nf_queue_handler 
*qh);
 void nf_unregister_queue_handler(void);
 void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

-void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
 void nf_queue_entry_free(struct nf_queue_entry *entry);

 static inline void init_hashrandom(u32 *jhash_initval)
diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
index 5ab0680db445..e39549c55945 100644
--- a/net/netfilter/nf_queue.c
+++ b/net/netfilter/nf_queue.c
@@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct 
nf_queue_entry *entry)
 }

 /* Bump dev refs so they don't vanish while packet is out */
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
 {
  struct nf_hook_state *state = &entry->state;

+   if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
+   return false;
+
  dev_hold(state->in);
  dev_hold(state->out);
-   if (state->sk)
-   sock_hold(state->sk);

 #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
  dev_hold(entry->physin);
  dev_hold(entry->physout);
 #endif
+   return true;
 }
 EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);

@@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
struct nf_hook_state *state,

  __nf_queue_entry_init_physdevs(entry);

-   nf_queue_entry_get_refs(entry);
+   if (!nf_queue_entry_get_refs(entry)) {
+   kfree(entry);
+   return -ENOTCONN;
+   }

  switch (entry->state.pf) {
  case AF_INET:
diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
index ea2d9c2a44cf..64a6acb6aeae 100644
--- a/net/netfilter/nfnetlink_queue.c
+++ b/net/netfilter/nfnetlink_queue.c
@@ -710,9 +710,15 @@ static struct nf_queue_entry *
 nf_queue_entry_dup(struct nf_queue_entry *e)
 {
  struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
-   if (entry)
-   nf_queue_entry_get_refs(entry);
-   return entry;
+
+   if (!entry)
+   return NULL;
+
+   if (nf_queue_entry_get_refs(entry))
+   return entry;
+
+   kfree(entry);
+   return NULL;
 }

 #if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)

[Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
diff --git a/include/net/netfilter/nf_queue.h b/include/net/netfilter/nf_queue.h
index 814058d0f167..f38cc6092c5a 100644
--- a/include/net/netfilter/nf_queue.h
+++ b/include/net/netfilter/nf_queue.h
@@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const struct 
nf_queue_handler *q
 void nf_unregister_queue_handler(struct net *net);
 void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);

-void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
 void nf_queue_entry_release_refs(struct nf_queue_entry *entry);

 static inline void init_hashrandom(u32 *jhash_initval)
diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
index 59340b3ef7ef..dbc45165c533 100644
--- a/net/netfilter/nf_queue.c
+++ b/net/netfilter/nf_queue.c
@@ -80,10 +80,13 @@ void nf_queue_entry_release_refs(struct nf_queue_entry 
*entry)
 EXPORT_SYMBOL_GPL(nf_queue_entry_release_refs);

 /* Bump dev refs so they don't vanish while packet is out */
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
 {
  struct nf_hook_state *state = &entry->state;

+   if (state->sk && !refcount_inc_not_zero(&state->sk->sk_refcnt))
+   return false;
+
  if (state->in)
   dev_hold(state->in);
  if (state->out)
@@ -102,6 +105,7 @@ void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
dev_hold(physdev);
  }
 #endif
+   return true;
 }
 EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);

@@ -159,7 +163,11 @@ static int __nf_queue(struct sk_buff *skb, const struct 
nf_hook_state *state,
   .size= sizeof(*entry) + afinfo->route_key_size,
  };

-   nf_queue_entry_get_refs(entry);
+   if (!nf_queue_entry_get_refs(entry)) {
+   kfree(entry);
+   return -ENOTCONN;
+   }
+
  afinfo->saveroute(skb, entry);
  status = qh->outfn(entry, queuenum);

diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetl

[Kernel-packages] [Bug 1239459] Re: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds

[Mahar]

Awesome post and a very helpful topic I will share it with my friends so that 
they can use this post. Keep it up.
https://maharpc.com/master-pdf-editor-crack/
https://maharpc.com/adobe-acrobat-pro-dc-crack/

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  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.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1239459/+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 1962485] Re: Kernel Crash [general protection fault: 0000 [#1] SMP NOPTI]

[Matthew Ruffell]

** Tags added: sts

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

Title:
  Kernel Crash [general protection fault:  [#1] SMP NOPTI]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am running openstack xena release on ubuntu focal. Today my compute
  node running ubuntu focal crashed with due to kernel and dump has been
  generated in /var/crash/. Below is the kernel trace in crash dump.

  [455151.890114] general protection fault:  [#1] SMP NOPTI
  [455151.890285] CPU: 43 PID: 83232 Comm: qemu-system-x86 Kdump: loaded 
Tainted: G   OE 5.4.0-88-generic #99-Ubuntu
  [455151.890612] Hardware name: Dell Inc. PowerEdge R6525/X, BIOS 2.5.6 
10/06/2021
  [455151.890842] RIP: 0010:count_subheaders.part.0+0x26/0x60
  [455151.890998] Code: 00 00 00 90 0f 1f 44 00 00 48 83 3f 00 74 4d 55 48 89 
e5 41 55 45 31 ed 41 54 45 31 e4 53 48 89 fb 48 8b 7b 18 48 85 ff 74 23 <48> 83 
3f 00 74 25 e8 cf ff ff ff 41 
  01 c5 48 83 c3 40 48 83 3b 00
  [455151.891552] RSP: 0018:a6b477487b88 EFLAGS: 00010202
  [455151.891707] RAX:  RBX: 9387c594f280 RCX: 

  [455151.891918] RDX: 0060 RSI: 9390702a72c0 RDI: 
0314a8c0f1b16f3e
  [455151.892130] RBP: a6b477487ba0 R08:  R09: 
bc6ed7f0
  [455151.892341] R10: a6b477487cd0 R11: 0001 R12: 

  [455151.892552] R13:  R14: 9391e5684000 R15: 
bd5f9880
  [455151.892767] FS:  7f69950c75c0() GS:9391feac() 
knlGS:
  [455151.893016] CS:  0010 DS:  ES:  CR0: 80050033
  [455151.893207] CR2: 7f61e9e45000 CR3: 017c54afa000 CR4: 
00340ee0
  [455151.893434] Call Trace:
  [455151.893514]  count_subheaders.part.0+0x31/0x60
  [455151.893646]  unregister_sysctl_table+0x30/0x90
  [455151.893781]  unregister_net_sysctl_table+0xe/0x10
  [455151.893922]  __devinet_sysctl_unregister.isra.0+0x2c/0x60
  [455151.894082]  devinet_sysctl_unregister+0x29/0x40
  [455151.894220]  inetdev_event+0x1e8/0x560
  [455151.894334]  ? skb_dequeue+0x5f/0x70
  [455151.89]  notifier_call_chain+0x55/0x80
  [455151.894565]  ? notifier_call_chain+0x55/0x80
  [455151.894693]  raw_notifier_call_chain+0x16/0x20
  [455151.894829]  call_netdevice_notifiers_info+0x2e/0x60
  [455151.894983]  ? tun_show_owner+0x60/0x60
  [455151.895098]  rollback_registered_many+0x36e/0x520
  [455151.895239]  unregister_netdevice_queue+0x94/0x120
  [455151.895383]  __tun_detach+0x421/0x430
  [455151.895495]  tun_chr_close+0x3a/0x70
  [455151.895605]  __fput+0xcc/0x260
  [455151.895698]  fput+0xe/0x10
  [455151.895792]  task_work_run+0x8f/0xb0
  [455151.895903]  exit_to_usermode_loop+0x131/0x160
  [455151.896036]  do_syscall_64+0x163/0x190
  [455151.896150]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [455151.896302] RIP: 0033:0x7f69965ba3fb
  [455151.896410] Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 
18 89 7c 24 0c e8 f3 fb ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 
00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 31 fc ff ff 8b 44
  [455151.896975] RSP: 002b:7ffdff14b350 EFLAGS: 0293 ORIG_RAX: 
0003
  [455151.897201] RAX:  RBX: 557fe0875e50 RCX: 
7f69965ba3fb
  [455151.897412] RDX: 557fe0748f40 RSI: 0001 RDI: 
002b
  [455151.897637] RBP: 557fe0887460 R08:  R09: 

  [455151.904390] R10: 0032 R11: 0293 R12: 
557fe0875e50
  [455151.911165] R13: 0001 R14: 557fe09efc10 R15: 
557fe0747900

  I didn't find any documented details on kernel 5.4 for this bug. I
  have uploaded the logs via ubuntu-bug linux command.

  # uname -a
  Linux kvm03-a1-r01-khi04.rapid.pk 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 
17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 5.4.0-88.99-generic 5.4.140

  I am using Dell R6525 with EPYC 7532 CPUs.

  Let me know if there is there are more information needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-88-generic 5.4.0-88.99
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 28 17:38 seq
   crw-rw 1 root audio 116, 33 Feb 28 17:38 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Mon Feb 28 21:20:20 2022
  InstallationDate: Installed on 2021-07-29 (214 days ago)
  InstallationMedia: Ubuntu-Ser

[Kernel-packages] [Bug 1239459] Re: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds

[jordanmichael07]

Thanks for Sharing such an amazing article. Keep working. Your Site is very 
nice, and it's very helping us.. this post is unique and interesting, thank you 
for sharing this awesome information.
https://bestproductkey.com/windows-10-crack/

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  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.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1239459/+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 1991551] Re: i2c-mlxbf.c: Sync up driver with upstreaming

[Stefan Bader]

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

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

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

** Changed in: linux-bluefield (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => Asmaa Mnebhi (asmaam)

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

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => Asmaa Mnebhi (asmaam)

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

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

Title:
  i2c-mlxbf.c: Sync up driver with upstreaming

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

Bug description:
  SRU Justification:

  [Impact]

  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4)
  and Jammy (5.15) and cherry-pick all changes from linux-next master.

  IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
  upgrading the UEFI firmware version. For BF1 and BF2 however, this
  driver should be backward compatible with older UEFI versions.

  [Fix]

  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from
  linux-next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.

  * i2c: mlxbf: incorrect base address passed during io write
  From 


  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 


  * i2c: mlxbf: remove IRQF_ONESHOT
  From 


  * i2c: mlxbf: Fix frequency calculation
  From 


  * i2c: mlxbf: support lock mechanism
  From 


  * i2c: mlxbf: add multi slave functionality
  From 


  * i2c: mlxbf: support BlueField-3 SoC
  From 


  * i2c: mlxbf: remove device tree support
  From 


  * Also add the i2c driver version to keep track of the changes
  internally.

  [Test Case]

  * Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
  * Check that the i2c module can be removed and reloaded without errors.
  * Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
  * Run ipmitool from the BMC as well: ipmitool -I ipmb mc info
  * This driver should be backward compatible
  * Make sure this driver is backward compatible with older UEFI version (only 
applicable for BF1 and BF2)
  * Make sure this driver works for BF1, BF2 and BF3 with the latest UEFI 
version.

  [Regression Potential]

  * The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
  * The i2c driver would fail to load due to a bug
  * IPMB code which utilises the i2c driver fails to work (ipmitool commands)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1991551/+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 1991704] Re: New Kinetic kernel (5.19.0-18-generic) won't boot

[Daniel van Vugt]

** Tags added: rls-kk-incoming

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

Title:
  New Kinetic kernel (5.19.0-18-generic) won't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  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-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  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 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1991286] Re: package linux-tools-5.15.0-48 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au

[Alexey Nikitin]

I have a similar problem

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

Title:
  package linux-tools-5.15.0-48 (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet
  linux-lowlatency-tools-5.15.0-48 5.15.0-48.54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bonjour,

  Des paquets synaptic ne s'installent pas.
  Avec Synaptic, il est difficile de savoir quoi installer alors qu'avec Ubuntu 
Software, les
  icones informaient tout de suite de quoi il s'agissait.

  Ubuntu software ne fonctionne pas, comment faire ?

  Avec mes remerciements

  Marie-Hélène

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-5.15.0-48 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marie  1863 F pulseaudio
   /dev/snd/controlC0:  marie  1863 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Sep 29 16:12:08 2022
  ErrorMessage: tentative de remplacement de « 
/usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet 
linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  InstallationDate: Installed on 2022-08-21 (39 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: ASUSTeK COMPUTER INC. X540YA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b3fc9ef4-e867-41a1-97ad-05154adeece5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  SourcePackage: linux
  Title: package linux-tools-5.15.0-48 (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/lib/libcpupower.so.5.15.0-48 », qui appartient aussi au paquet 
linux-lowlatency-tools-5.15.0-48 5.15.0-48.54
  UpgradeStatus: Upgraded to jammy on 2022-08-21 (38 days ago)
  dmi.bios.date: 12/31/2019
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540YA.323
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540YA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540YA.323:bd12/31/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX540YA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540YA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540YA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991286/+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 1991745] Re: snapd/2.57.1+22.10.1 ADT test failure with linux-raspi/5.19.0-1002.6

[Juerg Haefliger]

Maybe related: https://github.com/snapcore/spread/pull/155

** Description changed:

- This is a scripted bug report about ADT failures while running snapd
- tests for linux-raspi/5.19.0-1002.6 on kinetic. Whether this is caused
- by the dep8 tests of the tested source or the kernel has yet to be
- determined.
+ Testing failed on:
+ arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/s/snapd/20221003_171436_6321f@/log.gz
  
- Testing failed on:
- arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/s/snapd/20221003_171436_6321f@/log.gz
+ 
+ The tail of such a failure:
+ 
+ + snap install --classic go
+ 2022-10-03T17:10:59Z INFO Waiting for automatic snapd restart...
+ go 1.18.5 from Michael Hudson-Doyle (mwhudson) installed
+ + export GOPATH=/tmp/go
+ + /snap/bin/go install github.com/snapcore/spread/cmd/spread@latest
+ go: downloading github.com/snapcore/spread v0.0.0-20211206135717-b426a3f04d80
+ go: downloading github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e
+ go: downloading github.com/kr/text v0.1.0
+ go: downloading golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97
+ go: downloading golang.org/x/net v0.0.0-20210716203947-853a461950ff
+ go: downloading golang.org/x/oauth2 v0.0.0-20210628180205-a41e5a781914
+ go: downloading gopkg.in/tomb.v2 v2.0.0-20161208151619-d5d1b5820637
+ go: downloading gopkg.in/yaml.v2 v2.4.0
+ go: downloading golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1
+ go: downloading cloud.google.com/go v0.65.0
+ go: downloading golang.org/x/sys v0.0.0-20210615035016-665e8c7367d1
+ + groupadd --gid 12345 test
+ + adduser --uid 12345 --gid 12345 --disabled-password --gecos test
+ Adding user `test' ...
+ Adding new user `test' (12345) with group `test' ...
+ Creating home directory `/home/test' ...
+ Copying files from `/etc/skel' ...
+ + cat
+ + /tmp/go/bin/spread -v autopkgtest:adt-local:tests/smoke/
+ 2022-10-03 17:13:16 Found /tmp/autopkgtest.WgVVbr/build.gDT/src/spread.yaml.
+ 2022-10-03 17:13:20 Project content is packed for delivery (11.01MB).
+ 2022-10-03 17:13:20 Sequence of jobs produced with -seed=1664817200
+ 2022-10-03 17:13:20 If killed, discard servers with: spread -reuse-pid=3216 
-discard
+ 2022-10-03 17:13:20 Allocating autopkgtest:adt-local...
+ 2022-10-03 17:13:20 Waiting for autopkgtest:adt-local to make SSH available 
at localhost:22...
+ 2022-10-03 17:13:20 Allocated autopkgtest:adt-local.
+ 2022-10-03 17:13:20 Connecting to autopkgtest:adt-local...
+ 2022-10-03 17:14:20 Discarding autopkgtest:adt-local, cannot connect: cannot 
connect to autopkgtest:adt-local: ssh: handshake failed: ssh: unable to 
authenticate, attempted methods [none], no supported methods remain
+ 2022-10-03 17:14:20 Successful tasks: 0
+ 2022-10-03 17:14:20 Aborted tasks: 4
+ error: unsuccessful run
+ autopkgtest [17:14:20]: test integrationtests: ---]
+ integrationtests FAIL non-zero exit status 1
+ autopkgtest [17:14:21]: test integrationtests: - - - - - - - - - - results - 
- - - - - - - - -
+ autopkgtest [17:14:22]:  summary
+ integrationtests FAIL non-zero exit status 1

** Also affects: snapd (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** No longer affects: linux-raspi (Ubuntu)

** No longer affects: linux-raspi (Ubuntu Kinetic)

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-kernel-tests

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

Title:
  snapd/2.57.1+22.10.1 ADT test failure with linux-raspi/5.19.0-1002.6

Status in snapd package in Ubuntu:
  New
Status in snapd source package in Kinetic:
  New

Bug description:
  Testing failed on:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/s/snapd/20221003_171436_6321f@/log.gz

  
  The tail of such a failure:

  + snap install --classic go
  2022-10-03T17:10:59Z INFO Waiting for automatic snapd restart...
  go 1.18.5 from Michael Hudson-Doyle (mwhudson) installed
  + export GOPATH=/tmp/go
  + /snap/bin/go install github.com/snapcore/spread/cmd/spread@latest
  go: downloading github.com/snapcore/spread v0.0.0-20211206135717-b426a3f04d80
  go: downloading github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e
  go: downloading github.com/kr/text v0.1.0
  go: downloading golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97
  go: downloading golang.org/x/net v0.0.0-20210716203947-853a461950ff
  go: downloading golang.org/x/oauth2 v0.0.0-20210628180205-a41e5a781914
  go: downloading gopkg.in/tomb.v2 v2.0.0-20161208151619-d5d1b5820637
  go: downloading gopkg.in/yaml.v2 v2.4.0
  go: downloading golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1
  go: downloading cloud.google.com/