Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-02-15 Thread Marc-Robin Wendt 
Problem not solved. Running my laptop with unsecure old kernel. Any
suggestions?

Marc.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-01-13 Thread Marc-Robin Wendt 

On Fri, 2018-01-12 at 01:12 +, Ben Hutchings wrote:
> On Thu, 2018-01-11 at 12:25 +0100, Marc-Robin Wendt wrote:
> > Hello Ben and Michael,
> > 
> > thanks for taking time. Of course its DPMS. Sorry for the typo.
> > 
> > Reproducing the bug turns out, it first appears in linux-image-
> > 4.9.0-4-
> > amd64 and now linux-image-4.9.0-5-amd64.
> > 
> > When I boot the system from grub with old kernel linux-image-4.9.0-
> > 3-
> > amd64 or linux-image-4.9.0-2-amd64, behavior is as expected ok,
> > means
> > switching off the monitor doesnt trigger suspend of the system.
> 
> So are *you* switching off the monitor?  You mentioned DPMS, which is
> the way for the display adapter to control the monitor - it doesn't
> involve any signalling in the other direction.
> 
> And is the monitor attached to a VGA or digital port?  If it's a
> digital port, turning off power to the monitor will look exactly the
> same as unplugging it...
> 

I examined the problem more closely. Lid is closed, because the laptop
is on the dock. Connection via display port. When I connect via HDMI
there are no problems with turning on or off the monitor.

It doesn't matter how the monitor is switched off, manual or
screensaver or even by command from command line.
The suspend is actually triggered when you switch the monitor on(!)
again. I didn't noticed it so far, because it happens instantly, when
you touch anything keyboard or mouse to wake up the monitor from
screensaver.

So, monitor is switched off, system runs, I even could ping it. Wake up
the monitor will send the system into suspend. Even more strange
behavior.

Graphic card, see my first mail. Its a Lenovo T430s, so probably
NVIDIA
> > NVS 5200M inside. Monitor is LG 34UM88C-P.
> 
> ...and if you have a laptop that is already closed, unplugging the
> last
> external display is *supposed* to trigger suspend by default.  (The
> same as when you have the laptop open with no external display, and
> then close the laptop.)
> 
So you imply the old kernel had a bug? When I have my laptop on the
docking station, I want it to behave like a desktop. I least this was
the behavior the last 20 years. So of course the lid is closed and
turning off and on the last monitor shouldn't suspend the system. 


> But if this happens with the laptop still open, then this might be a
> kernel problem with lid switch detection.
> 
> Ben.
> 
> > Attached is the journalctl output once with linux-image-4.9.0-3-
> > amd64
> > booted and once with linux-image-4.9.0-4-amd64.
> 
> 

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-01-11 Thread Ben Hutchings 
On Thu, 2018-01-11 at 12:25 +0100, Marc-Robin Wendt wrote:
> Hello Ben and Michael,
> 
> thanks for taking time. Of course its DPMS. Sorry for the typo.
> 
> Reproducing the bug turns out, it first appears in linux-image-4.9.0-4-
> amd64 and now linux-image-4.9.0-5-amd64.
> 
> When I boot the system from grub with old kernel linux-image-4.9.0-3-
> amd64 or linux-image-4.9.0-2-amd64, behavior is as expected ok, means
> switching off the monitor doesnt trigger suspend of the system.

So are *you* switching off the monitor?  You mentioned DPMS, which is
the way for the display adapter to control the monitor - it doesn't
involve any signalling in the other direction.

And is the monitor attached to a VGA or digital port?  If it's a
digital port, turning off power to the monitor will look exactly the
same as unplugging it...

> Graphic card, see my first mail. Its a Lenovo T430s, so probably NVIDIA
> NVS 5200M inside. Monitor is LG 34UM88C-P.

...and if you have a laptop that is already closed, unplugging the last
external display is *supposed* to trigger suspend by default.  (The
same as when you have the laptop open with no external display, and
then close the laptop.)

