On Sun, 19 Apr 2015 08:46:14 +0200 Heinz Diehl wrote:
> On 18.04.2015, Pete Travis wrote:
>
> > Do consider the audience you sent this mail to, though.
> > It isn't the power management subsystem developer community..
>
> This is what I have been recommended to do after reporting a S2D bug on
On 19.04.2015, Ranjan Maitra wrote:
> Btw, do you have this issue with CentOS (they run 3.10 kernels).
The problem occurs with the latest Fedora kernels as well as with vanilla
3.19.x and 4.0.0. I'm on F21 on this machine (XFCE spin).
--
users mailing list
users@lists.fedoraproject.org
To u
On Sun, 19 Apr 2015 16:50:09 +0200 Heinz Diehl wrote:
> On 19.04.2015, Ranjan Maitra wrote:
>
> > Btw, do you have this issue with CentOS (they run 3.10 kernels).
>
> The problem occurs with the latest Fedora kernels as well as with vanilla
> 3.19.x and 4.0.0. I'm on F21 on this machine (XFCE
On 19.04.2015, Ranjan Maitra wrote:
> When did it start. For me, my problems started with kernel 3.16 or so
> (and that too, only on some machines).
On my Asus Laptop, both S2R and S2D has been working flawlessly ever since
(running Arch) - both with old and new kernels. On my PC, S2R works, but
Hi,
> On my Asus Laptop, both S2R and S2D has been working flawlessly ever since
> (running Arch) - both with old and new kernels. On my PC, S2R works, but the
> machine can't properly wake from S2D. It's a brand new machine, and I've not
> tried something older than 3.19.2. To date, I'm on 4.0.0.
On 2015-04-19 at 11:08:25 Ranjan Maitra wrote:
> Hi,
>
> > On my Asus Laptop, both S2R and S2D has been working flawlessly
> > ever since (running Arch) - both with old and new kernels. On my
> > PC, S2R works, but the machine can't properly wake from S2D. It's a
> > brand new machine, and I've n
>
> I don't know if it's interesting but I run kernel
> 3.19.3-200.fc21.x86_64 on Lenovo L430. I prefer suspend to hibernate
> and that has worked flawlessly. Just tried to hibernate and it didn't
> work. On my laptop I have exchanged 500 GB HDD with 500 GB SDD and I
> come back from suspend almos
On 04/19/2015 12:46 AM, Heinz Diehl wrote:
On 18.04.2015, Pete Travis wrote:
Do consider the audience you sent this mail to, though.
It isn't the power management subsystem developer community..
This is what I have been recommended to do after reporting a S2D bug on the
Linux
kernel bugzill
On 2015-04-19 at 12:36:29 Ranjan Maitra wrote:
> >
> > I don't know if it's interesting but I run kernel
> > 3.19.3-200.fc21.x86_64 on Lenovo L430. I prefer suspend to hibernate
> > and that has worked flawlessly. Just tried to hibernate and it
> > didn't work. On my laptop I have exchanged 500 G
On 04/19/2015 12:08 PM, Erik P. Olsen wrote:
On 2015-04-19 at 12:36:29 Ranjan Maitra wrote:
I don't know if it's interesting but I run kernel
3.19.3-200.fc21.x86_64 on Lenovo L430. I prefer suspend to hibernate
and that has worked flawlessly. Just tried to hibernate and it
didn't work. On my
> >> Do consider the audience you sent this mail to, though.
> >> It isn't the power management subsystem developer community..
> > This is what I have been recommended to do after reporting a S2D bug on the
> > Linux
> > kernel bugzilla:
> >
> > "Posting to the PM mailing list should be appropria
On Sun, 19 Apr 2015 20:08:08 +0200 "Erik P. Olsen" wrote:
> On 2015-04-19 at 12:36:29 Ranjan Maitra wrote:
>
> > >
> > > I don't know if it's interesting but I run kernel
> > > 3.19.3-200.fc21.x86_64 on Lenovo L430. I prefer suspend to hibernate
> > > and that has worked flawlessly. Just tried
On 04/19/2015 12:19 PM, Ranjan Maitra wrote:
On Sun, 19 Apr 2015 20:08:08 +0200 "Erik P. Olsen" wrote:
On 2015-04-19 at 12:36:29 Ranjan Maitra wrote:
I don't know if it's interesting but I run kernel
3.19.3-200.fc21.x86_64 on Lenovo L430. I prefer suspend to hibernate
and that has worked f
On 19.04.2015, Ranjan Maitra wrote:
> OK, if you see my post, F is now (since F20) designed by default to not
> resume from hibernate.
Now, THAT would be interesting to know what exactly has been done to achieve
this behaviour!
In my case, the machine resumes just fine from S2D about 6 times ou
On Sun, 19 Apr 2015 12:31:21 -0600 jd1008 wrote:
>
>
> On 04/19/2015 12:19 PM, Ranjan Maitra wrote:
> > On Sun, 19 Apr 2015 20:08:08 +0200 "Erik P. Olsen"
> > wrote:
> >
> >> On 2015-04-19 at 12:36:29 Ranjan Maitra wrote:
> >>
> I don't know if it's interesting but I run kernel
> 3.
On 04/19/2015 12:46 PM, Ranjan Maitra wrote:
On Sun, 19 Apr 2015 12:31:21 -0600 jd1008 wrote:
On 04/19/2015 12:19 PM, Ranjan Maitra wrote:
On Sun, 19 Apr 2015 20:08:08 +0200 "Erik P. Olsen" wrote:
On 2015-04-19 at 12:36:29 Ranjan Maitra wrote:
I don't know if it's interesting but I run
On Sun, 19 Apr 2015 14:24:27 -0600
jd1008 wrote:
> I have 2 swap devices that together add up to more than 16GB.
I vaguely recall reading that the swap where the image is stored has
to be a single partition.
> My RAM is 8GB.
> So, I will be adding the boot params:
> resume=/dev/sda4 resume=/dev
On 04/19/2015 04:12 PM, stan wrote:
On Sun, 19 Apr 2015 14:24:27 -0600
jd1008 wrote:
I have 2 swap devices that together add up to more than 16GB.
I vaguely recall reading that the swap where the image is stored has
to be a single partition.
My RAM is 8GB.
So, I will be adding the boot pa
18 matches
Mail list logo
