https://bugzilla.suse.com/show_bug.cgi?id=1205149https://bugzilla.suse.com/show_bug.cgi?id=1205149#c39
David Mair <dmair(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmair(a)suse.com,
| |lnussel(a)suse.com
Flags| |needinfo?(lnussel(a)suse.com)
| |,
| |needinfo?(martin.wilck@suse
| |.com)
--- Comment #39 from David Mair <dmair(a)suse.com> ---
@Ludwig, @Martin, should the change have been made conditional upon build_kmp?
By default the change seems to ultimately build require kernel-syms which is
not available for 32-bit products. i586 builds fail for several products as a
result because they are unable to fulfill requirement kernel-syms.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189791https://bugzilla.suse.com/show_bug.cgi?id=1189791#c24
Sarah Kriesch <ada.lovelace(a)gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #24 from Sarah Kriesch <ada.lovelace(a)gmx.de> ---
Thanks for this hint, Berthold.
I close this bugreport then.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207776http://bugzilla.opensuse.org/show_bug.cgi?id=1207776#c1
Stefan Dirsch <sndirsch(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrik.jakobsson(a)suse.com,
| |tiwai(a)suse.com,
| |tzimmermann(a)suse.com
Component|X.Org |Kernel
Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org
QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de
--- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> ---
Hmm. Looks like a kernel (driver) issue to me ... therefore reassigning.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1189791https://bugzilla.suse.com/show_bug.cgi?id=1189791#c23
Berthold Gunreben <azouhr(a)opensuse.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(azouhr(a)opensuse.o |
|rg) |
--- Comment #23 from Berthold Gunreben <azouhr(a)opensuse.org> ---
At the moment, I cannot reproduce this bug, because I don't have the needed
z/VM available. The next steps I will do are an upgrade of z15 -> z16, after
this I will perform an upgrade of the z/VM release.
After that, I can try to reproduce the issue. However, since I also have direct
support from IBM at hand for SLES releases, I can go forward with IBM then. So,
for me, it is ok to close this here. It will take some more months to reproduce
with SLES on the latest z/VM.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1207761
Bug ID: 1207761
Summary: CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot
determine SWAPIN and IO %
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: carlos.e.r(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Suddenly I noticed that "iotop" fails to produce adequate information:
Total DISK READ : 0.00 B/s | Total DISK WRITE : 18.63 K/s
Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 23.29 K/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
653 be/3 root 0.00 B/s 2.33 K/s ?unavailable? [jbd2/nvme0n1p5-]
1287 be/3 root 0.00 B/s 8.15 K/s ?unavailable? [jbd2/sdc5-8]
8764 be/4 cer 0.00 B/s 3.49 K/s ?unavailable? firefox
--sm-client-id 29~dd20a571983d [Cache2 I/O]
9660 be/4 cer 0.00 B/s 4.66 K/s ?unavailable? firefox
--sm-client-id 29~-dd20a571983d [LS Thread]
...
CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
I am not sure what update produced this. I know that it worked with 15.3.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1202566https://bugzilla.suse.com/show_bug.cgi?id=1202566#c11
Tamara Schmitz <tamara.schmitz(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tamara.schmitz(a)suse.com
--- Comment #11 from Tamara Schmitz <tamara.schmitz(a)suse.com> ---
(In reply to ted chang from comment #0)
> echo 0x1e | sudo tee -a /sys/module/drm/parameters/debug
> [sudo] password for root:
> 0x1e
> -> echo disk | sudo tee -a /sys/power/state
> disk
> ~> dmesg > dmesg-hibernation-6.1-with-0x1e-enabled
>
I followed your instructions on TW 20230129 GNOME Wayland, kernel
6.1.8-1-default from the TW main repository.
[ 316.877630] [drm:dc_link_set_backlight_level [amdgpu]] New Backlight level:
5654 (0x1616)
I manually set a screen brightness 316.877630 via the GNOME UI brightness
slider. I then suspended to disk. After waking the device, the brightness level
was successfully restored as soon as my GNOME session reappeared on screen:
[ 339.900786] [drm:dc_link_set_backlight_level [amdgpu]] New Backlight level:
5654 (0x1616)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1202570https://bugzilla.suse.com/show_bug.cgi?id=1202570#c7
--- Comment #7 from Tamara Schmitz <tamara.schmitz(a)suse.com> ---
(In reply to Tamara Schmitz from comment #6)
> I tested suspend on a clean TW Gnome installation on 6.1.8.
>
> I did not notice any issues. The screen came back on, there were no
> rendering issues, the screen brightness was retained. This worked twice in a
> row without reboot.
Oh but which state does SteamOS use? Freeze is still borged, suspend is fine.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1202570https://bugzilla.suse.com/show_bug.cgi?id=1202570#c6
--- Comment #6 from Tamara Schmitz <tamara.schmitz(a)suse.com> ---
I tested suspend on a clean TW Gnome installation on 6.1.8.
I did not notice any issues. The screen came back on, there were no rendering
issues, the screen brightness was retained. This worked twice in a row without
reboot.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1207703https://bugzilla.suse.com/show_bug.cgi?id=1207703#c6
Antonio Feijoo <antonio.feijoo(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
Assignee|dracut-maintainers(a)suse.de |kernel-bugs(a)opensuse.org
--- Comment #6 from Antonio Feijoo <antonio.feijoo(a)suse.com> ---
(In reply to Albert Hensel from comment #5)
> What about the issue that the kernel update makes a failed kernel
> installation the main boot entry in GRUB? Shouldn't the boot loader be
> configured to use the working kernel installation as default?
This is not a dracut issue. A new grub entry should not be created if the
initrd creation triggered by the kernel-default update fails.
> warning: %post(kernel-default-6.1.8-1.1.x86_64) scriptlet failed, exit status 1
Assigning the bug to the kernel team.
--
You are receiving this mail because:
You are the assignee for the bug.