But if this happens with the laptop still open, then this might be a
kernel problem with lid switch detection.

Ben.

> Attached is the journalctl output once with linux-image-4.9.0-3-amd64
> booted and once with linux-image-4.9.0-4-amd64.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.



signature.asc
Description: This is a digitally signed message part
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-01-11 Thread Marc-Robin Wendt 
Hello Ben and Michael,

thanks for taking time. Of course its DPMS. Sorry for the typo.

Reproducing the bug turns out, it first appears in linux-image-4.9.0-4-
amd64 and now linux-image-4.9.0-5-amd64.

When I boot the system from grub with old kernel linux-image-4.9.0-3-
amd64 or linux-image-4.9.0-2-amd64, behavior is as expected ok, means
switching off the monitor doesnt trigger suspend of the system.

Graphic card, see my first mail. Its a Lenovo T430s, so probably NVIDIA
NVS 5200M inside. Monitor is LG 34UM88C-P.

Attached is the journalctl output once with linux-image-4.9.0-3-amd64
booted and once with linux-image-4.9.0-4-amd64.

Regards
Marc-Robin


On Wed, 2018-01-10 at 21:50 +0100, Michael Biebl wrote:
> Control: tags -1 + moreinfo
> 
> On Wed, 10 Jan 2018 18:12:46 + Ben Hutchings  >
> wrote:
> > Control: reassign -1 systemd
> > 
> > On Tue, 2018-01-09 at 11:50 +0100, Marc-Robin Wendt wrote:
> > > Package: src:linux
> > > Version: 4.9.65-3+deb9u1
> > > Severity: normal
> > > 
> > > Dear Maintainer,
> > > 
> > > since linux-image-4.9.0-3-amd64 DKMS sends my system into
> > > suspend.
> > 
> > I guess you mean DPMS (Display Power Management System).
> > 
> > > Switching off the monitor causes suspend of the system. 
> > > With Kernel-Versions linux-image-4.9.0-1-amd64 and linux-image-
> > > 4.9.0-2-
> > > amd64 I had no problems.
> > > This problem is rather annoying, when my system starts the
> > > screensaver
> > > after 10 min, the monitor switches off and sends the system into
> > > suspend. Screensaver is not meant to send the system into
> > > suspend.
> > 
> > The standard Linux kernel does not decide when to suspend.  This is
> > usually controlled by systemd-logind.
> 
> Ben, were there any DRM related changes in the kernel which would
> explain, why 4.9.0-2 behaves differently then 4.9.0-1?
> 
> Marc-Robin, can you run (as root)
> systemd-analyze set-log-level debug
> then run journalctl -f
> and then trigger a suspend by letting the screensaver kick in.
> Then attach the output of journalctl.
> 
> Which graphics gard and desktop environment do you use?
> Jan 11 09:24:34 schroeder systemd[1]: Setting log level to debug.
Jan 11 09:24:34 schroeder systemd[1]: Sent message type=method_return 
sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1 
reply_cookie=1 error=n/a
Jan 11 09:24:34 schroeder systemd[1]: Got disconnect on private connection.
Jan 11 09:24:41 schroeder dhclient[2640]: DHCPREQUEST of 130.149.88.98 on eth0 
to 192.168.2.133 port 67
Jan 11 09:25:01 schroeder dhclient[2640]: DHCPREQUEST of 130.149.88.98 on eth0 
to 192.168.2.133 port 67
Jan 11 09:25:01 schroeder systemd[1]: systemd-journald.service: Got 
notification message from PID 327 (WATCHDOG=1)
Jan 11 09:25:01 schroeder CRON[3806]: pam_unix(cron:session): session opened 
for user root by (uid=0)
Jan 11 09:25:01 schroeder CRON[3807]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
Jan 11 09:25:01 schroeder CRON[3806]: pam_unix(cron:session): session closed 
for user root
Jan 11 09:25:03 schroeder systemd[1]: systemd-udevd.service: Got notification 
message from PID 368 (WATCHDOG=1)
Jan 11 09:25:03 schroeder systemd[1]: systemd-logind.service: Got notification 
message from PID 694 (WATCHDOG=1)

