[Kernel-packages] [Bug 2028953] [NEW] upgrading from 22.04 to 23.04 failed

2023-07-28 Thread Balakumar R
Public bug reported:

did the release upgrade from 22.04 to 23.04 and got the following error and 
upgrade is failed and not able to proceed 
sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  endeavour endeavour-common g++-11 g++-11-multilib gnome-todo ieee-data 
krosspython lib32stdc++-11-dev libabsl20210324 libappimage0 libavcodec58 
libavformat58
  libavutil56 libcfitsio9 libdav1d5 libecal-2.0-1 libedataserverui-1.2-3 
libgnome-todo libhcrypto4-heimdal:i386 libilmbase25 libjs-mootools 
libkdecorations2private9
  libkf5alarmcalendar-data libkf5alarmcalendar5abi2 libkf5kipi-data 
libkf5kipi32.0.0 libkf5waylandserver5 libkwaylandserver5 libkwinxrenderutils13 
libldap-2.5-0 libmpdec3
  libopenexr25 libpoppler118 libprocps8 libpython3.10 libpython3.10-dev 
libpython3.10-minimal libpython3.10-stdlib libqgpgme7 libqpdf28 libre2-9 
libroken18-heimdal:i386
  libsnapd-glib1 libsnapd-qt1 libsrt1.4-gnutls libstdc++-11-dev libswresample3 
libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5 libx264-163 libx32stdc++-11-dev 
libzxingcore1
  pulseaudio-module-gsettings python3-typed-ast python3.10 python3.10-dev 
python3.10-minimal xfce4-notes xfce4-notes-plugin xubuntu-core
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  libpcsclite1
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up linux-image-6.2.0-26-generic (6.2.0-26.26) ...
Setting up linux-headers-6.2.0-26-generic (6.2.0-26.26) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-26-generic
Sign command: /usr/bin/kmodsign
Binary update-secureboot-policy not found, modules won't be signed

Running the pre_build script:
Real System.map was found in '/boot/System.map-6.2.0-26-generic'
Generate "/var/lib/dkms/veeamsnap/6.0.3.1221/build/config.h" for kernel 
"6.2.0-26-generic".
System map "/boot/System.map-6.2.0-26-generic".
Exported function "blk_mq_make_request" not found
Exported function "blk_alloc_queue_rh" not found
Exported function "submit_bio_noacct" was found
Address of the function "__request_module" was defined
Address of the function "blk_mq_submit_bio" was defined

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.2.0-26-generic -C /lib/modules/6.2.0-26-generic/build 
M=/var/lib/dkms/veeamsnap/6.0.3.1221/build modules(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.0-26-generic (x86_64)
Consult /var/lib/dkms/veeamsnap/6.0.3.1221/build/make.log for more information.
dkms autoinstall on 6.2.0-26-generic/x86_64 succeeded for broadcom-sta 
broadcom-sta
dkms autoinstall on 6.2.0-26-generic/x86_64 failed for veeamsnap(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.2.0-26-generic (--configure):
 installed linux-headers-6.2.0-26-generic package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-6.2.0-26-generic; however:
  Package linux-headers-6.2.0-26-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 6.2.0.26.26); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.

  No apport report written because the error message 
indicates its a followup error from a previous failure.
Processing triggers for 
linux-image-6.2.0-26-generic (6.2.0-26.26) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-26-generic
Sign command: /usr/bin/kmodsign
Binary update-secureboot-policy not found, modules won't be signed

Running the pre_build script:
Real System.map was found in '/boot/System.map-6.2.0-26-generic'
Generate "/var/lib/dkms/veeamsnap/6.0.3.1221/build/config.h" for kernel 
"6.2.0-26-generic".
System map "/boot/System.map-6.2.0-26-generic".
Exported function "blk_mq_make_request" not found
Exported function "blk_alloc_queue_rh" not found
Exported function "submit_bio_noacct" 

[Kernel-packages] [Bug 1882669] Re: Focal Azure AMD64 instances crash with ftrace/test.d/00basic/basic2.tc in ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test

2023-07-28 Thread Magali Lemes do Sacramento
Seems to still be found on f:linux-aws-fips, cycle 2023-07-10

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

Title:
  Focal Azure AMD64 instances crash with ftrace/test.d/00basic/basic2.tc
  in ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Focal:
  Confirmed
Status in linux-azure source package in Groovy:
  Fix Released

Bug description:
  Issue found on 5.4.0-1013.13

  The ftrace in ubuntu_kernel_selftests failed on the second test:
  # === Ftrace unit tests ===
  # [1] Basic trace file check  [PASS]
  # [2] Basic test for tracers
  (System hang here)

  Syslog:
  kernel: [ 2234.408225] in mmio_trace_init
  kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs...
  kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16
  kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16
  kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16
  kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16
  kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16
  kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16
  kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16
  kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16
  kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16
  kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16
  kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16
  kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16
  kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16
  kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16
  kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16
  kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16
  kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16
  kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16
  kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16
  kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16
  kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16
  kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16
  kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16
  kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16
  kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16
  kernel: [ 2235.573759] smpboot: CPU 26 is now offline
  kernel: [ 2235.575071] mmiotrace: CPU26 is down.
  kernel: [ 2235.585643] smpboot: CPU 27 is now offline
  kernel: [ 2235.586699] mmiotrace: CPU27 is down.
  kernel: [ 2235.609679] smpboot: CPU 28 is now offline
  kernel: [ 2235.610788] mmiotrace: CPU28 is down.
  kernel: [ 2235.633530] smpboot: CPU 29 is now offline
  kernel: [ 2235.634511] mmiotrace: CPU29 is down.
  kernel: [ 2235.653652] smpboot: CPU 30 is now offline
  kernel: [ 2235.655415] mmiotrace: CPU30 is down.
  kernel: [ 2235.678126] smpboot: CPU 31 is now offline
  kernel: [ 2235.679061] mmiotrace: CPU31 is down.
  kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events.
  kernel: [ 2235.679063] mmiotrace: enabled.
  kernel: [ 2235.679128] in mmio_trace_reset
  kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs...
  kernel: [ 2235.732157] mmiotrace: enabled CPU1.
  kernel: [ 2235.772207] mmiotrace: enabled CPU2.
  kernel: [ 2235.812216] mmiotrace: enabled CPU3.
  kernel: [ 2235.844220] mmiotrace: enabled CPU4.
  kernel: [ 2235.876211] mmiotrace: enabled CPU5.
  kernel: [ 2235.916159] mmiotrace: enabled CPU6.
  kernel: [ 2235.956214] mmiotrace: enabled CPU7.
  kernel: [ 2235.988145] mmiotrace: enabled CPU8.
  kernel: [ 2236.020214] mmiotrace: enabled CPU9.
  kernel: [ 2236.060207] mmiotrace: enabled CPU10.
  kernel: [ 2236.096208] mmiotrace: enabled CPU11.
  kernel: [ 2236.128205] mmiotrace: enabled CPU12.
  /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, 
balancing is broken
  kernel: [ 2236.168204] mmiotrace: enabled CPU13.
  kernel: [ 2236.200206] mmiotrace: enabled CPU14.
  kernel: [ 2236.232207] mmiotrace: enabled CPU15.
  kernel: [ 2236.264224] mmiotrace: enabled CPU16.
  kernel: [ 2236.300207] mmiotrace: enabled CPU17.
  kernel: [ 2236.332210] mmiotrace: enabled CPU18.
  kernel: [ 2236.372224] mmiotrace: enabled CPU19.
  kernel: [ 2236.404147] mmiotrace: enabled CPU20.
  kernel: [ 2236.452153] mmiotrace: enabled CPU21.
  kernel: [ 2236.492152] mmiotrace: enabled CPU22.
  kernel: [ 2236.524153] mmiotrace: enabled CPU23.
  kernel: [ 2236.564211] mmiotrace: enabled CPU24.
  kernel: [ 2236.612204] mmiotrace: enabled CPU25.
  kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a
  kernel: [ 2236.645769] mmiotrace: enabled CPU26.
  kernel: [ 2236.684537] smpboot: 

[Kernel-packages] [Bug 2028932] Re: ubuntu_bpf failed to build with j-oem-6.1.0-1018.18

2023-07-28 Thread Po-Hsu Lin
I just finished bisect between -1007 and -1008

ca6f352ba5c8ccde01289d433401f28e6c260e07 is the first bad commit
commit ca6f352ba5c8ccde01289d433401f28e6c260e07
Author: Andrii Nakryiko 
Date:   Mon May 8 23:55:02 2023 -0700

libbpf: fix offsetof() and container_of() to work with CO-RE

BugLink: https://bugs.launchpad.net/bugs/2028528

[ Upstream commit bdeeed3498c7871c17465bb4f11d1bc67f9098af ]

It seems like __builtin_offset() doesn't preserve CO-RE field
relocations properly. So if offsetof() macro is defined through
__builtin_offset(), CO-RE-enabled BPF code using container_of() will be
subtly and silently broken.

To avoid this problem, redefine offsetof() and container_of() in the
form that works with CO-RE relocations more reliably.

Fixes: 5fbc220862fc ("tools/libpf: Add offsetof/container_of macro in 
bpf_helpers.h")
Reported-by: Lennart Poettering 
Signed-off-by: Andrii Nakryiko 
Acked-by: Yonghong Song 
Link: https://lore.kernel.org/r/20230509065502.2306180-1-and...@kernel.org
Signed-off-by: Alexei Starovoitov 
Signed-off-by: Sasha Levin 
Signed-off-by: Timo Aaltonen 

 tools/lib/bpf/bpf_helpers.h | 15 ++-
 1 file changed, 10 insertions(+), 5 deletions(-)

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

Title:
  ubuntu_bpf failed to build with j-oem-6.1.0-1018.18

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  Issue found with J-oem-6.1.0-1018.18

  Test build failed with:
  CLNG-BPF [test_maps] test_check_mtu.bpf.o
  CLNG-BPF [test_maps] test_cls_redirect.bpf.o
make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an 
integral constant expression 
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of 
a reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
 ^

/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:86:33:
 note: expanded from macro 'offsetof'
#define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
 ^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an 
integral constant expression
sizeof(flow_ports_t) !=
^~~ 
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of 
a reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
 ^

/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:86:33:
 note: expanded from macro 'offsetof'
#define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
 ^
2 errors generated.
make[1]: *** [Makefile:531: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.bpf.o]
 Error 1
make: *** [Makefile:160: all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2028932/+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 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm

2023-07-28 Thread Po-Hsu Lin
Test is good on L-azure and j-hwe-6.2 6.2.0-26.26~22.04.1

** Tags removed: verification-needed-jammy verification-needed-lunar
** Tags added: verification-done-jammy verification-done-lunar

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

Title:
  ftrace in ubuntu_kernel_selftests failed with "check if duplicate
  events are caught" on J-5.15 P9 / J-kvm / L-kvm

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  Issue found on Jammy 5.15.0-36.37 with Power9 node baltar

  Test failed with:
  # [15] Generic dynamic event - check if duplicate events are caught [FAIL]

  Test Log:
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
   TAP version 13
   1..1
   # selftests: ftrace: ftracetest
   # === Ftrace unit tests ===
   # [1] Basic trace file check [PASS]
   # [2] Basic test for tracers [PASS]
   # [3] Basic trace clock test [PASS]
   # [4] Basic event tracing check  [PASS]
   # [5] Change the ringbuffer size [PASS]
   # [6] Snapshot and tracing setting   [PASS]
   # [7] trace_pipe and trace_marker[PASS]
   # [8] Test ftrace direct functions against tracers   [UNRESOLVED]
   # [9] Test ftrace direct functions against kprobes   [UNRESOLVED]
   # [10] Generic dynamic event - add/remove eprobe events  [PASS]
   # [11] Generic dynamic event - add/remove kprobe events  [PASS]
   # [12] Generic dynamic event - add/remove synthetic events   [PASS]
   # [13] Generic dynamic event - selective clear (compatibility)   [PASS]
   # [14] Generic dynamic event - generic clear event   [PASS]
   # [15] Generic dynamic event - check if duplicate events are caught  [FAIL]
   # [16] event tracing - enable/disable with event level files [PASS]
   # [17] event tracing - restricts events based on pid notrace filtering   
[PASS]
   # [18] event tracing - restricts events based on pid [PASS]
   # [19] event tracing - enable/disable with subsystem level files [PASS]
   # [20] event tracing - enable/disable with top level files   [PASS]
   # [21] Test trace_printk from module [PASS]
   # [22] ftrace - function graph filters with stack tracer [PASS]
   # [23] ftrace - function graph filters   [PASS]
   # [24] ftrace - function pid notrace filters [PASS]
   # [25] ftrace - function pid filters [PASS]
   # [26] ftrace - stacktrace filter command[PASS]
   # [27] ftrace - function trace with cpumask  [PASS]
   # [28] ftrace - test for function event triggers [PASS]
   # [29] ftrace - function trace on module [PASS]
   # [30] ftrace - function profiling   [PASS]
   # [31] ftrace - function profiler with function tracing  [PASS]
   # [32] ftrace - test reading of set_ftrace_filter[PASS]
   # [33] ftrace - test for function traceon/off triggers   [PASS]
   # [34] ftrace - test tracing error log support   [PASS]
   # [35] Test creation and deletion of trace instances while setting an event  
[PASS]
   # [36] Test creation and deletion of trace instances [PASS]
   # [37] Kprobe dynamic event - adding and removing[PASS]
   # [38] Kprobe dynamic event - busy event check   [PASS]
   # [39] Kprobe dynamic event with arguments   [PASS]
   # [40] Kprobe event with comm arguments  [PASS]
   # [41] Kprobe event string type argument [PASS]
   # [42] Kprobe event symbol argument  [PASS]
   # [43] Kprobe event argument syntax  [PASS]
   # [44] Kprobes event arguments with types[PASS]
   # [45] Kprobe event user-memory access   [UNSUPPORTED]
   # [46] Kprobe event auto/manual naming   [PASS]
   # [47] Kprobe dynamic event with function tracer [PASS]
   # [48] Create/delete multiprobe on kprobe event  [PASS]
   # [49] Kprobe event parser error log check   [PASS]
   # [50] Kretprobe dynamic event with arguments[PASS]
   # [51] Kretprobe dynamic event with maxactive[PASS]
   # [52] Kretprobe %return suffix test [PASS]
   # [53] Register/unregister many kprobe events[PASS]
   # [54] Kprobe profile[PASS]
   # [55] Uprobe event parser error log check   [PASS]
   # [56] test for the preemptirqsoff tracer[UNSUPPORTED]
   # [57] Meta-selftest: Checkbashisms  [PASS]
   # [58] Test wakeup tracer[PASS]
   # [59] Test wakeup RT tracer [PASS]
   # [60] event trigger - test inter-event histogram trigger expected fail 
actions  [XFAIL]
   # [61] event trigger - test field variable support   [PASS]
   # [62] event trigger - test multiple actions on hist trigger [PASS]
   # [63] event trigger - test inter-event histogram trigger onchange action
[PASS]
   # [64] event trigger - test inter-event 

[Kernel-packages] [Bug 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)

2023-07-28 Thread Jack Howarth
The nvidia support is still messed up under 6.2.0-26 for those using
secure boot. In previous iterations of the nvidia drivers and kernels,
one could always count on the linux-signatures-nvidia-6.2.0-26-generic
and linux-modules-nvidia-535-6.2.0-26-generic to use pre-signed kernel
modules rather than dkms if the Software  & Updates panel was used to
select the tested nvidia driver. Now they are forcing the installation
of dkms with nvidia-driver-535 instead. If you try to removed dkms, it
removes nvidia-driver-535 of course which makes all of the nvidia
packages marked as unused in 'sudo apt-get dist-upgrade'. Hopefully
Ubuntu will fix this regression at some point as it is really annoying.

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

Title:
  missing nvidia kernel module for generic kernel (linux-objects-
  nvidia-535-6.2.0-25-generic)

Status in linux-restricted-modules package in Ubuntu:
  Confirmed

Bug description:
  For latest generic kernel for Ubuntu 23.04 there in no package of kernel 
module.
  Present is for previous kernel:

  # aptitude search linux-objects-nvidia-535.*generic 
  i A linux-objects-nvidia-535-6.2.0-24-generic- Linux 
kernel nvidia modules for version 6.2.0-24 (objects)
  p   linux-objects-nvidia-535-open-6.2.0-24-generic   - Linux 
kernel nvidia modules for version 6.2.0-24 (objects)
  p   linux-objects-nvidia-535-server-6.2.0-24-generic - Linux 
kernel nvidia modules for version 6.2.0-24 (objects)
  p   linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux 
kernel nvidia modules for version 6.2.0-24 (objects)

  There is no package for 6.2.0-25 kernel.
  So after upgrade to new kernel - gpu isn't working, as the module is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+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 1990621] Re: [SRU] PXE Boot contains wrong suggested link to ISO for live file system

2023-07-28 Thread Dominik Viererbe
** Tags removed: foundations-todo

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

Title:
  [SRU] PXE Boot contains wrong suggested link to ISO for live file
  system

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

Bug description:
  [ Impact ]

   * What are the effects of the bug on users?
     casper's intercative netmount fails to download the latest
     Ubuntu LTS ISOs after the release of the first point release
     (e.g. 22.04.1)

   * What is the justification for backporting the fix to the
     There are at least 2 bug reports about this problem
     (LP: #1990621, #1948884) and this fix will improve the
     user experience with a low probaility of side effects.

   * How does the upload fix the bug?

     - The patch adds a '-latest' to the download URLs (see more
   details here: 
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
     - Additionaly Łukasz Zemczak (sil2100) created symlinks that
   (as the name of the urls imply) always points to the latest
   Ubuntu ISO for a given version.

  [ Test Plan ]

   * How to reproduce the bug?

     - Just run the failling parts of the casper script on a
   22.04.1 <= x < 22.10 machine:

   # would normally be set by initramfs-tools
   $ DPKG_ARCH=amd64

   # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
   $ source /etc/os-release

   # see 
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
   $ 
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso

   # see 
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
   $ wget "${server_url}" -O /dev/null

   # You should observe an ERROR 404: Not Found.

   * Test that the new links work:
     - Test Script: 
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
     - New -latest URLs
   - 
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
   - https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-arm64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-ppc64el.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso

   * Łukasz Zemczak (sil2100) tested that casper can handle
     HTTP 301 redirects. (See 
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497/comments/1193559)

  [ Where problems could occur ]

   * The Ubuntu Release Team could forget or the automation
     could stop working to update the -latest links, but this
     would, in the worst case, result in a not more worse
     situation than the current bug.

  [ Other Info ]

   * Nick Rosbrook (enr0n) pointed out in comment #3 that the
     script allows the user to provide their own url.
     This should only be considered a temporary workaround as
     a user has to be aware of this bug and has to aquire a
     URL by themself. Copy & pasting URLs from the web is
     potentialy error prone and unsafe.

   * As far as I am aware, there was a discussion between
     Łukasz Zemczak (sil2100), Brian Murray (brian-murray) and
     Steve Langasek (~vorlon) about the link namining. Neither
     was particularly happy about the current solution, but no
     better solution was found.

   * Original Bug report:

  When PXE booting without pulling in squashfs correctly the system
  tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release
  contains a link to the old version which is not present anymore.

  ---
  Unable to find a medium containing a live file system
  Attempt interactive netboot from a URL?
  yes no (default yes):
  Two methods available for IP configuration:
    * static: for static IP configuration
    * dhcp: for automatic IP configuration
  static dhcp (default 'dhcp'):
  vlan id (optional):
   https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso 
(default)
   https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
  url:
  http_proxy (optional):
  [  125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: RX/TX
  [  125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount 
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ...

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  

[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

2023-07-28 Thread AaronMa
The issue is already verified in Jammy, but tag was changed by linux-
hwe-6.2 kernel bot.

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

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

Title:
  Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2

  [Fix]
  Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

  These 2 patches are already in Unstable and OEM-6.1 already got them
  via stable updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023539/+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 2023650] Re: Add microphone support of the front headphone port on P3 Tower

2023-07-28 Thread AaronMa
The issue is already verified in Jammy, but tag was changed by linux-
hwe-6.2 kernel bot.

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

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

Title:
  Add microphone support of the front headphone port on P3 Tower

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

Bug description:
  [Impact]
  The 3.5mm headphone port in front panel cannot detect the microphone. 

  [Fix]
  Add quirk for headset mic pin on P3 Tower.

  [Test]
  Tested with alsa audio, mic works fine.

  [Where problems could occur]
  Low risk to add specific hardware ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023650/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3

2023-07-28 Thread AceLan Kao
Don't have machine to verify the issue now, but confirmed the commit
exists in jammy and lunar kernels.

** Tags removed: verification-needed-jammy verification-needed-lunar
** Tags added: verification-done-jammy verification-done-lunar

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

Title:
  A deadlock issue in scsi rescan task while resuming from S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  During the S3 stress test, the system sometimes hangs when resuming. This is 
due to the SCSI rescan task being unable to acquire the mutex lock during the 
resumption from S3. The mutex lock has already been acquired by EH and is 
waiting for the device to be ready for a rescan. Unfortunately, the mutex lock 
is never released by either party, leading to a deadlock.

  [Fix]
  Kaiheng submitted a patch to fix this issue which defers the rescan if the 
disk is still suspended so the resume process of the disk device can proceed.
  
https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/

  Since the patch has not been accepted by the upstream yet, so submit
  it to the OEM kernel for now.

  The similiar patch has been included in v6.4-rc7
  6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume

  [Test]
  Verified on the machines by me and ODM.

  [Where problems could occur]
  It only defers the rescan task, and should not have any impact to current 
systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2023311] Re: Resolve synchronous exception on arm64

2023-07-28 Thread Tim Gardner
Tagging this bug as verification done. Boot testing has been successful.

** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic

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

Title:
  Resolve synchronous exception on arm64

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

Bug description:
  SRU Justification

  [Impact]

  MSFT has requested the inclusion of commit
  e8dfdf3162eb549d064b8c10b1564f7e8ee82591 ('arm64: efi: Recover from
  synchronous exceptions occurring in firmware'). It looks generic
  enough to apply to the master kernel.

  Unlike x86, which has machinery to deal with page faults that occur
  during the execution of EFI runtime services, arm64 has nothing like
  that, and a synchronous exception raised by firmware code brings down
  the whole system.

  [Test Plan]

  This looks like a hard one to reproduce. Boot and regression testing
  should be sufficient.

  [Regression Potential]

  Firmware exceptions could still take down the system.

  [Other Info]

  SF: #00362062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023311/+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 2013027] Re: Issues over broadcom brcmfmac43455 firmware

2023-07-28 Thread Sergio Callegari
I have diagnosed the problem as follows.

My broadcom 43455 adapter needs:

1. a different brcm43455-sdio.txt file from the one supplied in ubuntu,
which is a cypress provided version.

2. a different brcm43455-sdio.bin file from the one supplied in ubuntu,
that again is a cypress provided version

3. a different brcm43455-sdio.clm_blob file from the one supplied in
ubuntu


Now, 1 and 2 are no issue: I can supply the files needed by my hardware and put 
them side to side to the ubuntu supplied ones. This is because the system will 
seek `brcm43455-sdio.AZW-Z83 II.{txt, bin} first.
Incidentally, the txt file can be easily taken from the nvram of my system, 
while the bin file is the one that is supplied in armbian, libreelec etc, that 
for some reason is not the same as the cypress one found in ubuntu.

The real problem is 3. And this is because without the file made for my
hardware, the wifi will work in the 2.4 GHz band, but not in the 5GHz
band. However the file name for this does not appear to be adapted to my
system. Namely, if I put a 'brcm43455-sdio.AZW-Z83 II.clm_blob' file
side to side to 'brcm43455-sdio.clm_blob' that will be ignored.

This makes it impossible to place board specific brcm files *side to
side* the those currently specified by the distro (unless I miss
something). If this is the case, then there are two possible
workarounds:

1. Make a deb file with a diversion for the clm_blob file
2. Use the brcmfmac module option `alternative_fw_path` to specify and 
alternative firmware path for my brcm hardware and put my bin, txt and clm_blob 
files there

However, I really tend to think that these are just ugly workarounds for
what is ultimately an issue with the brcmfmac kernel module. If the
module can determine that for by board the filename should be
`brcm43455-sdio.AZW-Z83 II.{txt,bin}` for the txt and bin pieces of the
firmware, then why cannot it look at `brcm43455-sdio.AZW-Z83
II.clm_blob` before falling back to `brcm43455-sdio.clm_blob`? That
would make it easy to put different firmwares in the the brcm firmware
directory side by side and make the framework that is already there for
the txt and bin files actually useful.

Please consider reopening the issue, passing it to the brcmfmac
maintainers.

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

Title:
  Issues over broadcom brcmfmac43455 firmware

Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-firmware-raspi2 package in Ubuntu:
  Invalid

Bug description:
  Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom
  chipset for WIFI.

  The only way to make wifi on that PC work is to use the firmware from
  the windows image, even if that chipset is apparently managed in
  ubuntu.

  With the firmware files provided by ubuntu you get no 5GHz for wifi.
  The problem is that every time ubuntu updates the firmware package,
  firmware files dropped in /lib/firmware get overwritten, linking to
  some file in the cypress sub-directory.

  - Ideally, Ubuntu should provide all the firmware files that might be
  needed. Maybe this is not possible as there is a too large variety of
  different firmwares for broadcom chipsets or licesing issues
  preventing distribution.

  - As a second possibility, there should be a way to drop files in
  /lib/firmware 'side to side' to the distro ones, without having the
  risk of finding the manually added files rewritten. This implies that
  different pieces of hardware use firmware files with different
  filenames. Don't know if this is truly possible, as I do not know how
  the linux kernel decides the name of the firmware to load.

  - In cases like mine, it seems that the ubuntu firmware package puts
  in place symlinks to have brcmfmac43455 files point to the
  corresponding cypress cyfmac43455 files. Possibly, the package could
  avoid creating the symlinks if a brcmfmac43455 file is manually placed
  in lib/firmware.

  - As a last resort, I think that the documentation in
  `/usr/share/doc/linux-firmware` should be augmented to describe the
  most appropriate way to prevent custom firmware files from being
  rewritten: marking files not-writable? introducing diversions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+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 2028932] Re: ubuntu_bpf failed to build with j-oem-6.1.0-1018.18

2023-07-28 Thread Timo Aaltonen
** Changed in: linux-oem-6.1 (Ubuntu)
   Status: New => Invalid

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

Title:
  ubuntu_bpf failed to build with j-oem-6.1.0-1018.18

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  Issue found with J-oem-6.1.0-1018.18

  Test build failed with:
  CLNG-BPF [test_maps] test_check_mtu.bpf.o
  CLNG-BPF [test_maps] test_cls_redirect.bpf.o
make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an 
integral constant expression 
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of 
a reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
 ^

/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:86:33:
 note: expanded from macro 'offsetof'
#define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
 ^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an 
integral constant expression
sizeof(flow_ports_t) !=
^~~ 
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of 
a reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
 ^

/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:86:33:
 note: expanded from macro 'offsetof'
#define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
 ^
2 errors generated.
make[1]: *** [Makefile:531: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.bpf.o]
 Error 1
make: *** [Makefile:160: all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2028932/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

2023-07-28 Thread Timo Aaltonen
hwe-5.19 will be replaced by hwe-6.2 soon, and kinetic (and 5.19 kernel
with it) is EOL

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

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

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Won't Fix
Status in linux-oem-6.1 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix

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

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

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

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

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] 

[Kernel-packages] [Bug 2028932] Re: ubuntu_bpf failed to build with j-oem-6.1.0-1018.18

2023-07-28 Thread Po-Hsu Lin
** Also affects: linux-oem-6.1 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  ubuntu_bpf failed to build with j-oem-6.1.0-1018.18

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  Issue found with J-oem-6.1.0-1018.18

  Test build failed with:
  CLNG-BPF [test_maps] test_check_mtu.bpf.o
  CLNG-BPF [test_maps] test_cls_redirect.bpf.o
make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an 
integral constant expression 
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of 
a reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
 ^

/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:86:33:
 note: expanded from macro 'offsetof'
#define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
 ^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an 
integral constant expression
sizeof(flow_ports_t) !=
^~~ 
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of 
a reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
 ^

/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:86:33:
 note: expanded from macro 'offsetof'
#define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
 ^
2 errors generated.
make[1]: *** [Makefile:531: 
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.bpf.o]
 Error 1
make: *** [Makefile:160: all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2028932/+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 2028933] [NEW] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)

2023-07-28 Thread Carlos R Jones Jr
Public bug reported:

At boot up after the GRUB selection, these ACPI BIOS Error (bug) appear.

These errors were taken from dmesg but they report the similar error at boot up
[0.320650] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[0.320680] fbcon: Taking over console
[0.320694] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
[0.320700] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.320705] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
[0.320712] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
[0.320717] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.320720] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[0.320727] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
[0.320731] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.320734] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[0.320741] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
[0.320745] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.320793] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
[0.320801] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
[0.320806] ACPI: Skipping parse of AML opcode: Method (0x0014)


Then at runtime random Multiple Corrected error appear at this PCIe port
1c.0-[01]00.0  Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 
M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]1c.0-[01]00.0  
Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]

Not exactly connected but similar reports of ACPI error above is related
to NVIDIA. Not sure if it helps.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-78-generic 5.15.0-78.85~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
Uname: Linux 5.15.0-78-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 28 19:17:58 2023
InstallationDate: Installed on 2021-08-15 (712 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  ACPI BIOS Error (bug): Failure creating named object
  [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New

Bug description:
  At boot up after the GRUB selection, these ACPI BIOS Error (bug)
  appear.

  These errors were taken from dmesg but they report the similar error at boot 
up
  [0.320650] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320680] fbcon: Taking over console
  [0.320694] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320700] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320705] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320712] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320717] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320720] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320727] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320731] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320734] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320741] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320745] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320793] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320801] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [  

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

2023-07-28 Thread Timon Z.
Please fix this issue as soon as possible. I cannot work like this. My
system freezes during meetings.

cat /proc/version
Linux version 5.19.0-50-generic (buildd@lcy02-amd64-030) (x86_64-linux-gnu-gcc 
(Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#50-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 10 18:24:29 UTC 2023

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Triaged
Status in linux-oem-6.1 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Triaged

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

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

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

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

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled 

[Kernel-packages] [Bug 2028924] Re: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to install/upgrade: installed linux-headers-6.2.0-26-generic package post-installation script subprocess r

2023-07-28 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  error when upgrading from jelly to lobster

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-26-generic 6.2.0-26.26
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dean   3481 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jul 28 11:20:08 2023
  ErrorMessage: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-01-30 (178 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. Vostro 5590
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic 
root=UUID=547ef5cd-c496-41b7-bd7b-93f7189b22f9 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to 
install/upgrade: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-28 (0 days ago)
  dmi.bios.date: 03/16/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 051P23
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd03/16/2023:br1.23:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr:sku095A:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028924/+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 2028924] [NEW] package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to install/upgrade: installed linux-headers-6.2.0-26-generic package post-installation script subprocess

2023-07-28 Thread ibanez
Public bug reported:

error when upgrading from jelly to lobster

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-26-generic 6.2.0-26.26
ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
Uname: Linux 5.19.0-50-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dean   3481 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Jul 28 11:20:08 2023
ErrorMessage: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-01-30 (178 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Dell Inc. Vostro 5590
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic 
root=UUID=547ef5cd-c496-41b7-bd7b-93f7189b22f9 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to 
install/upgrade: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-07-28 (0 days ago)
dmi.bios.date: 03/16/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 051P23
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd03/16/2023:br1.23:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr:sku095A:
dmi.product.family: Vostro
dmi.product.name: Vostro 5590
dmi.product.sku: 095A
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: amd64 apport-package lunar

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  error when upgrading from jelly to lobster

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-26-generic 6.2.0-26.26
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dean   3481 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jul 28 11:20:08 2023
  ErrorMessage: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-01-30 (178 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. Vostro 5590
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-50-generic 
root=UUID=547ef5cd-c496-41b7-bd7b-93f7189b22f9 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to 
install/upgrade: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-28 (0 days ago)
  dmi.bios.date: 03/16/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 051P23
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd03/16/2023:br1.23:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr:sku095A:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


-- 
Mailing list: 

[Kernel-packages] [Bug 2021525] Re: [iotg][ADL-P] gpu performance patches

2023-07-28 Thread Jian Hui Lee
running the test on adl-p cdb:

$ ./matrix_multiply 
Running on device: Intel(R) Graphics [0x46a6]
Success!
GFlops: 43.8066


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

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

Title:
  [iotg][ADL-P] gpu performance patches

Status in linux-intel-iotg package in Ubuntu:
  Fix Committed
Status in linux-intel-iotg source package in Jammy:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2018575

  ---

  Description

  When testing Ubuntu 22.04 with 5.15 iotg kernel for ADL-P platform, we
  discovered that GPU performance when running oneapi application is
  about 7X slower when compare to kernel 5.19.

  The current 5.15 iotg kernel missing the patches to boost GPU
  frequency. This affects ADL platform. Attached patches fix the issue.

  ./matrix_multiply
  Running on device: Intel(R) Graphics [0x46a6]
  Success!
  GFlops: 3.29845

  Once the kernel is patched:

  ./matrix_multiply
  Running on device: Intel(R) Graphics [0x46a6]
  Success!
  GFlops: 47.5939

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2021525/+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 2024113] Re: Linux 6.2.0-20 kernel update tries to install low latency and oracle versions

2023-07-28 Thread Alexander
+1 upvote

See comment #17 & #49 here:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-530/+bug/2023946?comments=all

/ quote, copy and paste from my own comment #49 (bug 2023946) into this
ongoing bug report (2024113):

"Typing this from my phone rn, so bare with me please. I kept digging
into this because it turns out that the computer that my wife uses also
had a few Nvidia related issues recently, and she also has the Oracle
and low latency kernel installed, even though she didn't install these
manually, willingly or knowingly. There is a bunch of information about
this out there:

-
https://www.reddit.com/r/Kubuntu/comments/14ndb7a/why_do_i_keep_getting_these_oracle_and_lowlatency/

- https://ubuntuforums.org/showthread.php?t=2482558

- https://ubuntuforums.org/showthread.php?t=2473057

- https://ubuntuforums.org/showthread.php?t=2483064

Going by the information at hand, it seems that this is indeed caused
either by the Nvidia driver update in Ubuntu - or - it's a dependency
from Virtualbox or Gnome Boxes, which I mentioned in the comments of the
bug report further below. Two things here: a) having the kernel change
like this from the default Ubuntu kernel to something from Oracle
without any form of obvious user info or confirmation is something to
worry about imo b) it seems to be tied to some of the gpu driver update
issues that a few of us have been experiencing, and it has even nuked or
rendered some systems unusable too, see posts above

I haven't found the time to further diagnose my own Ubuntu + Nvidia
related issues
(https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776), and I
don't see myself troubleshooting my wife's computer right now, so I
leave this comment here just in case someone wants to open up a new or
separate bug report about this, which I'll gladly upvote in order to
provide whatever little information that I have right now. If there is
already an ongoing bug report for this available, a point in the right
direction is highly appreciated.

Thanks!"

/ End of quote.

The text above includes other related bug reports and also a few
additional links. I recommend looking into this asap as it seems to be
affecting a number of Nvidia, Virtualbox and Gnome Boxes users, causing
all sorts of issues and even rendering some systems unbootable. Ty!

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

Title:
  Linux 6.2.0-20 kernel update tries to install low latency and oracle
  versions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when I ran software updates to update my 23.04 Budgie system today to
  Linux 6.2.0-20-generic apt treis to install the low latency and Oracle
  versions of the kernel too, breaking my system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024113/+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 2012651] Re: Linux 6.2.0-18-generic memcpy detected field-spanning write in iwlwifi

2023-07-28 Thread Arjan
Hi, just a metoo report, owning a Lenovo T430, seen most recent with kernel 
6.2.0-26-generic #26-Ubuntu
The Wifi hardware is still the original:
 description: Wireless interface
 product: Centrino Advanced-N 6205 [Taylor Peak]
 vendor: Intel Corporation
Perhaps note that the wifi just works as it seems.

I don't see the dump when WiFi hardware is replaced with AX210 for
example.

The dump on my T430:
```
[   11.456072] memcpy: detected field-spanning write (size 32) of single field 
"sta_cmd.key.key" at drivers/net/wireless/intel/iwlwifi/dvm/sta.c:1103 (size 16)
[   11.456101] WARNING: CPU: 2 PID: 2505 at 
drivers/net/wireless/intel/iwlwifi/dvm/sta.c:1103 
iwlagn_send_sta_key+0x402/0x4d0 [iwldvm]
[   11.456123] Modules linked in: xt_CHECKSUM xt_MASQUERADE ccm algif_aead 
des_generic libdes algif_skcipher cmac md4 algif_hash af_alg nft_chain_nat 
nf_nat bridge stp llc bnep btusb btrtl uvcvideo btbcm btintel btmtk 
videobuf2_vmalloc videobuf2_memops bluetooth videobuf2_v4l2 videodev 
ecdh_generic ecc videobuf2_common mc ip6t_REJECT nf_reject_ipv6 xt_hl 
ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 nft_limit sunrpc xt_limit 
xt_addrtype nvidia_uvm(PO) xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables nfnetlink binfmt_misc intel_rapl_msr 
snd_ctl_led snd_hda_codec_realtek intel_rapl_common snd_hda_codec_generic 
x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_intel 
kvm_intel snd_intel_dspcfg snd_intel_sdw_acpi nvidia_drm(PO) snd_hda_codec kvm 
snd_hda_core nvidia_modeset(PO) irqbypass snd_hwdep thinkpad_acpi iwldvm rapl 
mei_pxp mei_hdcp snd_pcm nvram nvidia(PO) intel_cstate mac80211 snd_seq_midi 
snd_seq_midi_event libarc4
[   11.456178]  snd_rawmidi iwlwifi snd_seq mei_me snd_seq_device think_lmi 
essiv authenc snd_timer firmware_attributes_class dm_crypt wmi_bmof cfg80211 
ipmi_devintf at24 snd ipmi_msghandler mei soundcore ledtrig_audio 
platform_profile joydev input_leds mac_hid serio_raw pkcs8_key_parser msr 
parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 
drm_buddy i2c_algo_bit ttm drm_display_helper cec crct10dif_pclmul crc32_pclmul 
polyval_clmulni rc_core polyval_generic sdhci_pci ghash_clmulni_intel 
sha512_ssse3 drm_kms_helper aesni_intel syscopyarea crypto_simd sysfillrect 
cqhci ahci sysimgblt i2c_i801 cryptd psmouse sdhci libahci drm lpc_ich 
i2c_smbus xhci_pci e1000e xhci_pci_renesas video wmi
[   11.456237] CPU: 2 PID: 2505 Comm: iwd Tainted: P   O   
6.2.0-26-generic #26-Ubuntu
[   11.456239] Hardware name: LENOVO 23472K8/23472K8, BIOS G1ETC2WW (2.82 ) 
08/07/2019
[   11.456241] RIP: 0010:iwlagn_send_sta_key+0x402/0x4d0 [iwldvm]
[   11.456255] Code: ff ff b9 10 00 00 00 4c 89 e6 48 c7 c2 80 25 58 c2 48 c7 
c7 00 25 58 c2 89 85 68 ff ff ff c6 05 3a f0 02 00 01 e8 6e 94 d8 df <0f> 0b 8b 
85 68 ff ff ff e9 8f fd ff ff 41 8b 4d 14 89 4d 97 43 8b
[   11.456257] RSP: 0018:ac2103007718 EFLAGS: 00010246
[   11.456259] RAX:  RBX: 8bb60116a088 RCX: 
[   11.456261] RDX:  RSI:  RDI: 
[   11.456262] RBP: ac21030077c0 R08:  R09: 
[   11.456263] R10:  R11:  R12: 0020
[   11.456264] R13: 8bb603e23e30 R14: ac2103007734 R15: 8bb603e23e44
[   11.456266] FS:  7f736ad87740() GS:8bb92e68() 
knlGS:
[   11.456267] CS:  0010 DS:  ES:  CR0: 80050033
[   11.456269] CR2: 00c000a26000 CR3: 00010e7fa004 CR4: 001706e0
[   11.456270] Call Trace:
[   11.456272]  
[   11.456275]  iwl_set_dynamic_key+0x1b2/0x260 [iwldvm]
[   11.456289]  iwlagn_mac_set_key+0x1fd/0x290 [iwldvm]
[   11.456302]  drv_set_key+0xc6/0x1d0 [mac80211]
[   11.456364]  ieee80211_key_enable_hw_accel+0xe6/0x2c0 [mac80211]
[   11.456427]  ieee80211_key_replace+0x251/0xac0 [mac80211]
[   11.456487]  ? __pfx_call_rcu_hurry+0x10/0x10
[   11.456491]  ieee80211_key_link+0x133/0x350 [mac80211]
[   11.456551]  ieee80211_add_key+0x185/0x370 [mac80211]
[   11.456609]  nl80211_new_key+0x218/0x3a0 [cfg80211]
[   11.456669]  genl_family_rcv_msg_doit.isra.0+0xe8/0x150
[   11.456675]  genl_family_rcv_msg+0x180/0x250
[   11.456678]  ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211]
[   11.456724]  ? __pfx_nl80211_new_key+0x10/0x10 [cfg80211]
[   11.456772]  ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211]
[   11.456818]  genl_rcv_msg+0x4c/0xb0
[   11.456821]  ? __pfx_genl_rcv_msg+0x10/0x10
[   11.456824]  netlink_rcv_skb+0x5d/0x110
[   11.456827]  genl_rcv+0x28/0x50
[   11.456830]  netlink_unicast+0x247/0x390
[   11.456833]  netlink_sendmsg+0x25e/0x4e0
[   11.456836]  sock_sendmsg+0x6d/0x70
[   11.456840]  __sys_sendto+0x14d/0x1b0
[   11.456844]  __x64_sys_sendto+0x24/0x40
[   

[Kernel-packages] [Bug 1995147] Re: r8169 : eth0 link down after 5 minutes 'kernel: [ ] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out

2023-07-28 Thread DB
Hello,

There is some evolution.
I still use the r8169 module in the 5.19.0 kernel, r8168 and dkms are not 
present anymore. Neither r8169 nor r8168 are blacklisted.
lsmod shows that the r8169 module is loaded in memory.
dmesg | grep r81 shows that the eth0 link is up at startup of the laptop.

I set up NetworkManager to establish automatically the internet sharing
trough eth0 with IPV4 (IPv6 is desactivated). The ethernet sharing
doesn't come up automatically at startup of NetworkManager (even with
this option activated), but when I manually switch off and on the
ethernet link in NetworkManager, the ethernet sharing comes up and works
fine.

I can't still find if this bug comes from the r8169 module or from the 
NetworkManager package.
Any idea?

I also opened a bug report for NetworkManager #2028832

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

Title:
  r8169 : eth0 link down after 5 minutes 'kernel: [ ] NETDEV WATCHDOG:
  enp2s0 (r8169): transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I use reverse tethering trough an ethernet link: my Ubuntu 22.04 LTS laptop 
is providing internet access to a LG CL600 thin client.
  This ethernet link works fine from power up until 5 minutes after this power 
up, then the ethernet link freezes.

  I don't have this problem when my laptop is providing the same internet 
access with Debian 11 live (kernel 5.10.0): in this case reverse tethering 
trough ethernet works fluently trough the time, no ethernet freeze at all.
  So my hardware isn't faulty, but there seems to be a regression in the kernel 
r8169 module, between the 5.10 and 5.15 kernels.

  Can you solve this regression?

  The r8169 module is a part the linux-modules-extra-5.15.0-52-generic package.
  Here is the involved sample from /var/log/syslog:

  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053253] [ cut 
here ]
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053278] NETDEV WATCHDOG: 
enp2s0 (r8169): transmit queue 0 timed out
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053308] WARNING: CPU: 2 
PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x277/0x280
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053326] Modules linked 
in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq nft_counter 
nft_chain_nat xt_MASQUERADE nft_compat bridge stp llc rfcomm ccm nf_tables 
nfnetlink nf_nat_h323 binfmt_misc nf_conntrack_h323 nf_nat_pptp 
nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip 
nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c cmac algif_hash 
algif_skcipher af_alg bnep nls_iso8859_1 mei_hdcp intel_rapl_msr 
snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi 
snd_hda_intel intel_rapl_common snd_intel_dspcfg iwlmvm rtsx_usb_ms 
snd_intel_sdw_acpi mac80211 uvcvideo snd_usb_audio snd_hda_codec 
snd_usbmidi_lib snd_hda_core x86_pkg_temp_thermal intel_powerclamp 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev 
snd_hwdep libarc4 snd_seq_midi coretemp mc memstick snd_pcm snd_seq_m
 idi_event i915 kvm_intel snd_rawmidi snd_seq kvm
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053625]  iwlwifi ttm 
drm_kms_helper snd_seq_device snd_timer btusb crct10dif_pclmul btrtl btbcm 
ghash_clmulni_intel cec aesni_intel snd rc_core btintel crypto_simd 
i2c_algo_bit bluetooth mei_me cfg80211 cryptd mei soundcore at24 fb_sys_fops 
ecdh_generic ecc rapl intel_cstate syscopyarea sysfillrect sysimgblt joydev 
input_leds ideapad_laptop sparse_keymap serio_raw platform_profile mac_hid wmi 
acpi_pad sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp mtd 
ramoops pstore_blk pstore_zone parport drm reed_solomon efi_pstore ip_tables 
x_tables autofs4 hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb i2c_i801 r8169 
ahci xhci_pci psmouse i2c_smbus crc32_pclmul lpc_ich libahci realtek 
xhci_pci_renesas video
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053905] CPU: 2 PID: 0 
Comm: swapper/2 Not tainted 5.15.0-48-generic #54-Ubuntu
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053914] Hardware name: 
LENOVO 80FF/Lenovo G70-80, BIOS ABCN80WW 05/18/2015
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053918] RIP: 
0010:dev_watchdog+0x277/0x280
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053931] Code: eb 97 48 8b 
5d d0 c6 05 03 39 69 01 01 48 89 df e8 ee 67 f9 ff 44 89 e1 48 89 de 48 c7 c7 
50 49 cd 8d 48 89 c2 e8 a7 bb 19 00 <0f> 0b eb 80 e9 51 25 23 00 0f 1f 44 00 00 
55 48 89 e5 41 57 41 56
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053938] RSP: 
0018:c03440154e70 EFLAGS: 00010282
  Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [  537.053946] RAX: 
 RBX: 

