[Bug 832537] Home partition freezes in kernel?
http://bugzilla.opensuse.org/show_bug.cgi?id=832537
http://bugzilla.opensuse.org/show_bug.cgi?id=832537#c29
Takashi Iwai
I have been running kernel 4.0.4 for a little while now, and I think it's safe to recommend this to other users. I'm actually using openSUSE 13.2 but that option isn't in Bugzilla at the moment.
* could somebody please add 13.2 to Bugzilla?
openSUSE 13.2 appears in bugzilla.opensuse.org, but not in bugzilla.novell.com. I reassigned this bug now.
I think it's safe to include one of the 4.0.x kernels in the main repository as long as the package management system doesn't automatically propose it as an upgrade for everybody. But it would be great if users had the option of manually upgrading to a specific 4.0.x version without having to set up a repo with nightly builds.
The update of Kernel:stable isn't so frequent. But much more often than the normal openSUSE kernel update, yes. Actually Tumbleweed takes Kernel:stable, thus taking the kernel from FACTORY would be a safer option, too...
I think the USB issue is fixed, but I still have other problems. NFS is still a bit painful, although I think it might actually be a bit more solid with the network going up and down. I used to have to manually unmount and remount my shares, and now I think maybe I'm not having to do that as often.
The entire system still freezes while swapping. I think that's because I'm running swap over LVM over LUKS. Maybe swap is causing other disc I/O to stall, since everything runs over LVM/LUKS.
But 4.0.x is definitely a step forward and it seems to be compatible with all the 13.2 user-space tools. You should consider making it the default for 13.3 with the option to manually downgrade.
We're moving to the rolling update, so user gets always the latest and greatest :) Since the latest kernel works, I close the bug as UPSTREAM. If you still have any particular outstanding problem, please create a bug report for each issue. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com