[Kernel-packages] [Bug 2080853] Re: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=219283.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-09-16T13:30:32+00:00 colin.i.king wrote:

Created attachment 306882
dmesg showing lockup

exercising xattr with stress-ng on ext4 when it's been created with
ea_inode option causes a kernel hang.

Kernel: 6.11.0-7, AMD64 virtual machine 8 thread virtual machine (important, 
must be multiple CPU threads to trigger the regression)
20GB virtio drive on /dev/vdb, 1 partition /dev/vdb1

sudo mkfs.ext4 /dev/vdb1 -O ea_inode
sudo mount /dev/vdb1 /mnt

git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
make clean; make -j $(nproc)

sudo ./stress-ng --xattr 8 -t 120 --vmstat 1 --file-path /mnt

..wait a couple of minutes, you will see that the number of running
processes is not 8 as expected (from the --vmstat output of stress-ng)

cannot ^C stop stress-ng because of a kernel lockup, use another tty and
check dmesg, I get the following:

[ 247.028846] INFO: task jbd2/vdb1-8:1548 blocked for more than 122 seconds.
[ 247.030830] Not tainted 6.11.0-7-generic #7-Ubuntu
[ 247.032667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 247.034170] task:jbd2/vdb1-8 state:D stack:0 pid:1548 tgid:1548 ppid:2 
flags:0x4000
[ 247.034176] Call Trace:
[ 247.034178] 
[ 247.034182] __schedule+0x277/0x6c0
[ 247.034199] schedule+0x29/0xd0
[ 247.034203] jbd2_journal_wait_updates+0x77/0xf0
[ 247.034207] ? __pfx_autoremove_wake_function+0x10/0x10
[ 247.034213] jbd2_journal_commit_transaction+0x290/0x1a10
[ 247.034223] kjournald2+0xa8/0x250
[ 247.034228] ? __pfx_autoremove_wake_function+0x10/0x10
[ 247.034233] ? __pfx_kjournald2+0x10/0x10
[ 247.034236] kthread+0xe1/0x110
[ 247.034241] ? __pfx_kthread+0x10/0x10
[ 247.034244] ret_from_fork+0x44/0x70
[ 247.034247] ? __pfx_kthread+0x10/0x10
[ 247.034251] ret_from_fork_asm+0x1a/0x30
[ 247.034257] 

NOTE: this works fine for Linux 6.8.0, so this looks like a regression
for 6.11.0

Attached is the full kernel log.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080853/comments/2


On 2024-09-16T13:31:16+00:00 colin.i.king wrote:

Oops, typo, the reproducer should be:

sudo ./stress-ng --xattr 8 -t 120 --vmstat 1 --temp-path /mnt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080853/comments/3


On 2024-09-16T15:35:01+00:00 colin.i.king wrote:

Seems to occur on 6.10 but not 6.9, so it's a 6.10 regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080853/comments/5


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  oracular 6.11 kernel regression with ext4 and ea_inode mount flags and
  exercising xattrs

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

Bug description:
  How to reproduce this issue:

  Kernel: 6.11.0-7, AMD64 virtual machine, oracular, updated 16th Sept
  2024 @ 14:15 UK TZ

  8 thread virtual machine (important, must be multiple CPU threads to trigger 
the regression)
  20GB virtio drive on /dev/vdb, 1 partition /dev/vdb1

  sudo mkfs.ext4 /dev/vdb1 -O ea_inode
  sudo mount /dev/vdb1 /mnt

  git clone https://github.com/ColinIanKing/stress-ng
  cd stress-ng
  make clean; make -j $(nproc)

  ..wait a couple of minutes, you will see that the number of running
  processes is not 8 as expected (from the --vmstat output of stress-ng)

  cannot stop stress-ng because of a kernel lockup; so use another tty
  and check dmesg, I get the following:

  [  247.028846] INFO: task jbd2/vdb1-8:1548 blocked for more than 122 seconds.
  [  247.030830]   Not tainted 6.11.0-7-generic #7-Ubuntu
  [  247.032667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  247.034170] task:jbd2/vdb1-8 state:D stack:0 pid:1548  tgid:1548  
ppid:2  flags:0x4000
  [  247.034176] Call Trace:
  [  247.034178]  
  [  247.034182]  __schedule+0x277/0x6c0
  [  247.034199]  schedule+0x29/0xd0
  [  247.034203]  jbd2_journal_wait_updates+0x77/0xf0
  [  247.034207]  ? __pfx_autoremove_wake_function+0x10/0x10
  [  247.034213]  jbd2_journal_commit_transaction+0x290/0x1a10
  [  247.034223]  kjournald2+0xa8/0x250
  [  247.034228]  ? __pfx_autoremove_wake_function+0x10/0x10
  [  247.034233]  ? __pfx_kjournald2+0x10/0x10
  [  247.034236]  kthread+0xe1/0x110
  [  247.034241]  

