You are not logged in.
Pages: 1
Using stable
I boot up into a login terminal, do login and are at a bash prompt
I then open a second terminal with ctrl+alt+f2, and login there as well
when I later type exit in this second terminal to logout of the second
session, the system hangs: screens dead, keyboard dead, .. this happens consistently.
if I do not login to the second terminal all is ok and I can toggle back-and-forth between the terminals
Same happens when X is up (openbox)
Any ideas?
Last edited by Krymy (2019-07-12 19:40:42)
Offline
It's necessary to know what is your videocard and which videodriver you use.
Offline
lspci gives:
VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
Offline
Try to give some more info, maybe what is in Xorg.log? /var/log/Xorg.log
try
pkill -U <your username>
in second terminal. Does it still hang ?
Last edited by Panopticon (2019-07-11 14:40:59)
Offline
X is not involved
I boot to CLI and this is where the issue occurs consistently
scratch 'terminal' - the problem exists with pure CLI, no X
Offline
Ok so what about log messages?
dmesg --level=err,warn
Offline
(@PanOpticon - thx for helping)
output for dmesg:
[ 0.007987] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.007988] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.355058] pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping due to MTRR override.
[ 0.439533] pci 0000:00:02.0: BIOS left Intel GPU interrupts enabled; disabling
[ 8.865383] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.SBRG.GPBX) (20160831/utaddress-247)
[ 8.865388] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.SBRG.GPBX) (20160831/utaddress-247)
[ 8.865391] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.SBRG.GPBX) (20160831/utaddress-247)
[ 8.865394] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 9.947662] usb 6-1.7: firmware: failed to load ath3k-1.fw (-2)
[ 9.947711] usb 6-1.7: Direct firmware load for ath3k-1.fw failed with error -2
[ 9.947713] Bluetooth: Firmware file "ath3k-1.fw" not found
[ 9.947760] ath3k: probe of 6-1.7:1.0 failed with error -2
Offline
Ok so nothing stands out there.
From some investigation i found this.
https://bugs.freedesktop.org/show_bug.cgi?id=93164
Comment 9.
Created attachment 121092 [details]
xorg.log with crash backtrace -- intel hardwareHi, coming to this bug from https://bugs.debian.org/cgi-bin/bugrepo … bug=805605
In reproducing this bug, there seems to be a time-based component to getting X into a 'frozen' state. If there is a delay between step 4's chvt's, then all is fine after the second switch:
...
4. chvt 1; sleep 1; chvt 2In my case, Laurent's procedure above is modified to (less gdm):
1. startx on tty1
2. switch to tty2
3. login
4. chvt 1; chvt2Furthermore, when following the above to get into a 'frozen' X state (less `sleep 1`), it is not enough to produce an Xorg.log crash backtrace in my case. Instead, the crash does not happen until I 'switch' to the vt on which the frozen X is living. vt1 in the above example. Only then is a backtrace logged to the Xorg.log which should be attached. *note: this is using intel hardware.
try logging in on tty2 and 3 only and see if you get the same outcome ofa locked up console when trying to exit. Make sure tty1 and or 7 is logged out.
Last edited by Panopticon (2019-07-11 16:37:34)
Offline
logged out tty1
logged in tty2
logged in tty3
toggled between all three, doing ls on 2 & 3
logged out of 3
toggled to 2, ls etc all ok
logged in tty1
toggled tty2 & logged out
(wrong: toggled to 1 and hanged - hasty typing, sorry)
did same again but with startx (openbox) on tty1 and when exit on tty2 - hanged when switch back to 1
Last edited by Krymy (2019-07-11 17:27:58)
Offline
Did you need to do hard resets when the system hangs (press power button to shutdown).
Or can you freely ctrl-alt to another tty like 5 or 6 ?
Offline
hard reset
when the system hangs the keyboard is dead - even caps-lock & num-lock leds does not come on and monitors also shuts down as if power-off
so I have to use the power button in order to reboot
(currently I try to remember not to 'exit' an extra tty, but every now & then I forget and lose whatever wasn't saved on tty1)
Offline
On a hasty reading it looks to me like the getty doesn't respawn, which suggests a shell termination problem.
You might want to test this theory by inspecting the process list before and after exiting. E.g.:
login at tty1
type ps axww| grep getty
shift to tty2, login and then type exit
shift back to tty1 and type ps axww | grep getty again (or use up-arrow)
If the second getty list does include tty2, then it's not a respawn problem.
Otherwise the problem is likely that the shell doesn't complete it's termination, perhaps due waiting for an unavailable resource.
Offline
@ralph, would it be worth looking to see what is inside each of .bashrc .profile .bash_logout
Offline
Yes, if it's a case of the shell not terminating, then one of those might hold the cause.
There are also other problem cases where the shell indeed terminates, but getty still doesn't get duly respawned. It really depends on the particular set up of this system; i.e., what the OP means with "using stable".
Perhaps a telinit q command in tty1 (in my test sequence), will trigger a respawn. That would be an indication of some different problem, relating to init and its various configurations, and possibly including the hotplug handling s/w.
Offline
^ Good insight, thanks ralph. Might be a good idea to look in /etc/apt/sources.list as well. From experience reading on how some regularly break Debian i wouldn't be surprised if some abnormal "stable" conditions are present.
Offline
Can you log on to it from another system (eg via ssh)? If you can then try to use that session to gather data about what tasks are running before and after a hang. And try sudo shutdown -r now as a gentler way to reboot it than the power switch.
Chris
Offline
will return to this when I have free time
for now I just do not exit any second tty's & I make a point of saving stuff before I do ctrl+alt+fn ...
it's a pain and I will get back to this ...
Offline
Pages: 1