Hijiri 2017-02-01 13:06:25
I'm having an issue with X (I think)
Hijiri 2017-02-01 13:06:51
the desktop manager never starts, and if I open htop Xorg displays as being stuck in disk sleep
Hijiri 2017-02-01 13:07:16
actually the manager shows as having started but the graphical session doesn't display (?)
Hijiri 2017-02-01 13:07:44
If I try to use startx to start a new session from a virtual terminal the display hangs and I have to force reboot
Hijiri 2017-02-01 13:08:17
every so often I get messages that a kworker and Xorg blocked for a really long time
Hijiri 2017-02-01 13:11:02
here is some extended output from dmesg http://lpaste.net/351954
rdz 2017-02-01 13:12:34
hey all. is there way to disable logging for a specific systemd service unit?
aypea[1] 2017-02-01 13:13:13
but... everybody loves log!
Hijiri 2017-02-01 13:14:11
I can do things other than graphical things, for example ssh into the machine and use irc
Hijiri 2017-02-01 13:15:20
oh yeah, lspci also hangs
Hijiri 2017-02-01 13:15:26
If I try to do it
Hijiri 2017-02-01 13:16:04
some problem with virtual filesystem?
aypea[1] 2017-02-01 13:16:33
sounds more like a h/w issue (or a weird driver issue)
Hijiri 2017-02-01 13:16:41
shouldn't lspci still work?
Hijiri 2017-02-01 13:16:47
and not hang forever?
aypea[1] 2017-02-01 13:16:54
not if it can't query your h/w
Hijiri 2017-02-01 13:17:00
a
Hijiri 2017-02-01 13:17:09
how do I figure out what's wrong?
aypea[1] 2017-02-01 13:17:19
how often does this happen?
aypea[1] 2017-02-01 13:17:27
does it happen on an idle box?
Hijiri 2017-02-01 13:17:30
It only happened now
Hijiri 2017-02-01 13:17:35
it happens as soon as I boot
Hijiri 2017-02-01 13:17:42
it didn't happen before now though
aypea[1] 2017-02-01 13:17:51
does it happen if you boot without X?
Hijiri 2017-02-01 13:18:00
how do I boot without X?
Hijiri 2017-02-01 13:18:06
Also this started happening after losing power unsafely
aypea[1] 2017-02-01 13:18:14
ah
aypea[1] 2017-02-01 13:18:32
possible damage from unhappy electrons.
aypea[1] 2017-02-01 13:18:50
try booting into single user mode
Hijiri 2017-02-01 13:19:12
is that just the recovery mode option in grub or do I need to do something else?
aypea[1] 2017-02-01 13:19:20
that'll do
Hijiri 2017-02-01 13:19:49
I'm going to connect from webclient because I'm using the irc client from the problem machine
aypea[1] 2017-02-01 13:20:06
ok
Hijiri-webby 2017-02-01 13:21:21
ok, I've restarted in recovery mode
Hijiri-webby 2017-02-01 13:22:06
but it's still trying to boot with X
Hijiri-webby 2017-02-01 13:22:13
maybe I pressed something wrong when it was booting
aypea[1] 2017-02-01 13:22:37
yeah that doesn't sound right
Hijiri-webby 2017-02-01 13:23:38
is there another way to boot in single user mode
Hijiri-webby 2017-02-01 13:24:00
or I could look it up
aypea[1] 2017-02-01 13:24:05
edit the grub entry in the grub boot menu, find the line for the kernel, add 'single' at the end and boot
jjholt 2017-02-01 13:25:11
is there a way to force a process to use a specific core?
Hijiri-webby 2017-02-01 13:26:40
it says cannot open access to console the root account is locked
abrotman 2017-02-01 13:26:51
jjholt: cpuset ?
aypea[1] 2017-02-01 13:27:24
hijiri: you can't use your root passwd?
Hijiri-webby 2017-02-01 13:27:35
I think I removed the root password, do I need to set one?
aypea[1] 2017-02-01 13:27:48
hijiri: try just hitting enter
Hijiri-webby 2017-02-01 13:28:05
If I hit enter it goes to the normal login prompt
Hijiri-webby 2017-02-01 13:28:16
and then Xorg is already started
Hijiri-webby 2017-02-01 13:28:20
(and stuck)
aypea[1] 2017-02-01 13:28:30
sounds like a root passwd would be of use
Hijiri-webby 2017-02-01 13:28:58
ok
Hijiri-webby 2017-02-01 13:29:03
time for more rebootings
jjholt 2017-02-01 13:30:11
abrotman, thanks
Hijiri-webby 2017-02-01 13:30:18
aypea[1]: alright, I'm in with single user mode
Hijiri-webby 2017-02-01 13:30:28
and no Xorg
Hijiri-webby 2017-02-01 13:30:40
and whoops I froze it by trying to do lspci, I'll reboot again
Hijiri-webby 2017-02-01 13:31:26
alright, I'm back in
aypea[1] 2017-02-01 13:31:49
if you do find /sys does it still freeze?
Hijiri-webby 2017-02-01 13:32:09
nope
aypea[1] 2017-02-01 13:33:39
hmm
aypea[1] 2017-02-01 13:35:02
hijiri: try more /sys/devices/pci*/*/uevent
aypea[1] 2017-02-01 13:35:08
and go through them one by one
Hijiri-webby 2017-02-01 13:37:14
aypea[1]: got through them all without crashing
aypea[1] 2017-02-01 13:37:44
hijiri: ok. in /sus/devices/ is ther eonly one pci* dir?
Hijiri-webby 2017-02-01 13:38:07
yeah, only one
aypea[1] 2017-02-01 13:38:13
hijiri: cd into that
Hijiri-webby 2017-02-01 13:38:18
ok
Hijiri-webby 2017-02-01 13:38:38
I've cd'd into it
aypea[1] 2017-02-01 13:39:10
hijiri: run: for i in [0-9]*; do cat $i/uevent; lspci -s $i; read -p "Continue?"; done
aypea[1] 2017-02-01 13:39:22
hit enter at the continue prompt :)
Hijiri-webby 2017-02-01 13:40:13
just hit enter until something happens (or nothing happens)?
aypea[1] 2017-02-01 13:40:25
either it'll go to the next device or freeze :)
Hijiri-webby 2017-02-01 13:40:36
I didn't freeze
Hijiri-webby 2017-02-01 13:40:39
got through them all
tw 2017-02-01 13:41:05
Regarding my kernel keyring issue, it looks like there's some refcounting in the disk cache that won't let me drop the key as my session ends. If I flush the cache (echo 3 > /proc/sys/vm/drop/caches), my user-logon key frees itself. That kind of makes tying crypto to the process session kind of useless.
aypea[1] 2017-02-01 13:41:53
hijiri: hrm. lemme ponder a bit
abrotman 2017-02-01 13:43:10
!nodm
dpkg 2017-02-01 13:43:11
Debian does not use a specific runlevel for graphical display managers by default. Just remove the DM package(s) with "aptitude remove xdm kdm wdm login.app gdm gdm3 pdm slim". "echo false >/etc/X11/default-display-manager" will also disable the DM, or just hit ctrl-alt-fN to get to a console. nodm is the name of a minimal/automatic display manager (http://www.enricozini.org/sw/nodm/).
Hijiri-webby 2017-02-01 13:43:11
aypea[1]: alright, also thanks for the help so far
