Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #204714 > unrolled thread

system stops

Back to article view | Back to linux.debian.user

Contents

  system stops BELAHCENE Abdelkader <abdelkader.belahcene@enst.dz> - 2019-01-27 21:30 +0100
    Re: system stops Jens Holzhäuser <Jens.Holzhaeuser@gmx.net> - 2019-01-28 00:40 +0100
      Re: system stops Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-01-28 02:20 +0100
        Re: system stops Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-01-28 02:30 +0100
          Re: system stops David Wright <deblis@lionunicorn.co.uk> - 2019-01-28 03:20 +0100
    Re: system stops David Christensen <dpchrist@holgerdanske.com> - 2019-01-28 02:00 +0100
      Re: system stops Paul Sutton <zleap@disroot.org> - 2019-01-28 10:20 +0100
        Re: system stops David Christensen <dpchrist@holgerdanske.com> - 2019-01-28 19:30 +0100
          Re: system stops John Darrah <xyllyx@gmail.com> - 2019-01-28 19:50 +0100
            Re: system stops rhkramer@gmail.com - 2019-01-28 20:10 +0100
              Re: system stops John Darrah <xyllyx@gmail.com> - 2019-01-28 20:50 +0100
                Re: system stops rhkramer@gmail.com - 2019-01-28 21:50 +0100
                  Re: system stops Tixy <tixy@yxit.co.uk> - 2019-01-29 07:40 +0100
              Re: system stops <tomas@tuxteam.de> - 2019-01-29 10:00 +0100
                Re: system stops rhkramer@gmail.com - 2019-01-29 14:20 +0100
            Re: system stops David Christensen <dpchrist@holgerdanske.com> - 2019-01-29 02:20 +0100
        Re: system stops John Crawley <john@bunsenlabs.org> - 2019-01-29 02:50 +0100

#204714 — system stops

[Multipart message — attachments visible in raw view] — view raw

HI,
uname -a  gives
Linux mx 4.19.0-1-amd64 #1 SMP Debian 4.19.5-2~mx17+1 (2018-12-12) x86_64
GNU/Linux
Sometimes (maybe often) when I leave the system for a times without
touching it, when I come back, the system is frozen , juste the pointer of
mouse can move, but nothing else,  keyboard doesn't respond,  even
ctrl+alt+F1 , or F2,  ...
So the only  thing todo is stop button.
Here is some lines from messages (last line before the shutdown), hope that
someone can help me by reading this  log before the stopping system ( at
20:29).

Jan 27 20:29:52 mx kernel: [11479.565256] Bluetooth: hci0: BCM: Patch
brcm/BCM20702A1-0489-e032.hcd
not found
Jan 27 20:29:52 mx kernel: [11479.565248] bluetooth hci0: Direct firmware
load for brcm/BCM20702A1-0
489-e032.hcd failed with error -2
Jan 27 20:29:52 mx kernel: [11478.719457] ata1.00: configured for UDMA/133
Jan 27 20:29:52 mx kernel: [11478.513494] ata1: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Jan 27 20:29:52 mx kernel: [11477.409506] PM: suspend exit
Jan 27 20:29:52 mx kernel: [11477.374637] Bluetooth: hci0: BCM20702A1
(001.002.014) build 0000
Jan 27 20:29:52 mx kernel: [11477.373634] Bluetooth: hci0: BCM20702A
Jan 27 20:29:52 mx kernel: [11477.356632] Bluetooth: hci0: BCM: features
0x07
Jan 27 20:29:52 mx kernel: [11477.355640] Bluetooth: hci0: BCM: chip id 63
Jan 27 20:29:52 mx kernel: [11477.245215] Restarting tasks ... done.
Jan 27 20:29:52 mx kernel: [11477.245213] OOM killer enabled.
Jan 27 20:29:52 mx kernel: [11477.164547] usb 1-1.4: reset high-speed USB
device number 5 using ehci
-pci
Jan 27 20:29:52 mx kernel: [11477.106796] ata3.00: configured for UDMA/100
Jan 27 20:29:52 mx kernel: [11477.105193] ata3: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
Jan 27 20:29:52 mx kernel: [11477.022519] usb 1-1.3: reset full-speed USB
device number 4 using ehci
-pci
Jan 27 20:29:52 mx kernel: [11477.018509] usb 4-1.6: reset high-speed USB
device number 3 using ehci
-pci
Jan 27 20:29:52 mx kernel: [11476.837625] ACPI: button: The lid device is
not compliant to SW_LID.
Jan 27 20:29:52 mx kernel: [11476.619289] sd 0:0:0:0: [sda] Starting disk
Jan 27 20:29:52 mx kernel: [11476.608519] ACPI: EC: event unblocked
Jan 27 20:29:52 mx kernel: [11476.594662] ACPI: EC: interrupt unblocked
Jan 27 20:29:52 mx kernel: [11476.091515] ACPI: Waking up from system sleep
state S3
Jan 27 20:29:52 mx kernel: [11476.088916] CPU1 is up
Jan 27 20:29:52 mx kernel: [11476.088582]  cache: parent cpu1 should not be
sleeping
Jan 27 20:29:52 mx kernel: [11476.083485] smpboot: Booting Node 0 Processor
1 APIC 0x2
Jan 27 20:29:52 mx kernel: [11476.083484] x86: Booting SMP configuration:
Jan 27 20:29:52 mx kernel: [11476.083445] Enabling non-boot CPUs ...
Jan 27 20:29:52 mx kernel: [11476.082238] PM: Restoring platform NVS memory
Jan 27 20:29:52 mx kernel: [11476.082238] ACPI: EC: EC started
Jan 27 20:29:52 mx kernel: [11476.082190] ACPI: Low-level resume complete