[Kernel-packages] [Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=219101.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-07-28T04:25:49+00:00 launchpad wrote:

Hi. When using my Yoga 6 13ALC6 laptop, I frequently experience the
touchpad suddenly cease working. Sometimes there's a few seconds'
warning with reduced responsiveness, and sometimes it's completely
sudden. I reported this to Ubuntu, and they instructed me to report it
upstream here.

Output from kern.log when it happens often looks like this:

2024-07-09T21:31:51.573862-04:00 machinename kernel: i2c_designware 
AMDI0010:00: controller timed out
2024-07-09T21:31:51.577113-04:00 machinename kernel: i2c_designware 
AMDI0010:00: timeout in disabling adapter
2024-07-09T21:31:51.596828-04:00 machinename kernel: i2c_designware 
AMDI0010:00: timeout waiting for bus ready
2024-07-09T21:32:45.928870-04:00 machinename kernel: message repeated 2652 
times: [ i2c_designware AMDI0010:00: timeout waiting for bus ready]

The only workaround I've found is to sleep/hibernate or shut down the
laptop; it always works again on reboot.

You can see dmesg output and other relevant logs and information in the
original Ubuntu bug at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612 .

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/comments/13


On 2024-08-21T17:39:06+00:00 mario.limonciello wrote:

This is most likely to be a BIOS bug.  Is your BIOS up to date?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/comments/15


On 2024-08-21T17:52:59+00:00 launchpad wrote:

(In reply to Mario Limonciello (AMD) from comment #1)
> This is most likely to be a BIOS bug.  Is your BIOS up to date?

Yes, it is. From DMI:

dmi.bios.date: 03/26/2024
dmi.bios.release: 1.22
dmi.bios.vendor: LENOVO
dmi.bios.version: H6CN22WW(V1.15)

Per https://support.lenovo.com/us/en/downloads/ds549424-bios-update-for-
windows-10-64-bit-yoga-6-13alc6 , H6CN22WW is the most recent version,
released April 16 of this year. (I don't know why that date is later
than the one reported by DMI.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/comments/17


On 2024-08-21T17:57:32+00:00 mario.limonciello wrote:

What AGESA version is it?  "# dmidecode | grep AGESA"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/comments/18


On 2024-08-21T18:14:45+00:00 launchpad wrote:

(In reply to Mario Limonciello (AMD) from comment #3)
> What AGESA version is it?  "# dmidecode | grep AGESA"

That string doesn't appear in my dmidecode output. I also didn't see
anything called AGESA when I booted into UEFI and looked around.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/comments/19


On 2024-08-21T18:25:44+00:00 mario.limonciello wrote:

Ah too bad; then I guess Lenovo isn't exporting it on this system (most
OEMs do).

In any case, this timeout is something that comes from the hardware.
The method that is timing out did have a rework recently (commit
197ecadad8428 ("i2c: designware: Implement generic polling mode code for
Wangxun 10Gb NIC")) but I don't think it's likely to change your
scenario.

I use I2C touchpads all the time on AMD systems both reference and OEM systems.
This hasn't happened to me, but this to me looks like a BIOS issue, and I think 
you should raise it with Lenovo.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/comments/20


** Changed in: linux
   Status: Unknown => Incomplete

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  Lenovo touchpad intermittently stops working with i2c_designware
  errors

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Opinion

Bug description:
  Hi. When using my laptop, I frequently experience the touchpad
  suddenly cease working. Sometimes there's a few seconds' warning with
  reduced responsiveness, and sometimes it's completely sudden. I
  experienced this in Kubuntu 22.04, and I still experience it after
  upgrading to 24.04.

  Output from kern.log when it happens often looks like this:

  2024-07-09T21:31:51.573862-04:00 machinename kernel: i2c_designware 
AMDI0010:00: cont

[Kernel-packages] [Bug 2040977] Re: Mouse cursor stutters if nothing else is animating on screen

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  Mouse cursor stutters if nothing else is animating on screen

Status in Mutter:
  Fix Released
Status in linux package in Ubuntu:
  Opinion
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor
  stutters, unless something else is changing on screen (like running
  glmark2-wayland).

  Workaround:

  Put this in /etc/environment:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 15:48:28 2023
  InstallationDate: Installed on 2023-10-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2040977/+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 1832776] Re: Backport VMCI PPN64 patch

[Bug Watch Updater]

** Changed in: linux (Debian)
   Status: New => Fix Released

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

Title:
  Backport VMCI PPN64 patch

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Fix Released

Bug description:
  Hi,

  Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I
  have already filed a bug with Debian[2].

  Here is the commit log:

  commit f2db7361cb19bf3a6f7fd367f21d8eb325397946
  Author: Vishnu DASA 
  Commit: Greg Kroah-Hartman 

  VMCI: Support upto 64-bit PPNs

  Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI
  device exposes the capability for 64-bit PPNs.

  Thanks,
  Adit

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946
  [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  adit   3290 F pulseaudio
   /dev/snd/controlC0:  adit   3290 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723
  InstallationDate: Installed on 2018-11-06 (219 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T3600
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-51-generic N/A
   linux-backports-modules-4.15.0-51-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 08HPGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+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 2077142] Re: iproute2: removing /sbin/ip link breaks other packages and possibly user scripts

[Bug Watch Updater]

** Changed in: vlan (Debian)
   Status: New => Fix Released

** Changed in: vlan (Debian)
   Importance: Undecided => Unknown

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

Title:
  iproute2: removing /sbin/ip link breaks other packages and possibly
  user scripts

Status in iproute2 package in Ubuntu:
  New
Status in vlan package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1078721:

  Package: iproute2
  Version: 6.10.0-1
  Severity: critical
  Justification: breaks the whole system

  The first time I rebooted after iproute2 removed the /sbin/ip link, my system
  failed to boot. I eventually discovered this was because /sbin/vconfig (from
  the "vlan" package) calls /sbin/ip and when that failed the network was not
  configured. This meant having to boot into single user mode for diagnostics
  because systemd hung forever waiting for the network.

  My ideal solution would be to revert 1064795 and mark it "wontfix" as there's
  no way to know how many users have locally written scripts that call ip via
  what used to be a perfectly valid path (and because removing the symlink buys
  exactly nothing as far as I can tell).

  A less satisfactory solution would be to add a versioned Breaks and a version
  of the vlan package with a different path to /sbin/ip. (And, of course, any
  other package that might have broken, not including local scripts which we
  can't possibly identify.)

  -- System Information:
  Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 6.10.4-amd64 (SMP w/12 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages iproute2 depends on:
  ii  debconf [debconf-2.0]  1.5.87
  ii  libbpf11:1.4.5-1
  ii  libc6  2.39-6
  ii  libcap21:2.66-5
  ii  libcap2-bin1:2.66-5
  ii  libdb5.3t645.3.28+dfsg2-7
  ii  libelf1t64 0.191-2
  ii  libmnl01.0.5-2+b1
  ii  libselinux13.5-2+b4
  ii  libtirpc3t64   1.3.4+ds-1.3
  ii  libxtables12   1.8.10-4

  iproute2 recommends no packages.

  Versions of packages iproute2 suggests:
  ii  python3  3.12.5-1

  -- debconf information excluded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2077142/+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 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown

[Bug Watch Updater]

** Changed in: autopkgtest (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtest-virt-qemu on noble images sometimes hangs doing copydown

Status in Linux:
  Confirmed
Status in autopkgtest package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in autopkgtest package in Debian:
  Fix Released

Bug description:
  [Impact]

  It seems that kernel 6.8 introduced a regression in the 9pfs related
  to caching and netfslib, that can cause some user-space apps to read
  content from files that is not up-to-date (when they are used in a
  producer/consumer fashion).

  It seems that the offending commit is this one:

   80105ed2fd27 ("9p: Use netfslib read/write_iter")

  Reverting the commit seems to fix the problem. However the actual bug
  might be in netfslib or how netfslib is used in the 9p context.

  The regression has been reported upstream and we are still
  investigating (https://lore.kernel.org/lkml/Zj0ErxVBE3DYT2Ea@gpd/).

  In the meantime it probably makes sense to temporarily revert the
  commit as a SAUCE patch. Then we will drop the SAUCE patch once we'll
  have a proper fix upstream.

  [Test case]

  The following test should complete correctly without any timeout:

    pull-lp-source -d hello
    autopkgtest-buildvm-ubuntu-cloud -r noble
    autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img

  
  [Fix]

  Revert the following commit (until we have a proper fix upstream):

   80105ed2fd27 ("9p: Use netfslib read/write_iter")

  [Regression potential]

  We may experience other regressions related to 9pfs with this change,
  however it's quite unlikely to happen since we are reverting a commit,
  restoring the previous behavior.

  [Original bug report]

  autopkgtest-virt-qemu sometimes hangs when running tests on noble
  images. Originally reported by schopin, who also provided a
  reproducer:

    pull-lp-source -d hello
    autopkgtest-buildvm-ubuntu-cloud -r noble
    autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img

  I've been able to reproduce it with debugging enabled:

    autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
  /path/to/image

  It can get stuck during different stages, but AFAICT always during
  "copydown" operations, log excerpts follow. It may be a coincidence,
  but this started happening around the time linux-
  image-6.8.0-11-generic (6.8.0-11.11) migrated to noble. The testbeds I
  used booted 6.6 but then rebooted into that 6.8 kernel after being
  upgraded by autopkgtest.

  -- logs --

  Removing autopkgtest-satdep (0) ...
  [...]
  autopkgtest-virt-qemu: DBG: executing copydown 
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ /t/
  autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', 
'/tmp/autopkgtest.output.g8v75e]
  autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader 
name='/dev/null'>", 'deststdout']
  autopkgtest-virt-qemu: DBG:  +< tar --directory 
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ --
  autopkgtest-virt-qemu: DBG:  +> /tmp/autopkgtest-qemu.ztmr6f5k/runcmd sh -ec 
if ! test -d /tmp-
  autopkgtest-virt-qemu: DBG:  +>?

  -- or --

  autopkgtest: DBG: sending command to testbed: copydown 
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ 
/tmp/autopkgtest.H8NDfW/build.DLR/src/
  autopkgtest-virt-qemu: DBG: executing copydown 
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ 
/tmp/autopkgtest.H8NDfW/build.DLR/src/
  autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', 
'/tmp/autopkgtest.output.c9utq3bx/tests-tree/', '--warning=none', '-c', '.', 
'-f', '-'], ['/tmp/autopkgtest-qemu.qtkcgg5l/runcm]
  autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader 
name='/dev/null'>", 'deststdout', "<_io.BufferedReader name='/dev/null'>", 
'devnull_read', <_io.BufferedReader name='/dev/null'>]
  autopkgtest-virt-qemu: DBG:  +< tar --directory 
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ --warning=none -c . -f -
  autopkgtest-virt-qemu: DBG:  +> /tmp/autopkgtest-qemu.qtkcgg5l/runcmd sh -ec 
if ! test -d /tmp/autopkgtest.H8NDfW/build.DLR/src/; then mkdir -- 
/tmp/autopkgtest.H8NDfW/build.DLR/src/; fi; cd-
  autopkgtest-virt-qemu: DBG:  +>?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056461/+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 1832782] Re: Backport VMW_PVRDMA PPN64 patch

[Bug Watch Updater]

** Changed in: linux (Debian)
   Status: New => Fix Released

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

Title:
  Backport VMW_PVRDMA PPN64 patch

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Fix Released

Bug description:
  Hi,

  Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and
  later?

  Here is the commit log:

  commit 8aa04ad3b39396e315b23448c56d5465200fa777
  Author: Adit Ranadive 
  Date:   Sat Jan 26 05:09:36 2019 +

  RDMA/vmw_pvrdma: Support upto 64-bit PFNs

  Update the driver to use the new device capability to report 64-bit UAR
  PFNs.

  Thanks,
  Adit

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2010 F pulseaudio
adit   3290 F pulseaudio
   /dev/snd/controlC0:  gdm2010 F pulseaudio
adit   3290 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723
  InstallationDate: Installed on 2018-11-06 (219 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Dell Inc. Precision T3600
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-51-generic N/A
   linux-backports-modules-4.15.0-51-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 08HPGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+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 1978133] Re: System freeze followed by kernel panic or blank screen

[Bug Watch Updater]

** Changed in: linux
   Status: Fix Released => Incomplete

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

Title:
  System freeze followed by kernel panic or blank screen

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Invalid

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1978133/+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 2052744] Re: nouveau breaks 24.04 desktop

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  nouveau breaks 24.04 desktop

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

Bug description:
  nouveau: detected PR support, will not use DSM
  nouveau :01:00.0: NVIDIA GP107 (137000a1)
  usb 3-3: new high-speed USB device number 2 using xhci_hcd
  nouveau :01:00.0: bios: version 86.07.90.00.51
  nouveau :01:00.0: pmu: firmware unavailable
  nouveau :01:00.0: fb: 2048 MiB GDDR5
  nouveau :01:00.0: DRM: VRAM: 2048 MiB
  nouveau :01:00.0: DRM: GART: 536870912 MiB
  nouveau :01:00.0: DRM: BIT table 'A' not found
  nouveau :01:00.0: DRM: BIT table 'L' not found
  nouveau :01:00.0: DRM: Pointer to TMDS table not found
  nouveau :01:00.0: DRM: DCB version 4.1
  nouveau :01:00.0: DRM: MM: using COPY for buffer copies
  [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0
  nouveau :01:00.0: [drm] No compatible format found
  nouveau :01:00.0: [drm] Cannot find any crtc or sizes

  nouveau :01:00.0: bus: MMIO read of  FAULT at 6013d4 [ PRIVRING ]
  nouveau :01:00.0: bus: MMIO read of  FAULT at 122124 [ PRIVRING ]
  # above two repeat a lot

  And also stuff like this

  nouveau :01:00.0: bus: MMIO read of  FAULT at 6013d4 [ TIMEOUT ]
  [ cut here ]
  nouveau :01:00.0: timeout
  WARNING: CPU: 3 PID: 6419 at 
drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 
gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau]
  Modules linked in: rfcomm snd_seq_dummy snd_hrtimer nft_masq vhost_vsock 
vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm xt_CHECKSUM 
xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat 
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables 
nfnetlink bridge stp llc overlay qrtr cmac algif_hash algif_skcipher af_alg 
bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp 
snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic 
snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel 
snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation 
soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine 
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi x86_pkg_temp_thermal snd_hda_c
 odec intel_powerclamp
   snd_hda_core coretemp snd_hwdep snd_pcm uvcvideo kvm_intel snd_seq_midi 
iwlmvm btusb videobuf2_vmalloc snd_seq_midi_event btrtl uvc cmdlinepart kvm 
snd_rawmidi videobuf2_memops btintel dell_laptop spi_nor videobuf2_v4l2 
mac80211 snd_seq irqbypass btbcm processor_thermal_device_pci_legacy dell_wmi 
mtd videodev snd_seq_device rapl btmtk processor_thermal_device pmt_telemetry 
dell_smbios libarc4 mei_hdcp mei_pxp bluetooth pmt_class intel_rapl_msr 
dell_smm_hwmon iwlwifi videobuf2_common dcdbas snd_timer i2c_i801 
dell_wmi_sysman spi_intel_pci intel_cstate processor_thermal_rfim dell_wmi_ddv 
ecdh_generic mc ecc ledtrig_audio firmware_attributes_class dell_wmi_descriptor 
wmi_bmof snd i2c_smbus spi_intel mei_me cfg80211 processor_thermal_mbox 
soundcore essiv mei authenc processor_thermal_rapl intel_rapl_common 
intel_skl_int3472_tps68470 intel_soc_dts_iosf intel_vsec igen6_edac 
tps68470_regulator int3403_thermal clk_tps68470 int340x_thermal_zone 
int3400_thermal intel_hid intel_skl_int3472_
 discrete input_leds
   acpi_thermal_rel sparse_keymap acpi_pad joydev acpi_tad serio_raw mac_hid 
nbd msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables 
autofs4 dm_crypt zfs(PO) spl(O) raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
dm_mirror dm_region_hash dm_log hid_sensor_custom nvme hid_sensor_hub nvme_core 
nvme_common intel_ishtp_hid hid_multitouch ahci hid_generic libahci i915 
nouveau crct10dif_pclmul crc32_pclmul polyval_clmulni mxm_wmi polyval_generic 
drm_exec ghash_clmulni_intel gpu_sched drm_buddy sha256_ssse3 drm_ttm_helper 
i2c_algo_bit sha1_ssse3 ttm aesni_intel drm_display_helper cec i2c_hid_acpi 
rc_core intel_lpss_pci crypto_simd i2c_hid ucsi_acpi intel_ish_ipc 
drm_kms_helper hid typec_ucsi xhci_pci cryptd intel_lpss psmouse thunderbolt 
video idma64 intel_ishtp vmd drm xhci_pci_renesas typec wmi pinctrl_tigerlake
  CPU: 3 PID: 6419 Comm: gnome-shell Tainted: P   O   
6.6.0-14-generic #14-Ubuntu
  Hardware name: Dell Inc. Inspiron 7400/072W08, BIOS 1.16.0 04/13/2022
  RIP: 0010:gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau]
  Code: 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 6f c0 b

[Kernel-packages] [Bug 1978133] Re: System freeze followed by kernel panic or blank screen

[Bug Watch Updater]

** Changed in: linux
   Status: Incomplete => Fix Released

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

Title:
  System freeze followed by kernel panic or blank screen

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

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1978133/+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 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown

[Bug Watch Updater]

** Changed in: autopkgtest (Debian)
   Status: New => Fix Committed

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

Title:
  autopkgtest-virt-qemu on noble images sometimes hangs doing copydown

Status in Linux:
  Confirmed
Status in autopkgtest package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in autopkgtest package in Debian:
  Fix Committed

Bug description:
  [Impact]

  It seems that kernel 6.8 introduced a regression in the 9pfs related
  to caching and netfslib, that can cause some user-space apps to read
  content from files that is not up-to-date (when they are used in a
  producer/consumer fashion).

  It seems that the offending commit is this one:

   80105ed2fd27 ("9p: Use netfslib read/write_iter")

  Reverting the commit seems to fix the problem. However the actual bug
  might be in netfslib or how netfslib is used in the 9p context.

  The regression has been reported upstream and we are still
  investigating (https://lore.kernel.org/lkml/Zj0ErxVBE3DYT2Ea@gpd/).

  In the meantime it probably makes sense to temporarily revert the
  commit as a SAUCE patch. Then we will drop the SAUCE patch once we'll
  have a proper fix upstream.

  [Test case]

  The following test should complete correctly without any timeout:

    pull-lp-source -d hello
    autopkgtest-buildvm-ubuntu-cloud -r noble
    autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img

  
  [Fix]

  Revert the following commit (until we have a proper fix upstream):

   80105ed2fd27 ("9p: Use netfslib read/write_iter")

  [Regression potential]

  We may experience other regressions related to 9pfs with this change,
  however it's quite unlikely to happen since we are reverting a commit,
  restoring the previous behavior.

  [Original bug report]

  autopkgtest-virt-qemu sometimes hangs when running tests on noble
  images. Originally reported by schopin, who also provided a
  reproducer:

    pull-lp-source -d hello
    autopkgtest-buildvm-ubuntu-cloud -r noble
    autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img

  I've been able to reproduce it with debugging enabled:

    autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
  /path/to/image

  It can get stuck during different stages, but AFAICT always during
  "copydown" operations, log excerpts follow. It may be a coincidence,
  but this started happening around the time linux-
  image-6.8.0-11-generic (6.8.0-11.11) migrated to noble. The testbeds I
  used booted 6.6 but then rebooted into that 6.8 kernel after being
  upgraded by autopkgtest.

  -- logs --

  Removing autopkgtest-satdep (0) ...
  [...]
  autopkgtest-virt-qemu: DBG: executing copydown 
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ /t/
  autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', 
'/tmp/autopkgtest.output.g8v75e]
  autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader 
name='/dev/null'>", 'deststdout']
  autopkgtest-virt-qemu: DBG:  +< tar --directory 
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ --
  autopkgtest-virt-qemu: DBG:  +> /tmp/autopkgtest-qemu.ztmr6f5k/runcmd sh -ec 
if ! test -d /tmp-
  autopkgtest-virt-qemu: DBG:  +>?

  -- or --

  autopkgtest: DBG: sending command to testbed: copydown 
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ 
/tmp/autopkgtest.H8NDfW/build.DLR/src/
  autopkgtest-virt-qemu: DBG: executing copydown 
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ 
/tmp/autopkgtest.H8NDfW/build.DLR/src/
  autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory', 
'/tmp/autopkgtest.output.c9utq3bx/tests-tree/', '--warning=none', '-c', '.', 
'-f', '-'], ['/tmp/autopkgtest-qemu.qtkcgg5l/runcm]
  autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader 
name='/dev/null'>", 'deststdout', "<_io.BufferedReader name='/dev/null'>", 
'devnull_read', <_io.BufferedReader name='/dev/null'>]
  autopkgtest-virt-qemu: DBG:  +< tar --directory 
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ --warning=none -c . -f -
  autopkgtest-virt-qemu: DBG:  +> /tmp/autopkgtest-qemu.qtkcgg5l/runcmd sh -ec 
if ! test -d /tmp/autopkgtest.H8NDfW/build.DLR/src/; then mkdir -- 
/tmp/autopkgtest.H8NDfW/build.DLR/src/; fi; cd-
  autopkgtest-virt-qemu: DBG:  +>?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056461/+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 1833281] Re: System freeze when memory is put on SWAP in Linux >4.10.x

[Bug Watch Updater]

** Changed in: linux
   Status: Confirmed => Expired

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

Title:
  System freeze when memory is put on SWAP in Linux >4.10.x

Status in Linux:
  Expired
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm reporting this since it's reproduceable the 70% of the time.
  Summary:

  In different circumstances, when the systems starts to swap out RAM
  memory, even small amounts, the system becomes completely unusuable
  and the screen freezes up, no mouse movement, no TTY access or SSH
  access can be made, only SYSRQ keys seem to do something (only reboot,
  so REISUB worked so far though, OOM is useless since the memory/swap
  is not even full)

  The I/O Disk led is stuck to 100% in ALL the following cases when this
  happens.

  So far:
  - This happens even when only ZRAM is enabled, and no swap partition is used.
  - Happens when ZSWAP is used with a swap partition
  - Happens also when a partition without zram or zswap is used
  - Maybe it's AMD specific? 

  However, I'm not experiencing this on my laptop using the same tests.

  My laptop is an Intel one, while my desktop is an AMD Ryzen platform.

  Here are the specs:
  CPU: AMD Ryzen 5 1600 no OC
  GPU: AMD RX 580 8GB
  SSD: Crucial MX500 500GB
  MOBO: MSI B350M Grenade
  RAM: 8GB HyperX Kingston 2667Mhz

  Ubuntu version: 18.04 LTS, backports repo enabled
  Kernel version: 4.18.0-18, official ubuntu repo
  Bios settings: Default

  Additional info: Maybe I'm not 100% sure, but I noticed when using the
  5.0.0-17 generic kernel, the lockups seem to still happen, but they
  recover eventually. Happened only a few times though...

  But will always be frozen for at least 30 seconds, differently from my
  intel laptop where those do occur.

  The SSD make is the same. I bought two of these, they got also the
  same amount of RAM.

  In my laptop those do not occur at all. Swapping memory even huge
  quantities like 1GB or more, do not produce any issues.

  Tests made:
  For testing this behaviour I tried:

  - Compiling the chromium-browser source code (takes up a lot of system
  RAM)

  - Used the "stress" command, using a specific amount of memory to
  decide how many it will be swapped, and here I noticed that even small
  quantities like a couple of megabytes will cause the system to freeze
  the 70% of the times

  Example: "stress --vm 1 --vm-bytes=7G"

  What should happen:
  I expect system slowdowns when swapping out memory since I do not have enough 
RAM, but unlikely when using Windows or my laptop with the same Linux version, 
not a completely unusuable environment. The swap partition is in both cases on 
an SSD.

  Reproduceability: 70% of the times

  Additional info again:
  I'm not sure this is due to any hardware failure, my SSD health is fine, as 
my CPU and RAM. As I said swapping in Windows works fine...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  haru   2076 F pulseaudio
   /dev/snd/controlC2:  haru   2076 F pulseaudio
   /dev/snd/controlC0:  haru   2076 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic 
root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-17-generic N/A
   linux-backports-modules-5.0.0-17-generic  N/A
   linux-firmware1.173.6
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo video
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.K0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR (MS-7A37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.K0:bd01/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A37:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MMORTAR(MS-7A37):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct4:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
 

[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu
  24.04)

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

Bug description:
  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => New

** Changed in: linux
   Status: New => Fix Released

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

Title:
  Frequent boot to black display

Status in Linux:
  Fix Released
Status in Plymouth:
  New
Status in SDDM:
  New
Status in systemd:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  Incomplete
Status in sddm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2063143/+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 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: sddm
   Status: Unknown => New

** Changed in: plymouth
   Status: Unknown => New

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  New
Status in SDDM:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2063143/+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 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  Frequent boot to black display

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

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2063143/+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 1972728] Re: Night light not working on Nvidia Wayland

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  Night light not working on Nvidia Wayland

Status in Mutter:
  Fix Released
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Fix Released

Bug description:
  On the Wayland session using an Nvidia GPU, enabling the Night Light
  setting in the Settings app doesn't change the screen colour
  temperature to a warmer hue regardless of "Sunset to Sunrise" or
  "Manual Schedule" being selected. Switching to the X11 session results
  in Night Light working as expecting.

  I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti).

  $ lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 22:01:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-29 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1972728/+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 2056445] Re: external monitors flash white with every interrupt

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  external monitors flash white with every interrupt

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

Bug description:
  an interesting amdgpu issue:

  I currently have two external monitors, and only one will display the
  desktop at a time - the other is completely white. The interesting
  thing is that with each interrupt that the kernel receives from
  keyboard / mouse, the screens will flip which one is visible. With my
  monitors positioned above and to the left of the laptop's built-in
  display, the flashing monitors feel akin to attending an electronic
  light show, or perhaps a display of fireworks - the monitors flip
  visibility with each keypress.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 05:23:23 2024
  InstallationDate: Installed on 2024-02-02 (34 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+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 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update

[Bug Watch Updater]

** Changed in: linux-firmware
   Status: New => Fix Released

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

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

Status in Linux Firmware:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  Current version of amdgpu binaries in linux-firmware shipped with
  ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems
  when decoding VP9 content with the iGPU on modern AMD mobile processor
  (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).

  The issue has been reported and solved upstream:

  https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044

  [EDIT: fixed link]

  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.

  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding

  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9

  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd

  I'm currently running ubuntu 23.10 (mantic) with binaries from
  upstream and the issue is solved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2058830/+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 2041496] Re: btmgmt --index broken in Mantic

[Bug Watch Updater]

** Changed in: bluez
   Status: Unknown => Fix Released

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

Title:
  btmgmt --index broken in Mantic

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/2041496/+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 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update

[Bug Watch Updater]

** Changed in: linux-firmware
   Status: Unknown => New

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

Title:
  vp9 hw decode broken on modern AMD apus, needs amdgpu update

Status in Linux Firmware:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Mantic:
  New
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  Current version of amdgpu binaries in linux-firmware shipped with
  ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems
  when decoding VP9 content with the iGPU on modern AMD mobile processor
  (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor).

  The issue has been reported and solved upstream:

  https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044

  [EDIT: fixed link]

  Solution dates to the end of February: https://gitlab.com/kernel-
  firmware/linux-
  firmware/-/commit/977332782302476e1c863b09b840f463d0378807

  Ubuntu 24.04 already ships the updated binaries and should not be
  affected.

  Steps to reproduce:
  * on an affected system play a VP9 video with hardware decoding

  Additional links:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807
  * https://bugzilla.redhat.com/show_bug.cgi?id=2267714
  * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9

  Workaround:
  * download the amdgpu folder from upstream linux-firmware repos
  * compress each file with zstd
  * copy into /lib/firmware/amdgpu
  * regenerate the initrd

  I'm currently running ubuntu 23.10 (mantic) with binaries from
  upstream and the issue is solved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2058830/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2057693] Re: Activating autotrim results in high load average due to uninterruptible threads

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  Activating autotrim results in high load average due to
  uninterruptible threads

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When activating the autotrim feature on any ZFS version starting from
  2.2.0 this will lead to a permanent increase of the load average (as
  diplayed in top) due to an uninterruptible vdev_autotrim thread for
  each vdev capable of TRIM.

  This issue has been reported
  (https://github.com/openzfs/zfs/issues/15453) as well as fixed
  (https://github.com/openzfs/zfs/pull/15781) upstream but the fix is
  not yet backported to Ubuntu.

  Since this bug was introduced with version 2.2.0 both mantic as well
  as noble are affected.

  How to reproduce:
  1. Create a pool with at least one TRIM-capable device
  2. run "zpool set autotrim=on "
  3. watch the output of "top" or "runtime" and see how the load average 
increases permanently even when the system is idle by one per vdev
  4. running "ps aux | grep -w D" will show the broken threads:

  [root@test ~]# ps aux | grep -w D\<
  root7193  0.0  0.0  0 0 ?D<   13:07   0:00 
[vdev_autotrim]

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2057693/+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 2056445] Re: external monitors flash white with every interrupt

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  external monitors flash white with every interrupt

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

Bug description:
  an interesting amdgpu issue:

  I currently have two external monitors, and only one will display the
  desktop at a time - the other is completely white. The interesting
  thing is that with each interrupt that the kernel receives from
  keyboard / mouse, the screens will flip which one is visible. With my
  monitors positioned above and to the left of the laptop's built-in
  display, the flashing monitors feel akin to attending an electronic
  light show, or perhaps a display of fireworks - the monitors flip
  visibility with each keypress.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 05:23:23 2024
  InstallationDate: Installed on 2024-02-02 (34 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056445/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Bug Watch Updater]

** Changed in: zfs
   Status: New => Fix Released

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => New

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2056448] Re: hfs: weird file system free block state after creating files and removing them with a mix of i/o operations

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218571.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-03-07T13:11:58+00:00 colin.i.king wrote:

Summary:

create hfs file system, loop-back mount it, run iomix stessor with
stress-ng to exercise with a mix of file I/O operations and remove files
at end. File system is empty but a lot of blocks are used and can't seem
to be recovered.

Kernel: 6.8.0-11-generic

test case:
sudo apt-get install hfsprogs

dd if=/dev/zero of=fs.img bs=1M count=2048
mkfs.hfs fs.img
sudo mount fs.img /mnt
sudo mkdir /mnt/x
df /mnt
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop6 2097128 2015 2095113 1% /mnt

sudo stress-ng --temp-path /mnt/x --iomix 1 -t 2

df /mnt
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/loop6 2097128 674635 1422493 33% /mnt

ls -alR /mnt/
/mnt/:
total 4
drwxr-xr-x 1 root root 3 Mar 7 12:37 .
drwxr-xr-x 23 root root 4096 Feb 28 14:13 ..
drwxr-xr-x 1 root root 2 Mar 7 12:37 x

/mnt/x:
total 0
drwxr-xr-x 1 root root 2 Mar 7 12:37 .
drwxr-xr-x 1 root root 3 Mar 7 12:37 ..

..so file system is 33% full, but no files are on the file system.
Something looks wrong here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056448/comments/1


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  hfs: weird file system free block state after creating files and
  removing them with a mix of i/o operations

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

Bug description:
  Summary:

  create hfs file system, loop-back mount it, run iomix stessor with
  stress-ng to exercise with a mix of file I/O operations and remove
  files at end. File system is empty but a lot of blocks are used and
  can't seem to be recovered.

  Kernel: 6.8.0-11-generic

  test case:
  sudo apt-get install hfsprogs

  dd if=/dev/zero of=fs.img bs=1M count=2048
  mkfs.hfs fs.img 
  sudo mount fs.img /mnt
  sudo mkdir /mnt/x
  df /mnt
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/loop6   2097128  2015   2095113   1% /mnt

  
  sudo stress-ng --temp-path /mnt/x --iomix 1 -t 2

  df /mnt
  Filesystem 1K-blocks   Used Available Use% Mounted on
  /dev/loop6   2097128 674635   1422493  33% /mnt

  
  ls -alR /mnt/
  /mnt/:
  total 4
  drwxr-xr-x  1 root root3 Mar  7 12:37 .
  drwxr-xr-x 23 root root 4096 Feb 28 14:13 ..
  drwxr-xr-x  1 root root2 Mar  7 12:37 x

  /mnt/x:
  total 0
  drwxr-xr-x 1 root root 2 Mar  7 12:37 .
  drwxr-xr-x 1 root root 3 Mar  7 12:37 ..

  
  ..so file system is 33% full, but no files are on the file system. Something 
looks wrong here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2056448/+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 2056451] Re: hfs: concurrent create/unlink can trip -EEXIST on non-existent files

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218570.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-03-07T13:09:02+00:00 colin.i.king wrote:

Summary:

