linux-kernel - Re: Some sort corruption of my Thermal Subsystem after suspend to ram

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: <200805011457.51238.rjw@sisk.pl>
Date:	Thu, 1 May 2008 14:57:49 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Len Brown <lenb@...nel.org>, Gabriel C <nix.or.die@...glemail.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-pm@...ts.linux-foundation.org, pavel@...e.cz
Subject: Re: Some sort corruption of my Thermal Subsystem after suspend to ram

On Thursday, 1 of May 2008, Matthew Garrett wrote:
> On Thu, May 01, 2008 at 01:57:58AM -0400, Len Brown wrote:
> 
> > I'm not aware of a native Linux device driver that talks to this device
> > (nor can I think of a useful purpose for such a driver)
> > So it seems what is in play here is any BIOS code that talks to this device,
> > and Linux's standard PCI config space restore.
> 
> Perhaps we should be more aggressive about restoring PCI config space if 
> there's no driver bound to a device. The alternative in this case would 
> seem to be to write a driver for this device that does nothing other 
> than handle suspend/resume.

Well, we have default suspend/resume for PCI devices.  They are called for
devices that have no drivers bound to them and execute
pci_restore_state()/pci_restore_state(), among other things.  Isn't that
sufficient?

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/