• System hangs at GDM login or a bit later...

    From nimrod@21:1/5 to All on Wed Mar 27 18:50:01 2024
    Hi,

    I'm having this annoying behaviour from GDM (or something related).

    Quite ofter, after the GDM login screen appears, the host freezes
    completely: every input device is unresponsive, no ssh connection from
    another host is possible any more, no CTRL+ALT+CANC/F1-F6 is working.

    But the same happens also while I'm typing the username or the
    password, or after the login screen disappears because the login was successful, or even a bit after the dash has appeared at the bottom of
    the screen.

    Looking at boot.log, the last line before the next boot reads "[ OK ]
    Started gdm.service - GNOME Display Manager".

    Looking at syslog instead, the lines are not always the same, but
    usually there is something like this:

    2024-03-27T17:57:25.479168+01:00 SW-GIULIANO /usr/libexec/gdm-x-
    session[1831]: (II) Initializing extension RECORD 2024-03-27T17:57:25.479455+01:00 SW-GIULIANO /usr/libexec/gdm-x-
    session[1831]: (II) Initializing extension DPMS 2024-03-27T17:57:25.479734+01:00 SW-GIULIANO /usr/libexec/gdm-x-
    session[1831]: (II) Initializing ext2024-03-27T17:58:25.469753+01:00 SW-GIULIANO systemd-modules-load[394]: Inserted module 'lp' 2024-03-27T17:58:25.469853+01:00 SW-GIULIANO kernel: [ 0.000000]
    microcode: microcode updated early to revision 0xf4, date = 2023-02-23

    Please note how the third line suddenly ends with "ext", followed
    immediately by the first line written by the next boot sequence.

    The"gdm-x-session" lines above are just the last of a very long list. I
    can provide other logs if requested.

    Any hint would be veri appreciated.

    Best regards.


    <html><head></head><body><div>Hi,</div><div><br></div><div>I'm having this annoying behaviour from GDM (or something related).</div><div><br></div><div>Quite ofter, after the GDM login screen appears, the host freezes completely: every input device is
    unresponsive, no ssh connection from another host is possible any more, no CTRL+ALT+CANC/F1-F6 is working.</div><div><br></div><div>But the same happens also while I'm typing the username or the password, or after the login screen disappears because the
    login was successful, or even a bit after the dash has appeared at the bottom of the screen.</div><div><br></div><div>Looking at boot.log, the last line before the next boot reads <font face="Courier New, Courier, monospace">"[ OK ] Started gdm.service
    - GNOME Display Manager"</font>.</div><div><br></div><div>Looking at syslog instead, the lines are not always the same, but usually there is something like this:</div><div><br></div><div><font face="Courier New, Courier, monospace">2024-03-27T17:57:25.
    479168+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing extension RECORD</font></div><div><font face="Courier New, Courier, monospace">2024-03-27T17:57:25.479455+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing
    extension DPMS</font></div><div><font face="Courier New, Courier, monospace">2024-03-27T17:57:25.479734+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing <b><u>ext2024</u></b>-03-27T17:58:25.469753+01:00 SW-GIULIANO systemd-modules-
    load[394]: I</font><span style="font-family: &quot;Courier New&quot;, Courier, monospace;">nserted module 'lp'</span></div><div><font face="Courier New, Courier, monospace">2024-03-27T17:58:25.469853+01:00 SW-GIULIANO kernel: [ 0.000000] microcode:
    microcode updated early to revision 0xf4, date = 2023-02-23</font></div><div><br></div><div>Please note how the third line suddenly ends with "ext", followed immediately by the first line written by the next boot sequence.</div><div><br></div><div>The"
    gdm-x-session" lines above are just the last of a very long list. I can provide other logs if requested.</div><div><br></div><div>Any hint would be veri appreciated.</div><div><br></div><div>Best regards.</div><div><br></div><div><span></span></div></
    body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From nimrod@21:1/5 to Jeffrey Walton on Sun Mar 31 23:30:01 2024
    On Wed, 2024-03-27 at 18:32 -0400, Jeffrey Walton wrote:
    On Wed, Mar 27, 2024 at 4:47 PM nimrod <[email protected]> wrote:

    I'm having this annoying behaviour from GDM (or something related).

    Quite ofter, after the GDM login screen appears, the host freezes completely: every input device is unresponsive, no ssh connection
    from another host is possible any more, no CTRL+ALT+CANC/F1-F6 is
    working.

    But the same happens also while I'm typing the username or the
    password, or after the login screen disappears because the login
    was successful, or even a bit after the dash has appeared at the
    bottom of the screen.

    Looking at boot.log, the last line before the next boot reads "[ OK
    ] Started gdm.service - GNOME Display Manager".

    Looking at syslog instead, the lines are not always the same, but
    usually there is something like this:

    2024-03-27T17:57:25.479168+01:00 SW-GIULIANO /usr/libexec/gdm-x- session[1831]: (II) Initializing extension RECORD 2024-03-27T17:57:25.479455+01:00 SW-GIULIANO /usr/libexec/gdm-x- session[1831]: (II) Initializing extension DPMS 2024-03-27T17:57:25.479734+01:00 SW-GIULIANO /usr/libexec/gdm-x- session[1831]: (II) Initializing ext2024-03-
    27T17:58:25.469753+01:00 SW-GIULIANO systemd-modules-load[394]:
    Inserted module 'lp'
    2024-03-27T17:58:25.469853+01:00 SW-GIULIANO kernel: [ 0.000000]
    microcode: microcode updated early to revision 0xf4, date = 2023-
    02-23

    Please note how the third line suddenly ends with "ext", followed immediately by the first line written by the next boot sequence.

    The"gdm-x-session" lines above are just the last of a very long
    list. I can provide other logs if requested.

    Any hint would be veri appreciated.

    Can you boot to a previous kernel? Hold SHIFT when the BiOS hands off
    to Grub to get the Grub menu.

    I went back to 6.1.0-17 kernel a couple of days ago and the system
    didn't freeze so far. It's not enough to say the problem is solved,
    because it is very random, but two days without freezing is encouraging
    indeed.

    I'll let you know how is going, thanks.


    If not, then ... maybe a hardware problem. Start with a memory
    checker. Then move on to disabling the GPU.

    Jeff



    <html><head></head><body><div>On Wed, 2024-03-27 at 18:32 -0400, Jeffrey Walton wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Wed, Mar 27, 2024 at 4:47 PM nimrod &lt;<a href="
    mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>I'm having this annoying behaviour from GDM (or something related).<
    </div><div><br></div><div>Quite ofter, after the GDM login screen appears, the host freezes completely: every input device is unresponsive, no ssh connection from another host is possible any more, no CTRL+ALT+CANC/F1-F6 is working.<br></div><div><br><
    /div><div>But the same happens also while I'm typing the username or the password, or after the login screen disappears because the login was successful, or even a bit after the dash has appeared at the bottom of the screen.<br></div><div><br></div><div>
    Looking at boot.log, the last line before the next boot reads "[ OK ] Started gdm.service - GNOME Display Manager".<br></div><div><br></div><div>Looking at syslog instead, the lines are not always the same, but usually there is something like this:<br></
    <div><br></div><div>2024-03-27T17:57:25.479168+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing extension RECORD<br></div><div>2024-03-27T17:57:25.479455+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing
    extension DPMS<br></div><div>2024-03-27T17:57:25.479734+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing ext2024-03-27T17:58:25.469753+01:00 SW-GIULIANO systemd-modules-load[394]: Inserted module 'lp'<br></div><div>2024-03-27T17:58:
    25.469853+01:00 SW-GIULIANO kernel: [ 0.000000] microcode: microcode updated early to revision 0xf4, date = 2023-02-23<br></div><div><br></div><div>Please note how the third line suddenly ends with "ext", followed immediately by the first line written by
    the next boot sequence.<br></div><div><br></div><div>The"gdm-x-session" lines above are just the last of a very long list. I can provide other logs if requested.<br></div><div><br></div><div>Any hint would be veri appreciated.<br></div></blockquote><div><
    </div><div>Can you boot to a previous kernel? Hold SHIFT when the BiOS hands off<br></div><div>to Grub to get the Grub menu.<br></div></blockquote><div><br></div><div>I went back to 6.1.0-17 kernel a couple of days ago and the system didn't freeze so
    far. It's not enough to say the problem is solved, because it is very random, but two days without freezing is encouraging indeed.</div><div><br></div><div>I'll let you know how is going, thanks.</div><div><br></div><blockquote type="cite" style="margin:
    0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>If not, then ... maybe a hardware problem. Start with a memory<br></div><div>checker. Then move on to disabling the GPU.<br></div><div><br></div><div>Jeff<br></div><div><br></
    </blockquote><div><br></div><div><span></span></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From nimrod@21:1/5 to All on Sun Apr 7 18:30:01 2024
    Well,

    I've been trying a couple of kernels, 6.1.0-17/11, and with both the
    system freezes sometime in the way explained below. I did a RAM test
    which was passed successfully, but I guess I should also make a GPU RAM
    test, something I really don't know how to do. For the usual RAM I used MEMTEST86+ as a live ISO.

    Now I'm trying kernel subsubsub version 16 since a couple of days ago
    and the system has not frozen yet. But I'm not very optimistic.

    Anyway, how can I test GPU memory?

    Best regards.

    Il giorno dom, 31/03/2024 alle 23.20 +0200, nimrod ha scritto:
    On Wed, 2024-03-27 at 18:32 -0400, Jeffrey Walton wrote:
    On Wed, Mar 27, 2024 at 4:47 PM nimrod <[email protected]> wrote:

    I'm having this annoying behaviour from GDM (or something
    related).

    Quite ofter, after the GDM login screen appears, the host freezes completely: every input device is unresponsive, no ssh connection
    from another host is possible any more, no CTRL+ALT+CANC/F1-F6 is working.

    But the same happens also while I'm typing the username or the
    password, or after the login screen disappears because the login
    was successful, or even a bit after the dash has appeared at the
    bottom of the screen.

    Looking at boot.log, the last line before the next boot reads "[
    OK ] Started gdm.service - GNOME Display Manager".

    Looking at syslog instead, the lines are not always the same, but
    usually there is something like this:

    2024-03-27T17:57:25.479168+01:00 SW-GIULIANO /usr/libexec/gdm-x- session[1831]: (II) Initializing extension RECORD 2024-03-27T17:57:25.479455+01:00 SW-GIULIANO /usr/libexec/gdm-x- session[1831]: (II) Initializing extension DPMS 2024-03-27T17:57:25.479734+01:00 SW-GIULIANO /usr/libexec/gdm-x- session[1831]: (II) Initializing ext2024-03-
    27T17:58:25.469753+01:00 SW-GIULIANO systemd-modules-load[394]:
    Inserted module 'lp'
    2024-03-27T17:58:25.469853+01:00 SW-GIULIANO kernel: [ 0.000000] microcode: microcode updated early to revision 0xf4, date = 2023-
    02-23

    Please note how the third line suddenly ends with "ext", followed immediately by the first line written by the next boot sequence.

    The"gdm-x-session" lines above are just the last of a very long
    list. I can provide other logs if requested.

    Any hint would be veri appreciated.

    Can you boot to a previous kernel? Hold SHIFT when the BiOS hands
    off
    to Grub to get the Grub menu.

    I went back to 6.1.0-17 kernel a couple of days ago and the system
    didn't freeze so far. It's not enough to say the problem is solved,
    because it is very random, but two days without freezing is
    encouraging indeed.

    I'll let you know how is going, thanks.


    If not, then ... maybe a hardware problem. Start with a memory
    checker. Then move on to disabling the GPU.

    Jeff




    <html><head></head><body><div>Well,</div><div><br></div><div>I've been trying a couple of kernels, 6.1.0-17/11, and with both the system freezes sometime in the way explained below. I did a RAM test which was passed successfully, but I guess I should
    also make a GPU RAM test, something I really don't know how to do. For the usual RAM I used MEMTEST86+ as a live ISO.</div><div><br></div><div>Now I'm trying kernel subsubsub version 16 since a couple of days ago and the system has not frozen yet. But I'
    m not very optimistic.</div><div><br></div><div>Anyway, how can I test GPU memory?</div><div><br></div><div>Best regards.</div><div><br></div><div>Il giorno dom, 31/03/2024 alle 23.20 +0200, nimrod ha scritto:</div><blockquote type="cite" style="margin:0
    0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Wed, 2024-03-27 at 18:32 -0400, Jeffrey Walton wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Wed, Mar 27, 2024 at 4:
    47 PM nimrod &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>I'm having this annoying behaviour from
    GDM (or something related).<br></div><div><br></div><div>Quite ofter, after the GDM login screen appears, the host freezes completely: every input device is unresponsive, no ssh connection from another host is possible any more, no CTRL+ALT+CANC/F1-F6 is
    working.<br></div><div><br></div><div>But the same happens also while I'm typing the username or the password, or after the login screen disappears because the login was successful, or even a bit after the dash has appeared at the bottom of the screen.<
    </div><div><br></div><div>Looking at boot.log, the last line before the next boot reads "[ OK ] Started gdm.service - GNOME Display Manager".<br></div><div><br></div><div>Looking at syslog instead, the lines are not always the same, but usually there
    is something like this:<br></div><div><br></div><div>2024-03-27T17:57:25.479168+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing extension RECORD<br></div><div>2024-03-27T17:57:25.479455+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[
    1831]: (II) Initializing extension DPMS<br></div><div>2024-03-27T17:57:25.479734+01:00 SW-GIULIANO /usr/libexec/gdm-x-session[1831]: (II) Initializing ext2024-03-27T17:58:25.469753+01:00 SW-GIULIANO systemd-modules-load[394]: Inserted module 'lp'<br></
    <div>2024-03-27T17:58:25.469853+01:00 SW-GIULIANO kernel: [ 0.000000] microcode: microcode updated early to revision 0xf4, date = 2023-02-23<br></div><div><br></div><div>Please note how the third line suddenly ends with "ext", followed immediately by
    the first line written by the next boot sequence.<br></div><div><br></div><div>The"gdm-x-session" lines above are just the last of a very long list. I can provide other logs if requested.<br></div><div><br></div><div>Any hint would be veri appreciated.<
    </div></blockquote><div><br></div><div>Can you boot to a previous kernel? Hold SHIFT when the BiOS hands off<br></div><div>to Grub to get the Grub menu.<br></div></blockquote><div><br></div><div>I went back to 6.1.0-17 kernel a couple of days ago and
    the system didn't freeze so far. It's not enough to say the problem is solved, because it is very random, but two days without freezing is encouraging indeed.</div><div><br></div><div>I'll let you know how is going, thanks.</div><div><br></div><
    blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>If not, then ... maybe a hardware problem. Start with a memory<br></div><div>checker. Then move on to disabling the GPU.<br></div><div><
    </div><div>Jeff<br></div><div><br></div></blockquote><div><br></div><div><span></span></div></blockquote><div><br></div><div><span></span></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)