[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)
I checked /sys/bus/acpi/devices dir and there is a directory called ELAN0634:00 but the modalias file inside is empty for me. ** Description changed: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) - 2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is ALPS, Elan or Synatics + 2. Touchpad manufacturer: Elan 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: mrozwod1597 F pulseaudio - /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: mrozwod1597 F pulseaudio + /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-39-generic N/A - linux-backports-modules-5.4.0-39-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-39-generic N/A + linux-backports-modules-5.4.0-39-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO -- 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/1885573 Title: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) Status in linux package in Ubuntu: Incomplete Bug description: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) 2. Touchpad manufacturer: Elan 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrozwod1597 F pulseaudio /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku:
[Kernel-packages] [Bug 1684789] Re: trunc-file.sh.btrfs from ubuntu_ecryptfs test-suite failed on T-LTS
Didn't see this on X-4.4 (passed with all arches) and T-4.4 (passed with all arches), closing this bug. ** Changed in: ecryptfs Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => 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/1684789 Title: trunc-file.sh.btrfs from ubuntu_ecryptfs test-suite failed on T-LTS Status in eCryptfs: Invalid Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This test has failed on both amd64, i386 and arm64 T-LTS kernel For this test, it complains about the: size should be > 0 04/15 05:13:22 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib' 04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading package lists... 04/15 05:13:22 DEBUG| utils:0153| [stdout] Building dependency tree... 04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading state information... 04/15 05:13:22 DEBUG| utils:0153| [stdout] acl is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] build-essential is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] intltool is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] keyutils is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libtool is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] xfsprogs is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 04/15 05:13:22 DEBUG| utils:0116| Running 'which gcc' 04/15 05:13:22 DEBUG| utils:0153| [stdout] /usr/bin/gcc 04/15 05:13:22 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 04/15 05:13:34 ERROR| utils:0153| [stderr] size should be > 0 04/15 05:13:35 DEBUG| utils:0153| [stdout] trunc-file FAIL 04/15 05:13:35 DEBUG| utils:0153| [stdout] 04/15 05:13:35 DEBUG| utils:0153| [stdout] Test Summary: 04/15 05:13:35 DEBUG| utils:0153| [stdout] 0 passed 04/15 05:13:35 DEBUG| utils:0153| [stdout] 1 failed 04/15 05:13:35 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 12.9071211815 stdout: trunc-file FAIL Test Summary: 0 passed 1 failed stderr: size should be > 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1 ProcVersionSignature: User Name 4.4.0-74.95~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Thu Apr 20 13:58:58 2017 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1684789/+subscriptions
[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Description changed: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch ucm-simplify-get_by_card-in-parser.c.patch ucm-implement-AlwaysTrue-Condition.Type.patch ucm-Allow-empty-strings-in-var-.-substitutions.patch ucm-substitution-remove-duplicate-allow_empty-assign.patch ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch ucm-substitute-the-merged-tree-completely.patch add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols [Test Case] On the AMD Renoir machines: * Boot the system with these updated packages (already backported kernel drivers to Focal and oem-5.6 kernels), open the gnome-control-center - we could see the digital mic in the input device tab, and only one input device
[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Tags added: sru-20200629 sru-20200720
--
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/1802454
Title:
fanotify10 in ubuntu_ltp_syscalls failed
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
It seems that T/X poses with the same issue and we might be able to backport
it with the same logic, but I think we should target Bionic as it's a fix for
for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
iter_info.inode_mark
to:
iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
But the patch can still be backported with the same logic without this
commit.
The test with the syscalls test in LTP test suite shows no sign of
regression.
== Test Case ==
Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258:
[Kernel-packages] [Bug 1890222] Re: Enlarge hisi_sec2 capability
** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890222 Title: Enlarge hisi_sec2 capability Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge the capability. [Fix] commit 57b1aac1b426b7255afa195298ed691ffea204c6 Author: Longfang Liu Date: Mon Jun 8 22:01:11 2020 +0800 Subject: crypto: hisilicon - update SEC driver module parameter [Test] $ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1890222/+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 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed
** Tags added: sru-20200720 -- 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/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification == fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 This duplicated event was generated with operations on files with "fake" path. == Fix == * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) This patch can be cherry-picked into Disco. Older kernels are not affected by this issue (without commit d1d04ef8) == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ Verified on a KVM node, the fanotify06 test will pass with this patched disco kernel: fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event == Regression Potential == Low, fix limited to the overlayfs and just corrects the flag behaviour with "fake" path. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to:
[Kernel-packages] [Bug 1785207] Re: openat03 in ubuntu_ltp_syscall failed with Trusty
** Tags added: sru-20200720 -- 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/1785207 Title: openat03 in ubuntu_ltp_syscall failed with Trusty Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Triaged Bug description: <<>> tag=openat03 stime=1533289807 cmdline="openat03" contacts="" analysis=exit <<>> openat030 TINFO : creating a file with O_TMPFILE flag incrementing stop openat030 TINFO : writing data to the file openat030 TINFO : file size is '4096' openat030 TINFO : looking for the file in '.' openat030 TINFO : file not found, OK openat030 TINFO : renaming '/tmp/ltp-5saSOZV2Gx/opea7u155/#286254 (deleted)' -> 'tmpfile' openat030 TINFO : found a file: tmpfile openat031 TPASS : single file tests passed openat030 TINFO : create files in multiple directories openat030 TINFO : removing test directories openat030 TINFO : writing/reading temporary files openat030 TINFO : closing temporary files openat032 TPASS : multiple files tests passed openat030 TINFO : create multiple directories, link files into them openat030 TINFO : and check file permissions openat033 TFAIL : openat03.c:223: file mode read 0, but expected <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-153-generic 3.13.0-153.203 ProcVersionSignature: User Name 3.13.0-153.203-generic 3.13.11-ckt39 Uname: Linux 3.13.0-153-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 3 07:50 seq crw-rw 1 root audio 116, 33 Aug 3 07:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Aug 3 09:49:41 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-153-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-3.13.0-153-generic N/A linux-backports-modules-3.13.0-153-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1785207/+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 1768962] Re: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build
[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Expired -- 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/1768962 Title: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Expired Bug description: nothing more to say -> failed to build in apt dist-upgrade... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu21 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-122-generic (x86_64) Do 3. Mai 21:43:07 CEST 2018 make: *** Es wurden keine Ziele angegeben und keine „make“-Steuerdatei gefunden. Schluss. DKMSKernelVersion: 4.4.0-122-generic Date: Thu May 3 21:43:11 2018 InstallationDate: Installed on 2012-04-30 (2194 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageVersion: 0.6.5.6-0ubuntu21 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-06-03 (699 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1768962/+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 1881435] Re: System freeze
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881435 Title: System freeze Status in linux package in Ubuntu: Expired Bug description: Screen freezes randomly. Keyboard and mouse do not work at that time. I am not able to ssh to the computer or access tty. I am able to do only a hard reset. I tried some troubleshooting myself, but with my novice expertise with ubuntu. The freeze is more or less random. But it is possibly more frequent when running a video, like a youtube video in a browser. Freeze is more frequenty when going full screen with a video, a VM machine or a remote desktop through vnc4server. 1. Tried removing some software like chrome, dropbox, virtualbox, etc. That did not help. 2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 kernel. That did not help either. 3. Tried other distros like Mint and Fedora. Still had problem. 4. Tried running with NVidia driver and xserver-xorg. The problem occured with both. 5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured in both. 6. Tried all the suggestions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were applicable. None of the suggestions helped. 7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and experienced no crash/freeze with youtube running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 12:36:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651] InstallationDate: Installed on 2020-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E 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.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1870769] Re: System slow/freezing when copying files (Kernel 5.4.x)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870769 Title: System slow/freezing when copying files (Kernel 5.4.x) Status in linux package in Ubuntu: Expired Bug description: While coping files (more noticeable when copying/moving large files), the freezes randomly. Cursor freezes as well. After all files have been copied/moved, the system then behaves normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1844 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:43:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Acer Swift SF314-56 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd08/12/2019:svnAcer:pnSwiftSF314-56:pvrV1.14:rvnWL:rnStrongbow_WL:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56 dmi.product.sku: dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870769/+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 1826376] Re: cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1826376
Title:
cxgb4 : no VXLAN offloading with distro driver, only with OFED drivers
Status in linux package in Ubuntu:
Expired
Bug description:
Hi,
Using ubuntu 18.04 with kernel 4.15.0-47-generic, my Chelsio NIC can't
offload VXLAN with the distro drivers (features "tx-udp_tnl-
segmentation" and "tx-udp_tnl-csum-segmentation"), but with the OFED
driver ("ChelsioUwire-3.10.0.0"), it can.
Can we please get this in the distro driver ?
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-47-generic 4.15.0-47.50
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Apr 19 14:48 seq
crw-rw 1 root audio 116, 33 Apr 19 14:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Apr 25 08:53:20 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Supermicro Super Server
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic
root=UUID=7b06790c-9447-446a-b1cf-b25104638b26 ro console=ttyS1,115200 nosplash
iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor
RelatedPackageVersions:
linux-restricted-modules-4.15.0-47-generic N/A
linux-backports-modules-4.15.0-47-generic N/A
linux-firmware 1.173.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H11DSU-iN
dmi.board.vendor: Supermicro
dmi.board.version: 1.02A
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Super Server
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826376/+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 1863407] Re: Lenovo Ideapad L340 screen backlight stuck at maximum brightness
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863407 Title: Lenovo Ideapad L340 screen backlight stuck at maximum brightness Status in linux package in Ubuntu: Expired Bug description: acpi_osi=Linux and acpi_backlight=vendor do not fix. Depending on the kernel parameters, /sys/class/backlight contains either "acpi_video0" or "ideapad". I have also tried acpi_backlight=none ls /sys/class/backlight: acpi_video0 grep -r . /proc/acpi /proc/acpi/button/lid/LID/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:GPP0 S3*disabled /proc/acpi/wakeup:GPP1 S3*enabled pci::00:01.2 /proc/acpi/wakeup:GPP2 S3*enabled pci::00:01.3 /proc/acpi/wakeup:GPP3 S3*disabled /proc/acpi/wakeup:GPP4 S3*disabled /proc/acpi/wakeup:GPP5 S3*disabled /proc/acpi/wakeup:GPP6 S3*disabled /proc/acpi/wakeup:GP17 S3*enabled pci::00:08.1 /proc/acpi/wakeup:XHC0 S3*enabled pci::03:00.3 /proc/acpi/wakeup:XHC1 S3*enabled pci::03:00.4 /proc/acpi/wakeup:GP18 S3*enabled pci::00:08.2 iasl -d dsdt.dat Intel ACPI Component Architecture ASL+ Optimizing Compiler/Disassembler version 20180105 Copyright (c) 2000 - 2018 Intel Corporation Input file dsdt.dat, Length 0x6FA5 (28581) bytes ACPI: DSDT 0x 006FA5 (v01 LENOVO AMD 1000 INTL 20120711) Pass 1 parse of [DSDT] Pass 2 parse of [DSDT] Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions) Parsing completed Found 6 external control methods, reparsing with new information Pass 1 parse of [DSDT] Pass 2 parse of [DSDT] Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions) Parsing completed Disassembly completed ASL Output:dsdt.dsl - 318645 bytes iASL Warning: There were 6 external control methods found during disassembly, but only 0 were resolved (6 unresolved). Additional ACPI tables may be required to properly disassemble the code. This resulting disassembler output file may not compile because the disassembler did not know how many arguments to assign to the unresolved methods. Note: SSDTs can be dynamically loaded at runtime and may or may not be available via the host OS. To specify the tables needed to resolve external control method references, the -e option can be used to specify the filenames. Example iASL invocations: iasl -e ssdt1.aml ssdt2.aml ssdt3.aml -d dsdt.aml iasl -e dsdt.aml ssdt2.aml -d ssdt1.aml iasl -e ssdt*.aml -d dsdt.aml In addition, the -fe option can be used to specify a file containing control method external declarations with the associated method argument counts. Each line of the file must be of the form: External (, MethodObj, ) Invocation: iasl -fe refs.txt -d dsdt.aml ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eli1603 F pulseaudio /dev/snd/controlC0: eli1603 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 01:51:30 2020 InstallationDate: Installed on 2020-01-30 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81LY ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=97a5f239-2442-42e1-a2c8-b7bf4985a13a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: ARCN33WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad L340-17API dmi.modalias: dmi:bvnLENOVO:bvrARCN33WW:bd10/28/2019:svnLENOVO:pn81LY:pvrLenovoIdeaPadL340-17API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadL340-17API:
[Kernel-packages] [Bug 1882944] Re: Resolution and settings changed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882944 Title: Resolution and settings changed Status in linux package in Ubuntu: Expired Bug description: Resolution was set to 640x800 and not able to change it. Monitor and graphics drivers not recognized. All display settings changed and not correctable. Rebooted back to the 5.3 kernel and system is back to normal. May delete the 5.4 kernel until corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882944/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This is alsa-ucm-conf debdiff for Groovy. thx. ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889217/+attachment/5400274/+files/alsa-ucm-conf_1.2.2-1ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch
[Kernel-packages] [Bug 1890956] Re: Mouse and keyboard stop working after suspend
Please: 1. Reboot. 2. Suspend and reproduce the problem. 3. Reboot again. 4. Run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: gdm3 (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890956 Title: Mouse and keyboard stop working after suspend Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 dm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Booting off of a live usb, the trackpad, external mouse, and internal keyboard stop responding to input after suspend. On my updated install, the laptop trackpad works, but the other two inputs do not after suspend/wake. I can log in using the on screen keyboard. Unplugging the mouse and plugging it in does not fix it. The inputs don't respond while logged in either. Only a reboot fixes it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 14:00:59 2020 ExecutablePath: /usr/lib/gdm3/gdm-x-session InstallationDate: Installed on 2020-06-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1890956/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This is the pulseaudio debdiff for Groovy. thx. ** Patch added: "pulseaudio_13.99.1-1ubuntu9.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889217/+attachment/5400275/+files/pulseaudio_13.99.1-1ubuntu9.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch
[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This is the alsa-lib debdiff for Groovy. thx. ** Patch added: "alsa-lib_1.2.2-2.3ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889217/+attachment/5400273/+files/alsa-lib_1.2.2-2.3ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch
[Kernel-packages] [Bug 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
>From kernel oops, there is no root fs found. Possible root cause is bug 1890797, which needed kernel module udebs are not packed into legacy ISO. But this bug is filed against daily-live ISO, better to check if we have same issue on daily-live ISOs too. -- 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/1890884 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch Status in linux package in Ubuntu: Incomplete Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D06 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [8.375118] md: ... autorun DONE. [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [8.385955] Please append a correct "root=" boot option; here are the available partitions: [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.418879] Call trace: [8.421316] dump_backtrace+0x0/0x198 [8.424965] show_stack+0x24/0x30 [8.428269] dump_stack+0x98/0xbc [8.431572] panic+0x128/0x2a4 [8.434615] mount_block_root+0x210/0x2e8 [8.438610] mount_root+0x7c/0x8c [8.441912] prepare_namespace+0x144/0x1dc [8.445995] kernel_init_freeable+0x218/0x23c [8.450341] kernel_init+0x18/0x110 [8.453817] ret_from_fork+0x10/0x18 [8.457486] SMP: stopping secondary CPUs [8.461836] Kernel Offset: disabled [8.465312] CPU features: 0x03200a38 [8.468873] Memory Limit: none [8.473291] Unable to handle kernel paging request at virtual address 09865034 [8.481192] Mem abort info: [8.483972] ESR = 0x9661 [8.487013] Exception class = DABT (current EL), IL = 32 bits [8.492918] SET = 0, FnV = 0 [8.495958] EA = 0, S1PTW = 0 [8.499086] Data abort info: [8.501953] ISV = 0, ISS = 0x0061 [8.505774] CM = 0, WnR = 1 [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [8.515502] [09865034] *pgd=0a5fe003, *pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703 [8.526445] Internal error: Oops: 9661 [#1] SMP [8.531310] Modules linked in: [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO) [8.562144] pc : acpi_os_write_memory+0xac/0x158 [8.566749] lr : apei_write+0xb0/0xc0 [8.570397] sp : 09afb900 [8.573698] x29: 09afb900 x28: fffe [8.578996] x27: x26: ffa5 [8.584294] x25: ffbe x24: 0080 [8.589592] x23: 0005 x22: 0008 [8.594890] x21: 0040 x20: 0010 [8.600188] x19: 94110034 x18: 0003 [8.605486] x17: x16: 0009 [8.610784] x15: 001f x14: 8205169d4225fc6e [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 [8.631976] x7 : 0001 x6 : 94110034 [8.637274] x5 : 9411003c x4 : 09639fb8 [8.642571] x3 : x2 : 0034 [8.647869] x1 : 0010 x0 : 09865034 [8.653167] Call trace: [8.655601] acpi_os_write_memory+0xac/0x158 [8.659858] apei_write+0xb0/0xc0 [8.663160] __apei_exec_write_register+0x88/0xb0 [8.667851] apei_exec_write_register_value+0x2c/0x38 [8.672888] __apei_exec_run+0xac/0x108 [8.676711] erst_write+0x154/0x268 [8.680186] erst_writer+0x26c/0x3b0 [8.683751] pstore_dump+0x1b4/0x330 [8.687313] kmsg_dump+0xd0/0x100 [8.690615] panic+0x164/0x2a4 [8.693656] mount_block_root+0x210/0x2e8 [8.697652] mount_root+0x7c/0x8c [8.700953] prepare_namespace+0x144/0x1dc [8.705035] kernel_init_freeable+0x218/0x23c [8.709380] kernel_init+0x18/0x110 [8.712855]
[Kernel-packages] [Bug 1890867] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch
Ah, Please skip comment #2. This is different issue. Bug 1890797 only affects when you install with HWE kernels. This bug reports on 4.15 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch Status in linux package in Ubuntu: Confirmed Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D05 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 [6.657871] Call trace: [6.660308] dump_backtrace+0x0/0x198 [6.663957] show_stack+0x24/0x30 [6.667261] dump_stack+0x98/0xbc [6.670563] panic+0x128/0x2a4 [6.673606] mount_block_root+0x210/0x2e8 [6.677603] mount_root+0x7c/0x8c [6.680904] prepare_namespace+0x144/0x1dc [6.684987] kernel_init_freeable+0x218/0x23c [6.689331] kernel_init+0x18/0x110 [6.692806] ret_from_fork+0x10/0x18 [6.696428] SMP: stopping secondary CPUs [6.700345] Kernel Offset: disabled [6.703821] CPU features: 0x2008 [6.707382] Memory Limit: none [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+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 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
Ah, Please skip comment #2. This is different issue. Bug 1890797 only affects when you install with HWE kernels. This bug reports on 4.15 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890884 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch Status in linux package in Ubuntu: Incomplete Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D06 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [8.375118] md: ... autorun DONE. [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [8.385955] Please append a correct "root=" boot option; here are the available partitions: [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.418879] Call trace: [8.421316] dump_backtrace+0x0/0x198 [8.424965] show_stack+0x24/0x30 [8.428269] dump_stack+0x98/0xbc [8.431572] panic+0x128/0x2a4 [8.434615] mount_block_root+0x210/0x2e8 [8.438610] mount_root+0x7c/0x8c [8.441912] prepare_namespace+0x144/0x1dc [8.445995] kernel_init_freeable+0x218/0x23c [8.450341] kernel_init+0x18/0x110 [8.453817] ret_from_fork+0x10/0x18 [8.457486] SMP: stopping secondary CPUs [8.461836] Kernel Offset: disabled [8.465312] CPU features: 0x03200a38 [8.468873] Memory Limit: none [8.473291] Unable to handle kernel paging request at virtual address 09865034 [8.481192] Mem abort info: [8.483972] ESR = 0x9661 [8.487013] Exception class = DABT (current EL), IL = 32 bits [8.492918] SET = 0, FnV = 0 [8.495958] EA = 0, S1PTW = 0 [8.499086] Data abort info: [8.501953] ISV = 0, ISS = 0x0061 [8.505774] CM = 0, WnR = 1 [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [8.515502] [09865034] *pgd=0a5fe003, *pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703 [8.526445] Internal error: Oops: 9661 [#1] SMP [8.531310] Modules linked in: [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO) [8.562144] pc : acpi_os_write_memory+0xac/0x158 [8.566749] lr : apei_write+0xb0/0xc0 [8.570397] sp : 09afb900 [8.573698] x29: 09afb900 x28: fffe [8.578996] x27: x26: ffa5 [8.584294] x25: ffbe x24: 0080 [8.589592] x23: 0005 x22: 0008 [8.594890] x21: 0040 x20: 0010 [8.600188] x19: 94110034 x18: 0003 [8.605486] x17: x16: 0009 [8.610784] x15: 001f x14: 8205169d4225fc6e [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 [8.631976] x7 : 0001 x6 : 94110034 [8.637274] x5 : 9411003c x4 : 09639fb8 [8.642571] x3 : x2 : 0034 [8.647869] x1 : 0010 x0 : 09865034 [8.653167] Call trace: [8.655601] acpi_os_write_memory+0xac/0x158 [8.659858] apei_write+0xb0/0xc0 [8.663160] __apei_exec_write_register+0x88/0xb0 [8.667851] apei_exec_write_register_value+0x2c/0x38 [8.672888] __apei_exec_run+0xac/0x108 [8.676711] erst_write+0x154/0x268 [8.680186] erst_writer+0x26c/0x3b0 [8.683751] pstore_dump+0x1b4/0x330 [8.687313] kmsg_dump+0xd0/0x100 [8.690615] panic+0x164/0x2a4 [8.693656] mount_block_root+0x210/0x2e8 [8.697652] mount_root+0x7c/0x8c [8.700953] prepare_namespace+0x144/0x1dc [8.705035] kernel_init_freeable+0x218/0x23c [8.709380] kernel_init+0x18/0x110 [8.712855] ret_from_fork+0x10/0x18 [8.716418] Code: 54000380 710102bf 54000561 d5033e9f (f914) [8.722499] ---[ end
[Kernel-packages] [Bug 1890867] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch
>From kernel oops, there is no root fs found. Possible root cause is bug 1890797, which needed kernel module udebs are not packed into legacy ISO. But this bug is filed against daily-live ISO, better to check if we have same issue on daily-live ISOs too. -- 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/1890867 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D05 arm64 arch Status in linux package in Ubuntu: Confirmed Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D05 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [6.643543] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [6.651271] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 [6.657871] Call trace: [6.660308] dump_backtrace+0x0/0x198 [6.663957] show_stack+0x24/0x30 [6.667261] dump_stack+0x98/0xbc [6.670563] panic+0x128/0x2a4 [6.673606] mount_block_root+0x210/0x2e8 [6.677603] mount_root+0x7c/0x8c [6.680904] prepare_namespace+0x144/0x1dc [6.684987] kernel_init_freeable+0x218/0x23c [6.689331] kernel_init+0x18/0x110 [6.692806] ret_from_fork+0x10/0x18 [6.696428] SMP: stopping secondary CPUs [6.700345] Kernel Offset: disabled [6.703821] CPU features: 0x2008 [6.707382] Memory Limit: none [6.710438] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890867/+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 1890639] Re: touchpad not working after login dell xps 13
Didn't find suspend in the log. Please reproduce the issue and attach dmesg. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890639 Title: touchpad not working after login dell xps 13 Status in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: My touchpad stops working after login. These are the props using xinput: Device 'DLL075B:01 06CB:76AF Touchpad': Device Enabled (148): 1 Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (302): 1 libinput Tapping Enabled Default (303): 0 libinput Tapping Drag Enabled (304):1 libinput Tapping Drag Enabled Default (305):1 libinput Tapping Drag Lock Enabled (306): 0 libinput Tapping Drag Lock Enabled Default (307): 0 libinput Tapping Button Mapping Enabled (308): 1, 0 libinput Tapping Button Mapping Default (309): 1, 0 libinput Natural Scrolling Enabled (286): 1 libinput Natural Scrolling Enabled Default (287): 0 libinput Disable While Typing Enabled (310):1 libinput Disable While Typing Enabled Default (311):1 libinput Scroll Methods Available (288):1, 1, 0 libinput Scroll Method Enabled (289): 1, 0, 0 libinput Scroll Method Enabled Default (290): 1, 0, 0 libinput Click Methods Available (312): 1, 1 libinput Click Method Enabled (313):1, 0 libinput Click Method Enabled Default (314):1, 0 libinput Middle Emulation Enabled (315):0 libinput Middle Emulation Enabled Default (316):0 libinput Accel Speed (293): 0.00 libinput Accel Speed Default (294): 0.00 libinput Left Handed Enabled (298): 0 libinput Left Handed Enabled Default (299): 0 libinput Send Events Modes Available (271): 1, 1 libinput Send Events Mode Enabled (272):1, 0 libinput Send Events Mode Enabled Default (273):0, 0 Device Node (274): "/dev/input/event7" Device Product ID (275):1739, 30383 libinput Drag Lock Buttons (300): libinput Horizontal Scroll Enabled (301): 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: uri2562 F pulseaudio /dev/snd/controlC0: uri2562 F pulseaudio CRDA: global country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-20 (109 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 9360 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xuq7gc@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_xuq7gc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-25 (103 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890639/+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 1890639] Re: touchpad not working after login dell xps 13
Sorry, it should be "login". -- 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/1890639 Title: touchpad not working after login dell xps 13 Status in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: My touchpad stops working after login. These are the props using xinput: Device 'DLL075B:01 06CB:76AF Touchpad': Device Enabled (148): 1 Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (302): 1 libinput Tapping Enabled Default (303): 0 libinput Tapping Drag Enabled (304):1 libinput Tapping Drag Enabled Default (305):1 libinput Tapping Drag Lock Enabled (306): 0 libinput Tapping Drag Lock Enabled Default (307): 0 libinput Tapping Button Mapping Enabled (308): 1, 0 libinput Tapping Button Mapping Default (309): 1, 0 libinput Natural Scrolling Enabled (286): 1 libinput Natural Scrolling Enabled Default (287): 0 libinput Disable While Typing Enabled (310):1 libinput Disable While Typing Enabled Default (311):1 libinput Scroll Methods Available (288):1, 1, 0 libinput Scroll Method Enabled (289): 1, 0, 0 libinput Scroll Method Enabled Default (290): 1, 0, 0 libinput Click Methods Available (312): 1, 1 libinput Click Method Enabled (313):1, 0 libinput Click Method Enabled Default (314):1, 0 libinput Middle Emulation Enabled (315):0 libinput Middle Emulation Enabled Default (316):0 libinput Accel Speed (293): 0.00 libinput Accel Speed Default (294): 0.00 libinput Left Handed Enabled (298): 0 libinput Left Handed Enabled Default (299): 0 libinput Send Events Modes Available (271): 1, 1 libinput Send Events Mode Enabled (272):1, 0 libinput Send Events Mode Enabled Default (273):0, 0 Device Node (274): "/dev/input/event7" Device Product ID (275):1739, 30383 libinput Drag Lock Buttons (300): libinput Horizontal Scroll Enabled (301): 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: uri2562 F pulseaudio /dev/snd/controlC0: uri2562 F pulseaudio CRDA: global country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-20 (109 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 9360 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xuq7gc@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_xuq7gc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-25 (103 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890639/+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 1890865] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890865 Title: Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works Status in linux package in Ubuntu: Confirmed Bug description: Video of bug: https://youtu.be/O0__VNN9G_o At 0:11 in the video you see old web browser data showing up in my program. At 0:19 when I close a window in my program the texture for my piano key letters flicker. By luck the texture for my keys sometimes flickers to stuff previously displayed on my desktop. This flickering is linked to my mouse movement/placement. When I run my program with the proprietary 440 NVIDIA driver things work fine. I am on Ubuntu budgie 20.04 using XFCE on X.org X11. The SDL2 program source: https://github.com/kevinacahalan/piano_waterfall git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Aug 7 23:35:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251] InstallationDate: Installed on 2020-05-05 (95 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. OptiPlex 3010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5fe179e5-be36-426b-9297-8ef7a1af2c0c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/31/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Aug 7 21:38:07 2020 xserver.configfile: default xserver.errors: client bug: timer event11 debounce short: scheduled expiry is in the past (-2ms), your system is too slow xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890865/+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 1890865] Re: Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works
** Summary changed: - Nouveau X.org: Stale texture data and flicker in small SDL2 program + Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: nouveau -- 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/1890865 Title: Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works Status in linux package in Ubuntu: New Bug description: Video of bug: https://youtu.be/O0__VNN9G_o At 0:11 in the video you see old web browser data showing up in my program. At 0:19 when I close a window in my program the texture for my piano key letters flicker. By luck the texture for my keys sometimes flickers to stuff previously displayed on my desktop. This flickering is linked to my mouse movement/placement. When I run my program with the proprietary 440 NVIDIA driver things work fine. I am on Ubuntu budgie 20.04 using XFCE on X.org X11. The SDL2 program source: https://github.com/kevinacahalan/piano_waterfall git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Aug 7 23:35:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251] InstallationDate: Installed on 2020-05-05 (95 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. OptiPlex 3010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5fe179e5-be36-426b-9297-8ef7a1af2c0c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/31/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Aug 7 21:38:07 2020 xserver.configfile: default xserver.errors: client bug: timer event11 debounce short: scheduled expiry is in the past (-2ms), your system is too slow xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890865/+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 1890865] [NEW] Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works
You have been subscribed to a public bug: Video of bug: https://youtu.be/O0__VNN9G_o At 0:11 in the video you see old web browser data showing up in my program. At 0:19 when I close a window in my program the texture for my piano key letters flicker. By luck the texture for my keys sometimes flickers to stuff previously displayed on my desktop. This flickering is linked to my mouse movement/placement. When I run my program with the proprietary 440 NVIDIA driver things work fine. I am on Ubuntu budgie 20.04 using XFCE on X.org X11. The SDL2 program source: https://github.com/kevinacahalan/piano_waterfall git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Aug 7 23:35:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251] InstallationDate: Installed on 2020-05-05 (95 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. OptiPlex 3010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5fe179e5-be36-426b-9297-8ef7a1af2c0c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 042P49 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/31/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Aug 7 21:38:07 2020 xserver.configfile: default xserver.errors: client bug: timer event11 debounce short: scheduled expiry is in the past (-2ms), your system is too slow xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.2 xserver.video_driver: modeset ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works https://bugs.launchpad.net/bugs/1890865 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889780] Re: Unable to change screen resolution after upgrade to 5.4.0-42-generic
Hello Dave, Have you tried to re-install the NVIDIA proprietary driver with 5.4 kernel? I saw you were using it with 5.3 but not with 5.4, maybe that's the cause. lspci in 5.3: 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia lspci in 5.4: 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Kernel modules: nvidiafb, nouveau -- 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/1889780 Title: Unable to change screen resolution after upgrade to 5.4.0-42-generic Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: When booting using 5.4.0-42-generic kernel, screen resolution is fixed at 640x480 and there is no way to change it. Booting using 5.3.0-62-generic works fine. In "Displays", the dropdowns for Resolution only has 640x480 for selection. For Refresh Rate and Rotation there are no selections under dropdown. OS - 18.04 LTS Kernel - 5.4.0-42 previous 5.3.0-62-generic Dell Monitor NVIDIA GeForce GT 1030 CPU is AMD Ryzen 5 2600 X Socket AM4 Questions: How will I find out that this bug has been fixed? I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU work or are there specific video cards I should look at? Is there a site that recommends video cards for Linux? Thanks, Dave --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 2495 F pulseaudio /dev/snd/controlC1: dave 2495 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-27 (158 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING 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.:bvr2801:bd09/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 2639 F pulseaudio /dev/snd/controlC1: dave 2639 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-27 (161 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ddcd642f-6d40-4279-bfab-fb7564a302d6 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 RfKill: Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING
[Kernel-packages] [Bug 1566486] Re: package apmd (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/apm', que está también en el paquete atom 1.3.2
*** This bug is a duplicate of bug 1785064 *** https://bugs.launchpad.net/bugs/1785064 atom 1.3.2 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: apmd (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1785064 package apmd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/apm', which is also in package atom 1.28.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to apmd in Ubuntu. https://bugs.launchpad.net/bugs/1566486 Title: package apmd (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/apm', que está también en el paquete atom 1.3.2 Status in apmd package in Ubuntu: Invalid Bug description: Tried to install apmd (Advanced Power Management) through Terminal but failed. ~$ sudo apt upgrade apmd Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Calculando la actualización... Hecho Los paquetes indicados a continuación se instalaron de forma automática y ya no son necesarios. libgnome-menu2 php5-gd python-gmenu Utilice «sudo apt autoremove» para eliminarlos. Se instalarán los siguientes paquetes NUEVOS: apmd libapm1 0 actualizados, 2 nuevos se instalarán, 0 para eliminar y 0 no actualizados. Se necesita descargar 39,2 kB de archivos. Se utilizarán 274 kB de espacio de disco adicional después de esta operación. ¿Desea continuar? [S/n] s Des:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 libapm1 amd64 3.2.2-15 [8.302 B] Des:2 http://archive.ubuntu.com/ubuntu xenial/universe amd64 apmd amd64 3.2.2-15 [30,9 kB] Descargados 39,2 kB en 0s (48,8 kB/s) Seleccionando el paquete libapm1 previamente no seleccionado. (Leyendo la base de datos ... 475846 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../libapm1_3.2.2-15_amd64.deb ... Desempaquetando libapm1 (3.2.2-15) ... Seleccionando el paquete apmd previamente no seleccionado. Preparando para desempaquetar .../apmd_3.2.2-15_amd64.deb ... Desempaquetando apmd (3.2.2-15) ... dpkg: error al procesar el archivo /var/cache/apt/archives/apmd_3.2.2-15_amd64.deb (--unpack): intentando sobreescribir `/usr/bin/apm', que está también en el paquete atom 1.3.2 Procesando disparadores para systemd (229-3ubuntu2) ... Procesando disparadores para ureadahead (0.100.0-19) ... Procesando disparadores para man-db (2.7.5-1) ... Se encontraron errores al procesar: /var/cache/apt/archives/apmd_3.2.2-15_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ~$ apt-cache policy apmd apmd: Instalados: (ninguno) Candidato: 3.2.2-15 Tabla de versión: 3.2.2-15 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apmd (not installed) Uname: Linux 4.3.0-040300-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 AptOrdering: libapm1: Install apmd: Install libapm1: Configure apmd: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 5 14:10:10 2016 DpkgTerminalLog: Preparando para desempaquetar .../libapm1_3.2.2-15_amd64.deb ... Desempaquetando libapm1 (3.2.2-15) ... Seleccionando el paquete apmd previamente no seleccionado. Preparando para desempaquetar .../apmd_3.2.2-15_amd64.deb ... Desempaquetando apmd (3.2.2-15) ... ErrorMessage: intentando sobreescribir `/usr/bin/apm', que está también en el paquete atom 1.3.2 InstallationDate: Installed on 2015-07-08 (272 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.9 SourcePackage: apmd Title: package apmd (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/apm', que está también en el paquete atom 1.3.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apmd/+bug/1566486/+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 1785064] Re: package apmd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/apm', which is also in package atom 1.28.1
atom 1.28.1 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: apmd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to apmd in Ubuntu. https://bugs.launchpad.net/bugs/1785064 Title: package apmd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/apm', which is also in package atom 1.28.1 Status in apmd package in Ubuntu: Invalid Bug description: install attempt via "sudo apt install apmd" in terminal ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apmd (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon Jul 30 22:37:18 2018 ErrorMessage: trying to overwrite '/usr/bin/apm', which is also in package atom 1.28.1 InstallationDate: Installed on 2018-07-24 (8 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: apmd Title: package apmd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/apm', which is also in package atom 1.28.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apmd/+bug/1785064/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
the issue of computer frozen probably is caused by graphic driver, please add nomodeset in the bootargs or install the nvidia-driver-450 instead of in-tree driver nouveau. And please install 20.04 and upgrade all packages to the latest version, I believe the internal mic will work. -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1780809] Re: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 ** This bug has been marked a duplicate of bug 1772985 package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1780809 Title: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-0ubuntu1 Status in wireless-regdb package in Ubuntu: Confirmed Bug description: A requirement of update appeared and I've just accepted it. But during the process of installation, a failure happened. It seems to refer to the wireless register. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: wireless-regdb 2016.06.10-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Mon Jul 9 11:58:30 2018 Dependencies: DuplicateSignature: package:wireless-regdb:2016.06.10-0ubuntu1 Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over (2016.06.10-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-04WWLs/56-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-0ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-0ubuntu1 InstallationDate: Installed on 2017-09-03 (308 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: wireless-regdb Title: package wireless-regdb 2016.06.10-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1780809/+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 1782427] Re: package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 ** This bug has been marked a duplicate of bug 1772985 package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1782427 Title: package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 Status in wireless-regdb package in Ubuntu: Confirmed Bug description: Every time I start system, this error appears ProblemType: Package DistroRelease: Ubuntu 18.04 Package: wireless-regdb 2018.05.09-0ubuntu1~16.04.1 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 Date: Fri Jul 13 22:41:15 2018 Dependencies: DuplicateSignature: package:wireless-regdb:2018.05.09-0ubuntu1~16.04.1 Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over (2016.06.10-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Sc51aa/5-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 InstallationDate: Installed on 2018-04-27 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: wireless-regdb Title: package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1782427/+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 1772985] Re: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wireless-regdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1772985 Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: Confirmed Status in wireless-regdb package in Ubuntu: Confirmed Bug description: It is not an update from 16.04 to 18.04 as #1770916 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Wed May 23 20:24:52 2018 DuplicateSignature: package:crda:3.13-1 Unpacking crda (3.13-1ubuntu0.16.04.1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.13-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 InstallationDate: Installed on 2017-04-13 (404 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1772985/+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 1789032] Re: package crda 3.13-1 failed to install/upgrade: intentando sobreescribir `/lib/crda/pubkeys/sforshee.key.pub.pem', que está también en el paquete wireless-regdb 2018
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 ** This bug has been marked a duplicate of bug 1772985 package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1789032 Title: package crda 3.13-1 failed to install/upgrade: intentando sobreescribir `/lib/crda/pubkeys/sforshee.key.pub.pem', que está también en el paquete wireless-regdb 2018.05.09-0ubuntu1~16.04.1 Status in crda package in Ubuntu: New Bug description: me sale error siempre, que hago ProblemType: Package DistroRelease: Ubuntu 17.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 Date: Sat Aug 25 12:39:32 2018 ErrorMessage: intentando sobreescribir `/lib/crda/pubkeys/sforshee.key.pub.pem', que está también en el paquete wireless-regdb 2018.05.09-0ubuntu1~16.04.1 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: intentando sobreescribir `/lib/crda/pubkeys/sforshee.key.pub.pem', que está también en el paquete wireless-regdb 2018.05.09-0ubuntu1~16.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1789032/+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 1772985] Re: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubu
** Also affects: wireless-regdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1772985 Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: Confirmed Status in wireless-regdb package in Ubuntu: Confirmed Bug description: It is not an update from 16.04 to 18.04 as #1770916 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Wed May 23 20:24:52 2018 DuplicateSignature: package:crda:3.13-1 Unpacking crda (3.13-1ubuntu0.16.04.1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.13-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 InstallationDate: Installed on 2017-04-13 (404 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1772985/+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 1770916] Re: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.2
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 ** This bug has been marked a duplicate of bug 1772985 package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1770916 Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: Fix Released Bug description: On upgrading 16.04 - >18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: crda 3.18-1build1 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: crda:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 12 13:51:43 2018 DpkgTerminalLog: Preparing to unpack .../crda_3.18-1build1_amd64.deb ... Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 DuplicateSignature: package:crda:3.18-1build1 Unpacking crda (3.18-1build1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.18-1build1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: crda Title: package crda 3.18-1build1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1770916/+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 1791918] Re: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2018.05.09-0ubu
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 ** This bug has been marked a duplicate of bug 1772985 package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1791918 Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 Status in crda package in Ubuntu: New Bug description: this message just popped out on my screen and is giving me error message when I do the update. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-34-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Tue Sep 11 10:21:40 2018 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 InstallationDate: Installed on 2017-02-12 (575 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) Python3Details: /usr/bin/python3.5, Python 3.5.2, python3-minimal, 3.5.1-3 PythonDetails: /usr/bin/python2.7, Python 2.7.12, python-minimal, 2.7.12-1~16.04 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1791918/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
CubicSDR still triggers it for me even in 5.4.0-42.46, further a 5.8.0 mainline kernel also suffers the same. This was working for me until just a few days ago now it's not. -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] Users are experiencing a frequent NULL pointer dereference crash in i915_active_acquire when using kms, which is used by default. [Fix] The fix is a cherry pick from upstream which was supposed to be backported to 5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to resolve some uninitialized pointer usage. [Test] Verified by multiple bug reporters. [Regression Potential] Medium. Although there are a lot of lines added, they're mostly boilerplate, and this patch is confirmed by multiple users to fix a crash. --- uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter
[Kernel-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879287 Title: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly) Status in linux package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: I've recently installed Ubuntu on a laptop that has a Ryzen APU (with Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first issue that this kind of setup gives on a fresh install is that that PRIME render offloading doesn't work, I presume that Ubuntu currently sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia but that's another separate issue. As a workaround I created an Xorg configuration (attached in this report) that sets up both GPUs (with the appropiate BusIDs), after such configuration is applied the system boots fine with AMD integrated graphics being used and the ability to switch to Nvidia with PRIME render off-loading. The problem comes when I try to use the computer the next day, then it gives me a black screen without having the ability to switch to a tty, the boot log doesn't throw any errors I just see a black screen after Xorg tries to start. I can make it work again by entering in recovery mode, logging into a root console and switching between "nvidia" and "on-demand" modes using prime-select (I set it up to "on-demand" profile after installing Ubuntu). For the moment I cannot provide any relevant logs since it's now working fine (and I don't remember seeing any errors on Xorg logs), also I don't really know where to look for this kind of issues. My system information: -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) -RAM: 8 GB -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4) -Xorg 1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879287/+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 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879287 Title: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly) Status in linux package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: I've recently installed Ubuntu on a laptop that has a Ryzen APU (with Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first issue that this kind of setup gives on a fresh install is that that PRIME render offloading doesn't work, I presume that Ubuntu currently sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia but that's another separate issue. As a workaround I created an Xorg configuration (attached in this report) that sets up both GPUs (with the appropiate BusIDs), after such configuration is applied the system boots fine with AMD integrated graphics being used and the ability to switch to Nvidia with PRIME render off-loading. The problem comes when I try to use the computer the next day, then it gives me a black screen without having the ability to switch to a tty, the boot log doesn't throw any errors I just see a black screen after Xorg tries to start. I can make it work again by entering in recovery mode, logging into a root console and switching between "nvidia" and "on-demand" modes using prime-select (I set it up to "on-demand" profile after installing Ubuntu). For the moment I cannot provide any relevant logs since it's now working fine (and I don't remember seeing any errors on Xorg logs), also I don't really know where to look for this kind of issues. My system information: -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) -RAM: 8 GB -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4) -Xorg 1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879287/+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 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)
I have a very similar problem, today I asked a question on ask ubuntu https://askubuntu.com/questions/1265779/video-issues-with-amd-igpu-and-nvidia-gpu-in-an-aspire-a715-41g-laptop -- 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/1879287 Title: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly) Status in linux package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: I've recently installed Ubuntu on a laptop that has a Ryzen APU (with Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first issue that this kind of setup gives on a fresh install is that that PRIME render offloading doesn't work, I presume that Ubuntu currently sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia but that's another separate issue. As a workaround I created an Xorg configuration (attached in this report) that sets up both GPUs (with the appropiate BusIDs), after such configuration is applied the system boots fine with AMD integrated graphics being used and the ability to switch to Nvidia with PRIME render off-loading. The problem comes when I try to use the computer the next day, then it gives me a black screen without having the ability to switch to a tty, the boot log doesn't throw any errors I just see a black screen after Xorg tries to start. I can make it work again by entering in recovery mode, logging into a root console and switching between "nvidia" and "on-demand" modes using prime-select (I set it up to "on-demand" profile after installing Ubuntu). For the moment I cannot provide any relevant logs since it's now working fine (and I don't remember seeing any errors on Xorg logs), also I don't really know where to look for this kind of issues. My system information: -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) -RAM: 8 GB -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4) -Xorg 1.20.8-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879287/+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 1890960] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890960 Title: touchpad is not recognised on ideapad 5-15IIL05 Laptop - Type 81YK Status in linux package in Ubuntu: Confirmed Bug description: ubuntu@ubuntu:~$ cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3e/LNXVIDEO:01/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=13d3 Product=56ff Version=1917 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0005 Vendor=0a5c Product=4503 Version=0129 N: Name="BM30X mouse" P: Phys=3c:58:c2:66:4d:e1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/bluetooth/hci0/hci0:256/0005:0A5C:4503.0003/input/input11 U: Uniq=dc:2c:26:b1:6f:03 H: Handlers=mouse0 event9 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 < ubuntu@ubuntu:~$ cat version.log Ubuntu 5.4.0-42.46-generic 5.4.44 <- ubuntu@ubuntu:~$ cat lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:8a12] (rev 03) Subsystem: Lenovo Device [17aa:3804] 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: icl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a37] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap:
[Kernel-packages] [Bug 1890960] [NEW] touchpad is not recognised on ideapad 5-15IIL05 Laptop - Type 81YK
Public bug reported: ubuntu@ubuntu:~$ cat devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:3e/LNXVIDEO:01/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=13d3 Product=56ff Version=1917 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0005 Vendor=0a5c Product=4503 Version=0129 N: Name="BM30X mouse" P: Phys=3c:58:c2:66:4d:e1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/bluetooth/hci0/hci0:256/0005:0A5C:4503.0003/input/input11 U: Uniq=dc:2c:26:b1:6f:03 H: Handlers=mouse0 event9 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 < ubuntu@ubuntu:~$ cat version.log Ubuntu 5.4.0-42.46-generic 5.4.44 <- ubuntu@ubuntu:~$ cat lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:8a12] (rev 03) Subsystem: Lenovo Device [17aa:3804] 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: icl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a37] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Address: fee00018 Data: Masking: Pending: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@Niko: It looks ok. I have no idea what could be the problem. I'm sorry. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)
Kai-Heng answered: "Lenovo is aware of this issue, but I haven't got the hardware yet." There is an easy to apply solution in Bug-Report #1861610 that seems to work for some people. -- 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/1885573 Title: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) Status in linux package in Ubuntu: Incomplete Bug description: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) 2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is ALPS, Elan or Synatics 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrozwod1597 F pulseaudio /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
The output of 'lsmod | grep i2c' is i2c_algo_bit 16384 1 i915 elan_i2c 40960 0 i2c_i801 32768 0 i2c_hid28672 0 hid 131072 3 i2c_hid,usbhid,hid_generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
The solution of Ferenc worked for me, thank you a lot! That's very sad that there is no any official fix for this problem, although the bug is rather old. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@Niko: The right modules should be loaded at boot time according to modalias. What is the output of 'lsmod | grep i2c'? The elan_i2c module should be in the list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1890951] Re: btrfs not writable when mounted without "skip_balance"
Launchpad has imported 10 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=203405. 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 2019-04-24T00:34:54+00:00 furlongm wrote: If I mount with skip_balance, the following does not happen. But if I try to start a balance processes go into a D state and the balance hangs. [ 173.488407] kernel BUG at ../fs/btrfs/relocation.c:1449! [ 173.488410] invalid opcode: [#1] SMP PTI [ 173.488414] CPU: 7 PID: 2542 Comm: btrfs-balance Tainted: G O 4.12.14-lp150.12.58-default #1 openSUSE Leap 15.0 [ 173.488416] Hardware name: Dell Inc. OptiPlex 9020/00V62H, BIOS A24 10/24/2018 [ 173.488417] task: 8803c85f80c0 task.stack: c90002234000 [ 173.488439] RIP: 0010:create_reloc_root+0x1dc/0x1f0 [btrfs] [ 173.488440] RSP: 0018:c90002237910 EFLAGS: 00010282 [ 173.488442] RAX: ffef RBX: 880408c99c00 RCX: 0001 [ 173.488444] RDX: 0005 RSI: 88040bdc2a80 RDI: 0286 [ 173.488445] RBP: 8803dd514d98 R08: 88040b8c5a80 R09: [ 173.488447] R10: 0002 R11: 88040bdc2a80 R12: fff7 [ 173.488448] R13: 88040679c000 R14: 8803efafe800 R15: 000c4000 [ 173.488450] FS: () GS:88041ebc() knlGS: [ 173.488451] CS: 0010 DS: ES: CR0: 80050033 [ 173.488453] CR2: 7f26c9915b00 CR3: 0200a006 CR4: 001606e0 [ 173.488454] Call Trace: [ 173.488468] btrfs_init_reloc_root+0x5b/0xa0 [btrfs] [ 173.488478] record_root_in_trans+0xb7/0xf0 [btrfs] [ 173.488488] btrfs_record_root_in_trans+0x4e/0x60 [btrfs] [ 173.488497] start_transaction+0xa6/0x410 [btrfs] [ 173.488506] __btrfs_prealloc_file_range+0xbb/0x460 [btrfs] [ 173.488516] btrfs_prealloc_file_range+0x10/0x20 [btrfs] [ 173.488527] prealloc_file_extent_cluster+0x113/0x200 [btrfs] [ 173.488537] relocate_file_extent_cluster+0x8d/0x470 [btrfs] [ 173.488546] ? __btrfs_end_transaction+0x1c1/0x2e0 [btrfs] [ 173.488555] relocate_data_extent+0x5f/0xc0 [btrfs] [ 173.488564] relocate_block_group+0x495/0x6f0 [btrfs] [ 173.488573] btrfs_relocate_block_group+0x188/0x230 [btrfs] [ 173.488583] btrfs_relocate_chunk+0x4a/0xf0 [btrfs] [ 173.488592] btrfs_shrink_device+0x1c4/0x4c0 [btrfs] [ 173.488602] __btrfs_balance+0xd4/0xbe0 [btrfs] [ 173.488611] ? insert_balance_item.isra.33+0x9a/0x350 [btrfs] [ 173.488614] ? printk+0x43/0x4b [ 173.488624] ? btrfs_dev_replace_lock.part.6+0x15/0x20 [btrfs] [ 173.488634] ? btrfs_dev_replace_lock+0x85/0x90 [btrfs] [ 173.488643] btrfs_balance+0x2de/0x5c0 [btrfs] [ 173.488651] ? btrfs_balance+0x5c0/0x5c0 [btrfs] [ 173.488659] balance_kthread+0x56/0x80 [btrfs] [ 173.488662] kthread+0x11a/0x130 [ 173.488664] ? kthread_create_on_node+0x40/0x40 [ 173.488667] ret_from_fork+0x35/0x40 [ 173.488669] Code: 48 c7 83 dc 00 00 00 00 00 00 00 48 c7 83 e4 00 00 00 00 00 00 00 c6 83 ec 00 00 00 00 c6 83 ed 00 00 00 00 e9 1b ff ff ff 0f 0b <0f> 0b 0f 0b 0f 0b 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f [ 173.488687] Modules linked in: usblp ccm af_packet ebtable_filter ebtables nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit devlink nfnetlink_cthelper nfnetlink vboxpci(O) vboxnetadp(O) vboxnetflt(O) ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_pkttype xt_tcpudp vboxdrv(O) iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack bnep nf_conntrack libcrc32c ip6table_filter msr ip6_tables x_tables arc4 nls_iso8859_1 nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp iwlmvm kvm_intel btusb mac80211 kvm btrtl snd_hda_intel btbcm irqbypass btintel iwlwifi crc32_pclmul ghash_clmulni_intel snd_hda_codec pcbc bluetooth [ 173.488716] snd_hda_core dell_wmi dell_smbios ecdh_generic snd_hwdep aesni_intel sparse_keymap mei_wdt dcdbas aes_x86_64 crypto_simd glue_helper snd_pcm cryptd cfg80211 rfkill i2c_i801 pcspkr snd_timer lpc_ich wmi e1000e snd mei_me ptp pps_core shpchp mei thermal soundcore button btrfs xor hid_generic usbhid raid6_pq sr_mod cdrom i915 crc32c_intel i2c_algo_bit xhci_pci drm_kms_helper syscopyarea ehci_pci sysfillrect xhci_hcd sysimgblt fb_sys_fops ehci_hcd ahci libahci drm usbcore drm_panel_orientation_quirks video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 173.488750] ---[ end trace c9b049613add55d3 ]--- [ 173.488765] RIP: 0010:create_reloc_root+0x1dc/0x1f0 [btrfs] [ 173.488772] RSP: 0018:c90002237910 EFLAGS: 00010282 [ 173.488779]
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
** Bug watch added: Linux Kernel Bug Tracker #203405 https://bugzilla.kernel.org/show_bug.cgi?id=203405 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=203405 Importance: Unknown Status: 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The
[Kernel-packages] [Bug 1890951] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400189/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but
[Kernel-packages] [Bug 1890951] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400188/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab,
[Kernel-packages] [Bug 1890951] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400186/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but
[Kernel-packages] [Bug 1890951] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400190/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course,
[Kernel-packages] [Bug 1890951] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400183/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but
[Kernel-packages] [Bug 1890951] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400187/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to
[Kernel-packages] [Bug 1890951] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400185/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of
[Kernel-packages] [Bug 1890951] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400191/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of
[Kernel-packages] [Bug 1890951] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, this is a crutch, and when you can't run
[Kernel-packages] [Bug 1890951] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400184/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course,
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Tags added: apport-collected focal ** Description changed: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 - So this is obviously a btrfs bug that got introduced by the newer btrfs - code in the newer kernel, although, booting an older kernel didn't fix - it. Apparently something about the fs is messed up now and no balance - can be run. The only temporary remedy I found was to add the - skip_balance mount option to /etc/fstab, but of course, this is a - crutch, and when you can't run balance, then the fs is bound to run out - of space at some point. + So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is
[Kernel-packages] [Bug 1890951] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1890951 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
Unfortunately, producing the logs apart from the backtrace above isn't really possible. As soon as I reproduce the bug, the FS becomes unwritable, so that no logs can be obtained. That's a catch22 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: New Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only
[Kernel-packages] [Bug 1890951] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1890951 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff
[Kernel-packages] [Bug 1890951] [NEW] btrfs not writable when mounted without "skip_balance"
Public bug reported: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, this is a crutch, and when you can't run balance, then the fs is bound to run out of space at some point. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: New Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
The fix worked for me!!! Although it does not have the full functionality (double finger etc..) it still functions as a simple mouse which is enough for me at the moment! Hoping there will be a full functionality fix soon! Thank you so much for the help Ferenc, much appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hi Ferenc. The device is listed exactly as you say: acpi:ELAN0633:PNP0C50: How do I find the right module? Which modules are there? And how to load it? So gratefull you are helping! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@niko: Just a few tips: - See the output of 'cat /sys/bus/acpi/devices' (with or without the acpi patch) - If there is an item named like ELAN0633:00 then: 'cat /sys/bus/acpi/devices/ELAN0633:00/modalias' - If the output is not empty (contains text like acpi:ELAN0633:PNP0C50) then you are on the right track, the device is available according to the acpi. In this case you have to look for the right module to load. - Perhaps you can try the device as 'SYNA2B61' (cat /sys/bus/acpi/devices/SYNA2B61:00/modalias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)
I found the device with `ls /sys/bus/acpi/devices`, although it does not appear in /proc/bus/input/devices I found in Bug-Report #1853277 that Kai-Heng Feng stated "We are currently working with Lenovo and it might take a while." Is that still undergoing? -- 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/1885573 Title: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) Status in linux package in Ubuntu: Incomplete Bug description: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) 2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is ALPS, Elan or Synatics 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrozwod1597 F pulseaudio /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
No, that didn't work either. Sigh. And the device is still not listed in /proc/bus/input/devices Thanks anyway for your time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@Niko: You can try to commment out these lines too, but I doubt this fix
will work in your case:
//If ((TPTY == One))
//{
_HID = "ELAN0633"
BADR = 0x15
HID2 = One
Return (Zero)
//}
//
//If ((TPTY == 0x02))
//{
//_HID = "SYNA2B61"
//BADR = 0x2C
//HID2 = 0x20
//Return (Zero)
//}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1861610
Title:
'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux-oem-5.6 source package in Eoan:
Invalid
Status in linux-oem-osp1 source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux-oem-osp1 source package in Focal:
Invalid
Bug description:
[SRU Justification]
[Impact]
Touchpad function unavailable on some platforms with new ELAN touchpad
HIDs.
[Fix]
https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/
required to match these currently unsupported IDs.
[Test Case]
1. check if platform is affected, e.g. with ELAN0634:
$ sudo acpidump | grep -C3 ELAN
2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF
2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._
2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2.
2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634..
2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U
2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h.
2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
And the dsl. ** Attachment added: "dsdt.dsl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+attachment/5400116/+files/dsdt.dsl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Here it is (I have a Lenovo S145). ** Attachment added: "dsdt.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+attachment/5400107/+files/dsdt.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@Niko: That looks a different hardware. Could you please upload the full dsdt.dat? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@Frenec:
Ok, I simply commented out my lines:
Method (_STA, 0, NotSerialized) // _STA: Status
{
// If ((TPTY == Zero))
// {
// Return (Zero)
// }
// Else
// {
Return (0x0F)
// }
}
Then I follow your description with the new sed line. Instead of
<< find kernel | cpio -H newc --create > /boot/acpi_fixed.cpio
I had to do
<< find kernel | cpio -H newc --create > ./acpi_fixed.cpio
<< sudo move acpi_fixed.cpio /boot
but that shouldn't change a thing, right?
Unfortunately, didn't work for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1861610
Title:
'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux-oem-5.6 source package in Eoan:
Invalid
Status in linux-oem-osp1 source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux-oem-osp1 source package in Focal:
Invalid
Bug description:
[SRU Justification]
[Impact]
Touchpad function unavailable on some platforms with new ELAN touchpad
HIDs.
[Fix]
https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/
required to match these currently unsupported IDs.
[Test Case]
1. check if platform is affected, e.g. with ELAN0634:
$ sudo acpidump | grep -C3 ELAN
2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF
2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._
2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2.
2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634..
2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U
2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h.
2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
The change which introduced the issue https://code.launchpad.net/~aleks.bogdanov/livecd-rootfs/remove-vagrant- console-log/+merge/355598 -- 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hi Ferenc.
Tried your method. In /tmp/dsdt.dsl I found the HID of the touchpad: 0633 (!)
If ((TPTY == One))
{
_HID = "ELAN0633"
BADR = 0x15
HID2 = One
Return (Zero)
}
But then there is no "TPVD" to be found in the whole file. When
searching for "_STA" I find
Method (_STA, 0, NotSerialized) // _STA: Status
{
If ((TPTY == Zero))
{
Return (Zero)
}
Else
{
Return (0x0F)
}
}
Can you please help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1861610
Title:
'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux-oem-5.6 source package in Eoan:
Invalid
Status in linux-oem-osp1 source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux-oem-osp1 source package in Focal:
Invalid
Bug description:
[SRU Justification]
[Impact]
Touchpad function unavailable on some platforms with new ELAN touchpad
HIDs.
[Fix]
https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/
required to match these currently unsupported IDs.
[Test Case]
1. check if platform is affected, e.g. with ELAN0634:
$ sudo acpidump | grep -C3 ELAN
2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF
2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._
2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2.
2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634..
2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U
2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h.
2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Use this sed line instead: sed -i -E 's/^(\s*initrd\s+)(\S*\/)(.*)$/\1\2acpi_fixed.cpio \2\3/g' /boot/grub/grub.cfg.new -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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
