lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 3 Apr 2008 17:48:57 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Didier Raboud <didier@...oud.com>
Cc:	linux-kernel@...r.kernel.org, debian-kernel@...ts.debian.org
Subject: Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

On Thursday, 3 of April 2008, Didier Raboud wrote:
> Le mercredi, 2 avril 2008 14.06:29 Didier Raboud, vous avez écrit :
> > Le mardi, 1 avril 2008 23.22:35 Rafael J. Wysocki, vous avez écrit :
> > > On Tuesday, 1 of April 2008, Didier Raboud wrote:
> > > > Le mardi, 1 avril 2008 23.11:15 Rafael J. Wysocki, vous avez écrit :
> > > > > (...)
> > > > > Can you please test the in-kernel hibernation, then?
> > > > >
> > > > > Rafael
> > > >
> > > > Hi,
> > > >
> > > > would like to. How ?
> > > >
> > > > # echo -n disk > /sys/power/state
> > >
> > > Yes, should work without the "-n", too.  Of course, you have to use the
> > > 'resume=' kernel command line argument for this to work.
> > >
> > > Perhaps increase the console log level before that.
> > >
> > > Thanks,
> > > Rafael
> >
> > Ok. I found a "better" way to do it : just uninstall uswsusp and let
> > kpowersave use hal to use suspend :-)
> >
> > Anyway, so far so good (with USB_SUSPEND not set), no hang. I will test
> > with USB_SUSPEND set and the incoming 2.6.25-rc8.
> >
> > Regards,
> >
> > Didier
> 
> So far so good too with "stock" Debian Kernel (2.7.25-rc7-amd64) with 
> USB_SUSPEND set. No hang.
> 
> The kernel suspend is less user-friendly than uswsusp though...
> 
> So I bet there is a bug in uswsusp's kernel part ?

It's almost the same as the in-kernel one, especially as far as the resume is
concerned.  The simplest explanation coming to mind is that the image is
somehow damaged in the uswsusp case.

You can use the uswsusp's checksumming to verify that, though.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