Bug#850959: Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 19:37:37 +0100, Michael Biebl wrote:
> [moving this over to #850959]
> Am 11.01.2017 um 19:13 schrieb Michael Biebl:
> > Am 11.01.2017 um 19:12 schrieb Michael Biebl:
> >> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
> >>> What info do you need?
> >>
> >> A verbose debug log from shutdown would be helpful.
> > 
> > /usr/share/doc/systemd/README.Debian.gz →
> > Debugging boot/shutdown problems

This is not helpful:

  For shutdown problems, run "systemctl start debug-shell" as root,
  then shut down.

I recall that the problem occurs at the same time as resuming, i.e.
I can't do anything. In particular, the screen remains off.

Also, the problem has only occurred twice over 117 "Lid opened."
messages in 18 months. So, the verbose debug log from shutdown should
be permanently enabled, but without drawbacks for normal usage.

> If you had an unclean power off and a file corruption, please provide
> the fsck log for this incident.
> For / (and /usr) the logs are in /run/initramfs/, for other file systems
> the result is in the journal.

Unfortunately I have only the one corresponding to the last boot
there. No automatic backup of the previous ones?

In the journal, for the problem that occurred on 2015-07-25, in the
next reboot:

Jul 25 17:15:51 zira systemd-fsck[509]: /dev/sda1 was not cleanly unmounted, 
check forced.
Jul 25 17:15:51 zira systemd-fsck[509]: /dev/sda1: 333/62248 files (24.3% 
non-contiguous), 68102/248832 blocks
Jul 25 17:15:51 zira systemd[1]: Started File System Check on 
/dev/disk/by-uuid/7b3de7fd-236a-47f6-bb85-64831a06ca1f.

(/dev/sda1 is mounted on /boot). But also two days later:

Jul 27 16:47:46 zira systemd-fsck[512]: /dev/sda1 was not cleanly unmounted, 
check forced.

Here, it seems that the shutdown was aborted by a bug in the
nouveau driver, which I no longer use, BTW. I've got a few other
ones for known reasons (i.e. no shutdown or shutdown aborted due
to bugs).

Then, on December 23, in the next reboot:

Dec 23 10:52:09 zira systemd-fsck[511]: /dev/sda1 was not cleanly unmounted, 
check forced.
Dec 23 10:52:09 zira systemd-fsck[511]: /dev/sda1: 354/62248 files (26.8% 
non-contiguous), 150547/248832 blocks
Dec 23 10:52:09 zira systemd[1]: Started File System Check on 
/dev/disk/by-uuid/7b3de7fd-236a-47f6-bb85-64831a06ca1f.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850959: Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Control: severity -1 normal
Control: tags -1 moreinfo unreproducible

[moving this over to #850959]
Am 11.01.2017 um 19:13 schrieb Michael Biebl:
> Am 11.01.2017 um 19:12 schrieb Michael Biebl:
>> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
>>> What info do you need?
>>
>> A verbose debug log from shutdown would be helpful.
> 
> 
> /usr/share/doc/systemd/README.Debian.gz →
> Debugging boot/shutdown problems
> 

If you had an unclean power off and a file corruption, please provide
the fsck log for this incident.
For / (and /usr) the logs are in /run/initramfs/, for other file systems
the result is in the journal.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Am 11.01.2017 um 19:12 schrieb Michael Biebl:
> Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
>> On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
>>> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
 Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
>>> Why is this no normal shutdown?
>
> Services are not stopped as usual.

 How do you conclude that?
>>
>> There is no log for stopped services in the journald logs.
> 
> Not sure what that is supposed to show.
> 
>>> And if something is killing the power midway through the shutdown
>>> process, it's hardly something systemd can do about.
>>
>> What would kill the power?
> 
> You pressing the power button for too long, a faulty power supply, buggy
> bios, ...
> 
>>> That said, so far this bug report is lacking crucial information why
>>> this is supposed to be a systemd bug,
>>
>> What info do you need?
> 
> A verbose debug log from shutdown would be helpful.


/usr/share/doc/systemd/README.Debian.gz →
Debugging boot/shutdown problems

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Am 11.01.2017 um 18:55 schrieb Vincent Lefevre:
> On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
>> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
>>> Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
 On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
>> Why is this no normal shutdown?

 Services are not stopped as usual.
>>>
>>> How do you conclude that?
> 
> There is no log for stopped services in the journald logs.

Not sure what that is supposed to show.

>> And if something is killing the power midway through the shutdown
>> process, it's hardly something systemd can do about.
> 
> What would kill the power?

You pressing the power button for too long, a faulty power supply, buggy
bios, ...

>> That said, so far this bug report is lacking crucial information why
>> this is supposed to be a systemd bug,
> 
> What info do you need?

A verbose debug log from shutdown would be helpful.

So far what I see is:
logind receives a power button event and initiates a shutdown request
which is executed by systemd. I can't see the bug in systemd.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 17:40:09 +, Ben Hutchings wrote:
> On Wed, 2017-01-11 at 16:20 +0100, Vincent Lefevre wrote:
> > On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > > Unless you can show that some data had been written *and flushed* to
> > > disk by the application, but was not readable afterward - this does not
> > > count.  Writes are buffered, and user space has to deal with that.
> > 
> > If I understand the journalctl log correctly, the system does
> > a power off without a clean shutdown:
> 
> Sorry, I didn't understand what you were trying to point out in the
> system log.  I had thought that pressing the power button was causing
> an immediate power-off, but you're showing me that it results in a
> resume immediately followed by a software-controlled shutdown.  Right?

Yes, this is what seems to appear from the logs.

> It seems like there are two separate bugs:
> 
> 1. Power button resumes and also generates a power-off input event
> (kernel bug)
> 2. Some writes not flushed to disk during shutdown (probably a kernel
> bug, but systemd could potentially break this)

Bug 850959. Hmm... no shutdown or the journald log is truncated
for the same reason.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
> > Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> >> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> >>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
>  Why is this no normal shutdown?
> >>
> >> Services are not stopped as usual.
> > 
> > How do you conclude that?

There is no log for stopped services in the journald logs.

> And if something is killing the power midway through the shutdown
> process, it's hardly something systemd can do about.

What would kill the power?

> That said, so far this bug report is lacking crucial information why
> this is supposed to be a systemd bug,

What info do you need?

> even more a grave one.

There is file corruption (not just theoretical, it really happened
in practice).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Ben Hutchings]

On Wed, 2017-01-11 at 16:20 +0100, Vincent Lefevre wrote:
> On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > Unless you can show that some data had been written *and flushed* to
> > disk by the application, but was not readable afterward - this does not
> > count.  Writes are buffered, and user space has to deal with that.
> 
> If I understand the journalctl log correctly, the system does
> a power off without a clean shutdown:

Sorry, I didn't understand what you were trying to point out in the
system log.  I had thought that pressing the power button was causing
an immediate power-off, but you're showing me that it results in a
resume immediately followed by a software-controlled shutdown.  Right?

It seems like there are two separate bugs:

1. Power button resumes and also generates a power-off input event
(kernel bug)
2. Some writes not flushed to disk during shutdown (probably a kernel
bug, but systemd could potentially break this)

> [...]
> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color 
> Pro
> 
> then nothing after that!!! This is were the problem is, not in the
> application, which cannot know when the machine will power off.

That is why applications should flush writes before considering them
complete.  But in case of a software-controlled shutdown, all writes
sent to the kernel should get flushed even if applications don't
explicitly do so.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert
Coveyou



signature.asc
Description: This is a digitally signed message part

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Am 11.01.2017 um 18:28 schrieb Michael Biebl:
> Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
>> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
>>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
 Why is this no normal shutdown?
>>
>> Services are not stopped as usual.
> 
> How do you conclude that?

And if something is killing the power midway through the shutdown
process, it's hardly something systemd can do about.

That said, so far this bug report is lacking crucial information why
this is supposed to be a systemd bug, even more a grave one.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
>>> Why is this no normal shutdown?
> 
> Services are not stopped as usual.

How do you conclude that?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> > Why is this no normal shutdown?

Services are not stopped as usual.

> > Did you actually have a file corruption?

Yes, /var/log/monit.log, which got null bytes in it, and some
other file created my monit, which was empty (thus invalid).

> And why is this a systemd bug?

I assumed that this was systemd as it decided to power off the
machine: "systemd-logind[803]: Powering Off...". Otherwise, which
part is responsible for the shutdown?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> Am 11.01.2017 um 17:05 schrieb Vincent Lefevre:
>> Control: clone -1 -2
>> Control: reassign -2 systemd 232-8
>> Control: retitle -2 systemd: power off without always a normal shutdown when 
>> resuming after suspend with the power button
>> Control: severity -2 grave
>>
>> as the lack of shutdown yields visible file corruption and potentially
>> data loss.
>>
>> On 2017-01-11 16:20:35 +0100, Vincent Lefevre wrote:
>>> On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
 Unless you can show that some data had been written *and flushed* to
 disk by the application, but was not readable afterward - this does not
 count.  Writes are buffered, and user space has to deal with that.
>>>
>>> If I understand the journalctl log correctly, the system does
>>> a power off without a clean shutdown:
>>>
>>> [...]
>>> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
>>> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
>>> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate 
>>> Color Pro
>>>
>>> then nothing after that!!! This is where the problem is, not in the
>>> application, which cannot know when the machine will power off.
>>
>> Well, there are two problems:
>>
>> 1. The fact that the system powers down instead of just resuming.
>>systemd-logind reports "Power key pressed." but the power key
>>was used to resume, so that I suppose that systemd-logind
>>should have never seen this.
>>
>> 2. The fact that the system is powered off immediately without a
>>clean shutdown. When I use the power button to power off the
>>laptop, I get:
>>
>> Sep 17 19:36:13 zira systemd-logind[17281]: Power key pressed.
>> Sep 17 19:36:13 zira systemd-logind[17281]: Powering Off...
>> Sep 17 19:36:13 zira systemd-logind[17281]: System is powering down.
>> Sep 17 19:36:13 zira systemd[1]: Stopped target Bluetooth.
>> Sep 17 19:36:13 zira systemd[1]: Stopping Session 2041 of user vinc17.
>> Sep 17 19:36:13 zira systemd[1]: Deactivating swap 
>> /dev/disk/by-id/dm-uuid-LVM-K
>> Sep 17 19:36:13 zira systemd[1]: Stopping Disk Manager...
>> [...]
>>
>> i.e. a normal shutdown, but when this is used just after a suspend
>> in order to resume, I *occasionally* get (well, this occurred only
>> twice):
>>
>> Jul 25 17:15:17 zira systemd-logind[769]: Power key pressed.
>> Jul 25 17:15:17 zira systemd-logind[769]: Powering Off...
>> Jul 25 17:15:17 zira systemd-logind[769]: System is powering down.
>> -- Reboot --
>>
>> Dec 23 10:51:01 zira systemd-logind[803]: Power key pressed.
>> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
>> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
>> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color 
>> Pro
>> -- Reboot --
>>
>> No normal shutdown!
>>
> 
> Why is this no normal shutdown?
> Did you actually have a file corruption?
> 


And why is this a systemd bug?

/me is puzzled


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Michael Biebl]