[Kernel-packages] [Bug 2018236] Re: Fix ADL: System shutdwon automically when run Prime95 with i9-12900K

2023-07-28 Thread koba
@Andreas, re-ran the test case for 7 hours and system didn't reboot.
run stress-ng and mprime simutaneously.

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

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

Title:
  Fix ADL: System shutdwon automically when run Prime95 with
  i9-12900K

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Description]
  System shutdown automatically when stressing the machine.

  [Fix]
  Need these two to fix the issue.

  cbdd92b) Parse idsp and trips
  d385f20) Use PL1 max/min from PPCC when policies match
  
https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be

  [Test Case]
  1. Find a unit with i9-12900k CPU and air cooling
  2. Install tools
  #sudo apt install stress-ng s-tui
  #sudo systemctl stop thermald
  #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.txt &
  #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress
  4. Stress test: (you may need to open multiple terminals for the test)
  #./mprime
  #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v
  5. monitor cpu temperature for 6 hours if you didn’t hit overheat and 
shutdown issue.
  #sudo s-tui -c

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 1738534] Re: Processor turbo dsiabled/throttled after suspend

2023-07-28 Thread wwweb
The problem still persists.
Using latest stable Debian 11 and having the same issue - every time after 
suspend CPU turbo is disabled.

5.10.0-23-amd64 #1 SMP Debian 5.10.179-2 (2023-07-14) x86_64 GNU/Linux