Sorry if the list is long.
Thanks a lot
regards

[toc] | [next] | [standalone]

#204723

On Sun, Jan 27, 2019 at 09:11:33PM +0100, BELAHCENE Abdelkader wrote:
> Sometimes (maybe often) when I leave the system for a times without
> touching it, when I come back, the system is frozen , juste the pointer of
> mouse can move, but nothing else,  keyboard doesn't respond,  even
> ctrl+alt+F1 , or F2,  ...


> Jan 27 20:29:52 mx kernel: [11477.409506] PM: suspend exit
[...]
> Jan 27 20:29:52 mx kernel: [11476.619289] sd 0:0:0:0: [sda] Starting disk
[...]
> Jan 27 20:29:52 mx kernel: [11476.091515] ACPI: Waking up from system sleep state S3
[...]
> Jan 27 20:29:52 mx kernel: [11476.082190] ACPI: Low-level resume complete

Looks like your system is waking up from being suspended/hibernated.

Try disabling suspension/hibernation and see if that prevents the issue.
Something with the power management and system resume might not be
working correctly.

I am not very familiar with Linux hibernation, so there's not much more
I can help with here.

	Jens

[toc] | [prev] | [next] | [standalone]

#204730

On 1/27/19, Jens Holzhäuser <Jens.Holzhaeuser@gmx.net> wrote:
> On Sun, Jan 27, 2019 at 09:11:33PM +0100, BELAHCENE Abdelkader wrote:
>> Sometimes (maybe often) when I leave the system for a times without
>> touching it, when I come back, the system is frozen , juste the pointer
>> of
>> mouse can move, but nothing else,  keyboard doesn't respond,  even
>> ctrl+alt+F1 , or F2,  ...
>
>
>> Jan 27 20:29:52 mx kernel: [11477.409506] PM: suspend exit
> [...]
>> Jan 27 20:29:52 mx kernel: [11476.619289] sd 0:0:0:0: [sda] Starting disk
> [...]
>> Jan 27 20:29:52 mx kernel: [11476.091515] ACPI: Waking up from system
>> sleep state S3
> [...]
>> Jan 27 20:29:52 mx kernel: [11476.082190] ACPI: Low-level resume complete
>
> Looks like your system is waking up from being suspended/hibernated.
>
> Try disabling suspension/hibernation and see if that prevents the issue.
> Something with the power management and system resume might not be
> working correctly.


That's what I was thinking, too. Then, if it looks like all of that is
set for it to just sit there instead of shutting down, it's ok to say,
nope, it's still doing it....

Because mine does, too. I'll go off and do a few chores then come back
to it. It's obvious that it has still gone into some level of
bystanding mode in spite of my own settings. It takes its absolute
sweet time coming back out of it, too.

I had to change mine to not go into sleep/hibernation at all because
it just would not recover too frequently. Hitting that power button
was repeatedly the only way to recover in my case, too.

AND THAT... just reminded me that there was a thread where someone
here said something I'd never remembered hearing before... There's a
spot related to I THINK initramfs or something LIKE that
(initrd.img??) where we can accidentally be carrying over a wrong UUID
(or possibly PARTUUID, LABEL, etc) declaration.

That would, for example, happen if we copied over a live session from
one partition to another. It's well known that we immediately need to
change declarations in /etc/fstab to represent the new partition. This
other, though, just might answer some questions like this that have
otherwise long gone unsolved in the past..

OR NOT. *grin*