create hfs file system, loop-back mount it, run filename stressor with
stress-ng to exercise filename create/stat/unlink and we get unexpected -EEXIST 
errors.
This can be worked around by adding a sync() call after the unlink() to ensure
metadata is sync'd.

Kernel: 6.8.0-11-generic

test case:
sudo apt-get install hfsprogs

dd if=/dev/zero of=fs.img bs=1M count=2048
mkfs.hfs fs.img
sudo mount fs.img /mnt
sudo mkdir /mnt/x
sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20
stress-ng: info: [132412] setting to a 20 secs run per stressor
stress-ng: info: [132412] dispatching hogs: 8 filename
stress-ng: fail: [132424] filename: open failed on file of length 1 bytes, 
errno=17 (File exists)
stress-ng: fail: [132428] filename: open failed on file of length 20 bytes, 
errno=17 (File exists)
stress-ng: fail: [132423] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
stress-ng: fail: [132421] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
stress-ng: fail: [132428] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
stress-ng: fail: [132426] filename: open failed on file of length 23 bytes, 
errno=17 (File exists)
stress-ng: fail: [132425] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
stress-ng: fail: [132428] filename: open failed on file of length 1 bytes, 
errno=17 (File exists)
stress-ng: fail: [132423] filename: open failed on file of length 7 bytes, 
errno=17 (File exists)
stress-ng: fail: [132423] filename: open failed on file of length 11 bytes, 
errno=17 (File exists)
stress-ng: fail: [132426] filename: open failed on file of length 24 bytes, 
errno=17 (File exists)

adding a sync() call in the stress-ng stressor fixes the issue:

git diff
diff --git a/stress-filename.c b/stress-filename.c
index a64898fb1..b8266f91e 100644
--- a/stress-filename.c
+++ b/stress-filename.c
@@ -308,6 +308,7 @@ static void stress_filename_test(
VOID_RET(int, shim_stat(filename, &buf));

(void)shim_unlink(filename);
+ (void)sync();
}

/* exercise dcache lookup of non-existent filename */

sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20
stress-ng: info: [132461] setting to a 20 secs run per stressor
stress-ng: info: [132461] dispatching hogs: 8 filename
stress-ng: info: [132461] skipped: 0
stress-ng: info: [132461] passed: 8: filename (8)
stress-ng: info: [132461] failed: 0
stress-ng: info: [132461] metrics untrustworthy: 0
stress-ng: info: [132461] successful run completed in 20.05 secs

The sync should not be required by the way, I just added it to
illustrate that there is a racy metadata sync issue in hfs.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056451/comments/1


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  hfs: concurrent create/unlink can trip -EEXIST on non-existent files

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

Bug description:
  Summary:

  create hfs file system, loop-back mount it, run filename stressor with
  stress-ng to exercise filename create/stat/unlink and we get unexpected 
-EEXIST errors.
  This can be worked around by adding a sync() call after the unlink() to ensure
  metadata is sync'd.  

  Kernel: 6.8.0-11-generic

  test case:
  sudo apt-get install hfsprogs

  dd if=/dev/zero of=fs.img bs=1M count=2048
  mkfs.hfs fs.img 
  sudo mount fs.img /mnt
  sudo mkdir /mnt/x
  sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20
  stress-ng: info:  [132412] setting to a 20 secs run per stressor
  stress-ng: info:  [132412] dispatching hogs: 8 filename
  stress-ng: fail:  [132424] filename: open failed on file of length 1 bytes, 
errno=17 (File exists)
  stress-ng: fail:  [132428] filename: open failed on file of length 20 bytes, 
errno=17 (File exists)
  stress-ng: fail:  [132423] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
  stress-ng: fail:  [132421] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
  stress-ng: fail:  [132428] filename: open failed on file of length 30 bytes, 
errno=17 (File exists)
  stress-ng: fail:  [132426] filename: open failed on file of length 23 bytes, 
errno=17 (

[Kernel-packages] [Bug 2051720] Re: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218416.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-01-24T14:29:28+00:00 nickolas wrote:

This issue is still present on kernel 6.7.1 and firmware 20240115. 
Opening a new bug for this as directed in this old bug: 
https://bugzilla.kernel.org/show_bug.cgi?id=215167

$ uname -a
Linux andromeda 6.7.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:14:10 
+ x86_64 GNU/Linux

$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl -b | egrep -i bluetooth
egrep: warning: egrep is obsolescent; using grep -E
Jan 24 00:20:24 andromeda kernel: Bluetooth: Core ver 2.22
Jan 24 00:20:24 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI device and connection manager 
initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: SCO socket layer initialized
Jan 24 00:20:25 andromeda systemd[1]: Reached target Bluetooth Support.
Jan 24 00:20:25 andromeda NetworkManager[790]:   [1706077225.3441] Loaded 
device plugin: NMBluezManager 
(/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: Reading Intel version 
command failed (-110)

Not sure what other logs or info you need, but just let me know if it
would help.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720/comments/0


On 2024-01-30T14:21:11+00:00 nickolas wrote:

This issue is still present in kernel 6.7.2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720/comments/1


On 2024-01-30T17:05:12+00:00 dustin wrote:

I'm also experiencing this issue. It started with kernel 6.5. Bluetooth
has been broken ever since. The issue was not present in earlier
versions of the kernel.

```
$ uname -a

Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```

```
$ lsusb | grep -i bluetooth

Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
```

```
$ journalctl -b | egrep -i bluetooth

Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
```

```
linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

** Bug watch added: Linux Kernel Bug Tracker #215167
   https://bugzilla.kernel.org/show_bug.cgi?id=215167

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

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

Bug description:
  ```
  kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  ```

  This issue started with kernel 6.5. Bluetooth has been broken ever
  since. The issue was not present in earlier versions of the kernel.

  ```
  $ uname -a

  Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth

  Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  ```

  ```
  $ journalctl -b | egrep -i bluetooth

  Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
  Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
  Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
  ```

  ```
  linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2051720/+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 2046504] Re: AMD GPU display is blank when set lower resolution than native mode on eDP

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  AMD GPU display is blank when set lower resolution than native mode on
  eDP

Status in HWE Next:
  Fix Released
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  AMD GPU display is blank when set lower resolution than native mode on eDP.

  [Fix]
  On eDP the invalid modes are set, call mode set for valid modes instead.

  [Test]
  Tested on hardware, all the modes shown in gnome menu can be set OK.

  [Where problems could occur]
  It may break AMD display.

  This issue is not reproduced on v6.2- kernel versions, so SRU for
  oem-6.5 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 482380] Re: Sluggish system after "ACPI: EC: GPE storm detected"

[Bug Watch Updater]

Launchpad has imported 76 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=13502.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-06-10T20:04:11+00:00 sveina wrote:

Starting in 2.6.30, using select() on any file under /proc/acpi/battery
gives the wrong reply, in that it suggests they should be readable
immediately but a read() call in fact blocks for 4-5 seconds.

Prior to this, select worked correctly in that read in fact always
returned immediately.

This is on a MacBookPro4,1, as far as read-edid is concerned. I'll
happily help with any further information you might find useful,
although since I'm using this machine for work I can't take it offline
to run a git-bisection.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/0


On 2009-06-10T20:10:47+00:00 akpm wrote:

I marked this as a regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/1


On 2009-06-11T16:01:23+00:00 astarikovskiy wrote:

please provide dmesg and acpidump outputs.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/2


On 2009-06-11T16:08:54+00:00 sveina wrote:

Created attachment 21854
dmesg output at 20:41 hours uptime, including sleep

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/3


On 2009-06-11T16:09:19+00:00 sveina wrote:

Created attachment 21855
acpidump output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/4


On 2009-06-11T17:07:33+00:00 astarikovskiy wrote:

please uncomment "#define DEBUG" at the beginning of drivers/acpi/ec.c
and attach new dmesg.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/5


On 2009-06-11T20:15:17+00:00 sveina wrote:

Of course that produces a humongous amount of output that overruns the
kernel buffer in short order. Here's /var/log/messages instead, which
means the boot messages are missing.

The system switches from "sort of working" to "non-working" at ~21:59:26
in that log. "Sort of working" meaning reading it takes only 0.1 seconds
on average, which is still a problem, but not as much of one.

I don't really care about how long reading these files take. It can take
a second, or a minute. However, select needs to work correctly on them.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/6


On 2009-06-11T20:15:59+00:00 sveina wrote:

Created attachment 21860
kernel log w/debug on (16MB unpacked)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/7


On 2009-06-11T20:21:17+00:00 astarikovskiy wrote:

select() never returned anything meaningful from /proc/acpi, it is just
not implemented. So, the regression is 4 second read of battery instead
of almost instant...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/8


On 2009-06-11T20:24:32+00:00 sveina wrote:

That regression should be a separate bug, then. The one I reported was
for select.. I suppose that's a WILL_NOT_FIX, if it's an old bug?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/9


On 2009-06-11T20:37:48+00:00 astarikovskiy wrote:

it's a "feature" of procfs. There is no estimate on how long read from
syntetic file takes. Yes, WILL_NOT_FIX is quite probable. You could edit
the header to track the regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/10


On 2009-06-12T07:48:31+00:00 yakui.zhao wrote:

Hi, Sveina
From the acpidump it seems that the battery info is obtained by using the 
SMBUS controller that resides in the EC controller.
But there also exists the acpi device of sbshc/sbs(battery). I don't know 
whether there exists the conflicts.
Will you please disable "CONFIG_ACPI_SBS" in kernel configuration and see 
whether it still takes about 4-5 seconds to read the file of 
/proc/acpi/battery/*
   thanks.

Reply

[Kernel-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  dummy sound on huawei mate d15 laptop

Status in Linux:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I tried different options, but I couldn't raise the sound.
  saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release
  NAME="Green Linux"
  VERSION="21.2 (Victoria)"
  ID=linuxmint
  ID_LIKE="ubuntu debian"
  PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)"
  VERSION_ID="21"
  HOME_URL="https://greenlinux.ru/";
  SUPPORT_URL="https://forum.linuxmint.su/";
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/";
  PRIVACY_POLICY_URL="https://greenlinux.ru/";
  VERSION_CODENAME=victoria
  UBUNTU_CODENAME=jammy
  saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 
   0 [Generic]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xd03c irq 80
   1 [acp]: acp - acp
HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2
  saber716rus@saber716rus-BOM-WXX9 ~>

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2029010/+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 2043905] Re: VT6307 IEEE1394 card causes reboot loop

[Bug Watch Updater]

** Changed in: linux
   Status: In Progress => Fix Released

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

Title:
  VT6307 IEEE1394 card causes reboot loop

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

Bug description:
  used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to 
Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works...  all of the 6.5.0 
64 bit kernel versions do a reboot loop prior to the splash screen display. 
  Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 
gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... 
  latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg 
update" in root terminal reports no available updates.

  in the advanced options of grub I can boot into mantic with the lunar
  6.2.0-36 kernel. Cell phone video capture of the bad boot included...

  Further testing found that a Mantic beta July 3rd build will boot (6.3
  kernel)

  booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing 
hardware 1 piece at a time then replacing if the loop occurred found that as 
soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will 
boot properly. as soon as the card is reinstalled the panic reboot loop starts 
up again... If there was a log generated from the loop I have been unable to 
find one in the /var/log directory...
  I have been unable to get kdump to work...

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2043905/+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 1993668] Re: mSBC codec not available only CVSD one

[Bug Watch Updater]

** Changed in: pipewire
   Status: New => Fix Released

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

Title:
  mSBC codec not available only CVSD one

Status in Linux:
  Confirmed
Status in PipeWire:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in pipewire package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 22.10 and my headset Pixel Buds Pro works correctly
  but only the low-quality CVSD codec is available and not the mSBC one
  for the Handsfree profile.

  I know the Pixel Buds Pro headset are compatible with mSBC because on
  another machine also running Ubuntu 22.10, this headset correctly
  works with the mSBC codec (and the audio quality is much better for
  both input and output audio).

  My motherboard is an Aorus x670 with AMD Zen 4 CPU.

  The bluetooth controller seems to be:

  ```
  Bus 005 Device 003: ID 0e8d:0616 MediaTek Inc. Wireless_Device
  ```

  Let me know if you need more informations.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-09-27 (22 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pipewire 0.3.58-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Tags:  kinetic
  Uname: Linux 5.19.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1993668/+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 2048827] Re: [amdgpu] Mouse cursor theme is grey instead of black

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  [amdgpu] Mouse cursor theme is grey instead of black

Status in Linux:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Triaged

Bug description:
  - this is a fresh install of the latest Ubuntu 24.04

  - I have fully updated the debs and snaps

  - my mouse cursor is grey when it should be black

  - the strange thing is the cursor looks normal when I boot off the USB
  and then looks grey on first boot

  - even more strange is when I went to screenshot the cursor for this
  bug report, it looked normal in the screenshot

  - For graphics I have AMD 6600XT

  
  - I will try in X11 as well to see if this is a Wayland-only issue

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: yaru-theme-gtk 22.04.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 21:57:08 2024
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2048827/+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 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217914.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-09-15T19:33:01+00:00 laktak wrote:

Overview:

Several users report that after upgrading from 6.4.12 to 6.5 the process
scsi_eh_1 will constantly consume >10% CPU resources. This happens most
often in VMs.

Steps to Reproduce:

- Create a VM (e.g. VMware Fusion)
- Create an SCSI disk
- Connect a virtual CD ROM (IDE)
- Boot a 6.4.12 kernel
- Boot a 6.5 kernel

Actual Results:

- no issues for the 6.4.12 kernel
- scsi_eh consumes too much CPU with the 6.5 kernel

Expected Results:

scsi_eh should not consume significant resources.

Build Date & Hardware:

Linux arch 6.5.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 06 Sep 2023 21:01:01 + 
x86_64 GNU/Linux
inside a VMware Fusion VM

Additional Builds and Platforms:

Other users were able to reproduce the error on bare metal hardware.

Additional Information:

More details can be found in this thread:
https://bbs.archlinux.org/viewtopic.php?id=288723

The users loqs and leonshaw helped to narrow it down to this commit:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea

good: 6.4.0-rc1-1-7-g152e52fb6ff1
bad: 6.4.0-rc1-1-8-g624885209f31

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.5/+bug/2048945/comments/0


On 2023-09-15T20:42:23+00:00 bvanassche wrote:

On 9/15/23 12:33, bugzilla-dae...@kernel.org wrote:
> The users loqs and leonshaw helped to narrow it down to this commit:
> 
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea

Damien, can you please take a look?

Thanks,

Bart.

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.5/+bug/2048945/comments/1


On 2023-09-15T20:55:28+00:00 loberman wrote:

On Fri, 2023-09-15 at 13:42 -0700, Bart Van Assche wrote:
> On 9/15/23 12:33, bugzilla-dae...@kernel.org wrote:
> > The users loqs and leonshaw helped to narrow it down to this
> > commit:
> > 
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea
> 
> Damien, can you please take a look?
> 
> Thanks,
> 
> Bart.
> 
I had a quick look at this and its not making sense. The only calls I
see are in the scan when the devices is added and in the re-scan.
It should not be consuming the scsi_eh thread unless some type of udev
events keeps happening.

Would be good to get some
cat /proc//stack of the scsi_eh threads if they are constantly
consuming CPUY

I will try reproduce and try figure out what is going on here.

Thanks
Laurence

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.5/+bug/2048945/comments/2


On 2023-09-15T21:06:07+00:00 loberman wrote:

Not reproducible generically for me

[root@penguin8 ~]# uname -a
Linux penguin8 6.5.0+ #2 SMP PREEMPT_DYNAMIC 

[root@penguin8 ~]# lsscsi
[0:0:0:0]diskATA  Samsung SSD 850  3B6Q  /dev/sdb 
[1:0:0:0]diskATA  Samsung SSD 850  3B6Q  /dev/sda 


USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root1649  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_0]
root1651  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_1]
root1653  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_2]
root1655  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_3]
root1668  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_4]
root1670  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_5]
root1672  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_6]
root1674  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_7]
root1866  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_8]
root1887  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_9]

root1649  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_0]
root1651  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_1]
root1653  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_2]
root1655  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_3]
root1668  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_4]
root1670  0.0  0.0  0 0 ?S16:58   0:00 [scsi_eh_5]
root1672  0.0  0.0  0 0 ?

[Kernel-packages] [Bug 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

[Bug Watch Updater]

** Changed in: bluez (Debian)
   Status: New => Confirmed

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Debian:
  Confirmed

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=194763.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-03-02T11:22:24+00:00 daznis wrote:

Bond0 interface doesn't accept MTU higher than 1500.I can set MTU
perfectly fine for the slave devices. Recreating the bond0 didn't help
to up the MTU.


05:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ 
Network Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ 
Network Connection (rev 01)

[ 1626.840818] bond0: Invalid MTU 9000 requested, hw max 1500
[ 1668.913497] ixgbe :05:00.0 enp5s0f0: changing MTU from 1500 to 9000
[ 1669.176015] ixgbe :05:00.0 enp5s0f0: speed changed to 0 for port enp5s0f0
[ 1669.237523] ixgbe :05:00.0 enp5s0f0: detected SFP+: 5
[ 1669.487920] ixgbe :05:00.0 enp5s0f0: NIC Link is Up 10 Gbps, Flow 
Control: RX/TX
[ 1675.591234] ixgbe :05:00.1 enp5s0f1: changing MTU from 1500 to 9000
[ 1675.855232] ixgbe :05:00.1 enp5s0f1: speed changed to 0 for port enp5s0f1
[ 1675.911259] ixgbe :05:00.1 enp5s0f1: detected SFP+: 6
[ 1676.159087] ixgbe :05:00.1 enp5s0f1: NIC Link is Up 10 Gbps, Flow 
Control: RX/TX
[ 1684.745389] bond0: Invalid MTU 9000 requested, hw max 1500



Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 90:e2:ba:15:68:20
Active Aggregator Info:
Aggregator ID: 2
Number of ports: 2
Actor Key: 13
Partner Key: 221
Partner Mac Address: 02:1c:73:b2:9a:29

Slave Interface: enp5s0f0
MII Status: up
Speed: 1 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:15:68:20
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 90:e2:ba:15:68:20
port key: 13
port priority: 255
port number: 1
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 02:1c:73:b2:9a:29
oper key: 221
port priority: 16000
port number: 373
port state: 61

Slave Interface: enp5s0f1
MII Status: up
Speed: 1 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:15:68:21
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 90:e2:ba:15:68:20
port key: 13
port priority: 255
port number: 2
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 02:1c:73:b2:9a:29
oper key: 221
port priority: 17000
port number: 33141
port state: 61

Settings for enp5s0f0:
Supported ports: [ FIBRE ]
Supported link modes:   1000baseT/Full 
1baseT/Full 
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes:  1000baseT/Full 
1baseT/Full 
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

Settings for enp5s0f1:
Supported ports: [ FIBRE ]
Supported link modes:   1000baseT/Full 
1baseT/Full 
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes:  1000baseT/Full 
1baseT/Full 
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: external
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-
edge/+bug/1679823/comments/0


On 2017-03-06T13:28:00+00:00 jarod wrote:

The fix for this has been added to the net tree and is

[Kernel-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop

[Bug Watch Updater]

** Bug watch added: github.com/codepayne/linux-sound-huawei/issues #26
   https://github.com/codepayne/linux-sound-huawei/issues/26

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

Title:
  dummy sound on huawei mate d15 laptop

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I tried different options, but I couldn't raise the sound.
  saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release
  NAME="Green Linux"
  VERSION="21.2 (Victoria)"
  ID=linuxmint
  ID_LIKE="ubuntu debian"
  PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)"
  VERSION_ID="21"
  HOME_URL="https://greenlinux.ru/";
  SUPPORT_URL="https://forum.linuxmint.su/";
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/";
  PRIVACY_POLICY_URL="https://greenlinux.ru/";
  VERSION_CODENAME=victoria
  UBUNTU_CODENAME=jammy
  saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 
   0 [Generic]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xd03c irq 80
   1 [acp]: acp - acp
HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2
  saber716rus@saber716rus-BOM-WXX9 ~>

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2029010/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
  screen (no screen detected)

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

Bug description:
  When I go into "fullscreen" watching a video while browsing in Firefox
  or when playing a game through Steam (fullscreen mode), the screen
  goes black.

  The workaround I have discovered to get back is to enter the gdm from
  "Ctrl + alt + F1" and then return to the session you were in
  (normally, "Ctrl + alt + F2).

  Edit: It happens when I connect a second monitor and use it as the
  primary display while the laptop screen is disabled.

  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  noctis 2095 F wireplumber
   /dev/snd/controlC0:  noctis 2095 F wireplumber
   /dev/snd/seq:noctis 2090 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:00:55 2023
  InstallationDate: Installed on 2023-10-13 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 amdgpudrmfb
   1 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2020
  dmi.bios.release: 1.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17EKAMS.101
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17EK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
  dmi.product.family: Al
  dmi.product.name: Alpha 17 A4DEK
  dmi.product.sku: 17EK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2044131] Re: i915 regression introduced with 5.5 kernel

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2044131/+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 1917813] Re: HWP and C1E are incompatible - Intel processors

[Bug Watch Updater]

Launchpad has imported 45 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=210741.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-12-17T01:13:11+00:00 dsmythies wrote:

Created attachment 294171
Graph of load sweep up and down at 347 Hertz.

Consider a steady state periodic single threaded workflow, with a work/sleep 
frequency of 347 Hertz and a load somewhere in the ~75% range at the steady 
state operating point.
For the intel-cpufreq CPU frequency scaling driver and powersave governor and 
hwp disabled, it goes indefinitely without any issues.
For the acpi-cpufreq CPU frequency scaling driver and ondemand governor, it 
goes indefinitely without any issues.
For the intel-cpufreq CPU frequency scaling driver and powersave governor and 
hwp enabled, it suffers from overruns.

Why?

For unknown reasons, HWP seems to incorrectly decide that the processor
is idle and spins the PLL down to a very low frequency. Upon exit from
the sleep portion of the periodic workflow it takes a very long time (on
the order of 20 milliseconds (supporting data for that statement will
added in a later posting)), resulting in the periodic job no being able
to complete its work before the next interval, whereas it normally has
plenty of time to do its work. Actually, typical worst case overruns are
around 12 milliseconds, or several work/sleep periods (i.e. it takes a
very long time to catch up.)

The probability of this occurring is about 3%, but varies significantly.
Obviously, the recovery time is also a function of EPP, but mostly this
work has been done with the default EPP of 128. I believe this to be a
sampling and anti-aliasing issue, but can not prove it because HWP is
black box. My best GUESS is:

If the periodic load is busy on a jiffy boundary, such that the tick is on.
Then if it is sleeping at the next jiffy boundary, with a pending wake such 
that idle state 2 was used.
  Then if the rest of the system was idle such that HWP decides to spin down 
the PLL.
Then it is highly probable that upon that idle state 2 exit, the PLL is too 
slow to ramp up and the task will overrun as a result.
Else everything will be fine.

For a 1000 Hz kernel the above suggests that a work/sleep frequency of 500 Hz 
should behave in a binary way, either lots of overruns or none. It does.
For a 1000 Hz kernel the above suggests that a work/sleep frequency of 333.333 
Hz should behave in a binary way, either lots of overruns or none. It does.
Note: in all cases the sleep time has to be within the window of opportunity.

Now, actually I can not prove if the idle state 2 part is a cause or
consequence, but it never happens with it disabled, but at the cost of
significant power.

Another way this issue would manifest itself is as seeming to be an
extraordinary idle exit latency, but would be rather difficult to
isolate as the cause.

processors tested:
Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz (mine)
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (not mine)

HWP has been around for years, why am I just reporting this now?

I never owned an HWP capable processor before. My older i7-2600K based
test computer was getting a little old, so I built a new test computer.
I noticed this issue the same day I first enabled HWP. That was months
ago (notice the dates on the graphs that will eventually be added to
this), and I tried, repeatedly, to get help from Intel via the linux-pm
e-mail list.

Now, given the above system response issue, a new test was developed to
focus specifically on this issue, dubbed the "Inverse Impulse Response"
test. It examines in great detail the CPU frequency rise time after a
brief, less than 1 millisecond, gap in an otherwise continuous workflow.
I'll attach graphs and details in subsequent postings to this bug
report.

While I believe this is an issue entirely within HWP, I have not been
able to prove that there was nothing sent from the kernel somehow
telling HWP to spin down.

Notes:

CPU affinity does not need to be forced, but sometimes is for data
acquisition.

1000 hertz kernels were tested back to kernel 5.2, all failed.

Kernel 5.10-rc7 (I have yet to compile 5.10) also fails.

A 250 hertz kernel was tested, and it did not have this issue in this
area. Perhaps elsewhere, I didn't look.

Both teo and menu idle governors were tested, and while both suffer from
the unexpected CPU frequency drop, teo seems much worse. However failure
points for both governors are repeatable.

The test computers were always checked for any throttling log sticky
bits, and regardless were never anywhere even close to throttling.

Note, however that every HWP capable computer I was to acquire data from
has at least one of those sticky bits set after boot, so they

[Kernel-packages] [Bug 1495124] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=104461.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-09-12T17:54:32+00:00 caravena wrote:

Open bug in launchpad.net :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495124

dmesg:
[ 1739.516411] iwlwifi :01:00.0: Microcode SW error detected.  Restarting 
0x200.
[ 1739.516426] iwlwifi :01:00.0: CSR values:
[ 1739.516435] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
[ 1739.516447] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00
[ 1739.516458] iwlwifi :01:00.0:  CSR_INT_COALESCING: 0Xff40
[ 1739.516469] iwlwifi :01:00.0: CSR_INT: 0X
[ 1739.516479] iwlwifi :01:00.0:CSR_INT_MASK: 0X
[ 1739.516491] iwlwifi :01:00.0:   CSR_FH_INT_STATUS: 0X
[ 1739.516502] iwlwifi :01:00.0: CSR_GPIO_IN: 0X0038
[ 1739.516513] iwlwifi :01:00.0:   CSR_RESET: 0X
[ 1739.516525] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5
[ 1739.516537] iwlwifi :01:00.0:  CSR_HW_REV: 0X00b0
[ 1739.516549] iwlwifi :01:00.0:  CSR_EEPROM_REG: 0Xc4540ffd
[ 1739.516561] iwlwifi :01:00.0:   CSR_EEPROM_GP: 0X9801
[ 1739.516572] iwlwifi :01:00.0:  CSR_OTP_GP_REG: 0X00030001
[ 1739.516583] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044
[ 1739.516594] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0Xf3ad
[ 1739.516605] iwlwifi :01:00.0:   CSR_GP_DRIVER_REG: 0X
[ 1739.516617] iwlwifi :01:00.0:   CSR_UCODE_DRV_GP1: 0X
[ 1739.516628] iwlwifi :01:00.0:   CSR_UCODE_DRV_GP2: 0X
[ 1739.516639] iwlwifi :01:00.0: CSR_LED_REG: 0X0040
[ 1739.516651] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X880c9dea
[ 1739.516662] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
[ 1739.516674] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X
[ 1739.516685] iwlwifi :01:00.0:  CSR_MONITOR_STATUS_REG: 0X43f7ff57
[ 1739.516697] iwlwifi :01:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
[ 1739.516708] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X
[ 1739.516716] iwlwifi :01:00.0: FH register values:
[ 1739.516739] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X0c9e4600
[ 1739.516760] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X00c9e440
[ 1739.516781] iwlwifi :01:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X00e0
[ 1739.516802] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X80801114
[ 1739.516822] iwlwifi :01:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
[ 1739.516843] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0703
[ 1739.516864] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
[ 1739.516885] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
[ 1739.516906] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 
0X
[ 1739.516916] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1
[ 1739.517047] iwlwifi :01:00.0: Start IWL Error Log Dump:
[ 1739.517055] iwlwifi :01:00.0: Status: 0x02CC, count: 6
[ 1739.517063] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT  
[ 1739.517070] iwlwifi :01:00.0: 0x00015920 | uPc
[ 1739.517076] iwlwifi :01:00.0: 0x00015910 | branchlink1
[ 1739.517082] iwlwifi :01:00.0: 0x00015910 | branchlink2
[ 1739.517088] iwlwifi :01:00.0: 0xDBEA | interruptlink1
[ 1739.517094] iwlwifi :01:00.0: 0x | interruptlink2
[ 1739.517100] iwlwifi :01:00.0: 0x0457 | data1
[ 1739.517107] iwlwifi :01:00.0: 0x0001 | data2
[ 1739.517114] iwlwifi :01:00.0: 0x01DC | line
[ 1739.517121] iwlwifi :01:00.0: 0x8080E6B3 | beacon time
[ 1739.517127] iwlwifi :01:00.0: 0x6723C94D | tsf low
[ 1739.517134] iwlwifi :01:00.0: 0x | tsf hi
[ 1739.517141] iwlwifi :01:00.0: 0x | time gp1
[ 1739.517147] iwlwifi :01:00.0: 0x672BAF8D | time gp2
[ 1739.517154] iwlwifi :01:00.0: 0x | time gp3
[ 1739.517161] iwlwifi :01:00.0: 0x754312A8 | uCode version
[ 1739.517168] iwlwifi :01:00.0: 0x00B0 | hw version
[ 1739.517176] iwlwifi :01:00.0: 0x00484B00 | board version
[ 1739.517183] iwlwifi :01:00.0: 0x001C | hcmd
[ 1739.517190] iwlwifi :01:00.0: 0x2F863000 | isr0
[ 1739.517198] iwlwifi :01:00.0: 0x1189F800 | isr1
[ 1739.517205] iwlwifi :01:00.0: 0x0E02 | isr2
[ 1739.51

[Kernel-packages] [Bug 1222440] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.

[Bug Watch Updater]

Launchpad has imported 19 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=60981.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-09-08T15:47:15+00:00 caravena wrote:

Open bug in launchpad.net:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222440


01:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 
[8086:088e] (rev 24)
Subsystem: Intel Corporation Centrino Advanced-N 6235 AGN [8086:4060]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: iwlwifi


[  231.692719] iwlwifi :01:00.0: Microcode SW error detected.  Restarting 
0x200.
[  231.692732] iwlwifi :01:00.0: CSR values:
[  231.692738] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
[  231.692747] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00
[  231.692756] iwlwifi :01:00.0:  CSR_INT_COALESCING: 0Xff40
[  231.692764] iwlwifi :01:00.0: CSR_INT: 0X
[  231.692773] iwlwifi :01:00.0:CSR_INT_MASK: 0X
[  231.692781] iwlwifi :01:00.0:   CSR_FH_INT_STATUS: 0X
[  231.692789] iwlwifi :01:00.0: CSR_GPIO_IN: 0X0038
[  231.692797] iwlwifi :01:00.0:   CSR_RESET: 0X
[  231.692806] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5
[  231.692814] iwlwifi :01:00.0:  CSR_HW_REV: 0X00b0
[  231.692822] iwlwifi :01:00.0:  CSR_EEPROM_REG: 0Xc4540ffd
[  231.692830] iwlwifi :01:00.0:   CSR_EEPROM_GP: 0X9801
[  231.692838] iwlwifi :01:00.0:  CSR_OTP_GP_REG: 0X00030001
[  231.692845] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044
[  231.692854] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0Xd0ed
[  231.692862] iwlwifi :01:00.0:   CSR_GP_DRIVER_REG: 0X
[  231.692870] iwlwifi :01:00.0:   CSR_UCODE_DRV_GP1: 0X
[  231.692877] iwlwifi :01:00.0:   CSR_UCODE_DRV_GP2: 0X
[  231.692885] iwlwifi :01:00.0: CSR_LED_REG: 0X0040
[  231.692893] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X881187ae
[  231.692901] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
[  231.692909] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X
[  231.692917] iwlwifi :01:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
[  231.692925] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X
[  231.692930] iwlwifi :01:00.0: FH register values:
[  231.692948] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X116b8500
[  231.692966] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X01158430
[  231.692983] iwlwifi :01:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X00f0
[  231.693000] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X80801114
[  231.693018] iwlwifi :01:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
[  231.693035] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0703
[  231.693053] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
[  231.693070] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
[  231.693088] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 
0X
[  231.693099] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1
[  231.693109] iwlwifi :01:00.0: FW error in SYNC CMD 
REPLY_TX_LINK_QUALITY_CMD
[  231.693126] CPU: 0 PID: 158 Comm: kworker/u16:7 Tainted: GF  O 
3.11.0-5-generic #11-Ubuntu
[  231.693130] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 
530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
[  231.693163] Workqueue: iwlwifi iwl_bg_scan_completed [iwldvm]
[  231.693172]  01f4 880115307af0 816f23a1 
880116c0
[  231.693181]  880115307b58 a02cf1ef  

[  231.693189]  88011530aee0 810854e0 880115307b20 
880115307b20
[  231.693197] Call Trace:
[  231.693210]  [] dump_stack+0x45/0x56
[  231.693234]  [] iwl_trans_pcie_send_hcmd+0x53f/0x5d0 
[iwlwifi]
[  231.693237] iwlwifi :01:00.0: Start IWL Error Log Dump:
[  231.693244] iwlwifi :01:00.0: Status: 0x004C, count: 6
[  231.693250] iwlwifi :01:00.0: 0x2075 | ADVANCED_SYSASSERT  
[  231.693255] iwlwifi :01:00.0: 0x9BF4 | uPc
[  231.693261] iwlwifi :01:00.0: 0x9BCE | branchlink1
[  231.693266] iwlwifi :01:00.0: 0x9BC

[Kernel-packages] [Bug 1374760] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=90171.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-12-21T05:12:39+00:00 caravena wrote:

[ 2961.582067] iwlwifi :01:00.0: Microcode SW error detected.  Restarting 
0x200.
[ 2961.582079] iwlwifi :01:00.0: CSR values:
[ 2961.582084] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
[ 2961.582092] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00
[ 2961.582100] iwlwifi :01:00.0:  CSR_INT_COALESCING: 0Xff40
[ 2961.582107] iwlwifi :01:00.0: CSR_INT: 0X
[ 2961.582114] iwlwifi :01:00.0:CSR_INT_MASK: 0X
[ 2961.582122] iwlwifi :01:00.0:   CSR_FH_INT_STATUS: 0X
[ 2961.582129] iwlwifi :01:00.0: CSR_GPIO_IN: 0X0038
[ 2961.582136] iwlwifi :01:00.0:   CSR_RESET: 0X
[ 2961.582143] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5
[ 2961.582151] iwlwifi :01:00.0:  CSR_HW_REV: 0X00b0
[ 2961.582158] iwlwifi :01:00.0:  CSR_EEPROM_REG: 0Xcc540ffd
[ 2961.582166] iwlwifi :01:00.0:   CSR_EEPROM_GP: 0X9801
[ 2961.582173] iwlwifi :01:00.0:  CSR_OTP_GP_REG: 0X00030001
[ 2961.582180] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044
[ 2961.582187] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0X22d0
[ 2961.582194] iwlwifi :01:00.0:   CSR_GP_DRIVER_REG: 0X
[ 2961.582201] iwlwifi :01:00.0:   CSR_UCODE_DRV_GP1: 0X
[ 2961.582209] iwlwifi :01:00.0:   CSR_UCODE_DRV_GP2: 0X
[ 2961.582216] iwlwifi :01:00.0: CSR_LED_REG: 0X0040
[ 2961.582224] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X880cdd12
[ 2961.582231] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200
[ 2961.582238] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X
[ 2961.582246] iwlwifi :01:00.0:  CSR_MONITOR_STATUS_REG: 0X43f7f757
[ 2961.582253] iwlwifi :01:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
[ 2961.582260] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X
[ 2961.582265] iwlwifi :01:00.0: FH register values:
[ 2961.582282] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X1193c500
[ 2961.582299] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X01190060
[ 2961.582315] iwlwifi :01:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X00d8
[ 2961.582331] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X80801114
[ 2961.582348] iwlwifi :01:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
[ 2961.582364] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0703
[ 2961.582380] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
[ 2961.582397] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff0001
[ 2961.582414] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 
0X
[ 2961.582419] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1
[ 2961.582543] iwlwifi :01:00.0: Start IWL Error Log Dump:
[ 2961.582549] iwlwifi :01:00.0: Status: 0x02CC, count: 6
[ 2961.582554] iwlwifi :01:00.0: 0x28AA | ADVANCED_SYSASSERT  
[ 2961.582558] iwlwifi :01:00.0: 0x00015984 | uPc
[ 2961.582562] iwlwifi :01:00.0: 0x00015974 | branchlink1
[ 2961.582566] iwlwifi :01:00.0: 0x00015974 | branchlink2
[ 2961.582570] iwlwifi :01:00.0: 0xDBEA | interruptlink1
[ 2961.582574] iwlwifi :01:00.0: 0x | interruptlink2
[ 2961.582578] iwlwifi :01:00.0: 0x0729 | data1
[ 2961.582582] iwlwifi :01:00.0: 0x0023 | data2
[ 2961.582586] iwlwifi :01:00.0: 0x01F3 | line
[ 2961.582590] iwlwifi :01:00.0: 0x1F00D2F0 | beacon time
[ 2961.582594] iwlwifi :01:00.0: 0xBD8A8D10 | tsf low
[ 2961.582598] iwlwifi :01:00.0: 0x0033 | tsf hi
[ 2961.582601] iwlwifi :01:00.0: 0x | time gp1
[ 2961.582605] iwlwifi :01:00.0: 0xB029F31F | time gp2
[ 2961.582609] iwlwifi :01:00.0: 0x | time gp3
[ 2961.582613] iwlwifi :01:00.0: 0x754312A8 | uCode version
[ 2961.582617] iwlwifi :01:00.0: 0x00B0 | hw version
[ 2961.582621] iwlwifi :01:00.0: 0x00484B00 | board version
[ 2961.582625] iwlwifi :01:00.0: 0x001C | hcmd
[ 2961.582629] iwlwifi :01:00.0: 0xAF863000 | isr0
[ 2961.582633] iwlwifi :01:00.0: 0x1189F800 | isr1
[ 2961.582637] iwlwifi :01:00.0: 0x0E1A | isr2
[ 2961.582641] iwlwifi :01:00.0: 0x0543FCC2 | isr3
[ 2961.582645] iwlwifi :01:00.0: 0x | is

[Kernel-packages] [Bug 1284397] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=71121.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-02-25T01:38:55+00:00 caravena wrote:

Open bug in launchpad.net

"[ 4497.019702] iwlwifi :01:00.0: Microcode SW error detected. Restarting 
0x200.
[ 4497.019714] iwlwifi :01:00.0: CSR values:
[ 4497.019719] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
[ 4497.019729] iwlwifi :01:00.0: CSR_HW_IF_CONFIG_REG: 0X00484b00
[ 4497.019738] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40
[ 4497.019746] iwlwifi :01:00.0: CSR_INT: 0X
[ 4497.019754] iwlwifi :01:00.0: CSR_INT_MASK: 0X
[ 4497.019763] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X
[ 4497.019771] iwlwifi :01:00.0: CSR_GPIO_IN: 0X003c
[ 4497.019778] iwlwifi :01:00.0: CSR_RESET: 0X
[ 4497.019787] iwlwifi :01:00.0: CSR_GP_CNTRL: 0X080403c5
[ 4497.019795] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0
[ 4497.019803] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xcc140ffd
[ 4497.019810] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801
[ 4497.019818] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001
[ 4497.019827] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044
[ 4497.019835] iwlwifi :01:00.0: CSR_GP_UCODE_REG: 0X7027
[ 4497.019842] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X
[ 4497.019850] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X
[ 4497.019858] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X
[ 4497.019866] iwlwifi :01:00.0: CSR_LED_REG: 0X0040
[ 4497.019874] iwlwifi :01:00.0: CSR_DRAM_INT_TBL_REG: 0X880c2d84
[ 4497.019882] iwlwifi :01:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
[ 4497.019889] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X
[ 4497.019897] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a
[ 4497.019905] iwlwifi :01:00.0: CSR_DBG_HPET_MEM_REG: 0X
[ 4497.019910] iwlwifi :01:00.0: FH register values:
[ 4497.019929] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0bba9700
[ 4497.019946] iwlwifi :01:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00bb9290
[ 4497.019964] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X0050
[ 4497.019981] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114
[ 4497.01] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc
[ 4497.020030] iwlwifi :01:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0703
[ 4497.020048] iwlwifi :01:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
[ 4497.020066] iwlwifi :01:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
[ 4497.020084] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X
[ 4497.020091] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1
[ 4497.020218] iwlwifi :01:00.0: Start IWL Error Log Dump:
[ 4497.020226] iwlwifi :01:00.0: Status: 0x02CC, count: 6
[ 4497.020235] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT
[ 4497.020243] iwlwifi :01:00.0: 0x00015920 | uPc
[ 4497.020250] iwlwifi :01:00.0: 0x00015910 | branchlink1
[ 4497.020257] iwlwifi :01:00.0: 0x00015910 | branchlink2
[ 4497.020264] iwlwifi :01:00.0: 0xDBEA | interruptlink1
[ 4497.020277] iwlwifi :01:00.0: 0x | interruptlink2
[ 4497.020281] iwlwifi :01:00.0: 0x0A0D | data1
[ 4497.020284] iwlwifi :01:00.0: 0x0008 | data2
[ 4497.020288] iwlwifi :01:00.0: 0x01DC | line
[ 4497.020292] iwlwifi :01:00.0: 0xA00157F5 | beacon time
[ 4497.020296] iwlwifi :01:00.0: 0x823E480B | tsf low
[ 4497.020299] iwlwifi :01:00.0: 0x0002 | tsf hi
[ 4497.020302] iwlwifi :01:00.0: 0x | time gp1
[ 4497.020306] iwlwifi :01:00.0: 0x0B64FC55 | time gp2
[ 4497.020309] iwlwifi :01:00.0: 0x | time gp3
[ 4497.020313] iwlwifi :01:00.0: 0x754312A8 | uCode version
[ 4497.020316] iwlwifi :01:00.0: 0x00B0 | hw version
[ 4497.020320] iwlwifi :01:00.0: 0x00484B00 | board version
[ 4497.020323] iwlwifi :01:00.0: 0x001C | hcmd
[ 4497.020327] iwlwifi :01:00.0: 0xAFA63840 | isr0
[ 4497.020331] iwlwifi :01:00.0: 0x1189F800 | isr1
[ 4497.020335] iwlwifi :01:00.0: 0x0E1F | isr2
[ 4497.020339] iwlwifi :01:00.0: 0x0147FCC2 | isr3
[ 4497.020343] iwlwifi :01:00.0: 0x | isr4
[ 4497.020347] iwlwifi :01:00.0: 0x1112 | isr_pref
[ 4497.020351] iwlwifi :01:00.0: 0x000260A4 | wait_event
[ 4497.020355] iwlwifi :01:00.0: 0x61F6 | l2p_control
[ 4497.020359] iwlwifi :01:00.0: 0xA735 | l2p_duration
[ 4497.020363] iwlwifi :01:00.0: 0x0003 | l2p_mhvalid
[ 4497.020367] iwlwifi :01:00.0: 0x00101040 | l2p_addr_match
[ 4497.020372] iwlwifi :01:00.0: 0x0005 | lmpm_pmg_sel
[ 4497.

[Kernel-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
  screen (no screen detected)

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

Bug description:
  When I go into "fullscreen" watching a video while browsing in Firefox
  or when playing a game through Steam (fullscreen mode), the screen
  goes black.

  The workaround I have discovered to get back is to enter the gdm from
  "Ctrl + alt + F1" and then return to the session you were in
  (normally, "Ctrl + alt + F2).

  Edit: It happens when I connect a second monitor and use it as the
  primary display while the laptop screen is disabled.

  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  noctis 2095 F wireplumber
   /dev/snd/controlC0:  noctis 2095 F wireplumber
   /dev/snd/seq:noctis 2090 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:00:55 2023
  InstallationDate: Installed on 2023-10-13 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 amdgpudrmfb
   1 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2020
  dmi.bios.release: 1.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17EKAMS.101
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17EK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
  dmi.product.family: Al
  dmi.product.name: Alpha 17 A4DEK
  dmi.product.sku: 17EK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2043905] Re: VT6307 IEEE1394 card causes reboot loop

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217993.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-10-10T21:00:25+00:00 matthias.schrumpf wrote:

Kernel 6.5 causes a crash immediately after selecting it in GRUB or
trying to boot with it via other means. This crash always leads into a
bootloop if no other kernel is selected.

A successful boot with kernel 6.5 is impossible, so no log data could be
collected.

This error can be reproduced on many distros including Arch, Endeavour
OS, Manjaro, Fedora and OpenSuse.

The computer is working perfectly fine with older kernels up to and
including 6.4. CPU, RAM and hard drives have all been checked thoroughly
and no errors could be found.

Current OS: 
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.4.15-200.fc38.x86_64 (64-bit)
Graphics Platform: X11

Hardware: 
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C91
System Version: 1.0

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/0


On 2023-10-11T14:41:55+00:00 aros wrote:

Could you please bisect?

https://docs.kernel.org/admin-guide/bug-bisect.html

Otherwise this bug report has very slim chances of being fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/1


On 2023-10-12T09:39:15+00:00 bagasdotme wrote:

Do you have any out-of-tree modules that may cause this regression?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/2


On 2023-10-16T21:01:04+00:00 matthias.schrumpf wrote:

(In reply to Artem S. Tashkinov from comment #1)
> Could you please bisect?
> 
> https://docs.kernel.org/admin-guide/bug-bisect.html
> 
> Otherwise this bug report has very slim chances of being fixed.
I'm sorry, I don't have the basic knowledge necessary for performing a 
bisection. 

(In reply to Bagas Sanjaya from comment #2)
> Do you have any out-of-tree modules that may cause this regression?
No, not to my knowledge. I tried this with live images or fresh installs of 
Arch, Endeavour OS, Manjaro, Fedora and OpenSuse and I didn't change anything 
beyond the settings and customizations that these distros do by default.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/3


On 2023-10-16T23:55:15+00:00 bagasdotme wrote:

On 17/10/2023 04:01, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=217993
> 
> --- Comment #3 from matthias.schru...@freenet.de ---
> (In reply to Artem S. Tashkinov from comment #1)
>> Could you please bisect?
>>
>> https://docs.kernel.org/admin-guide/bug-bisect.html
>>
>> Otherwise this bug report has very slim chances of being fixed.
> I'm sorry, I don't have the basic knowledge necessary for performing a
> bisection. 
> 

Then refer to Documentation/admin-guide/bug-bisect.rst in the kernel
sources for instructions.

> (In reply to Bagas Sanjaya from comment #2)
>> Do you have any out-of-tree modules that may cause this regression?
> No, not to my knowledge. I tried this with live images or fresh installs of
> Arch, Endeavour OS, Manjaro, Fedora and OpenSuse and I didn't change anything
> beyond the settings and customizations that these distros do by default.
> 

So you have this regression there?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/4


On 2023-10-18T21:36:42+00:00 matthias.schrumpf wrote:

(In reply to Bagas Sanjaya from comment #4)
> So you have this regression there?

What do you mean?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/5


On 2023-10-24T14:54:14+00:00 aros wrote:

Given that seemingly you're the only Linux user who has this issue, your
only bet of fixing it is performing regression testing.

The URL provided above has enough information to do so.

If that's not enough, you may simply Google the appropriate questions,
e.g.

1) How to compile and install the Linux kernel
2) How to install GCC in Distro_X

It's all quite easy if you get down to it. No one but you can do it
unfortunately.

Reply at:
https://bugs.

[Kernel-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Bug Watch Updater]

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Bug Watch Updater]

** Changed in: linux
   Status: Fix Released => Confirmed

** Bug watch added: Linux Kernel Bug Tracker #218050
   https://bugzilla.kernel.org/show_bug.cgi?id=218050

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1878279/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => New

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2042867] Re: Changing display resolution leads into black screen

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  Changing display resolution leads into black screen

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Since updating into 23.10, when I change my build-in display from
  2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen
  black and unable to use.

  The only resolution that works is the predefined one.

  This bug wasn't present on the previous release, 23.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 19:37:48 2023
  InstallationDate: Installed on 2023-05-05 (185 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
  dmi.bios.date: 04/18/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UM5401QAB_UM5401QA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UM5401QAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UM5401QAB_UM5401QA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042867/+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 1848013] Re: [needs-packaging] liburing package needed for >= 5.1 kernels

[Bug Watch Updater]

** Changed in: debian
   Status: Unknown => Fix Released

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

Title:
  [needs-packaging] liburing package needed for >= 5.1 kernels

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Debian:
  Fix Released

Bug description:
  eoan will ship with a 5.3 kernel and has support for the io_uring
  interface.

  In order to allow applications to use that the userspace library
  liburing (http://git.kernel.dk/cgit/liburing/) should be packaged in
  addition to the 5.3 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1848013/+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 2042357] Re: Merge crash 8.0.3 into Noble

[Bug Watch Updater]

** Changed in: crash (Debian)
   Status: New => Fix Released

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress
Status in crash package in Debian:
  Fix Released

Bug description:
  Work in progress; rebasing on 8.0.3+ds1-3, and testing.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #218092
   https://bugzilla.kernel.org/show_bug.cgi?id=218092

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  [Impact]

  Keyboard and touchpad doesn't work on some recent systems, and also
  s2idle is broken.

  [Fix]

  Two upstream commits.

  128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT 
compatibility
  3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops

  [Test case]

  boot a fixed kernel and test that input and s2idle works.

  [Where problems could occur]

  A buggy bios could maybe advertise a system being PCAT compatible when
  it's not, though in such a case it might have been already caught
  before.

  --

  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2042357] Re: Merge crash 8.0.3 into Noble

[Bug Watch Updater]

** Changed in: crash (Debian)
   Status: Unknown => New

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

Title:
  Merge crash 8.0.3 into Noble

Status in crash package in Ubuntu:
  In Progress
Status in crash package in Debian:
  New

Bug description:
  Work in progress; testing changes on PPA.

  Debian bugs:

  https://bugs.debian.org/1054805
  Please update crash to 8.0.3

  https://bugs.debian.org/1055117
  FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  22.04.3, zen 4 7840, screen turn white exception

Status in Linux:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  New

Bug description:
  My screen suddenly turned completely white, then only the bottom half
  was white, but I can still operate the application window. When moving
  the application window, the bottom half of the screen turns the Ubuntu
  theme color.

  Only lock and unlock the screen or turn off the screen can fix the
  situation.

  There are some photo about the exception attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3
  Uname: Linux 6.5.0-1006-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 12:26:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3818]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 83AM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem 
root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2023
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MKCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: XiaoXinPro 14 APH8
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8:
  dmi.product.family: XiaoXinPro 14 APH8
  dmi.product.name: 83AM
  dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8
  dmi.product.version: XiaoXinPro 14 APH8
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042054/+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 2041903] Re: Bluetooth stutters because of bug in kernel

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217673.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-07-14T22:29:56+00:00 cydiaimpactor2003 wrote:

Created attachment 304639
The dmesg output after boot for the 6.5 RC1 mainline kernel

I have a Lenovo ThinkPad X1 Yoga Gen 7 running Arch Linux. Linux 6.4 and
higher, cause audio distortion. Sometimes, this occurs to the point that
nearly nothing is discernible. This carries over to wired headphones.
The issue occurs on the entire mainline 6.4.x kernel series and also the
6.4.3 stable and 6.5 RC1 kernel, which are the latest at the time of
writing. The issue occurs on both the Arch distributed kernels, and the
mainline kernels.

Linux kernels 6.3.x are not affected and neither is the 6.1 LTS kernel
series which is what I am temporarily using. On Windows 10/11 too, the
audio works as it should. This indicates that my hardware is not at
fault. Bluetooth audio is not impacted from my testing, either.

The distortion doesn't start immediately. It either occurs automatically
after a random amount of time, or when I increase/decrease the volume,
or when I skip forward/backward to a section. In order to stop the
distortion, I have to either increase/decrease the volume until it
stops, or skip forward/backward until it stops, or restart Pipewire via
systemd, however it starts again due to one of the aforementioned
reasons.

At the time of this report, I am running Pipewire 0.3.74 and Wireplumber
0.4.14. This also doesn't seem like a Pipewire/Wireplumber issue, since
these same versions work fine on the 6.1 LTS kernels without causing any
audio distortion.

I wrote about this on the Arch Linux forums, too, and seems like at
least two other people are facing this issue. Here's the forum post:
https://bbs.archlinux.org/viewtopic.php?id=287068

Furthermore, I filed a bug report on the Arch Linux Bug Reporter, where
they suggested that the issue is a kernel regression and should be
reported upstream, here. Here's the bug report that I filed on the Arch
Linux Bug Reporter for anyone interested:
https://bugs.archlinux.org/task/79081?project=1&pagenum=10

I have attached the dmesg outputs of the mainline 6.5 RC1 kernel.

Here's some audio related hardware information from my device:

inxi -A

Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio
driver: sof-audio-pci-intel-tgl
API: ALSA v: k6.5.0-rc1-1-mainline status: kernel-api


pactl info

Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 138
Tile Size: 65472
User Name: tux
Host Name: NSA-Terminal-4
Server Name: PulseAudio (on PipeWire 0.3.74)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: 
alsa_output.pci-_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink
Default Source: 
alsa_input.pci-_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_6__source
Cookie: f9dc:5e7a


I can't figure out why this is happening. Kindly ask for any more information 
that is necessary. Thank you.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041903/comments/0


On 2023-07-14T22:33:17+00:00 cydiaimpactor2003 wrote:

Created attachment 304640
Pactl detailed sound card information

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041903/comments/1


On 2023-07-14T22:48:27+00:00 cydiaimpactor2003 wrote:

Also, please pardon me if I did something wrong with filing the bug
report. This is my first time filing one.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041903/comments/2


On 2023-07-15T10:46:43+00:00 bagasdotme wrote:

(In reply to Iyer from comment #0)
> Created attachment 304639 [details]
> The dmesg output after boot for the 6.5 RC1 mainline kernel
> 
> I have a Lenovo ThinkPad X1 Yoga Gen 7 running Arch Linux. Linux 6.4 and
> higher, cause audio distortion. Sometimes, this occurs to the point that
> nearly nothing is discernible. This carries over to wired headphones. The
> issue occurs on the entire mainline 6.4.x kernel series and also the 6.4.3
> stable and 6.5 RC1 kernel, which are the latest at the time of writing. The
> issue occurs on both the Arch distributed kernels, and the mainline kernels.
> 
> Linux kernels 6.3.x are not affected and neither is the 6.1 LTS kernel
> series which is what I am temporarily using. On Windows 10/11 too, the audio
> works as it should

[Kernel-packages] [Bug 2041670] Re: tmpfs: O_DIRECT | O_CREATE open reports open failure but actually creates a file.

[Bug Watch Updater]

** Changed in: linux
   Status: Confirmed => Unknown

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

Title:
   tmpfs: O_DIRECT | O_CREATE open reports open failure but actually
  creates a file.

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

Bug description:
  creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
  O_CREAT, 0666) reports an open failure error EINVAL, but still creates
  the file. The file should not be created if we hit such an error.

  Tested and fails on:
  mantic amd64: 6.5.0-10-generic
  lunar amd64: 6.2.0-35-generic
  jammie amd64: 5.15.0-generic
  focal: 5.4.0-165-generic
  bionic: 4.15.0-213-generic
  trusty: 4.4.0-148-generic

  
  sudo mkdir /mnt/tmpfs
  sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
  sudo chmod 666 /mnt/tmpfs
  gcc reproducer.c -o reproducer
  sudo ./reproducer

  Run the attached program. It reports an open failure (errno 22,
  EINVAL) but still manages to create the file.

  Note this was original discovered by running stress-ng on tmpfs with
  the open stressor: stress-ng --open 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2041670/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

[Bug Watch Updater]

Launchpad has imported 87 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218003.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-10-12T07:44:05+00:00 suroto wrote:

Hello,

I have installed fedora workstation 38, with kernel default (versi 6.2 ??).
But keyboard not working.
Then I try ubuntu 22.04.3 LTS . it's same problem.
Then try upgrade kernel of Fedora Workstation 38 to kernel 6.6..
keyboard still not working.

It's possible fix it ?

Thank You
SUroto

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/26


On 2023-10-12T08:25:24+00:00 suroto wrote:

additional details hardware:
S/N : Pf4DM1wG
Model Name:  Lenovo V14 G4 AMN.  ( before any typo mistake, G14)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/27


On 2023-10-12T09:20:16+00:00 bagasdotme wrote:

(In reply to Suroto from comment #0)
> Hello,
> 
> I have installed fedora workstation 38, with kernel default (versi 6.2 ??).
> But keyboard not working.
> Then I try ubuntu 22.04.3 LTS . it's same problem.
> Then try upgrade kernel of Fedora Workstation 38 to kernel 6.6..
> keyboard still not working.
> 

Does hotkeys (usually laptop-specific) have problem?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/28


On 2023-10-12T09:44:55+00:00 suroto wrote:

hotkey working only on the contras screen key

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/29


On 2023-10-12T12:20:24+00:00 aros wrote:

Mario, could you take a look please?


This was reported months ago:

https://forum.manjaro.org/t/lenovo-amd-no-keyboard/141597/5

https://unix.stackexchange.com/questions/751668/lenovo-v15-g4-amn-mouse-
and-keyboard-is-not-working-under-linux

https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.2/+bug/2034477

https://askubuntu.com/questions/1480477/laptop-keyboard-and-mosuepad-
dosnt-work-on-lenovo-v15-g4-amn-type-82yu

Multiple Lenovo laptops exhibit this issue and the company doesn't seem
to care one bit. They could have fixed the issue themselves. Please just
don't buy or recommend their products to anyone who cares about Linux.
I've no idea who to ping or what to do.

I've heard that some modern laptops have some sort of I2C (?)
multiplexors which need to be set up properly in order to enable
keyboard input but how it all works, again I've no clue.

I'm CC'ing Mario Limonciello because I remember he knows something about
that. Maybe he could chime in and give the instructions how to debug the
issue and fix it all the affected people.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/30


On 2023-10-12T12:28:21+00:00 aros wrote:

CC'ing Tamim Khan for good measure.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/31


On 2023-10-13T01:56:45+00:00 suroto wrote:

Thank you for your explanation.

Since 15 years ago, I have installed Linux on various brands and types of 
computers,
Just recently, I encountered a hardware problem that Linux doesn't recognize.

I will try to send an issue ticket to Levono

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/32


On 2023-10-13T15:29:25+00:00 p0lloc wrote:

Same issue with IdeaPad Slim 3 14AMN8, quite a lot of good info in
https://bugzilla.kernel.org/show_bug.cgi?id=217873 but no solution.

I have tried an immense amount of kernel parameter combinations and
patching the latest mainline kernel with IRQ quirks of different
combinations, to no avail.

The only combination of i8042 parameters that do ANYTHING is
"i8042.direct i8042.dumbkbd i8042.noloop i8042.nopnp" which finally gets
a working keyboard (but with an insane delay of 15-60 seconds per
keypress). Dumbkbd doesn't seem strictly necessary but you receive 10-20
commas before any actual keyboard input gets through.

Really hoping for a solution or any suggestions on what to try next.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/39


On 2023-10-13T15:32:10+00:00 mario.limonciello wrote:

Can both of you guys please test with the latest 6.6-rc, and if it
co

[Kernel-packages] [Bug 2041670] Re: tmpfs: O_DIRECT | O_CREATE open reports open failure but actually creates a file.

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218049.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-10-27T13:53:48+00:00 colin.i.king wrote:

Created attachment 305300
C reproducer of the problem. Run it on a tmpfs file system mounted on /mnt/tmpfs

creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
O_CREAT, 0666) reports an open failure error EINVAL, but still creates
the file. The file should not be created if we hit such an error.

Tested this on 6.6.0-rc7 and 6.1.0-13 mainline kernels, x86-64.

mkdir /mnt/tmpfs
sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
sudo chmod 666 /mnt/tmpfs

Run the attached program. It reports an open failure (errno 22, EINVAL)
but still manages to create the file.

Note this was original discovered by running stress-ng on tmpfs with the
open stressor: stress-ng --open 1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/0


On 2023-10-27T14:30:36+00:00 colin.i.king wrote:

See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/3


On 2023-10-27T14:36:29+00:00 colin.i.king wrote:

Also occurs on ramfs too.

Seems to occur on kernels from 4.4.x to current 6.6-rc6 (not tested
anything newer).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/4


On 2023-10-27T14:48:49+00:00 aros wrote:

Confirming and CC'ing Christian Brauner.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/5


On 2023-10-27T14:50:39+00:00 aros wrote:

Actually Hugh Dickins added O_DIRECT support, CC'ing him as well.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/6


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
   tmpfs: O_DIRECT | O_CREATE open reports open failure but actually
  creates a file.

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

Bug description:
  creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
  O_CREAT, 0666) reports an open failure error EINVAL, but still creates
  the file. The file should not be created if we hit such an error.

  Tested and fails on:
  mantic amd64: 6.5.0-10-generic
  lunar amd64: 6.2.0-35-generic
  jammie amd64: 5.15.0-generic
  focal: 5.4.0-165-generic
  bionic: 4.15.0-213-generic
  trusty: 4.4.0-148-generic

  
  sudo mkdir /mnt/tmpfs
  sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
  sudo chmod 666 /mnt/tmpfs
  gcc reproducer.c -o reproducer
  sudo ./reproducer

  Run the attached program. It reports an open failure (errno 22,
  EINVAL) but still manages to create the file.

  Note this was original discovered by running stress-ng on tmpfs with
  the open stressor: stress-ng --open 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2041670/+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 2040102] Re: kernel warning when open the lid

[Bug Watch Updater]

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217947.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-09-25T09:12:13+00:00 jirislaby wrote:

Downstream report:
https://bugzilla.suse.com/show_bug.cgi?id=1215602

LKML link:
https://lore.kernel.org/all/047d3c51-0a9e-4c3e-beef-625a7aa4f...@kernel.org/

according to logs, since 6.3 (up to 6.5.4 now), I repeatedly see:
> WARNING: CPU: 14 PID: 962 at drivers/acpi/platform_profile.c:74
> platform_profile_show+0xb1/0x100 [platform_profile]
> Modules linked in: ccm michael_mic ...
> CPU: 14 PID: 962 Comm: power-profiles- Kdump: loaded Not tainted
> 6.5.4-6-default #1 openSUSE Tumbleweed (unreleased)
> dd37106c593be78644bb80e3c1534d801bf4cb36
> Hardware name: LENOVO 21CRS0K83K/21CRS0K83K, BIOS R22ET60W (1.30 ) 02/09/2023
> RIP: 0010:platform_profile_show+0xb1/0x100 [platform_profile]
> Code: d0 a8 ...
> RSP: 0018:9c1ac0b97db0 EFLAGS: 00010296
> RAX:  RBX:  RCX: 8fc35be0
> RDX:  RSI: 9c1ac0b97db4 RDI: c0a8b0a0
> RBP: 8955ca54 R08: 895b9f1ed180 R09: 895559ea1bc0
> R10: 031a400e R11: 0003f680 R12: 895b9f1ed180
> R13: 9c1ac0b97e50 R14: 0001 R15: 9c1ac0b97ee8
> FS:  7f71b0e71900() GS:895b9f10() knlGS:
> CS:  0010 DS:  ES:  CR0: 80050033
> CR2: 7fe402ea3400 CR3: 00012004c000 CR4: 00750ee0
> PKRU: 5554
> Call Trace:
>  
>  sysfs_kf_seq_show+0xab/0x100
>  seq_read_iter+0x123/0x480
>  vfs_read+0x1b8/0x300

It's:
WARN_ON((profile < 0) || (profile >= ARRAY_SIZE(profile_names

So I put there one more print:
dev_warn(dev, "profile=%d profile_get=%ps\n",
 profile, cur_profile->profile_get);

and I see:
: profile=-1883022368 profile_get=dytc_profile_get [thinkpad_acpi]
: profile=-1510173440 profile_get=dytc_profile_get [thinkpad_acpi]
: profile=-1510173440 profile_get=dytc_profile_get [thinkpad_acpi]
: profile=-966231712 profile_get=dytc_profile_get [thinkpad_acpi]
: profile=-1578420592 profile_get=dytc_profile_get [thinkpad_acpi]
: profile=-1578420592 profile_get=dytc_profile_get [thinkpad_acpi]
: profile=-1578420592 profile_get=dytc_profile_get [thinkpad_acpi]

I wonder about dev passed to dytc_profile_get() having empty name
(nothing before colon above)? Is that expected?

Ah, convert_dytc_to_profile()'s retval is not checked in 
dytc_profile_refresh(). Adding:
--- a/drivers/platform/x86/thinkpad_acpi.c
+++ b/drivers/platform/x86/thinkpad_acpi.c
@@ -10418,7 +10418,14 @@ static void dytc_profile_refresh(void)
return;

perfmode = (output >> DYTC_GET_MODE_BIT) & 0xF;
-   convert_dytc_to_profile(funcmode, perfmode, &profile);
+   err = convert_dytc_to_profile(funcmode, perfmode, &profile);
+   if (err) {
+   pr_warn("%s: mmc=%u psc=%u mmc_get=%u funcmode=%d output=0x%x 
perfmode=%d\n",
+  __func__, !!(dytc_capabilities & BIT(DYTC_FC_MMC)),
+  !!(dytc_capabilities & BIT(DYTC_FC_PSC)),
+  dytc_mmc_get_available, funcmode, output, perfmode);
+   return;
+   }
if (profile != dytc_current_profile) {
dytc_current_profile = profile;
platform_profile_notify();

fixes the warning, of course.

The output is:
dytc_profile_refresh: mmc=0 psc=1 mmc_get=0 funcmode=0 output=0x1f001 
perfmode=15

So using psc mode, it retrieves DYTC (0x1f001) as follows:
0x1 -> VSTD=1 -> STD mode
0x.f... -> CICM=0xf, DYTC_GET_MODE_BIT(12) -> dunno what it is in STD
0x..0.. -> CICF=0x0, DYTC_GET_FUNCTION_BIT(8) -> DYTC_FUNCTION_STD
0x1 -> GOOD

But convert_dytc_to_profile() doesn't handle this at all. Do I have a newer 
DYTC interface? Or a broken one?
Case (0x00)
{
Local1 = 0x0100
Local1 |= 0x8000
Local1 |= 0x00
Local1 |= 0x01
}

I.e. version 8.0, it seems.

My DYTC for CMD_GET looks like:
   Case (0x02)
   {
   Local5 = VSTD /* \VSTD */
   Local5 |= (VCQL << 0x01)
   Local5 |= (VSTP << 0x04)
   Local5 |= (VADM << 0x07)
   Local5 |= (VTMS << 0x09)
   Local5 |= (VDLS << 0x0A)
   Local5 |= (VMSC << 0x0C)
   Local5 |= (VPSC << 0x0D)
   Local1 = (CICF << 0x08)
   If ((CICF == 0x03))
   {
   CICM = SMYH /* \SMYH */
   }
   ElseIf ((CICF == 0x0B))
   {
   CICM = SMMC /* \SMMC */
   }
   ElseIf ((CICF == 0x0D))
   {
   CICM = SPSC /* \SPSC */
   }
   ElseIf ((CICF == 0x0F))
   {
   CICM 

[Kernel-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu

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

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2033327] Re: dGPU suspend fails under memory pressure

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  dGPU suspend fails under memory pressure

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

Bug description:
  Hardware:

  - Desktop PC (Intel i5 4th gen)
  - GPU: AMD RX580
  - Ubuntu 22.04 with kernel HWE 6.2

  Steps to reproduce:

  1. Start the device
  2. Suspend
  3. Resume by pressing a key on the keyboard

  Expected results:

  The screen lights up, showing the screen to put my password to resume
  the session.

  Actual result:

  The screen OSD displays a "No Signal" message before turning off.
  Nothing seems to happen when I press keyboard keys or move the mouse.

  Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see
  the logs (that's how I filed this bug).

  Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows
  the cursor and nothing else (black screen).

  Switching to login screen (Ctrl+Alt+F1) works: I can see the list of
  users, select on and enter my password... but then I'm back to the
  same black screen with the mouse cursor.

  This is not a regression, as the same problem happened already with
  the previous point release (I believe it was Linux kernel 5.15).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Aug 29 09:15:49 2023
  InstallationDate: Installed on 2022-12-28 (243 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  pieq   2262 F pulseaudio
   /dev/snd/controlC1:  pieq   2262 F pulseaudio
   /dev/snd/controlC0:  pieq   2262 F pulseaudio
   /dev/snd/controlC2:  pieq   2262 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-28 (245 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-26-generic N/A
   linux-backports-modules-6.2.0-26-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.17
  RfKill:
   
  StagingDrivers: r8188eu
  Tags:  jammy staging
  Uname: Linux 6.2.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/26/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2033327/+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 2039601] Re: [ kernel 6.5 regression ] nvme not working on some laptops

[Bug Watch Updater]

Launchpad has imported 27 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=217802.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-08-16T20:21:23+00:00 gjunk2 wrote:

Failure manually transcribed:

kernel: nvme nvme0: controller is down; will reset: CSTS:0x, 
PCI_STATUS=0x
kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
kernel: nvme nvme0: try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" 
and report a bug
kernel: nvme :04:00.0: Unable to change power state from D3cold to D0, 
device inaccessible
kernel: nvme nvme0: Disabling device after reset failure: -19
mount[353]: mount /sysroot: can't read suprtblock on /dev/nvme0n1p5.
mount[353]:   dmesg(1) may have more information after failed moutn system 
call.
kernel: nvme0m1: detected capacity change from 2000409264 to 0
kernel: EXT4-fs (nvme0n1p5): unable to read superblock
systemd([1]: sysroot.mount: Mount process exited, code=exited, status=32/n/a
...

All kernels are upstream, untainted and compiled on Arch linux using:

 gcc version 13.2.1

Kernels Tested:
 - 6.4.10 - works fine
 - 6.5-rc6 - fails
 - 6.4.11 with 1 revert also fails

Revert "nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G"

This reverts commit 061fbf64825fb47367bbb6e0a528611f08119473.

Hardware:
  model name  : Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  stepping: 9
  microcode   : 0xf4

nvme:
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961/SM963

All tests on dell laptop running Arch. All

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/comments/0


On 2023-08-16T20:33:07+00:00 gjunk2 wrote:

Also I did try 6.4.11 with the suggested options : 
   nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

Also did not boot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/comments/1


On 2023-08-17T01:38:23+00:00 gjunk2 wrote:

git bisect results on lkml

https://lkml.org/lkml/2023/8/16/1363

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/comments/2


On 2023-08-17T10:19:28+00:00 gjunk2 wrote:

Just FYI in case of interest to anyone.

I can confirm that blacklisting the drivers (rtsx_pci_and sdmmc and
rtsx_pci) and rebuilding the initramfs - rebooting then works fine for
both 6.4.11 and 6.5-rc6.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/comments/3


On 2023-08-27T14:03:44+00:00 jastxakajasmineteax wrote:

(In reply to Gene from comment #1)
> Also I did try 6.4.11 with the suggested options : 
>nvme_core.default_ps_max_latency_us=0 pcie_aspm=off
> 
> Also did not boot.

Hello,
I'm facing this same problem with linux-mainline-6.5rc6-1 (built by 
Chaotic-AUR), linux-zen-6.4.12 and linux-lts-6.1.47-1. OS is Garuda Linux. I 
understand that here, support is not given for downstream kernels like Zen and 
LTS. 

In my case, adding 
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off
did fix it for me and some others facing similar issues (they didn't get thrown 
into an emergency shell after failing to switch root though - they got stuck on 
a black screen instead). None of us tried blacklisting the kernels, as these 
boot params suggested by the error worked. 
Everyone affected by this used NVMe devices, a lot of them from Samsung.

I use a Dell XPS 15 9560 (Toshiba KXG50ZNV512G NVMe 512GB). It has the 
problematic Realtek card reader.
I'm unsure if I should make a new report since the problem is only slightly 
different, with newer kernels. Reporting kernel bugs is very new to me so 
please let me know the right course of action for reporting this :) (not just 
Gene, but anyone here).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/comments/4


On 2023-08-27T14:06:36+00:00 jastxakajasmineteax wrote:

(In reply to Jasmine T from comment #4)
> None of us tried blacklisting the kernels


Sorry, typo... modules, not kernels. Need sleep.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/comments/5


On 2023-08-29T06:32:22+00:00 bronecki.damian wrote:

I have same issues since 6.4.11 on my Dell XPS 15 9560 laptop using
Fedora 38.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/203960

[Kernel-packages] [Bug 2039345] Re: Powerstatus for Pen "ELAN 25B2:00 04F3:25B1" is not correct.

[Bug Watch Updater]

** Changed in: upower
   Status: Unknown => Fix Released

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

Title:
  Powerstatus for Pen "ELAN 25B2:00 04F3:25B1" is not correct.

Status in Upower:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The PEN of my ASUS TP401M the "ELAN 25B2:00 04F3:25B1" shows permanetly a 
battery status of 1% even I change the battery.
  The Pen itself works without problem, but Ubuntu bothers me permanently with 
a warning for low energy.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michel 2329 F wireplumber
   /dev/snd/seq:michel 2315 F pipewire
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-08-15 (791 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a03 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 002: ID 13d3:3530 IMC Networks Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP401MAR_TP401MA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=17569d0a-f002-401c-b0a1-bfa41c1c0916 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-34-generic N/A
   linux-backports-modules-6.2.0-34-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8
  Tags: wayland-session lunar
  Uname: Linux 6.2.0-34-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (159 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP401MAR.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP401MAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP401MAR.301:bd06/12/2020:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP401MAR_TP401MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP401MAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP401MAR_TP401MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/2039345/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in linux source package in Mantic:
  Confirmed
Status in mutter source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2032386] Re: Aug 21 17:08:54 jak-t14-g3 kernel: amdgpu 0000:04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:1 pasid:32782, for process firefox pid 1163281 thread fir

[Bug Watch Updater]

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  Aug 21 17:08:54 jak-t14-g3 kernel: amdgpu :04:00.0: amdgpu:
  [gfxhub] page fault (src_id:0 ring:40 vmid:1 pasid:32782, for process
  firefox pid 1163281 thread firefox:cs0 pid 1163466) Aug 21 17:08:54
  jak-t14-g3 kernel: amdgpu :04:00.0: amdgpu:   in page starting at
  address 0x800111ec from client 0x1b (UTCL2) Aug 21 17:08:54
  jak-t14-g3 kernel: amdgpu :04:00.0: amdgpu:
  GCVM_L2_PROTECTION_FAULT_STATUS:0x Aug 21 17:08:54 jak-t14-g3
  kernel: amdgpu :04:00.0: amdgpu:  Faulty UTCL2 client ID:
  CB/DB (0x0) Aug 21 17:08:54 jak-t14-g3 kernel: amdgpu :04:00.0:
  amdgpu:  MORE_FAULTS: 0x0 Aug 21 17:08:54 jak-t14-g3 kernel:
  amdgpu :04:00.0: amdgpu:  WALKER_ERROR: 0x0 Aug 21
  17:08:54 jak-t14-g3 kernel: amdgpu :04:00.0: amdgpu:
  PERMISSION_FAULTS: 0x0 Aug 21 17:08:54 jak-t14-g3 kernel: amdgpu
  :04:00.0: amdgpu:  MAPPING_ERROR: 0x0 Aug 21 17:08:54
  jak-t14-g3 kernel: amdgpu :04:00.0: amdgpu:  RW: 0x0 Aug
  21 17:09:04 jak-t14-g3 kernel: [drm:amdgpu_job_timedout [amdgpu]]
  *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I'm sorry I don't have more information than the dmesg output but
  firefox (snap) just hang; bug could be either mesa or kernel (I mean
  generally I'd say that if userspace can DoS the GPU that's also a
  kernel bug regardless but YMMV)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.3.0-7-generic 6.3.0-7.7+1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Aug 21 17:09:36 2023
  InstallationDate: Installed on 2022-11-26 (268 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.3.0-7-generic N/A
   linux-backports-modules-6.3.0-7-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2023
  dmi.bios.release: 1.35
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET65W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET65W(1.35):bd03/21/2023:br1.35:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2032386/+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 1879755] Re: cp --reflink support

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  cp --reflink support

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  With the recent efforts of promoting ZFS in Ubuntu, it might be a good
  idea to add support for 'cp --reflink=always' such that proven
  workflows for Btrfs can be easily transferred to ZFS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1879755/+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 1899249] Re: OpenZFS writing stalls, under load

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => New

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

Title:
  OpenZFS writing stalls, under load

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry
  Pi 8GB. ZFS deduplication, and LZJB compression is enabled.

  This issue seems to occur, intermittently, after some time (happens
  with both SMB access, via Samba, and when interacting with the system,
  via SSH), and never previously occurred, until a few months ago, and I
  sometimes have to force a reboot of the system (at the cost of some
  data loss), in order to use it again.

  The "dmesg" log reports:

  [25375.911590] z_wr_iss_h  D0  2161  2 0x0028
  [25375.911606] Call trace:
  [25375.911627]  __switch_to+0x104/0x170
  [25375.911639]  __schedule+0x30c/0x7c0
  [25375.911647]  schedule+0x3c/0xb8
  [25375.911655]  io_schedule+0x20/0x58
  [25375.911668]  rq_qos_wait+0x100/0x178
  [25375.911677]  wbt_wait+0xb4/0xf0
  [25375.911687]  __rq_qos_throttle+0x38/0x50
  [25375.911700]  blk_mq_make_request+0x128/0x610
  [25375.911712]  generic_make_request+0xb4/0x2d8
  [25375.911722]  submit_bio+0x48/0x218
  [25375.911960]  vdev_disk_io_start+0x670/0x9f8 [zfs]
  [25375.912181]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
  [25375.912400]  zio_nowait+0xd4/0x170 [zfs]
  [25375.912617]  vdev_mirror_io_start+0xa8/0x1b0 [zfs]
  [25375.912839]  zio_vdev_io_start+0x248/0x2b8 [zfs]
  [25375.913057]  zio_execute+0xac/0x110 [zfs]
  [25375.913096]  taskq_thread+0x2f8/0x570 [spl]
  [25375.913108]  kthread+0xfc/0x128
  [25375.913119]  ret_from_fork+0x10/0x1c
  [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds.
  [25375.919916]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.934835] txg_syncD0  2333  2 0x0028
  [25375.934850] Call trace:
  [25375.934869]  __switch_to+0x104/0x170
  [25375.934879]  __schedule+0x30c/0x7c0
  [25375.934887]  schedule+0x3c/0xb8
  [25375.934899]  schedule_timeout+0x9c/0x190
  [25375.934908]  io_schedule_timeout+0x28/0x48
  [25375.934946]  __cv_timedwait_common+0x1a8/0x1f8 [spl]
  [25375.934982]  __cv_timedwait_io+0x3c/0x50 [spl]
  [25375.935205]  zio_wait+0x130/0x2a0 [zfs]
  [25375.935423]  dsl_pool_sync+0x3fc/0x498 [zfs]
  [25375.935650]  spa_sync+0x538/0xe68 [zfs]
  [25375.935867]  txg_sync_thread+0x2c0/0x468 [zfs]
  [25375.935911]  thread_generic_wrapper+0x74/0xa0 [spl]
  [25375.935924]  kthread+0xfc/0x128
  [25375.935935]  ret_from_fork+0x10/0x1c
  [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds.
  [25375.942780]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.957702] zbackup D0 75339   5499 0x
  [25375.957716] Call trace:
  [25375.957732]  __switch_to+0x104/0x170
  [25375.957742]  __schedule+0x30c/0x7c0
  [25375.957750]  schedule+0x3c/0xb8
  [25375.957789]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.957823]  __cv_wait+0x30/0x40 [spl]
  [25375.958045]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.958263]  zil_commit+0x48/0x70 [zfs]
  [25375.958481]  zfs_create+0x544/0x7d0 [zfs]
  [25375.958698]  zpl_create+0xb8/0x178 [zfs]
  [25375.958711]  lookup_open+0x4ec/0x6a8
  [25375.958721]  do_last+0x260/0x8c0
  [25375.958730]  path_openat+0x84/0x258
  [25375.958739]  do_filp_open+0x84/0x108
  [25375.958752]  do_sys_open+0x180/0x2b0
  [25375.958763]  __arm64_sys_openat+0x2c/0x38
  [25375.958773]  el0_svc_common.constprop.0+0x80/0x218
  [25375.958781]  el0_svc_handler+0x34/0xa0
  [25375.958791]  el0_svc+0x10/0x2cc
  [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds.
  [25375.965564]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.980479] zbackup D0 95187   5499 0x
  [25375.980493] Call trace:
  [25375.980514]  __switch_to+0x104/0x170
  [25375.980525]  __schedule+0x30c/0x7c0
  [25375.980536]  schedule+0x3c/0xb8
  [25375.980578]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.980612]  __cv_wait+0x30/0x40 [spl]
  [25375.980834]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.981052]  zil_commit+0x48/0x70 [zfs]
  [25375.981280]  zfs_write+0xa3c/0xb90 [zfs]
  [25375.981498]  zpl_write_common_iovec+0xac/0x120 [zfs]
  [25375.981726]  zpl_iter_write+0xe4/0x150 [zfs]
  [25375.981766]  new_sync_write+0x100/0x1a8
  [25375.981776]  __vfs_write+0x74/0x90
  [25375.981784]  vfs_write+0xe4/0x1c8
  [25375.981794]  ksys_write+0x78/0x100
  [25375.981803]  __arm64_sys_write+0x24/0x30
  [25375.981813]  el0_svc_common

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed

[Bug Watch Updater]

** Changed in: zfs
   Status: New => Fix Released

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  &zp->z_sa_hdl)) failed

Status in Native ZFS for Linux:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-raspi source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Won't Fix
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1913342] Re: zfs.8 man page snapshot listing instructions are confusing

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  zfs.8 man page snapshot listing instructions are confusing

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  The zfs.8 man page describes in 3 places how to include snapshots in
  "zfs list":

  1) Snapshots are displayed if the listsnaps property is on (the default is 
off).
  2) Snapshots are displayed if the listsnaps property is on.  The default is 
off.  See zpool(8) for more information on pool properties.
  3) For example, specifying -t snapshot displays only snapshots.

  The first of these has twice now (I'm just learning zfs) sent me down
  a rabbit hole, looking for a zfs dataset property "listsnaps".  There
  is no such property (of datasets).

  I'm on version 0.8.3 of zfsutils-linux that has this man page, but
  when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html
  it seems that the above is still true in 0.8.6

  Suggestion, to help us newbies reduce our learning time to list
  snapshots:

  Change both of the first 2 of the above 3 places in zfs.8 to:
  "
  "zfs list" displays snapshots only if either the "listsnapshots" property of 
the underlying zpool is on, or if the "zfs list -t snapshot" option is 
specified.

  Extra Credit:

  Just now it seems to me that the following command does _NOT_ list
  snapshots, on a dataset that has some snapshots ... so the zfs.8
  documentation that the "zfs list -t type" can be a "comma-separated
  list of types to display" seems incorrect:

  zfs list -t filesystem,snapshot myzfsdataset

  Whether this "Extra Credit" discrepancy is a bug in the documentation,
  or in the zfs command code, or newbie operator error, I'll leave as an
  exercise to the reader .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jan 26 13:41:16 2021
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1913342/+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 1912188] Re: Load growing continously