-- Logs begin at Thu 2018-01-11 09:28:20 CET. --
Jan 11 09:29:38 schroeder systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=387 
reply_cookie=0 error=n/a
Jan 11 09:29:38 schroeder systemd[1]: Startup finished in 6.955s (kernel) + 
1min 11.695s (userspace) = 1min 18.650s.
Jan 11 09:29:38 schroeder systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=StartupFinished cookie=388 
reply_cookie=0 error=n/a
Jan 11 09:29:38 schroeder systemd[1]: systemd-update-utmp-runlevel.service: 
cgroup is empty
Jan 11 09:29:38 schroeder systemd[1]: Sent message type=signal sender=n/a 
destination=n/a 
object=/org/freedesktop/systemd1/unit/systemd_2dupdate_2dutmp_2drunlevel_2eservice
 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=389 
reply_cookie=0 error=n/a
Jan 11 09:29:38 schroeder systemd[1]: Sent message type=signal sender=n/a 
destination=n/a 
object=/org/freedesktop/systemd1/unit/systemd_2dupdate_2dutmp_2drunlevel_2eservice
 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=390 
reply_cookie=0 error=n/a
Jan 11 09:29:38 schroeder systemd[1]: systemd-journald.service: Received 
EPOLLHUP on stored fd 41 (stored), closing.
Jan 11 09:29:38 schroeder systemd[1]: Got cgroup empty notification for: 
/system.slice/systemd-update-utmp-runlevel.service
Jan 11 09:29:38 schroeder systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1/agent 
interface=org.freedesktop.systemd1.Agent

Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-01-10 Thread Michael Biebl 
Control: tags -1 + moreinfo

On Wed, 10 Jan 2018 18:12:46 + Ben Hutchings 
wrote:
> Control: reassign -1 systemd
> 
> On Tue, 2018-01-09 at 11:50 +0100, Marc-Robin Wendt wrote:
> > Package: src:linux
> > Version: 4.9.65-3+deb9u1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > since linux-image-4.9.0-3-amd64 DKMS sends my system into suspend.
> 
> I guess you mean DPMS (Display Power Management System).
> 
> > Switching off the monitor causes suspend of the system. 
> > With Kernel-Versions linux-image-4.9.0-1-amd64 and linux-image-4.9.0-2-
> > amd64 I had no problems.
> > This problem is rather annoying, when my system starts the screensaver
> > after 10 min, the monitor switches off and sends the system into
> > suspend. Screensaver is not meant to send the system into suspend.
> 
> The standard Linux kernel does not decide when to suspend.  This is
> usually controlled by systemd-logind.

Ben, were there any DRM related changes in the kernel which would
explain, why 4.9.0-2 behaves differently then 4.9.0-1?

Marc-Robin, can you run (as root)
systemd-analyze set-log-level debug
then run journalctl -f
and then trigger a suspend by letting the screensaver kick in.
Then attach the output of journalctl.

Which graphics gard and desktop environment do you use?

-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-01-10 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + moreinfo
Bug #886731 [systemd] linux-image-4.9.0-4-amd64: DKMS sends system in suspend 
since linux-image-4.9.0-3-amd64
Added tag(s) moreinfo.

-- 
886731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#886731: linux-image-4.9.0-4-amd64: DKMS sends system in suspend since linux-image-4.9.0-3-amd64

2018-01-10 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 systemd
Bug #886731 [src:linux] linux-image-4.9.0-4-amd64: DKMS sends system in suspend 
since linux-image-4.9.0-3-amd64
Bug reassigned from package 'src:linux' to 'systemd'.
No longer marked as found in versions linux/4.9.65-3+deb9u1.
Ignoring request to alter fixed versions of bug #886731 to the same values 
previously set

-- 
886731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers