http://bugzilla.opensuse.org/show_bug.cgi?id=1043103
http://bugzilla.opensuse.org/show_bug.cgi?id=1043103#c2
--- Comment #2 from Heinz Kohl ---
In the meantime for some updates I checked it, but there was no change.
But the actual state is:
resume=/dev/disk/by-uuid/105646d5-63ca-4ea5-84b0-e26f7437693d splash=silent
quiet showopts resume=/dev/sda2 splash=silent quiet showopts resume=/dev/sda2
splash=silent quiet showopts
I had reduced to:
resume=/dev/disk/by-uuid/105646d5-63ca-4ea5-84b0-e26f7437693d splash=silent
quiet showopts resume=/dev/sda2 splash=silent quiet showopts
That's only one additional entry.
So in the moment it is a very sporadic growing.
In the meantime I updated the system every day, using only automatic update
procedure and Yast2.
Usually while normal system operation, but for updates which are tangling the
boot procedure (e.g. new kernels) it was still necessary to use DVD update.
E.g. the last automatic update, which included change from kernel 4.11.4.1 to
4.11.5-1.g8ffa6bb-vanilla was not finishing. I tried also a normal yast2 update
(also a hanger).
Thinking back, I'm remembering only one singulary situation:
update to a new kernel during normal system operation.
This wasn't completely finishing, the boot entries were incomplete (yast2
looping endlessly while trying to finish the boot entries; after restart there
was no boot entry for my second linux system).
I'll try to find out more
--
You are receiving this mail because:
You are on the CC list for the bug.