[Bug Watch Updater]

** Changed in: zfs-ubuntu
   Status: New => Fix Released

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

Title:
  Load growing continously

Status in zfs-ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently load started growing with no end. After a while random
  processes become zombies.

   11:32:22 up 26 min,  1 user,  load average: 196.16, 186.30, 138.60

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-generic 5.8.0.36.40+21.04.38
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2361 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 11:30:11 2021
  InstallationDate: Installed on 2020-12-31 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago)
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2721 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-12-31 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-33-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (28 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs-ubuntu/+bug/1912188/+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 1814983] Re: zfs poor sustained read performance from ssd pool

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   0:54.51 arc_prune 
  
  18472 root  20   00.0m   0.0m   0.0m R  53.6  0.0   2:08.73 arc_prune 
  
  29525 root  20   00.0m   0.0m   0.0m R  53.6  0.0   1:35.81 arc_prune 
  
  32291 root  20   00.0m   0.0m   0.0m S  53.6  0.0   1:28.00 arc_prune 
  
   3156 root  20   00.0m   0.0m   0.0m R  53.3  0.0   3:17.68 arc_prune 
   

[Kernel-packages] [Bug 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)

[Bug Watch Updater]

** Changed in: bluez (Debian)
   Status: Unknown => New

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

Title:
  ConfigurationDirectory 'bluetooth' already exists but the mode is
  different. (File system: 755 ConfigurationDirectoryMode: 555)