As an aside, can we address that by simply updating initramfs via that
command that was just provided in that one thread a couple days ago?

Maybe that's something we're supposed to be doing after copying over
to a new partition, and some of us just hadn't seen that memo yet? Or
would that not help because we still need to manually change that
particular "declaration" first before we update... if it's even about
update-initramfs in the first place? :)

One other thing I've noticed lately is about things like shutting
programs down to bring them back up and having it just sit there for
the longest time before things finally happen. I started watching
"free -m" during those times IF there was enough memory available to
even run that command, GRIN.

Time and again I've sat here and watched it SLOWLY pull things out of
swap and put it back I PRESUME into "ram"... and THEN it FINALLY shuts
the program on down. :)

While what I just wrote is about shutting programs down, I've imagined
it playing some potentially similar part in spending the same amount
of time watching it come back up from a hibernation it was never
expected to take in the first place. :D

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#204731

On 1/27/19, Cindy-Sue Causey <butterflybytes@gmail.com> wrote:
>
> AND THAT... just reminded me that there was a thread where someone
> here said something I'd never remembered hearing before... There's a
> spot related to I THINK initramfs or something LIKE that
> (initrd.img??) where we can accidentally be carrying over a wrong UUID
> (or possibly PARTUUID, LABEL, etc) declaration.
>
> That would, for example, happen if we copied over a live session from
> one partition to another. It's well known that we immediately need to
> change declarations in /etc/fstab to represent the new partition. This
> other, though, just might answer some questions like this that have
> otherwise long gone unsolved in the past..
>
> OR NOT. *grin*


Sorry, I did it AGAIN. Left out the rationale for even bringing that up.

Whichever kind Debian User brought that topic up in last couple months
said that it's a place where our systems would be tapping into when
bringing things up to speed. If the wrong declaration is sitting in
that position, our systems will stall while they're scratching their
heads trying to figure out what to do next when they can't find that
wrong UUID (or possibly PARTUUID or LABEL) that was accidentally
carried over from another partition or suchly..

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#204733

On Sun 27 Jan 2019 at 20:23:38 (-0500), Cindy-Sue Causey wrote:
> On 1/27/19, Cindy-Sue Causey <butterflybytes@gmail.com> wrote:
> >
> > AND THAT... just reminded me that there was a thread where someone
> > here said something I'd never remembered hearing before... There's a
> > spot related to I THINK initramfs or something LIKE that
> > (initrd.img??) where we can accidentally be carrying over a wrong UUID
> > (or possibly PARTUUID, LABEL, etc) declaration.
> >
> > That would, for example, happen if we copied over a live session from
> > one partition to another. It's well known that we immediately need to
> > change declarations in /etc/fstab to represent the new partition. This
> > other, though, just might answer some questions like this that have
> > otherwise long gone unsolved in the past..
> >
> > OR NOT. *grin*
> 
> 
> Sorry, I did it AGAIN. Left out the rationale for even bringing that up.
> 
> Whichever kind Debian User brought that topic up in last couple months
> said that it's a place where our systems would be tapping into when
> bringing things up to speed. If the wrong declaration is sitting in
> that position, our systems will stall while they're scratching their
> heads trying to figure out what to do next when they can't find that
> wrong UUID (or possibly PARTUUID or LABEL) that was accidentally
> carried over from another partition or suchly..

Sounds like you're referring to /etc/initramfs-tools/conf.d/resume
which needs to be present in the initramfs as well as the filesystem.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#204729

On 1/27/19 12:11 PM, BELAHCENE Abdelkader wrote:
> Sometimes (maybe often) when I leave the system for a times without
> touching it, when I come back, the system is frozen , juste the pointer of
> mouse can move, but nothing else,  keyboard doesn't respond,  even
> ctrl+alt+F1 , or F2,  ...
> So the only  thing todo is stop button.

Install the package:

     openssh-server


Configure your host and/or network so that you can log in over the network.


David

[toc] | [prev] | [next] | [standalone]

#204737

[Multipart message — attachments visible in raw view] — view raw

On 28/01/2019 00:55, David Christensen wrote:
> On 1/27/19 12:11 PM, BELAHCENE Abdelkader wrote:
>> Sometimes (maybe often) when I leave the system for a times without
>> touching it, when I come back, the system is frozen , juste the
>> pointer of
>> mouse can move, but nothing else,  keyboard doesn't respond,  even
>> ctrl+alt+F1 , or F2,  ...
>> So the only  thing todo is stop button.
>
> Install the package:
>
>     openssh-server
>
>
> Configure your host and/or network so that you can log in over the
> network.
>
>
> David


Holding alt-sysrq (print screen key usually) and then typing RSEIUB may
also restart the system but cleanly as in unmounting file systems etc. 
however I agree with the above option too. 


-- 
Paul Sutton
http://www.zleap.net
https://www.linkedin.com/in/zleap/

[toc] | [prev] | [next] | [standalone]

#204769

On 1/28/19 1:18 AM, Paul Sutton wrote:
> On 28/01/2019 00:55, David Christensen wrote:
>> On 1/27/19 12:11 PM, BELAHCENE Abdelkader wrote:
>>> Sometimes (maybe often) when I leave the system for a times without
>>> touching it, when I come back, the system is frozen , juste the
>>> pointer of
>>> mouse can move, but nothing else,  keyboard doesn't respond,  even
>>> ctrl+alt+F1 , or F2,  ...
>>> So the only  thing todo is stop button.
>>
>> Install the package:
>>
>>      openssh-server
>>
>>
>> Configure your host and/or network so that you can log in over the
>> network.
> 
> Holding alt-sysrq (print screen key usually) and then typing RSEIUB may
> also restart the system but cleanly as in unmounting file systems etc.
> however I agree with the above option too.

Where is that documented?


David

[toc] | [prev] | [next] | [standalone]

#204772

On 1/28/2019 10:21 AM, David Christensen wrote:
> On 1/28/19 1:18 AM, Paul Sutton wrote:
>> On 28/01/2019 00:55, David Christensen wrote:
>>> On 1/27/19 12:11 PM, BELAHCENE Abdelkader wrote:
>>>> Sometimes (maybe often) when I leave the system for a times without
>>>> touching it, when I come back, the system is frozen , juste the
>>>> pointer of
>>>> mouse can move, but nothing else,  keyboard doesn't respond,  even
>>>> ctrl+alt+F1 , or F2,  ...
>>>> So the only  thing todo is stop button.
>>>
>>> Install the package:
>>>
>>>      openssh-server
>>>
>>>
>>> Configure your host and/or network so that you can log in over the
>>> network.
>>
>> Holding alt-sysrq (print screen key usually) and then typing RSEIUB may
>> also restart the system but cleanly as in unmounting file systems etc.
>> however I agree with the above option too.
>
> Where is that documented?
>
>
> David
>
>
Right here: https://en.wikipedia.org/wiki/Magic_SysRq_key

-- john

[toc] | [prev] | [next] | [standalone]

#204774

Hmm, it might be my day to be disagreeable, and I'm not the OP, nor (iirc) 
have I posted in this thread prior to this, but ...

On Monday, January 28, 2019 01:41:41 PM John Darrah wrote:
> On 1/28/2019 10:21 AM, David Christensen wrote:
> > Where is that documented?
> > 
> > 
> > David
> 
> Right here: https://en.wikipedia.org/wiki/Magic_SysRq_key

I don't consider that documentation.

You should read all of wikipedia before using a piece of software?  Or some 
selection based on words you can remember / think of?