A workaround I've found is to edit /etc/sysfs.conf:

mode power/state = 0777
owner power/state = root:root
devices/system/cpu/cpu0/cpufreq/boost = 1
devices/system/cpu/cpu1/cpufreq/boost = 1
devices/system/cpu/cpu2/cpufreq/boost = 1
devices/system/cpu/cpu3/cpufreq/boost = 1
devices/system/cpu/cpu0/cpufreq/scaling_governor = performance
devices/system/cpu/cpu1/cpufreq/scaling_governor = performance
devices/system/cpu/cpu2/cpufreq/scaling_governor = performance
devices/system/cpu/cpu3/cpufreq/scaling_governor = performance

change scaling_governor to any other supported mode (ondemand,
conservative, etc.), then restart sysfsutils:

sudo service sysfsutils restart

and then change scaling_governor back to performance and restart
sysfsutils again.

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

Title:
  Processor turbo dsiabled/throttled after suspend

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

Bug description:
  After suspending/resuming my laptop on battery power, I noticed choppy
  video playback.  I've narrowed it down to the CPU being locked to
  lower frequencies after suspend/resume (only on battery).  Plugging
  the laptop back in does not restore the normal performance, nor does
  suspend/resume after plugging it back in.  The performance doesn't
  drop until after the suspend/resume, I'm not sure if it is _supposed_
  to throttle when on battery, but either way the behaviour is wrong.

  Doing a full shutdown and restart restores the performance to normal.

  Prior to a suspend/resume cycle, cpupower reports:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.26 GHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes
  2800 MHz max turbo 4 active cores
  2800 MHz max turbo 3 active cores
  2800 MHz max turbo 2 active cores
  3000 MHz max turbo 1 active cores

  Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has
  no effect) and turbo is disabled:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 950 MHz (asserted by call to kernel)