Status in bluez package in Ubuntu:
  New
Status in bluez package in Debian:
  New

Bug description:
  Hi,

  when my system boots it logs the following warning in the journal:

  $ journalctl | grep ConfigurationDirectory
  Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 
ConfigurationDirectoryMode: 555)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluez 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 13:28:20 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 70:9C:D1:50:1F:7B  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 2036998] Re: [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Fix Released

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

Title:
  [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0

Status in Linux:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in 
random order.
  May have reported this earlier myself. Details to be filled later.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 21 20:20:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (512 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2036998/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => New

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

Status in Linux:
  New
Status in Mutter:
  New
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in linux source package in Mantic:
  Confirmed
Status in mutter source package in Mantic:
  In Progress

Bug description:
  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

[Bug Watch Updater]

** Changed in: gdm
   Status: Unknown => Fix Released

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

Title:
  Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

Status in gdm:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Jammy:
  Triaged
Status in linux source package in Jammy:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in gdm3 source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Confirmed
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in linux package in Fedora:
  Fix Released

Bug description:
  [ Impact ] 
  The fbdev subsystem has been deprecated for a long time. We should drop it in 
favour of using simpledrm with fbdev emulation layer.

  This requires Kernel config changes:

  FB_EFI=n
  FB_VESA=n

  fbcon will still require FB to be available, but will use the fbdev
  emulation layer

  When this stack is enabled, it changes boot timing such that some
  drivers may take a longer time to boot and GDM may hang in a black
  screen.

  [ Test Plan ]
  * Ensure that a kernel with required kernel changes can boot to GDM using DRM 
driver (amdgpu, i915, or nouveau)

  [ Where Problems could occur ]
  * Race conditions could be exposed to DE environments
  * Software that expects to find DRM device at /dev/dri/card0 may have a 
problem.
  * Some older versions of NVIDIA driver might not work properly.

  [ Other Info ]
  * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1965303/+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 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

[Bug Watch Updater]

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2022385.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2021-11-11T14:33:25+00:00 bcotton wrote:

This is a tracking bug for Change: Replace the fbdev drivers with simpledrm and 
the DRM fbdev emulation layer
For more details, see: 
https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

This change replaces the legacy Linux frame buffer device (fbdev)
drivers that are still used in Fedora, with the latest simpledrm driver
and the DRM fbdev emulation layer.

If you encounter a bug related to this Change, please do not comment
here. Instead create a new bug and set it to block this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/0


On 2021-12-23T11:26:38+00:00 fmartine wrote:

This change has been present in the Fedora kernel since
https://gitlab.com/cki-project/kernel-
ark/-/commit/53d2c01aef5aaad8b8bb54e4254f6ae671c76ee5

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/1


On 2021-12-23T11:44:17+00:00 fmartine wrote:

*** Bug 1986222 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/2


On 2022-02-08T21:06:33+00:00 bcotton wrote:


This bug appears to have been reported against 'rawhide' during the Fedora 
Linux 36 development cycle.
Changing version to 36.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/3


On 2022-02-22T16:34:36+00:00 bcotton wrote:

We have reached the 'Change complete (100% complete)' deadline in the
Fedora Linux 36 release schedule.

At this time, all Changes should be fully complete. Indicate this by
setting this tracking bug to ON_QA.

If you need to defer this Change to a subsequent release, please
needinfo me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/4


On 2022-05-10T14:41:45+00:00 bcotton wrote:

F36 was released today. If this Change did not land in the release,
please notify bcotton as soon as possible.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/6


** Changed in: linux (Fedora)
   Status: Unknown => Fix Released

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Jammy:
  Triaged
Status in linux source package in Jammy:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in gdm3 source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Confirmed
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in linux package in Fedora:
  Fix Released

Bug description:
  [ Impact ] 
  The fbdev subsystem has been deprecated for a long time. We should drop it in 
favour of using simpledrm with fbdev emulation layer.

  This requires Kernel config changes:

  FB_EFI=n
  FB_VESA=n

  fbcon will still require FB to be available, but will use the fbdev
  emulation layer

  When this stack is enabled, it changes boot timing such that some
  drivers may take a longer time to boot and GDM may hang in a black
  screen.

  [ Test Plan ]
  * Ensure that a kernel with required kernel changes can boot to GDM using DRM 
driver (amdgpu, i915, or nouveau)

  [ Where Problems could occur ]
  * Race conditions could be exposed to DE environments
  * Software that expects to find DRM device at /dev/dri/card0 may have a 
problem.
  * Some older versions of NVIDIA driver might not work properly.

  [ Other Info ]
  * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions


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

[Kernel-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1959888/+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 2030680] Re: AMD 6800h internal graphics: flickering white screen

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  AMD 6800h internal graphics: flickering white screen

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  New
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 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
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  I am getting a flickering white screen occasionally.

  I have an Alienware M17 R5 AMD with a Ryzen 6800h CPU and an nvidia
  RTX 3070 Ti dedicated CPU.

  I'm getting a constant flickering white screen. According to a web
  search, this could be fixed in 6.2 with the kernel option
  amdgpu.sg_display=0.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1017.17
  ProcVersionSignature: Ubuntu 6.1.0-1017.17-oem 6.1.34
  Uname: Linux 6.1.0-1017-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug  7 22:27:51 2023
  InstallationDate: Installed on 2017-10-23 (2114 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: Upgraded to jammy on 2022-12-05 (245 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2030680/+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 2034088] Re: 4k white screen on kernel-6.20 with AMD7950x

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  4k white screen on kernel-6.20 with AMD7950x

Status in Linux:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  1. AMD7950X, without any other gpu
  2. 4k display
  3. if kernel.version >= 6.14
  => the 4k display white screen

  ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354
  ps2: this bug has occured long time ago, but amd never fix it, so i can not 
upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 10:46:23 2023
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
  InstallationDate: Installed on 2023-07-31 (35 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago)
  dmi.bios.date: 07/28/2023
  dmi.bios.release: 16.36
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1636
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B650M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034088/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

** Changed in: xorg-server
   Status: New => Fix Released

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

Status in Linux:
  New
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

Status in X.Org X server:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2034619/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => Fix Released

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

Title:
  Laptop screen blinked, no tty works and 200 dmesg errors per second

Status in Mesa:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New

Bug description:
  I was using my laptop and suddenly the screen blinked. After that, all
  I could do was to move the mouse, no interaction worked. Trying to
  change to a TTY would open the black screen but the text cursor wasn't
  blinking and nothing happened.

  I accessed the laptop via SSH and used:

  screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace

  To reload xfwm4. After that, the graphical interface started working
  again. However, no TTY is accessible and there are 200 dmesg errors
  per second. These are the errors that repeat endlessly:

  [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring 

  [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)

  And while I was writing this report, another problem happened:

  [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 
timeout, signaled seq=2, emitted seq=6
  [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process obs pid 38687 thread obs:cs0 pid 38694
  [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin!
  [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 
0x0001 != 0x0002
  [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 
0x0100 != 0x
  [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 
0x0001 != 0x0002
  [44566.731204] [ cut here ]
  [44566.731205] WARNING: CPU: 15 PID: 29333 at 
drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu]
  [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) 
zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) 
rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram 
binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir 
snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci 
ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel 
snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress 
nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core 
snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl 
snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk 
snd_rawmidi uvcvideo
  [44566.731465]  snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm 
videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a 
irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device 
snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw 
snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd 
k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap 
platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat 
sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc 
nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon 
pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc 
virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf 
drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at
 h10k_pci
  [44566.731504]  ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii 
nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core 
drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni 
sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm 
sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd 
r8169 video i2c_piix4 i2c_hid xhci_pci_renesas nvme_common realtek wmi hid
  [44566.731529] CPU: 15 PID: 29333 Comm: kworker/u32:1 Tainted: PW  O  
 6.2.0-31-generic #31~22.04.1-Ubuntu
  [44566.731531] Hardware name: LENOVO 82MJ/LNVNB161216, BIOS H3CN36WW(V2.06) 
09/30/2022
  [44566.731533] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]
  [44566.731539] RIP: 0010:amdgpu_irq_put+0xa4/0xc0 [amdgpu]
  [44566.731702] Code: 31 f6 31 ff c3 cc cc cc c

[Kernel-packages] [Bug 1374084] Re: Bluetooth: hci0 SCO packet for unknown connection handle 41

[Bug Watch Updater]

** Changed in: linux
   Status: Confirmed => Invalid

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

Title:
  Bluetooth: hci0 SCO packet for unknown connection handle 41

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  [63716.030347] input: 00:1E:7C:22:33:21 as /devices/virtual/input/input13
  [63721.787306] Bluetooth: hci0 SCO packet for unknown connection handle 41
  [63721.787316] Bluetooth: hci0 SCO packet for unknown connection handle 41
  [63814.034162] Bluetooth: hci0 SCO packet for unknown connection handle 35
  [63814.034176] Bluetooth: hci0 SCO packet for unknown connection handle 35
  [63814.034183] Bluetooth: hci0 SCO packet for unknown connection handle 35

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-17-generic 3.16.0-17.23 [modified: 
boot/vmlinuz-3.16.0-17-generic]
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2110 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2110 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 25 15:36:47 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-17-generic.efi.signed 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-17-generic N/A
   linux-backports-modules-3.16.0-17-generic  N/A
   linux-firmware 1.134
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1374084/+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 2034088] Re: 4k white screen on kernel-6.20 with AMD7950x

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => New

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

Title:
  4k white screen on kernel-6.20 with AMD7950x

Status in Linux:
  New
Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  1. AMD7950X, without any other gpu
  2. 4k display
  3. if kernel.version >= 6.14
  => the 4k display white screen

  ps1: https://gitlab.freedesktop.org/drm/amd/-/issues/2354
  ps2: this bug has occured long time ago, but amd never fix it, so i can not 
upgrade my ubuntu kernel version to default 6.20 for ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 10:46:23 2023
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8877]
  InstallationDate: Installed on 2023-07-31 (35 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=656f1bf0-3f83-44eb-9793-47a2aeaa819a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-08-30 (5 days ago)
  dmi.bios.date: 07/28/2023
  dmi.bios.release: 16.36
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1636
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B650M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1636:bd07/28/2023:br16.36:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034088/+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 2029345] Re: Missing DG2 HUC firmware (i915)

[Bug Watch Updater]

** Changed in: firmware-nonfree (Debian)
   Status: Unknown => Fix Released

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

Title:
  Missing DG2 HUC firmware (i915)

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in firmware-nonfree package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  Missing HUC firmware. For whatever it is required for, it won't work
  without the firmware.

  [ Fix ]

  Upstream linux-firmware commit
  8f86b5ab3e051170ea240fc409d457e16e24bc21.

  [ Test Case ]

  $ cat /sys/kernel/debug/dri/1/gt/uc/huc_info

  Should report HUC FW information.

  [ Where Problems Could Occur ]

  Limited to i915 DG2 (Arc2?) GPUs.

  [ Original Description ]

  $ sudo update-initramfs -k $(uname -r) -u
  update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
  W: Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module 
i915
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/vgubuntu-swap_1)
  I: Set the RESUME variable to override this.
  $

  i915/dg2_huc_gsc.bin seems to be missing. While this is an
  experimental (?) Intel driver for Arc2 dedicated GPUs, and some of
  these products are no longer being sold, there will probably be people
  out there using it, and wishing to use the newer driver and HUC
  support.

  Are there reasons not to include this firmware, or was it just an
  oversight, possibly following Debian's?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.16
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mona   2342 F pulseaudio
   /dev/snd/controlC1:  mona   2342 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  2 10:44:39 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  InstallationDate: Installed on 2023-02-12 (170 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Microsoft Corporation Surface Laptop 4
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-26-generic N/A
   linux-backports-modules-6.2.0-26-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.16
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2023
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 22.101.143
  dmi.board.name: Surface Laptop 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr22.101.143:bd04/11/2023:svnMicrosoftCorporation:pnSurfaceLaptop4:pvr124I00061T000M010D0B05F1C01P16Y1U00S0:rvnMicrosoftCorporation:rnSurfaceLaptop4:rvr:cvnMicrosoftCorporation:ct9:cvr:skuSurface_Laptop_4_19501951:
  dmi.product.family: Surface
  dmi.product.name: Surface Laptop 4
  dmi.product.sku: Surface_Laptop_4_1950:1951
  dmi.product.version: 124I:00061T:000M:010D:0B:05F:1C:01P:16Y:1U:00S:0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029345/+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 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  zfs recv PANIC at range_tree.c:304:range_tree_find_impl()

Status in Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Bionic:
  Confirmed

Bug description:
  Same as bug 1861228 but with a newer kernel installed.

  [  790.702566] VERIFY(size != 0) failed
  [  790.702590] PANIC at range_tree.c:304:range_tree_find_impl()
  [  790.702611] Showing stack for process 28685
  [  790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P   O 
4.15.0-76-generic #86-Ubuntu
  [  790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 
2.0 12/17/2015
  [  790.702616] Call Trace:
  [  790.702626]  dump_stack+0x6d/0x8e
  [  790.702637]  spl_dumpstack+0x42/0x50 [spl]
  [  790.702640]  spl_panic+0xc8/0x110 [spl]
  [  790.702645]  ? __switch_to_asm+0x41/0x70
  [  790.702714]  ? arc_prune_task+0x1a/0x40 [zfs]
  [  790.702740]  ? dbuf_dirty+0x43d/0x850 [zfs]
  [  790.702745]  ? getrawmonotonic64+0x43/0xd0
  [  790.702746]  ? getrawmonotonic64+0x43/0xd0
  [  790.702775]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702778]  ? getrawmonotonic64+0x43/0xd0
  [  790.702805]  ? dmu_zfetch+0x49a/0x500 [zfs]
  [  790.702807]  ? mutex_lock+0x12/0x40
  [  790.702833]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [  790.702866]  range_tree_find_impl+0x88/0x90 [zfs]
  [  790.702870]  ? spl_kmem_zalloc+0xdc/0x1a0 [spl]
  [  790.702902]  range_tree_clear+0x4f/0x60 [zfs]
  [  790.702930]  dnode_free_range+0x11f/0x5a0 [zfs]
  [  790.702957]  dmu_object_free+0x53/0x90 [zfs]
  [  790.702983]  dmu_free_long_object+0x9f/0xc0 [zfs]
  [  790.703010]  receive_freeobjects.isra.12+0x7a/0x100 [zfs]
  [  790.703036]  receive_writer_thread+0x6d2/0xa60 [zfs]
  [  790.703040]  ? set_curr_task_fair+0x2b/0x60
  [  790.703043]  ? spl_kmem_free+0x33/0x40 [spl]
  [  790.703048]  ? kfree+0x165/0x180
  [  790.703073]  ? receive_free.isra.13+0xc0/0xc0 [zfs]
  [  790.703078]  thread_generic_wrapper+0x74/0x90 [spl]
  [  790.703081]  kthread+0x121/0x140
  [  790.703084]  ? __thread_exit+0x20/0x20 [spl]
  [  790.703085]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  790.703088]  ret_from_fork+0x35/0x40
  [  967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds.
  [  967.636979]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637076] txg_quiesce D0 14810  2 0x8000
  [  967.637080] Call Trace:
  [  967.637089]  __schedule+0x24e/0x880
  [  967.637092]  schedule+0x2c/0x80
  [  967.637106]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637114]  ? wait_woken+0x80/0x80
  [  967.637122]  __cv_wait+0x15/0x20 [spl]
  [  967.637210]  txg_quiesce_thread+0x2cb/0x3d0 [zfs]
  [  967.637278]  ? txg_delay+0x1b0/0x1b0 [zfs]
  [  967.637286]  thread_generic_wrapper+0x74/0x90 [spl]
  [  967.637291]  kthread+0x121/0x140
  [  967.637297]  ? __thread_exit+0x20/0x20 [spl]
  [  967.637299]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  967.637304]  ret_from_fork+0x35/0x40
  [  967.637326] INFO: task zfs:28590 blocked for more than 120 seconds.
  [  967.637371]   Tainted: P   O 4.15.0-76-generic #86-Ubuntu
  [  967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.637467] zfs D0 28590  28587 0x8080
  [  967.637470] Call Trace:
  [  967.637474]  __schedule+0x24e/0x880
  [  967.637477]  schedule+0x2c/0x80
  [  967.637486]  cv_wait_common+0x11e/0x140 [spl]
  [  967.637491]  ? wait_woken+0x80/0x80
  [  967.637498]  __cv_wait+0x15/0x20 [spl]
  [  967.637554]  dmu_recv_stream+0xa51/0xef0 [zfs]
  [  967.637630]  zfs_ioc_recv_impl+0x306/0x1100 [zfs]
  [  967.637679]  ? dbuf_read+0x34a/0x920 [zfs]
  [  967.637725]  ? dbuf_rele+0x36/0x40 [zfs]
  [  967.637728]  ? _cond_resched+0x19/0x40
  [  967.637798]  zfs_ioc_recv_new+0x33d/0x410 [zfs]
  [  967.637809]  ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl]
  [  967.637816]  ? spl_vmem_alloc+0x19/0x20 [spl]
  [  967.637828]  ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair]
  [  967.637834]  ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair]
  [  967.637840]  ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair]
  [  967.637905]  zfsdev_ioctl+0x451/0x610 [zfs]
  [  967.637913]  do_vfs_ioctl+0xa8/0x630
  [  967.637917]  ? __audit_syscall_entry+0xbc/0x110
  [  967.637924]  ? syscall_trace_enter+0x1da/0x2d0
  [  967.637927]  SyS_ioctl+0x79/0x90
  [  967.637930]  do_syscall_64+0x73/0x130
  [  967.637935]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [  967.637938] RIP: 0033:0x7fc305a905d7
  [  967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 
0010
  [  967.637943] RAX: ffda RBX: 5a46 RCX: 
7fc305a905d7

[Kernel-packages] [Bug 1982483] Re: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274)

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #207423
   https://bugzilla.kernel.org/show_bug.cgi?id=207423

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