Am 11.01.2017 um 17:05 schrieb Vincent Lefevre:
> Control: clone -1 -2
> Control: reassign -2 systemd 232-8
> Control: retitle -2 systemd: power off without always a normal shutdown when 
> resuming after suspend with the power button
> Control: severity -2 grave
> 
> as the lack of shutdown yields visible file corruption and potentially
> data loss.
> 
> On 2017-01-11 16:20:35 +0100, Vincent Lefevre wrote:
>> On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
>>> Unless you can show that some data had been written *and flushed* to
>>> disk by the application, but was not readable afterward - this does not
>>> count.  Writes are buffered, and user space has to deal with that.
>>
>> If I understand the journalctl log correctly, the system does
>> a power off without a clean shutdown:
>>
>> [...]
>> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
>> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
>> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color 
>> Pro
>>
>> then nothing after that!!! This is where the problem is, not in the
>> application, which cannot know when the machine will power off.
> 
> Well, there are two problems:
> 
> 1. The fact that the system powers down instead of just resuming.
>systemd-logind reports "Power key pressed." but the power key
>was used to resume, so that I suppose that systemd-logind
>should have never seen this.
> 
> 2. The fact that the system is powered off immediately without a
>clean shutdown. When I use the power button to power off the
>laptop, I get:
> 
> Sep 17 19:36:13 zira systemd-logind[17281]: Power key pressed.
> Sep 17 19:36:13 zira systemd-logind[17281]: Powering Off...
> Sep 17 19:36:13 zira systemd-logind[17281]: System is powering down.
> Sep 17 19:36:13 zira systemd[1]: Stopped target Bluetooth.
> Sep 17 19:36:13 zira systemd[1]: Stopping Session 2041 of user vinc17.
> Sep 17 19:36:13 zira systemd[1]: Deactivating swap 
> /dev/disk/by-id/dm-uuid-LVM-K
> Sep 17 19:36:13 zira systemd[1]: Stopping Disk Manager...
> [...]
> 
> i.e. a normal shutdown, but when this is used just after a suspend
> in order to resume, I *occasionally* get (well, this occurred only
> twice):
> 
> Jul 25 17:15:17 zira systemd-logind[769]: Power key pressed.
> Jul 25 17:15:17 zira systemd-logind[769]: Powering Off...
> Jul 25 17:15:17 zira systemd-logind[769]: System is powering down.
> -- Reboot --
> 
> Dec 23 10:51:01 zira systemd-logind[803]: Power key pressed.
> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color 
> Pro
> -- Reboot --
> 
> No normal shutdown!
> 

Why is this no normal shutdown?
Did you actually have a file corruption?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

Control: clone -1 -2
Control: reassign -2 systemd 232-8
Control: retitle -2 systemd: power off without always a normal shutdown when 
resuming after suspend with the power button
Control: severity -2 grave

as the lack of shutdown yields visible file corruption and potentially
data loss.

On 2017-01-11 16:20:35 +0100, Vincent Lefevre wrote:
> On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > Unless you can show that some data had been written *and flushed* to
> > disk by the application, but was not readable afterward - this does not
> > count.  Writes are buffered, and user space has to deal with that.
> 
> If I understand the journalctl log correctly, the system does
> a power off without a clean shutdown:
> 
> [...]
> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color 
> Pro
> 
> then nothing after that!!! This is where the problem is, not in the
> application, which cannot know when the machine will power off.

Well, there are two problems:

1. The fact that the system powers down instead of just resuming.
   systemd-logind reports "Power key pressed." but the power key
   was used to resume, so that I suppose that systemd-logind
   should have never seen this.

2. The fact that the system is powered off immediately without a
   clean shutdown. When I use the power button to power off the
   laptop, I get:

Sep 17 19:36:13 zira systemd-logind[17281]: Power key pressed.
Sep 17 19:36:13 zira systemd-logind[17281]: Powering Off...
Sep 17 19:36:13 zira systemd-logind[17281]: System is powering down.
Sep 17 19:36:13 zira systemd[1]: Stopped target Bluetooth.
Sep 17 19:36:13 zira systemd[1]: Stopping Session 2041 of user vinc17.
Sep 17 19:36:13 zira systemd[1]: Deactivating swap /dev/disk/by-id/dm-uuid-LVM-K
Sep 17 19:36:13 zira systemd[1]: Stopping Disk Manager...
[...]