boost state support:
  Supported: no
  Active: no
  2800 MHz max turbo 4 active cores
  2800 MHz max turbo 3 active cores
  2800 MHz max turbo 2 active cores
  3000 MHz max turbo 1 active cores

  Trying to re-enable turbo mode by setting the no_turbo intel_pstate
  /sys/ entry back to 0 is rejected:

  $ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
  0
  tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted

  However, these two commands *do* work around the problem, forcing
  turbo mode back on and then restoring the normal frequency range:

  sudo x86_energy_perf_policy --turbo-enable 1
  sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz

  I also see this error in dmesg after some resumes (but the above
  problem sometimes happens without this error message):

  Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by
  BIOS or unavailable on processor

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaun  1194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 16 11:18:12 2017
  InstallationDate: Installed 

[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU

2023-07-28 Thread koba
put cpu-load and gpu-laod simultaneously
1. cpu-load, phoronix-test-suite benchmark compress-7zip
2. gpu-load, phoronix-test-suite benchmark unigine-super
   resolution: 2560*, full-screen, ultra quality.

use nvidia-smi to monitor gpu temperature, performance and utilization
#sudo nvidia-smi -pm 1, watch -n 1 nvidia-smi

kernel,
~~~
$ uname -a
Linux u 6.0.0-1020-oem #20-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 14 13:12:17 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
~~~

With 2.4.9-1ubuntu0.2,
observed the gpu was put into P3(performance state), the max power watt is 
limited under 30W.
the gpu temperature is under 70 and lower.
even cpu load is finished, the p state of gpu is still P3 and gpu performance 
is limited.
gpu load is still running after cpu load is finished.

With 2.4.9-1ubuntu0.3,
didn't observe the throttled symptom during run cpu load.
gpu is keepin in P0 and max power watt, 80w.
the gpu temperature is over 70 and higher.

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

Title:
  thermald prematurely throttling GPU

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Fix]
  This fix is removed the code refactoring part and keep the necessary.

  (patch: 0009-Install-passive-default.patch)
  82609c7) Separate Adaptive engine and GDDV

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, ADL/TGL/CML/CFL/KBL.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  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: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

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