similar to: Restoring Windows to Minimzed State after Sleeping

I am running CentOS 6.6 on both a couple of servers and on a laptop. When I let the laptop sleep, window states and positions are restored correctly when I awaken it. However, when I shut down the laptop, later turn it on and log in, none of the terminal windows and directory windows are restored correctly to e.g. minimized state, instead they are restored to when they last were in use.

On 2016-02-18, H <agents at meddatainc.com> wrote: > I am running CentOS 6.6 on both a couple of servers and on a laptop. > When I let the laptop sleep, window states and positions are restored > correctly when I awaken it. However, when I shut down the laptop, > later turn it on and log in, none of the terminal windows and > directory windows are restored correctly to e.g.

https://bugs.freedesktop.org/show_bug.cgi?id=31139 Summary: Wake from sleep doesn't turn on display(s) Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi Lukas, Sorry for the delay, I finally found some time to reviewd and test the patches and found some issues (some of them might already be present in v4.15 without your patches though, I did not try). Test environment: - Branch switcheroo_devlink_v2 (commit v4.15-20-gb33d50c5c6ad) - Laptop: Clevo P651RA (nouveau uses PR3), lspci: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200

I''m having some issues with Workers dying after a period of several hours. Each worker runs a loop that asks Amazon SQS for work to do. If there is a message in the queue the work is completed (image processing, etc...); if there is no message the worker will sleep for X seconds (sleep 10, etc...). I''ve noticed that the workers will frequently exhibit two negative

After an S3 host resume, I''m seeing: [48002.772629] ACPI: Low-level resume complete [48002.772802] PM: Restoring platform NVS memory [48002.776143] xen_acpi_processor: Uploading Xen processor PM info [48002.776691] ------------[ cut here ]------------ [48002.776712] WARNING: CPU: 0 PID: 10235 at drivers/base/syscore.c:104 syscore_resume+0x9a/0xe0() [48002.776751] Interrupts enabled after

On Fri, Dec 04, 2015 at 02:37:50PM +0100, Petr Mladek wrote: > fill_balloon() and leak_balloon() manipulate only a limited number > of pages in one call. This is the reason why remove_common() calls > leak_balloon() in a while cycle. > > remove_common() is called also when the system is being frozen. > But fill_balloon() is called only once when the system is being >

On Fri, Dec 04, 2015 at 02:37:50PM +0100, Petr Mladek wrote: > fill_balloon() and leak_balloon() manipulate only a limited number > of pages in one call. This is the reason why remove_common() calls > leak_balloon() in a while cycle. > > remove_common() is called also when the system is being frozen. > But fill_balloon() is called only once when the system is being >

On Fri 23-02-18 15:47:36, Mark Rutland wrote: > Hi all, > > While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a > number of splats in the block layer: > > * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in > jbd2_trans_will_send_data_barrier > > * BUG: sleeping function called from invalid context at mm/mempool.c:320 > > * WARNING:

Hi, Keir, This patch is a bugfix for saving and restoring MSI/MSI-X across S3. Currently, Dom0''s PCI layer unmaps MSI when S3 and maps them back when resuming. However, this triggers unexpected behaviors. For example, if the drivers still holds that irq at the point of unmapping MSI, Xen will force unbind that pirq. But after resume, we have no mechanism to rebind that pirq. The device

https://bugs.freedesktop.org/show_bug.cgi?id=41608 Summary: Suspending/resuming system with cursor on external screen prevents said screen from restoring after resume Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium

I have a program where the process seems to be sleeping a lot (waiting on something) What would be the right approach to figure out via dtrace where it is sleeping and why it is sleeping? In my current process, using truss -D shows that it reaches pollsys and the whole process sleeps for 1.5 - 1.8 seconds before it awakes again. Its the only significant process running on this two CPU

On Mon, Feb 26, 2018 at 11:52:56AM +0100, Jan Kara wrote: > On Fri 23-02-18 15:47:36, Mark Rutland wrote: > > Hi all, > > > > While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a > > number of splats in the block layer: > > > > * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in > > jbd2_trans_will_send_data_barrier > >

On Mon, Feb 26, 2018 at 11:52:56AM +0100, Jan Kara wrote: > On Fri 23-02-18 15:47:36, Mark Rutland wrote: > > Hi all, > > > > While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a > > number of splats in the block layer: > > > > * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in > > jbd2_trans_will_send_data_barrier > >

Hi, after solving the issue I had with a DVB tuner I tested again suspending and resuming from S3. I am now running Xen 4.2.0 and have applied patches [1] and [2] (any idea why they are still not in mainline?) over a 3.5.3 kernel. I only tried once since I upgraded my Xen, but after resuming I got the following back trace: [ 142.267299] pcieport 0000:00:1c.5: wake-up capability enabled by ACPI

On Tue, Aug 28, 2018 at 10:23:24AM +0800, Daniel Drake wrote: > On Fri, Aug 24, 2018 at 11:42 PM, Peter Wu <peter at lekensteyn.nl> wrote: > > Are these systems also affected through runtime power management? For > > example: > > > > modprobe nouveau # should enable runtime PM > > sleep 6 # wait for runtime suspend to kick in > >

On 10/20/2013 10:34 AM, Fengguang Wu wrote: > Greetings, > > I got the below dmesg and the first bad commit is > > commit 3ab098df35f8b98b6553edc2e40234af512ba877 > Author: Jason Wang <jasowang at redhat.com> > Date: Tue Oct 15 11:18:58 2013 +0800 > > virtio-net: don't respond to cpu hotplug notifier if we're not ready > > We're

Hi all, While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a number of splats in the block layer: * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in jbd2_trans_will_send_data_barrier * BUG: sleeping function called from invalid context at mm/mempool.c:320 * WARNING: CPU: 0 PID: 0 at block/blk.h:297 generic_make_request_checks+0x670/0x750 ... I've included the

Hi all, While fuzzing arm64/v4.16-rc2 with syzkaller, I simultaneously hit a number of splats in the block layer: * inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-R} usage in jbd2_trans_will_send_data_barrier * BUG: sleeping function called from invalid context at mm/mempool.c:320 * WARNING: CPU: 0 PID: 0 at block/blk.h:297 generic_make_request_checks+0x670/0x750 ... I've included the

Hi Jason, On Tue, Oct 22, 2013 at 04:35:32PM +0800, Jason Wang wrote: > On 10/20/2013 10:34 AM, Fengguang Wu wrote: > > Greetings, > > > > I got the below dmesg and the first bad commit is > > > > commit 3ab098df35f8b98b6553edc2e40234af512ba877 > > Author: Jason Wang <jasowang at redhat.com> > > Date: Tue Oct 15 11:18:58 2013 +0800 > >