Re: F22 unusable - system freezes on login
On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke mwoehlke.fl...@gmail.com wrote: I recently installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seems to run okay, but when I try to boot the installed OS, it freezes when I try to log in. The machine is effectively unusable as a result. Is it actual frozen? Or you just can't see anything on the display? Can you ssh into it? Kinda hard to enable ssh if the screen is frozen, so a bit of a catch 22 there unless you can blindly login and enable ssh without making a single mistake :-P Try booting with boot parameter nomodeset. Does that change anything? -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On Thu, Jul 2, 2015 at 1:05 PM, Matthew Woehlke mwoehlke.fl...@gmail.com wrote: On 2015-07-02 13:56, Chris Murphy wrote: On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke wrote: I recently installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seems to run okay, but when I try to boot the installed OS, it freezes when I try to log in. The machine is effectively unusable as a result. Is it actual frozen? The login *process chain* is frozen. On a good day (although I don't think this has been the case since the originally-installed kernel) I can switch to a different TTY and futilely try again. Or you just can't see anything on the display? The display is unchanged; I still see the login dialog / prompt / whatever was on screen previously. (Although with updated kernels, TTY switching results in an unrecoverable black screen.) Can you ssh into it? Ah... no? This affects login regardless of the method: graphical, tty, *SSH* [...] (emphasis added) That is, ssh connects, but the login never completes and I never get to a shell. I get Last login: [...], and then nothing; it's stuck at that point. (And if I kill ssh and try again, I can still connect, so indeed, the kernel is still alive.) (In my various attempts to make things better in emergency mode - the only way I've been able to get a usable shell - I was able to enable sshd and coax the network into coming up on boot.) Try booting with boot parameter nomodeset. Does that change anything? Hmm... Yes. Seems to work okay with nomodeset. But why does that break *ssh*? (And where - that is, against what - do I file a bug report?) If nomodeset solves the problem, then the problem is graphics related. You can use: journalctl -b-1 to get information about he previous boot and journalctl -b-2 to get information from the boot before that, etc. Current boot is -b / -b-0 which isn't as helpful because it will contain the successful nomodeset boot. But the previous boot will get written to the journal as long as switchroot happened. Another possibility is that this is just a problem with gdm on Wayland with your hardware and not a more general problem. So to disable gdm on Wayland, to revert to gdm on X, you need to edit: /etc/gdm/custom.conf And uncomment the WaylandEnable=false line. Then reboot (without nomodeset). If that also solves the problem, then it's a gdm on Wayland problem. Once you've figured out in what case the failures do and don't happen, you'll know which component to file the bug against, and what to include in the bug report. Chris Murphy -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-23 21:22, Suvayu Ali wrote: On Tue, Jun 23, 2015 at 10:00:14AM -0400, Matthew Woehlke wrote: On 2015-06-22 14:15, Marko Vojinovic wrote: As a side note, AFAIK now sshd is disabled on fresh installs. Do a systemctl enable sshd and systemctl start sshd (and verify with systemctl status sshd), and retry to log in over the network. I doubt it will work, but it's worth a try. I did figure out the appropriate incantations to get the network to be active on boot (sshd - 'systemctl enable sshd' was comparatively easy). I'm seeing the same behavior with ssh login as with local; it appears to accept the password, but I never get a shell. (If it wasn't a brand spanking new install - and happening for root also - I would suspect something being run via .bashrc...) Did you try with -vvv? That could give you where it gets stuck. ... debug2: shell request accepted on channel 0 Last login: Thu Jul 2 14:52:56 2015 from 192.168.1.183 ...and it's stuck. AFAICT there's nothing wrong with ssh; it's spinning up a login session / shell that doesn't work. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 07/02/2015 12:05 PM, Matthew Woehlke wrote: The display is unchanged; I still see the login dialog / prompt / whatever was on screen previously. (Although with updated kernels, TTY switching results in an unrecoverable black screen.) Have you tried the Magic SysRq key? Even in single-user mode, you should be able to do what's needed to activate it. Check the third post in this thread for details: http://forums.fedoraforum.org/showthread.php?t=304057highlight=magic+sysrq I'd also suggest doing a little experimenting before you reboot, so that you know exactly what combination of keys works. If it works in single-user mode, but not when you need it, there's a good chance that whatever's wrong is hardware, but try booting into a CLI because it just might be a video driver issue. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-07-02 13:56, Chris Murphy wrote: On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke wrote: I recently installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seems to run okay, but when I try to boot the installed OS, it freezes when I try to log in. The machine is effectively unusable as a result. Is it actual frozen? The login *process chain* is frozen. On a good day (although I don't think this has been the case since the originally-installed kernel) I can switch to a different TTY and futilely try again. Or you just can't see anything on the display? The display is unchanged; I still see the login dialog / prompt / whatever was on screen previously. (Although with updated kernels, TTY switching results in an unrecoverable black screen.) Can you ssh into it? Ah... no? This affects login regardless of the method: graphical, tty, *SSH* [...] (emphasis added) That is, ssh connects, but the login never completes and I never get to a shell. I get Last login: [...], and then nothing; it's stuck at that point. (And if I kill ssh and try again, I can still connect, so indeed, the kernel is still alive.) (In my various attempts to make things better in emergency mode - the only way I've been able to get a usable shell - I was able to enable sshd and coax the network into coming up on boot.) Try booting with boot parameter nomodeset. Does that change anything? Hmm... Yes. Seems to work okay with nomodeset. But why does that break *ssh*? (And where - that is, against what - do I file a bug report?) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-22 14:15, Marko Vojinovic wrote:
If the same set of steps don't work and then start working and then
don't work again, I am thinking memory or the harddrive.
Hmm... and... first try (just now) to boot the LiveCD got stuck ('LSB
init' IIRC). Second worked...
Boot from a live image, do a memcheck
How do I do that? (Last I recall this was a tool one had to boot into,
but I don't see an option for that?)
FWIW The Dell OBD extended memory check passed.
and do a fsck on all partitions.
I get an updating bad block inode on every single partition...? But
otherwise nothing, despite doing a thorough non-destructive write scan.
(Is this indicative of a real problem? Or just because I can never do a
clean shutdown?)
Does the machine work reliably under the live image?
See above. Otherwise, seems okay, though I've not done much.
Also, just for completeness, what is your video hardware?
ATI/AMD Saturn XT [FirePro M6100]
Another stab in the dark is CPU temperature --- is the machine maybe
overheating? Does the cpu fan work? Does it sound normal? Are any parts
of the machine unusually hot to touch?
Fan and exterior temp seem okay. HW sensors report the CPU cores around
54°-59° (C), which is slightly lower than my other laptop.
As a side note, AFAIK now sshd is disabled on fresh installs. Do a
systemctl enable sshd and systemctl start sshd (and verify with
systemctl status sshd), and retry to log in over the network. I doubt
it will work, but it's worth a try.
I did figure out the appropriate incantations to get the network to be
active on boot (sshd - 'systemctl enable sshd' was comparatively easy).
I'm seeing the same behavior with ssh login as with local; it appears to
accept the password, but I never get a shell. (If it wasn't a brand
spanking new install - and happening for root also - I would suspect
something being run via .bashrc...)
--
Matthew
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On Tue, Jun 23, 2015 at 10:00:14AM -0400, Matthew Woehlke wrote: On 2015-06-22 14:15, Marko Vojinovic wrote: As a side note, AFAIK now sshd is disabled on fresh installs. Do a systemctl enable sshd and systemctl start sshd (and verify with systemctl status sshd), and retry to log in over the network. I doubt it will work, but it's worth a try. I did figure out the appropriate incantations to get the network to be active on boot (sshd - 'systemctl enable sshd' was comparatively easy). I'm seeing the same behavior with ssh login as with local; it appears to accept the password, but I never get a shell. (If it wasn't a brand spanking new install - and happening for root also - I would suspect something being run via .bashrc...) Did you try with -vvv? That could give you where it gets stuck. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-20 06:38, Tim wrote: Allegedly, on or about 19 June 2015, Matthew Woehlke sent: Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh, *not at all*. No login -- never even tries to start X (not as my user, anyway). (Hrm... on that note, it's interesting to note that the one and only GUI program I was able to try to run is Konsole... I have to ask: If you were unable to login, how were you able to run anything (such as Konsole)? *Once and only once* I was able to get a desktop session, which allowed me to *try*, unsuccessfully, to run Konsole. (IIRC this was on the second attempt; the first had already failed in the manner that I'm now seeing always, and I was intending to run updates.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 20:27, Suvayu Ali wrote: On Fri, Jun 19, 2015 at 05:47:49PM -0400, Matthew Woehlke wrote: On 2015-06-19 17:27, Suvayu Ali wrote: In emergency mode, could you look at what logind was up to in the previous boot? Something like the following should work: # journalctl -b -1 -u systemd-logind You could compare with the current boot by switching the -1 to 0. Maybe this will give you clues. 16:47:38 New session c1 of user sddm. 16:47:56 New session 1 of user matthew. 16:48:24 Power key pressed. 16:48:24 Powering Off... 16:48:24 System is powering down. Nope, nothing interesting. Okay that tells me the login actually worked from the perspective of logind, but something else prevented the next step. [...] you could try booting with enforcing=0 among your kernel arguments and see if you can login. And of course checking permissions is easy from emergency mode. Actually, I tried that already... no joy. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On Mon, 22 Jun 2015 12:16:09 -0400 Matthew Woehlke mwoehlke.fl...@gmail.com wrote: On 2015-06-20 06:38, Tim wrote: Allegedly, on or about 19 June 2015, Matthew Woehlke sent: Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh, *not at all*. No login -- never even tries to start X (not as my user, anyway). (Hrm... on that note, it's interesting to note that the one and only GUI program I was able to try to run is Konsole... I have to ask: If you were unable to login, how were you able to run anything (such as Konsole)? *Once and only once* I was able to get a desktop session, which allowed me to *try*, unsuccessfully, to run Konsole. (IIRC this was on the second attempt; the first had already failed in the manner that I'm now seeing always, and I was intending to run updates.) Hardware failure? Gambling behavior of the machine usually points to faulty hardware. If the same set of steps don't work and then start working and then don't work again, I am thinking memory or the harddrive. Boot from a live image, do a memcheck and do a fsck on all partitions. Does the machine work reliably under the live image? If there are no glitches with the live image, memory is probably ok, and the most likely culprit is the harddrive. Most system files seem to be intact because the system boots, but as soon as you try to login, the system tries to access (either to read or to write) something additional on the disk, and fails too badly to be able to recover. For example, I don't really know if the system can recover from a corrupt /etc/shadow, or something like that. Also, just for completeness, what is your video hardware? I've seen cases of the nouveau driver failing so badly that it locks up the machine in ways you could never expect (like in the middle of a TTY session, etc.). Another stab in the dark is CPU temperature --- is the machine maybe overheating? Does the cpu fan work? Does it sound normal? Are any parts of the machine unusually hot to touch? As a side note, AFAIK now sshd is disabled on fresh installs. Do a systemctl enable sshd and systemctl start sshd (and verify with systemctl status sshd), and retry to log in over the network. I doubt it will work, but it's worth a try. HTH, :-) Marko -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
Allegedly, on or about 19 June 2015, Matthew Woehlke sent: Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh, *not at all*. No login -- never even tries to start X (not as my user, anyway). (Hrm... on that note, it's interesting to note that the one and only GUI program I was able to try to run is Konsole... I have to ask: If you were unable to login, how were you able to run anything (such as Konsole)? -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. ZNQR LBH YBBX! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On Fri, 2015-06-19 at 17:04 -0400, Matthew Woehlke wrote: On 2015-06-19 16:29, Joe Zeff wrote: On 06/19/2015 01:13 PM, Matthew Woehlke wrote: I'm increasingly unconvinced that it has anything whatsoever to do with X. More like it can't start a login session. I'd guess that recovery mode does something that's just a bit different, as that is the*only* way I can get to a usable environment of any kind. Have you tried creating a new user? Yes. *No* user can log in. Not the user I created at install, not a newly created user, ***not root***. The only way I can interact with the system *in any way* is in emergency mode. Forgive me if this has already been asked, but have you run fsck on your filesystem? Some of the things you've mentioned (corrupted /var/log/messages) make me wonder whether something has happened to the filesystem. Jonathan -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On Fri, Jun 19, 2015 at 05:04:40PM -0400, Matthew Woehlke wrote: The only way I can interact with the system *in any way* is in emergency mode. In emergency mode, could you look at what logind was up to in the previous boot? Something like the following should work: # journalctl -b -1 -u systemd-logind You could compare with the current boot by switching the -1 to 0. Maybe this will give you clues. Cheers, -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 15:10, Joe Zeff wrote: On 06/19/2015 11:26 AM, Matthew Woehlke wrote: On 2015-06-18 17:47, Joe Zeff wrote: There should also be a ~/.xsession-errors.old and with luck, it might have something in it. There isn't. (I'd be inclined to suspect that things have only gotten to the point where a .xsession-errors would be created the one time.) Interesting. My guess is that there's a three step process here: delete .xsession-errors.old, move .xsession-errors to .xsession-errors.old, create a new version of .xsession-errors, one right after the other. Probably, but... Having no .old file makes it look like it crashed between steps one and two, which seems improbable. I do wish I knew what that meant! ...my guess is that once and only once has it even gotten to step 1. Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh, *not at all*. No login -- never even tries to start X (not as my user, anyway). I'm increasingly unconvinced that it has anything whatsoever to do with X. More like it can't start a login session. I'd guess that recovery mode does something that's just a bit different, as that is the *only* way I can get to a usable environment of any kind. (Hrm... on that note, it's interesting to note that the one and only GUI program I was able to try to run is Konsole... which tries to start a new pty and shell session immediately, i.e. isn't entirely unlike logging in a second time. I'd *almost* say it's starting the shell that's the trouble, except I'm not sure why that would work in emergency mode but not otherwise.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/19/2015 01:13 PM, Matthew Woehlke wrote: I'm increasingly unconvinced that it has anything whatsoever to do with X. More like it can't start a login session. I'd guess that recovery mode does something that's just a bit different, as that is the*only* way I can get to a usable environment of any kind. Have you tried creating a new user? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 16:29, Joe Zeff wrote: On 06/19/2015 01:13 PM, Matthew Woehlke wrote: I'm increasingly unconvinced that it has anything whatsoever to do with X. More like it can't start a login session. I'd guess that recovery mode does something that's just a bit different, as that is the*only* way I can get to a usable environment of any kind. Have you tried creating a new user? Yes. *No* user can log in. Not the user I created at install, not a newly created user, ***not root***. The only way I can interact with the system *in any way* is in emergency mode. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/19/2015 02:04 PM, Matthew Woehlke wrote: Yes.*No* user can log in. Not the user I created at install, not a newly created user, ***not root***. The only way I can interact with the system*in any way* is in emergency mode. Thank you. I'm sure that you mentioned this at the beginning, but I'd forgotten. Does your system create /var/log/boot.log? (I don't think that it does so by default and don't remember off-hand how to change that.) If so, you might find some hints there. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-19 17:27, Suvayu Ali wrote: In emergency mode, could you look at what logind was up to in the previous boot? Something like the following should work: # journalctl -b -1 -u systemd-logind You could compare with the current boot by switching the -1 to 0. Maybe this will give you clues. 16:47:38 New session c1 of user sddm. 16:47:56 New session 1 of user matthew. 16:48:24 Power key pressed. 16:48:24 Powering Off... 16:48:24 System is powering down. Nope, nothing interesting. Alas, because I can't log in, the only things I can do to debug are hope that log files get left. (Is there a way to start the VTY login handling *without* losing the emergency shell?) (@Joe, boot.log seems to just be the systemd startup output... nothing obvious there...) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/19/2015 02:47 PM, Matthew Woehlke wrote: (@Joe, boot.log seems to just be the systemd startup output... nothing obvious there...) Oh well, it was worth looking. BTW, I don't know if this will work from the emergency shell, but have you tried logging in from there as yourself? Just type login, press Enter and see what it does. I've no idea if it's supposed to work, but You Never Know... -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On Fri, Jun 19, 2015 at 05:47:49PM -0400, Matthew Woehlke wrote: On 2015-06-19 17:27, Suvayu Ali wrote: In emergency mode, could you look at what logind was up to in the previous boot? Something like the following should work: # journalctl -b -1 -u systemd-logind You could compare with the current boot by switching the -1 to 0. Maybe this will give you clues. 16:47:38 New session c1 of user sddm. 16:47:56 New session 1 of user matthew. 16:48:24 Power key pressed. 16:48:24 Powering Off... 16:48:24 System is powering down. Nope, nothing interesting. Okay that tells me the login actually worked from the perspective of logind, but something else prevented the next step. My first guess would be SELinux or maybe some sort of permissions problem in the home directory. Not sure how to check for SELinux issues, some ausearch incantation in emergency mode would be best. But otherwise, you could try booting with enforcing=0 among your kernel arguments and see if you can login. And of course checking permissions is easy from emergency mode. Hope this helps, -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 17:47, Joe Zeff wrote: There should also be a ~/.xsession-errors.old and with luck, it might have something in it. There isn't. (I'd be inclined to suspect that things have only gotten to the point where a .xsession-errors would be created the one time.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/19/2015 11:26 AM, Matthew Woehlke wrote: On 2015-06-18 17:47, Joe Zeff wrote: There should also be a ~/.xsession-errors.old and with luck, it might have something in it. There isn't. (I'd be inclined to suspect that things have only gotten to the point where a .xsession-errors would be created the one time.) Interesting. My guess is that there's a three step process here: delete .xsession-errors.old, move .xsession-errors to .xsession-errors.old, create a new version of .xsession-errors, one right after the other. Having no .old file makes it look like it crashed between steps one and two, which seems improbable. I do wish I knew what that meant! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 17:46, Rick Stevens wrote: Maybe we can catch log entries before it completely dies. Bring the system up in single user mode, then edit /etc/systemd/journald.conf. Find the line: #ForwardToSyslog=no Change it to: ForwardToSyslog=yes and save the file. This should cause journald to forward log entries to the old system logger. Reboot and force the crash. Hopefully, the messages will get logged to /var/log/messages before you lose the log daemon. Haha... that's completely unhelpful as I *have* no /var/log/messages. Not that is in any way useful: Jun 19 14:30:51 gryphon rsyslogd-2027: imjournal: fscanf on state file `/var/lib/rsyslog/imjournal.state' failed [v8.8.0 try http://www.rsyslog.com/e/2027 ] That is THE ENTIRE FILE. (Well, that exact message a few times with various dates, plus a bunch of NUL's.) I'm starting to wonder about the disk(s)... though the OBD's¹ pass, which doesn't give a lot of ammunition to take to Dell's support. Anything else I can run to further diagnose, or better yet, confirm if there is a HW problem? (¹ Not useless-for-this-purpose POST, but the Dell OBD's that take several minutes to run just the basic tests.) Oh, and... apparently some update (or just additional use) made things worse; I can no longer VTY switch *at all* after a normal boot. (I'd be inclined to believe that the SSD went read-only or something, except I *can* apparently install updates - dnf succeeds, grub shows a new kernel - and /var is on the magnetic disk.) The only other message I can access is: snd_hda_intel :01:00.1 CORB reset timeout#2, CORBRP = 65535 Anything else is going into the bitbucket. The above *does* seem to happen right before the system dies, but it seems innocuous? BTW, this is *all without running X* (AFAIK)... the system freezes trying to go from single-user mode to 'systemctl start graphical.target' without ever seeing kdm start. (I do get kdm when booting normally; in that case, it's hitting enter after typing my password when the system freezes.) ...although in that case, freezes means the original TTY is no longer usable, but I can VTY switch (alt-f2) to another, log in, and get the last login... message, but no further. Same deal with ssh; I can get as far as the last login... message but never get a shell. This last time I also arranged to have a 'dmesg -w' running at the time; no output of any kind from that on login attempts. (On a different note, Fedora is also unable to reboot or power off this machine, although that's been par for the course with Dell Precision M's.) -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) -- do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. does # df -h show enough space in root? you might try installing a lightweight DM like LXDE or XFCE4.. if you can get in as single user you might look at journalctl to see what happened when it locks up -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 18.06.2015, Matthew Woehlke wrote: I don't know offhand how to set up serial login Set up the console and output in grub.cfg: serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1 terminal_input serial terminal_output serial Then tell the kernel to use it (grub.cfg, as a kernel parameter): console=tty0 console=ttyUSB0 Now, you just have to connect another PC to the serial port of your machine. Reboot, and fire up minicom or something similar, and you'll get a login screen (and the redirected output). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. does # df -h show enough space in root? / 108G /boot 336M /boot/efi 55M /var 119G /home 881G New system, remember? There's nothing on it but the initial install (modulo updates). I haven't even gotten to installing additional software that I'll eventually want, because the system is unusable ATM. if you can get in as single user you might look at journalctl to see what happened when it locks up Hmm... is it expected that there are no entries *at all* for the last few boots? The only entries I have are for June 5. (And yes, my system date is correct: June 18.) Anyway, I have no idea what I'd be looking for. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 12:54, Matthew Woehlke wrote: I just installed F22 (KDE spin) from scratch on a new Dell M6800. The Live CD seemed to run okay, but when I try to boot the installed OS, it (almost¹) invariably freezes when I try to log in. The machine is effectively unusable as a result. HEY! Turns out I *really can't log in*! I managed to persuade the machine to bring the network up on startup, and *I can't log in remotely either*. Same symptoms; as soon as I try, the machine locks up. KDM remains more or less responsive, but TTY switching, which would otherwise work, results in a permanently black screen. Oh... and /var/log/messages isn't actually just unhelpful, it's *corrupt*... both less and vi show a bunch of '^@' special characters where recent log entries ought to be. I have (many) entries from June 5, then one or two fragments from June 14 and again from today... but literally just a few lines, *nothing* like the hundreds of lines I *should* have from a normal boot-up. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/18/2015 01:52 PM, Matthew Woehlke wrote: Hmm... is it expected that there are no entries*at all* for the last few boots? The only entries I have are for June 5. (And yes, my system date is correct: June 18.) Anyway, I have no idea what I'd be looking for. If memory serves, most of the file system isn't mounted in single-user mode. You can use this to mount everything once you've gotten to a command line: mount -a Once you've done that, you can go to your regular user's home directory: cd /home/$USER and examine the hidden file .xsession-errors to see if X even started, and why it crashed. Just remember, you'll be running as root, so be very, very careful about deleting files. (My preference when I have to do things like this is to rename them instead of deleting them, although it's easy to forget to clean up later. Still, it's better than nuking something that you really, really needed.) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/18/2015 01:52 PM, Matthew Woehlke wrote: On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. Then you definitely have a graphics issue. Bring it up in single user mode and have a look at the /var/log/Xorg.0.log file to see if there's anything that might point to an issue. I had an issue on one machine with nouveau on a specific video card. Using an nVidia binary blob driver overcame that. does # df -h show enough space in root? / 108G /boot 336M /boot/efi 55M /var 119G /home 881G New system, remember? There's nothing on it but the initial install (modulo updates). I haven't even gotten to installing additional software that I'll eventually want, because the system is unusable ATM. if you can get in as single user you might look at journalctl to see what happened when it locks up Hmm... is it expected that there are no entries *at all* for the last few boots? The only entries I have are for June 5. (And yes, my system date is correct: June 18.) Anyway, I have no idea what I'd be looking for. If it croaked before the log entries got flushed to disk, yeah, that's possible. By default, syncs to disk occur every five minutes so if journald or systemd seize up before that period, you have no logs. Yet another stupid idea forced on us by the systemd/journald idiocy. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - We are born naked, wet and hungry. Then things get worse. - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 2015-06-18 17:16, Rick Stevens wrote: On 06/18/2015 01:52 PM, Matthew Woehlke wrote: On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. Then you definitely have a graphics issue. Bring it up in single user mode and have a look at the /var/log/Xorg.0.log file to see if there's anything that might point to an issue. I had an issue on one machine with nouveau on a specific video card. Using an nVidia binary blob driver overcame that. It's an AMD (GPU, not CPU). Anyway, I am allergic to proprietary software :-). Nothing in any of the Xorg.*.log*'s jumps out at me. ~user/.xsession-errors is empty. -- Matthew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/18/2015 02:27 PM, Matthew Woehlke wrote: On 2015-06-18 17:16, Rick Stevens wrote: On 06/18/2015 01:52 PM, Matthew Woehlke wrote: On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. Then you definitely have a graphics issue. Bring it up in single user mode and have a look at the /var/log/Xorg.0.log file to see if there's anything that might point to an issue. I had an issue on one machine with nouveau on a specific video card. Using an nVidia binary blob driver overcame that. It's an AMD (GPU, not CPU). Anyway, I am allergic to proprietary software :-). Nothing in any of the Xorg.*.log*'s jumps out at me. ~user/.xsession-errors is empty. If it makes you feel any better or gives you hope: [root@hamster log]# cat /etc/issue Fedora release 21 (Twenty One) Kernel \r on an \m (\l) [root@hamster log]# uname -r 4.0.4-201.fc21.x86_64 [root@hamster log]# lspci | grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [root@hamster log]# grep ATI Xorg.0.log [64.198] (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), ATI Radeon Mobility X300 (M24) 3152 (PCIE), ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI), ATI Radeon X600 (RV380) 3E50 (PCIE), ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP), ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP), ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP), ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP), ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP), ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650, ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330M/340M/350M (U2) 4337, ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI), ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP), ATI Radeon X800PRO (R420) JI (AGP), ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP), ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP), ATI Radeon Mobility 9800 (M18) JN (AGP), ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP), ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP), ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP), ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP), ATI Radeon Mobility M7 LW (AGP), ATI Mobility FireGL 7800 M7 LX (AGP), ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP), ATI FireGL Mobility 9000 (M9) Ld (AGP), ATI Radeon Mobility 9000 (M9) Lf (AGP), ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI, ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP), ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP), ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP), ATI Radeon Mobility 9600 (M10) NQ (AGP), ATI Radeon Mobility 9600 (M11) NR (AGP), ATI Radeon Mobility 9600 (M10) NS (AGP), ATI FireGL Mobility T2 (M10) NT (AGP), ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI), ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI), ATI Radeon Mobility X300 (M22) 5460 (PCIE), ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE), ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE), ATI Radeon X800PRO (R423) UI (PCIE), ATI Radeon X800LE (R423) UJ (PCIE), ATI Radeon X800SE (R423) UK (PCIE), ATI Radeon X800 XTP
Re: F22 unusable - system freezes on login
On 06/18/2015 02:27 PM, Matthew Woehlke wrote: Nothing in any of the Xorg.*.log*'s jumps out at me. ~user/.xsession-errors is empty. That would probably tell us quite a bit if we knew just when in the session the file gets created. Alas, I don't, but maybe somebody else will. There should also be a ~/.xsession-errors.old and with luck, it might have something in it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 unusable - system freezes on login
On 06/18/2015 02:27 PM, Matthew Woehlke wrote: On 2015-06-18 17:16, Rick Stevens wrote: On 06/18/2015 01:52 PM, Matthew Woehlke wrote: On 2015-06-18 14:04, Paul Cartwright wrote: On 06/18/2015 12:54 PM, Matthew Woehlke wrote: (¹ *Once and only once* I was able to log in, but the system froze as soon as I tried to run an application. Also, I can log in in single-user mode, but this isn't good for much but running dnf and fiddling with enabled services. I *have* applied all updates as of a few hours ago to no effect.) do you have a choice of logins, like KDE/gnome?? maybe you didn't allow enough space for root.. Does TTY count? I'd be quite surprised if changing DE works when I can't log in at a TTY either. It *might* be kdm, though I don't claim to know how to change that. BTW, 'systemctl start graphical.target' from single-user mode also kills the system. Then you definitely have a graphics issue. Bring it up in single user mode and have a look at the /var/log/Xorg.0.log file to see if there's anything that might point to an issue. I had an issue on one machine with nouveau on a specific video card. Using an nVidia binary blob driver overcame that. It's an AMD (GPU, not CPU). Anyway, I am allergic to proprietary software :-). Nothing in any of the Xorg.*.log*'s jumps out at me. ~user/.xsession-errors is empty. Maybe we can catch log entries before it completely dies. Bring the system up in single user mode, then edit /etc/systemd/journald.conf. Find the line: #ForwardToSyslog=no Change it to: ForwardToSyslog=yes and save the file. This should cause journald to forward log entries to the old system logger. Reboot and force the crash. Hopefully, the messages will get logged to /var/log/messages before you lose the log daemon. Reboot again to single user mode and look at /var/log/messages to see if you caught it. Change the line in /etc/systemd/journald.conf back to put things back the way they were. NOTE: I've not tried this myself. Others have told me it works and I'm just passing it along. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - UNIX is actually quite user friendly. The problem is that it's - - just very picky of who its friends are! - -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
