Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
screen stops working with 4.19.37 kernel
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Philippe23
Tux's lil' helper
Tux's lil' helper


Joined: 20 Dec 2006
Posts: 118
Location: Rome, NY

PostPosted: Wed May 08, 2019 1:18 pm    Post subject: screen stops working with 4.19.37 kernel Reply with quote

I upgraded and rebooted into sys-kernel/gentoo-sources-4.19.37 yesterday and when the machine came up, app-misc/screen-4.6.1 would only run as root. Non-root users would just have screen immediately exit without any error message.

Booting into my previous sys-kernel/gentoo-sources-4.19.27-r1 and screen works again.

Diff between the two kernel's configs is pretty minor:

Code:

--- linux-4.19.27-gentoo-r1/.config     2019-03-09 16:36:56.835872778 -0500
+++ linux-4.19.37-gentoo/.config        2019-05-06 10:59:40.760973081 -0400
@@ -1,5 +1,5 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/x86 4.19.27-gentoo-r1 Kernel Configuration
+# Linux/x86 4.19.37-gentoo Kernel Configuration
 #

@@ -3202,4 +3202,5 @@
 # CONFIG_N_GSM is not set
 # CONFIG_TRACE_SINK is not set
+CONFIG_LDISC_AUTOLOAD=y
 CONFIG_DEVMEM=y
 # CONFIG_DEVKMEM is not set
@@ -3271,5 +3272,4 @@
 # CONFIG_HW_RANDOM_VIRTIO is not set
 CONFIG_NVRAM=m
-# CONFIG_R3964 is not set
 # CONFIG_APPLICOM is not set

@@ -5293,4 +5293,5 @@
 # CONFIG_INTEL_TURBO_MAX_3 is not set
 # CONFIG_I2C_MULTI_INSTANTIATE is not set
+# CONFIG_INTEL_ATOMISP2_PM is not set
 CONFIG_PMC_ATOM=y
 # CONFIG_CHROME_PLATFORMS is not set


Any suggestions on what to check or what may have changed between these two kernels?

Thanks in advance.
Back to top
View user's profile Send private message
Anon-E-moose
Advocate
Advocate


Joined: 23 May 2008
Posts: 3968
Location: Dallas area

PostPosted: Wed May 08, 2019 1:38 pm    Post subject: Reply with quote

On 4.19.37 as a user execute screen from the command line, when it exits do "echo $?" what is the return code?
_________________
Asus m5a99fx, FX 8320 - nouveau, oss4, rx550 for qemu passthrough
Acer laptop E5-575, i3-7100u - i965, alsa
---both---
5.0.13 zen kernel, profile 17.0 (no-pie) amd64-no-multilib
gcc 8.2.0, eudev, openrc, openbox, palemoon
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13867

PostPosted: Thu May 09, 2019 1:33 am    Post subject: Reply with quote

Does strace show anything interesting? Can you bisect to determine which kernel patch caused this?
Back to top
View user's profile Send private message
russK
l33t
l33t


Joined: 27 Jun 2006
Posts: 630

PostPosted: Thu May 09, 2019 1:49 am    Post subject: Reply with quote

FWIW,

I updated to 4.19.37 and my screen works fine.
Did you remember to 'make modules' and 'make modules_install'?

Regards
Back to top
View user's profile Send private message
Philippe23
Tux's lil' helper
Tux's lil' helper


Joined: 20 Dec 2006
Posts: 118
Location: Rome, NY

PostPosted: Thu May 09, 2019 5:32 pm    Post subject: Appologies Reply with quote

I didn't want to take the original instance down, so I snapshot'ed it and launched a clone.

I booted the clone, screen ran fine on 4.19.27-r1. Booted into the 4.19.37 kernel on the clone, and ... screen runs fine. :-|

I'm thoroughly confused. I did re-install screen before I made the image just to make sure that the permissions on /tmp/screen were correct. Not sure if that fixed it (pretty sure the permissions were unchanged). Or if a second boot fixed it?

I'll try to boot the original instance back into 4.19.37 tomorrow just to make sure and report back, but right now it's looking like I'm just crazy.

Footnote: screen doesn't like to be run via strace. "strace -o strace.log screen" complains about the permissions on /tmp/screen (which is why I did the reinstall).

Thanks all. Your help is appreciated.
Back to top
View user's profile Send private message
Philippe23
Tux's lil' helper
Tux's lil' helper


Joined: 20 Dec 2006
Posts: 118
Location: Rome, NY

PostPosted: Thu May 09, 2019 7:26 pm    Post subject: Reply with quote

Just had a chance to reboot the original instance. Screen works. So this is all a false alarm. Not sure what happened the first time.

Thanks again for the help & debugging suggestions though.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum