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: <200901130907.13820.borntraeger@de.ibm.com>
Date:	Tue, 13 Jan 2009 09:07:13 +0100
From:	Christian Borntraeger <borntraeger@...ibm.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	lkml <linux-kernel@...r.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@...e.de>, linux-usb@...r.kernel.org
Subject: Re: Regression 2.6.28-git: suspend/resume failure. git bisected to usb suspend/resume patch

Am Montag 12 Januar 2009 schrieb Rafael J. Wysocki:
> > Please try if suspend-resume works for you if you make commit
> > fa58d305d9925b01830e535896a7227a868a9e15
> > (PCI PM: Add suspend counterpart of pci_reenable_device) the head of your
> > tree ('git checkout -b test-branch 
fa58d305d9925b01830e535896a7227a868a9e15').
> > 
> > If it does, please check the same for commit
> > 571ff7584bb9e05fca0eb79752ae55a46faf3a98
> > (PCI PM: Power-manage devices without drivers during suspend-resume).
> 
> Ah, please do the above with the USB commit
> a0d4922da2e4ccb0973095d8d29f36f6b1b5f703 reverted.

Will do.

In the meantime I have bisected another problem: 
commit 7503bfbae89eba07b46441a5d1594647f6b8ab7d
Author: Mike Travis <travis@....com>
Date:   Sun Jan 4 05:18:09 2009 -0800

    cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write

but I just see that this is already known.
O dear. How many patches do we know that broke S2R in this merge window? 4? 5?


Christian
--
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