i.e. a normal shutdown, but when this is used just after a suspend
in order to resume, I *occasionally* get (well, this occurred only
twice):

Jul 25 17:15:17 zira systemd-logind[769]: Power key pressed.
Jul 25 17:15:17 zira systemd-logind[769]: Powering Off...
Jul 25 17:15:17 zira systemd-logind[769]: System is powering down.
-- Reboot --

Dec 23 10:51:01 zira systemd-logind[803]: Power key pressed.
Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color Pro
-- Reboot --

No normal shutdown!

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> Unless you can show that some data had been written *and flushed* to
> disk by the application, but was not readable afterward - this does not
> count.  Writes are buffered, and user space has to deal with that.

If I understand the journalctl log correctly, the system does
a power off without a clean shutdown:

[...]
Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color Pro

then nothing after that!!! This is were the problem is, not in the
application, which cannot know when the machine will power off.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Ben Hutchings]

Control: severity -1 important

On Wed, 2017-01-11 at 15:52 +0100, Vincent Lefevre wrote:
> Control: severity -1 grave
> 
> because it can corrupt files.
>
> When this occurred on December 23, the log file of monit got
> corrupted:
> 
> [CET Dec 22 07:35:07] info : 'zira' Monit reloaded
> [CET Dec 22 07:35:07] error: Queued event file: unable to read event size 
> -- end of file
> [CET Dec 23 10:51:01] error: 'eth0' link down
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@[CET
>  Dec 23 10:52:10] info : Starting Monit 5.20.0 daemon
> [CET Dec 23 10:52:10] info : 'zira' Monit 5.20.0 started
> [...]

Unless you can show that some data had been written *and flushed* to
disk by the application, but was not readable afterward - this does not
count.  Writes are buffered, and user space has to deal with that.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert
Coveyou



signature.asc
Description: This is a digitally signed message part

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

Control: severity -1 grave

because it can corrupt files.

When this occurred on December 23, the log file of monit got
corrupted:

[CET Dec 22 07:35:07] info : 'zira' Monit reloaded
[CET Dec 22 07:35:07] error: Queued event file: unable to read event size 
-- end of file
[CET Dec 23 10:51:01] error: 'eth0' link down
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@[CET
 Dec 23 10:52:10] info : Starting Monit 5.20.0 daemon
[CET Dec 23 10:52:10] info : 'zira' Monit 5.20.0 started
[...]

And from journalctl:

[...]
Dec 23 10:51:01 zira kernel: PM: Finishing wakeup.
Dec 23 10:51:01 zira kernel: Restarting tasks ... 
Dec 23 10:51:01 zira kernel: acpi PNP0501:00: Still not present
Dec 23 10:51:01 zira kernel: done.
Dec 23 10:51:01 zira kernel: pci_bus :02: Allocating resources
Dec 23 10:51:01 zira kernel: pci_bus :3b: Allocating resources
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: bridge window [io  
0x1000-0x0fff] to [bus 5f] add_size 1000
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: res[13]=[io  0x1000-0x0fff] 
res_to_dev_res add_size 1000 min_align 1000
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: res[13]=[io  0x1000-0x1fff] 
res_to_dev_res add_size 1000 min_align 1000
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: no space for [io  
size 0x1000]
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: failed to assign 
[io  size 0x1000]
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: no space for [io  
size 0x1000]
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: failed to assign 
[io  size 0x1000]
Dec 23 10:51:01 zira kernel: Bluetooth: hci0: read Intel version: 
370710018002030d00
Dec 23 10:51:01 zira kernel: Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Dec 23 10:51:01 zira systemd[1]: Time has been changed
Dec 23 10:51:01 zira rtkit-daemon[2080]: The canary thread is apparently 
starving. Taking action.
Dec 23 10:51:01 zira systemd[1394]: Time has been changed
Dec 23 10:51:01 zira rtkit-daemon[2080]: Demoting known real-time threads.
Dec 23 10:51:01 zira systemd-logind[803]: Lid opened.
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2097 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1]: apt-daily.timer: Adding 4h 42min 58.832894s 
random time.
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2096 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1606]: Time has been changed
Dec 23 10:51:01 zira kernel: video LNXVIDEO:00: Restoring backlight state
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2095 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1]: apt-daily.timer: Adding 1h 5min 28.127060s 
random time.
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2079 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 23 10:51:01 zira rtkit-daemon[2080]: Demoted 4 threads.
Dec 23 10:51:01 zira systemd[1]: bluetooth.target: Unit not needed anymore. 
Stopping.
Dec 23 10:51:01 zira acpid[751]: client 984[0:0] has disconnected
Dec 23 10:51:01 zira systemd[1]: Stopped target Bluetooth.
Dec 23 10:51:01 zira postfix/smtpd[11811]: connect from 

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

Package: src:linux
Version: 4.8.11-1
Severity: important

After suspending my laptop (13:54:33 below), when I pressed the power
button to resume (19:35:53 below), the laptop was automatically
powered off. This is a regression (tried twice, occurred twice,
but there was no such problem in the past, AFAIK).

Excerpt from journalctl output:

