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]
Message-Id: <200905260138.12880.rjw@sisk.pl>
Date:	Tue, 26 May 2009 01:38:12 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Cc:	Richard Atterer <richard@...9.atterer.net>,
	linux-kernel@...r.kernel.org,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: [Bug #13371] s2disk hangs with kernel 2.6.29 and later, SATA, Gigabyte EG45M-DS2H

On Tuesday 26 May 2009, Bartlomiej Zolnierkiewicz wrote:
> On Tuesday 26 May 2009 01:11:40 Rafael J. Wysocki wrote:
> > On Monday 25 May 2009, Richard Atterer wrote:
> > > On Mon, May 25, 2009 at 04:30:21PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > > Hmm, we added ACPI NVS memory handling there and some machines seem
> > > > to have trouble with it.  I think it would be worth to check it first.
> > > > 
> > > > Richard, could you try s2disk on some recent 2.6.30-rc kernel while
> > > > booting using "acpi_sleep=s4_nonvs"?
> > > 
> > > I just tried that with 2.6.30-rc7, unfortunately it doesn't make any 
> > > difference.
> > > 
> > > It turns out that if I wait long enough (just over 1 minute) both during 
> > > suspend and resume, I *am* able to suspend and resume the machine. I have 
> > > to manually turn it off or reset it though.
> > > 
> > > Another possibly interesting observation: My DVD writer apparently gets 
> > > reset before the 1-minute hang and my USB hub after the hang.
> > 
> > You replied to Jeff that hibernation worked with CONFIG_IDE=n.  What was wrong
> > with that test?
> 
> It didn't work.  That was wrong.
> 
> Please at least read the current thread before asking such questions.

Sorry, I was wondering why Richard told Jeff that the test worked at that time.

I should have asked differently or something, perhaps.

Best,
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