Title:
  No sound from built-in speakers HP Pavilion All-in-One Desktop
  27-ca1xxx (ALC274)

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have tried:

  options snd-hda-intel model=alc285-hp-amp-init
  options snd-hda-intel model=alc274-dell-aio

  and newer kernels up to 5.19-rc6.

  21: PCI 1f.3: 0403 Audio device 
[Created at pci.386]
Unique ID: nS1_.2CriaNVEdN5
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Device Name: "Onboard - Sound"
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x7ad0 
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x89e9 
Revision: 0x11
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable)
Memory Range: 0x610500-0x61050f (rw,non-prefetchable)
IRQ: 161 (1098 events)
Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_sof_pci_intel_tgl is active
  Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl"
Config Status: cfg=new, avail=yes, need=no, active=unknown

  
<6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
<6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
<6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
<6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
<6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs:
<6>[3.582367] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19
<6>[3.582369] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  Alsa-info:

  https://alsa-
  project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31

  Here is a kernel bug report:

  https://bugzilla.kernel.org/show_bug.cgi?id=216139
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ernst  1560 F pulseaudio
   /dev/snd/controlC0:  ernst  1560 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (143 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem 
root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off 
mitigations=off vt.handoff=7
  ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0
  RelatedPackageVersions:
   linux-restricted-modules-6.0.0-1006-oem N/A
   linux-backports-modules-6.0.0-1006-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.6
  Tags:  jammy wayland-session
  Uname: Linux 6.0.0-1006-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/09/2022
  dmi.bios.release: 15.2
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.name: 89E9
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW:
  dmi.product.family: 103C_53311M HP Pavilion
  dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx
  dmi.product.sku: 661Q7EA#UUW
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1982483/+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 1817097] Re: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices

[Bug Watch Updater]

** Changed in: lvm2
   Status: Confirmed => Fix Released

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

Title:
  pvmove causes file system corruption without notice upon move from 512
  -> 4096 logical block size devices

Status in lvm2:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  Problem Description---
  Summary
  ===
  Environment: IBM Z13 LPAR and z/VM Guest
   IBM Type: 2964 Model: 701 NC9
  OS:  Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x)
   Package: lvm2 version 2.02.176-4.1ubuntu3
  LVM: pvmove operation corrupts file system when using 4096 (4k) logical block 
size
   and default block size being 512 bytes in the underlying devices
  The problem is immediately reproducible.

  We see a real usability issue with data destruction as consequence - which is 
not acceptable.
  We expect 'pvmove' to fail with error in such situations to prevent fs 
destruction,
  which might possibly be overridden by a force flag.

  
  Details
  ===
  After a 'pvmove' operation is run to move a physical volume onto an ecrypted
  device with 4096 bytes logical block size we experience a file system 
corruption.
  There is no need for the file system to be mounted, but the problem surfaces
  differently if so.

  Either, the 'pvs' command after the pvmove shows
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument

  or

  a subsequent mount shows (after umount if the fs had previously been mounted 
as in our
  setup)
  mount: /mnt: wrong fs type, bad option, bad superblock on 
/dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error.

  A minimal setup of LVM using one volume group with one logical volume defined,
  based on one physical volume is sufficient to raise the problem. One more 
physical
  volume of the same size is needed to run the pvmove operation to. 

LV
 |
  VG: LOOP_VG [ ]
 |
  PV: /dev/loop0   -->   /dev/mapper/enc-loop
  ( backed by /dev/mapper/enc-loop )

  The physical volumes are backed by loopback devices (losetup) to base the
  problem report on, but we have seen the error on real SCSI multipath volumes
  also, with and without cryptsetup mapper devices in use.

  
  Further discussion
  ==
  https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html
  The problem does not occur on block devices with native size of 4k.
  E.g. DASDs, or file systems with mkfs -b 4096 option.

  
  Terminal output
  ===
  See attached file pvmove-error.txt

  
  Debug data
  ==
  pvmove was run with -dd (maximum debug level)
  See attached journal file.
   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type: 2964 Model: 701 NC9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1.) Create two image files of 500MB in size
  and set up two loopback devices with 'losetup -fP FILE'
  2.) Create one physical volume and one volume group 'LOOP_VG',
  and one logical volume 'VG'
  Run:
  pvcreate /dev/loop0
  vgcreate LOOP_VG /dev/loop0
  lvcreate -L 300MB LOOP_VG -n LV /dev/loop0
  3.) Create a file system on the logical volume device:
  mkfs.ext4 /dev/mapper/LOOP_VG-LV
  4.) mount the file system created in the previous step to some empty 
available directory:
  mount /dev/mapper/LOOP_VG-LV /mnt
  5.) Set up a second physical volume, this time encrypted with LUKS2,
  and open the volume to make it available:
  cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
  cryptsetup luksOpen /dev/loop1 enc-loop
  6.) Create the second physical volume, and add it to the LOOP_VG
  pvcreate /dev/mapper/enc-loop
  vgextend LOOP_VG /dev/mapper/enc-loop
  7.) Ensure the new physical volume is part of the volume group:
  pvs
  8.) Move the /dev/loop0 volume onto the encrypted volume with maximum debug 
option:
  pvmove -dd /dev/loop0 /dev/mapper/enc-loop
  9.) The previous step succeeds, but corrupts the file system on the logical 
volume
   We expect an error here. 
   There might be a command line flag to override used because corruption 
does not cause a data loss.
  
   
  Userspace tool common name: pvmove 
   
  The userspace tool has t

[Kernel-packages] [Bug 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes

[Bug Watch Updater]

** Changed in: linux-firmware
   Status: New => Fix Released

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

Title:
  AMD Rembrandt / Phoenix PSR-SU related freezes

Status in Linux Firmware:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
   After a non-deterministic amount of time the system may hang with a message 
like this in the logs:
   "[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed 
out]"

   Affects users of laptops that contain:
   * AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
   * eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)

  [ Test Plan ]

   * Test an affected laptop with the newer firmware and ensure that PSR-SU 
function can be enabled and system is stable.
   * Ensure other functions such as hotplugging monitors and suspending 
continue to work.

  [ Where problems could occur ]

   * Affected firmware only is loaded on Rembrandt and Phoenix laptops.
  Problems would be localized to these machines.

  [ Other Info ]
  The minimum firmware needed to help these hangs:
  * Rembrandt: 0x43a or later
  * Phoenix: 0x8001000 or later

  The following commit upgrades the firmware for Rembrandt 
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
  9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")

  The following commit upgrades the firmware for Phoenix 
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
  045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")

  The TCON in a given laptop can be identified from the DPCD with this script:
  https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes

[Bug Watch Updater]

** Changed in: linux-firmware
   Status: Unknown => New

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

Title:
  AMD Rembrandt / Phoenix PSR-SU related freezes

Status in Linux Firmware:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Lunar:
  New
Status in linux-firmware source package in Mantic:
  New

Bug description:
  [ Impact ]

   When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
   After a non-deterministic amount of time the system may hang with a message 
like this in the logs:
   "[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed 
out]"

   Affects users of laptops that contain:
   * AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
   * eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)

  [ Test Plan ]

   * Test an affected laptop with the newer firmware and ensure that PSR-SU 
function can be enabled and system is stable.
   * Ensure other functions such as hotplugging monitors and suspending 
continue to work.

  [ Where problems could occur ]

   * Affected firmware only is loaded on Rembrandt and Phoenix laptops.
  Problems would be localized to these machines.

  [ Other Info ]
  The minimum firmware needed to help these hangs:
  * Rembrandt: 0x43a or later
  * Phoenix: 0x8001000 or later

  The following commit upgrades the firmware for Rembrandt 
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
  9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")

  The following commit upgrades the firmware for Phoenix 
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
  045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")

  The TCON in a given laptop can be identified from the DPCD with this script:
  https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2019736] Re: Fix hangs when connected to Freesync displays

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  Fix hangs when connected to Freesync displays

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

Bug description:
  [ Impact ]

   * Selecting certain resolutions causes hangs when an AMD GPU is
  connected to a display that supports FreeSync

  [ Test Plan ]

   * Verify display with freesync doesn't hang anymore

  [ Where problems could occur ]

   * AMD GPU could stop displaying

  [ Other Info ]

   * This issue was reported upstream to AMD here:  
https://gitlab.freedesktop.org/drm/amd/-/issues/2162
   * It has been fixed in kernel 6.4-rc1:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da5e14909776edea4462672fb4a3007802d262e7

   * AMD will CC it to stable to fix any remaining affected open stable
  releases, but as 5.19 is EOL upstream, want to ensure that Canonical
  picks up this patch in the 5.19 series as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2019736/+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 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets

[Bug Watch Updater]

** Bug watch added: Linux Kernel Bug Tracker #217526
   https://bugzilla.kernel.org/show_bug.cgi?id=217526

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1767654] Re: [Intel Braswell/Cherryview] Cursor gets stuck on left side of the screen

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  [Intel Braswell/Cherryview] Cursor gets stuck on left side of the
  screen

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

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1767654/+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 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191

[Kernel-packages] [Bug 1861633] Re: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot
  be changed using echo

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

Bug description:
  GPU=Rx vega m gl
  Release=Focal, 20.04 (development)
  xserver-xorg-video-amdgpu version=19.1.0-1 (active development)

  /sys/class/drm/card1/device/pp_od_clk_voltage cannot be change beyond
  the parameters stated at the bottom of this file within the title
  OD_RANGE, as follows:

  OD_RANGE:
  SCLK: 225MHz   1011MHz
  MCLK: 300MHz700MHz
  VDDC: 750mV 750mV

  The parameters in OD_RANGE are too constrictive and do not allow
  practicable overclocking/undervolting. Please could these values be
  changed to the following?:

  OD_RANGE:
  SCLK: 225MHz   1500MHz
  MCLK: 300MHz850MHz
  VDDC: 300mV 1500mV

  This bug was also found here;
  https://gitlab.freedesktop.org/drm/amd/issues/574

  The voltages and clock speeds cannot be amended above 1011Mhz, the
  HBM2 cannot exceed 700MHz and all voltages can only equal 750mV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1861633/+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 1965563] Re: GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

[Bug Watch Updater]

** Changed in: egl-wayland
   Status: New => Fix Released

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

Title:
  GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions

Status in NVIDIA / egl-wayland:
  Fix Released
Status in GTK+:
  Fix Released
Status in egl-wayland package in Ubuntu:
  Fix Released
Status in egl-wayland source package in Jammy:
  Triaged

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/egl-wayland/+bug/1965563/+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