(I guess I don't doubt that it is documented somewhere in something that I 
would consider documentation (like a man page associated with Linux or the 
specific app), but an entry in wikipedia is not documentation.

Hmm, should I wait and rethink before posting this -- nah, even if I wait, at 
most I'll do something like add some musing just like this ;-)

[toc] | [prev] | [next] | [standalone]

#204776

On 1/28/2019 11:08 AM, rhkramer@gmail.com wrote:
> Hmm, it might be my day to be disagreeable, and I'm not the OP, nor (iirc)
> have I posted in this thread prior to this, but ...
>
> On Monday, January 28, 2019 01:41:41 PM John Darrah wrote:
>> On 1/28/2019 10:21 AM, David Christensen wrote:
>>> Where is that documented?
>>>
>>>
>>> David
>> Right here: https://en.wikipedia.org/wiki/Magic_SysRq_key
> I don't consider that documentation.
>
> You should read all of wikipedia before using a piece of software?  Or some
> selection based on words you can remember / think of?
>
> (I guess I don't doubt that it is documented somewhere in something that I
> would consider documentation (like a man page associated with Linux or the
> specific app), but an entry in wikipedia is not documentation.
>
> Hmm, should I wait and rethink before posting this -- nah, even if I wait, at
> most I'll do something like add some musing just like this ;-)
>
>
Is this better?: 
https://www.kernel.org/doc/html/v4.18/admin-guide/sysrq.html

-- john

[toc] | [prev] | [next] | [standalone]

#204779

On Monday, January 28, 2019 02:45:26 PM John Darrah wrote:
> On 1/28/2019 11:08 AM, rhkramer@gmail.com wrote:
> > I don't consider that documentation.

> Is this better?:
> https://www.kernel.org/doc/html/v4.18/admin-guide/sysrq.html

Yes, thank you!

[toc] | [prev] | [next] | [standalone]

#204787

On Mon, 2019-01-28 at 15:43 -0500, rhkramer@gmail.com wrote:
> On Monday, January 28, 2019 02:45:26 PM John Darrah wrote:
> > On 1/28/2019 11:08 AM, rhkramer@gmail.com wrote:
> > > I don't consider that documentation.
> 
> > Is this better?:
> > https://www.kernel.org/doc/html/v4.18/admin-guide/sysrq.html
> 
> Yes, thank you!

Debian kernels don't seem to have the process killing and debug dump
keys disabled by default...

# cat /boot/config-4.9.0-8-amd64 | grep SYSRQ
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6

I guess it was decided that the disabled options could allow
unauthorised users access to sensitive information and programs.

-- 
Tixy

[toc] | [prev] | [next] | [standalone]

#204788

[Multipart message — attachments visible in raw view] — view raw

On Mon, Jan 28, 2019 at 02:07:05PM -0500, rhkramer@gmail.com wrote:

[...]

> You should read all of wikipedia before using a piece of software?  Or some 
> selection based on words you can remember / think of?

You can leave out that page on fern [1]. And that other on slime mold [2]

(Uh-oh. Now everyone knows I've been procrastinating :-/

[1] https://en.wikipedia.org/wiki/Fern
[2] https://en.wikipedia.org/wiki/Slime_mold
-- t

[toc] | [prev] | [next] | [standalone]

#204791

On Tuesday, January 29, 2019 03:58:21 AM tomas@tuxteam.de wrote:
> On Mon, Jan 28, 2019 at 02:07:05PM -0500, rhkramer@gmail.com wrote:
> 
> [...]
> 
> > You should read all of wikipedia before using a piece of software?  Or
> > some selection based on words you can remember / think of?
> 
> You can leave out that page on fern [1]. And that other on slime mold [2]

That helps, thanks ;-)

> (Uh-oh. Now everyone knows I've been procrastinating :-/

Uh, I won't say anything

> 
> [1] https://en.wikipedia.org/wiki/Fern
> [2] https://en.wikipedia.org/wiki/Slime_mold
> -- t

[toc] | [prev] | [next] | [standalone]

#204784

On 1/28/19 10:41 AM, John Darrah wrote:
> On 1/28/2019 10:21 AM, David Christensen wrote:
>> On 1/28/19 1:18 AM, Paul Sutton wrote:
>>> On 28/01/2019 00:55, David Christensen wrote:
>>>> On 1/27/19 12:11 PM, BELAHCENE Abdelkader wrote:
>>>>> Sometimes (maybe often) when I leave the system for a times without
>>>>> touching it, when I come back, the system is frozen , juste the
>>>>> pointer of
>>>>> mouse can move, but nothing else,  keyboard doesn't respond,  even
>>>>> ctrl+alt+F1 , or F2,  ...
>>>>> So the only  thing todo is stop button.
>>>>
>>>> Install the package:
>>>>
>>>>      openssh-server
>>>>
>>>>
>>>> Configure your host and/or network so that you can log in over the
>>>> network.
>>>
>>> Holding alt-sysrq (print screen key usually) and then typing RSEIUB may
>>> also restart the system but cleanly as in unmounting file systems etc.
>>> however I agree with the above option too.
>>
>> Where is that documented?
>>
> Right here: https://en.wikipedia.org/wiki/Magic_SysRq_key

Why RSEIUB, rather than REISUB as recommended by Wikipedia?


David

[toc] | [prev] | [next] | [standalone]

#204785

On 28/01/2019 18.18, Paul Sutton wrote:
>> On 1/27/19 12:11 PM, BELAHCENE Abdelkader wrote:
>>> Sometimes (maybe often) when I leave the system for a times without
>>> touching it, when I come back, the system is frozen , juste the
>>> pointer of
>>> mouse can move, but nothing else,  keyboard doesn't respond,  even
>>> ctrl+alt+F1 , or F2,  ...
>>> So the only  thing todo is stop button.
> 
> Holding alt-sysrq (print screen key usually) and then typing RSEIUB may
> also restart the system but cleanly as in unmounting file systems etc.

Unfortunately in this case the keyboard is not responding, so RSEISUB 
(boots and braces) probably won't help. (It's a good thing to try though.)

-- 
John

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web