[...]
Jan 02 13:54:33 zira systemd-logind[725]: Lid closed.
Jan 02 13:54:33 zira systemd-logind[725]: Suspending...
Jan 02 13:54:33 zira systemd[1]: Reached target Sleep.
Jan 02 13:54:33 zira systemd[1]: Starting Suspend...
Jan 02 13:54:33 zira systemd[1]: Stopping Atop advanced performance monitor...
Jan 02 13:54:34 zira systemd[1]: Stopped Atop advanced performance monitor.
Jan 02 13:54:34 zira systemd-sleep[13376]: Suspending system...
Jan 02 13:54:34 zira kernel: PM: Syncing filesystems ... done.
Jan 02 13:54:34 zira kernel: PM: Preparing system for sleep (mem)
Jan 02 13:54:35 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Jan 02 19:35:53 zira kernel: (NULL device *): firmware: direct-loading firmware 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Jan 02 19:35:53 zira kernel: (NULL device *): firmware: direct-loading firmware 
iwlwifi-7260-17.ucode
Jan 02 19:35:53 zira kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
Jan 02 19:35:53 zira kernel: Double checking all user space processes after OOM 
killer disable... (elapsed 0.000 seconds) 
Jan 02 19:35:53 zira kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
Jan 02 19:35:53 zira kernel: PM: Suspending system (mem)
Jan 02 19:35:53 zira kernel: Suspending console(s) (use no_console_suspend to 
debug)
Jan 02 19:35:53 zira kernel: wlp61s0: deauthenticating from 00:1f:33:89:73:4e 
by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 02 19:35:53 zira kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 02 19:35:53 zira kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 02 19:35:53 zira kernel: parport_pc 00:04: disabled
Jan 02 19:35:53 zira kernel: e1000e: EEE TX LPI TIMER: 0011
Jan 02 19:35:53 zira kernel: PM: suspend of devices complete after 1306.520 
msecs
Jan 02 19:35:53 zira kernel: PM: late suspend of devices complete after 0.440 
msecs
Jan 02 19:35:53 zira kernel: ehci-pci :00:1d.0: System wakeup enabled by 
ACPI
Jan 02 19:35:53 zira kernel: ehci-pci :00:1a.0: System wakeup enabled by 
ACPI
Jan 02 19:35:53 zira kernel: e1000e :00:19.0: System wakeup enabled by ACPI
Jan 02 19:35:53 zira kernel: xhci_hcd :00:14.0: System wakeup enabled by 
ACPI
Jan 02 19:35:53 zira kernel: PM: noirq suspend of devices complete after 70.928 
msecs
Jan 02 19:35:53 zira kernel: ACPI: Preparing to enter system sleep state S3
Jan 02 19:35:53 zira kernel: ACPI : EC: EC stopped
Jan 02 19:35:53 zira kernel: PM: Saving platform NVS memory
Jan 02 19:35:53 zira kernel: Disabling non-boot CPUs ...
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 1 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 2 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 3 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 4 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 17
Jan 02 19:35:53 zira kernel: Broke affinity for irq 32
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 5 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 17
Jan 02 19:35:53 zira kernel: Broke affinity for irq 32
Jan 02 19:35:53 zira kernel: Broke affinity for irq 33
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 6 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 1
Jan 02 19:35:53 zira kernel: Broke affinity for irq 8
Jan 02 19:35:53 zira kernel: Broke affinity for irq 9
Jan 02 19:35:53 zira kernel: Broke affinity for irq 12
Jan 02 19:35:53 zira kernel: Broke affinity for irq 16
Jan 02 19:35:53 zira kernel: Broke affinity for irq 17
Jan 02 19:35:53 zira kernel: Broke affinity for irq 32
Jan 02 19:35:53 zira kernel: Broke affinity for irq 33
Jan 02 19:35:53 zira kernel: Broke affinity for irq 36
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 7 is now offline
Jan 02 19:35:53 zira kernel: ACPI: Low-level resume complete
Jan 02 19:35:53 zira kernel: ACPI : EC: EC started
Jan 02 19:35:53 zira kernel: PM: Restoring platform NVS memory
Jan 02 19:35:53 zira kernel: Enabling non-boot CPUs ...
Jan 02 19:35:53 zira kernel: x86: Booting SMP configuration:
Jan 02 19:35:53 zira kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jan 02 19:35:53 zira kernel:  cache: parent cpu1 should not be sleeping
Jan 02 19:35:53 zira kernel: