October 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1177577] [Build 20201011] openQA test fails in cifs
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177577 https://bugzilla.suse.com/show_bug.cgi?id=1177577#c7 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Takashi Iwai from comment #6) > (In reply to Fabian Vogt from comment #5) > > (In reply to Takashi Iwai from comment #3) > > > The current way to list up all modules explicitly, and I guess it's hard to > > > process the list at the build time. Maybe this needs two step processes: > > > one to prepare the module list from modinfo of modules included in the > > > target kernel, then repackage from the list. > > > > I made a sr which does this: > > > > %define crypto_modules \ > > %(rpm -ql %{kernel_package_name} | grep -E > > 'kernel/crypto/|kernel/arch/.*/crypto/' | xargs basename -a | cut -d. -f1) > > > > I don't really like that it's fragile (rpm ignores errors), but other than > > that it's definitely better than mentioning everything explicitly IMO. What > > do you think? > > Looks like a good workaround! > > BTW, did you check whether the regex really work as Michal mentioned in > comment 4? Yes, that's already used for some modules like ipt_* and nft_*, but it only works on module names and not directories, so would still result in a long list which needs manual updates. I accepted and forwarded the sr now, so closing as fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177577] [Build 20201011] openQA test fails in cifs
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177577 https://bugzilla.suse.com/show_bug.cgi?id=1177577#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Fabian Vogt from comment #5) > (In reply to Takashi Iwai from comment #3) > > The current way to list up all modules explicitly, and I guess it's hard to > > process the list at the build time. Maybe this needs two step processes: > > one to prepare the module list from modinfo of modules included in the > > target kernel, then repackage from the list. > > I made a sr which does this: > > %define crypto_modules \ > %(rpm -ql %{kernel_package_name} | grep -E > 'kernel/crypto/|kernel/arch/.*/crypto/' | xargs basename -a | cut -d. -f1) > > I don't really like that it's fragile (rpm ignores errors), but other than > that it's definitely better than mentioning everything explicitly IMO. What > do you think? Looks like a good workaround! BTW, did you check whether the regex really work as Michal mentioned in comment 4? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177577] [Build 20201011] openQA test fails in cifs
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177577 https://bugzilla.suse.com/show_bug.cgi?id=1177577#c5 --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Takashi Iwai from comment #3) > The current way to list up all modules explicitly, and I guess it's hard to > process the list at the build time. Maybe this needs two step processes: > one to prepare the module list from modinfo of modules included in the > target kernel, then repackage from the list. I made a sr which does this: %define crypto_modules \ %(rpm -ql %{kernel_package_name} | grep -E 'kernel/crypto/|kernel/arch/.*/crypto/' | xargs basename -a | cut -d. -f1) I don't really like that it's fragile (rpm ignores errors), but other than that it's definitely better than mentioning everything explicitly IMO. What do you think? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177428 https://bugzilla.suse.com/show_bug.cgi?id=1177428#c60 --- Comment #60 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1177428) was mentioned in https://build.opensuse.org/request/show/841342 Factory / kernel-firmware -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177428 http://bugzilla.opensuse.org/show_bug.cgi?id=1177428#c59 --- Comment #59 from Christian Hartmann <chris-hartmann(a)gmx.de> --- (In reply to Takashi Iwai from comment #58) > (In reply to Christian Hartmann from comment #57) > > So, I've just checked going back to the official released version and boot > > fails. > > OK. Did you uninstall kernel-firmware-amdgpu package once? Or only > upgrade/downgrade the package? If it's the latter case, try the following: > > - Uninstall kernel-firmware-amdgpu once > % zypper rm -u kernel-firmware-amdgpu > > - Remove stale files in /lib/firmware/amdgpu, if any > % rm -f /lib/firmware/amdgpu > > - Install the kernel-firmware-amdgpu package again from TW > % zypper in kernel-firmware-amdgpu-20201005 > (pass some option to specify the repo or specify the proper rpm release > number to get the TW package.) > > I guess this would make it working for yours, too. > > In anyway, it seems that the symlink version of fdupes works better, and I'm > going to submit it now. Yes, after uninstalling and deleting the files my system boots normally with the version from the official repo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177428 http://bugzilla.opensuse.org/show_bug.cgi?id=1177428#c58 --- Comment #58 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Christian Hartmann from comment #57) > So, I've just checked going back to the official released version and boot > fails. OK. Did you uninstall kernel-firmware-amdgpu package once? Or only upgrade/downgrade the package? If it's the latter case, try the following: - Uninstall kernel-firmware-amdgpu once % zypper rm -u kernel-firmware-amdgpu - Remove stale files in /lib/firmware/amdgpu, if any % rm -f /lib/firmware/amdgpu - Install the kernel-firmware-amdgpu package again from TW % zypper in kernel-firmware-amdgpu-20201005 (pass some option to specify the repo or specify the proper rpm release number to get the TW package.) I guess this would make it working for yours, too. In anyway, it seems that the symlink version of fdupes works better, and I'm going to submit it now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177428] AMDGPU resume fail
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177428 http://bugzilla.opensuse.org/show_bug.cgi?id=1177428#c57 --- Comment #57 from Christian Hartmann <chris-hartmann(a)gmx.de> --- So, I've just checked going back to the official released version and boot fails. (In reply to Takashi Iwai from comment #51) > I prepared another kernel-firmware packages in OBS home:tiwai:test:fw-fix > repo. It uses fdupes with -s option to make the duped file symlinks instead > of hard-links, as it might work better. > Please test just a simple update of kernel-firmware-amdgpu package from: > > http://download.opensuse.org/repositories/home:/tiwai:/test:/fw-fix/ > openSUSE_Factory/noarch/kernel-firmware-amdgpu-20201005-336.1.noarch.rpm > > It's just to confirm that switching to symlink doesn't break things. Usingt this version I was able to boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177577] [Build 20201011] openQA test fails in cifs
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177577 https://bugzilla.suse.com/show_bug.cgi?id=1177577#c4 --- Comment #4 from Michal Suchanek <msuchanek(a)suse.com> --- you can use regular expression like sha256.* -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177564] Touchpad Bug Ideapad 5
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177564 https://bugzilla.suse.com/show_bug.cgi?id=1177564#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P5 - None --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Also, please don't touch the Priority field on Bugzilla. It's a field to be adjusted only developer's side. The reporter can adjust Severity state instead. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1177541] System freezes under high disk I/O usage
by bugzilla_noreply＠suse.com 12 Oct '20

12 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177541 https://bugzilla.suse.com/show_bug.cgi?id=1177541#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |DUPLICATE --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- OK, let's move on. *** This bug has been marked as a duplicate of bug 1159882 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0