linux-kernel - Re: swsusp hangs on headless resume-from-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: <200607281055.47526.rjw@sisk.pl>
Date:	Fri, 28 Jul 2006 10:55:47 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Al Boldi <a1426z@...ab.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: swsusp hangs on headless resume-from-ram

On Wednesday 26 July 2006 23:34, Al Boldi wrote:
> Rafael J. Wysocki wrote:
> > On Wednesday 26 July 2006 21:06, Al Boldi wrote:
> > > swsusp is really great, most of the time.  But sometimes it hangs after
> > > coming out of STR.  I suspect it's got something to do with display
> > > access, as this problem seems hw related.  So I removed the display
> > > card, and it positively does not resume from ram on 2.6.16+.
> > >
> > > Any easy fix for this?
> >
> > I have one idea, but you'll need a patch to test.  I'll try to prepare it
> > tomorrow.
> >
> > I guess your box is an i386?
> 
> That should be assumed by default :)

I had hoped I would be able to test it somewhere, but I couldn't.  I hope
it will compile. :-)

If it does, please send me the output of dmesg after a fresh boot.

Rafael


--
 arch/i386/kernel/setup.c |   34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

Index: linux-2.6.18-rc2/arch/i386/kernel/setup.c
===================================================================
--- linux-2.6.18-rc2.orig/arch/i386/kernel/setup.c	2006-07-28 10:27:44.000000000 +0200
+++ linux-2.6.18-rc2/arch/i386/kernel/setup.c	2006-07-28 10:51:33.000000000 +0200
@@ -1301,14 +1301,33 @@ void __init remapped_pgdat_init(void)
 	}
 }
 
+/* Mark pages corresponding to given address range as nosave */
+static void __init
+e820_mark_nosave_range(unsigned long start, unsigned long end)
+{
+	unsigned long pfn, max_pfn;
+
+	if (start >= end)
+		return;
+
+	printk("Nosave address range: %016lx - %016lx\n", start, end);
+	max_pfn = end >> PAGE_SHIFT;
+	for (pfn = start >> PAGE_SHIFT; pfn < max_pfn; pfn++)
+		if(pfn_valid(pfn))
+			SetPageNosave(pfn_to_page(pfn));
+}
+
 /*
  * Request address space for all standard RAM and ROM resources
  * and also for regions reported as reserved by the e820.
+ *
+ * Mark memory gaps and the reserved regions as nosave.
  */
 static void __init
 legacy_init_iomem_resources(struct resource *code_resource, struct resource *data_resource)
 {
 	int i;
+	unsigned long paddr;
 
 	probe_roms();
 	for (i = 0; i < e820.nr_map; i++) {
@@ -1344,6 +1363,21 @@ legacy_init_iomem_resources(struct resou
 #endif
 		}
 	}
+
+	paddr = (e820.map[0].addr + e820.map[0].size) & ~(PAGE_SIZE - 1);
+	for (i = 1; i < e820.nr_map; i++) {
+		struct e820entry *ei = &e820.map[i];
+		unsigned long base;
+
+		/* Check if we have any nosave pages here */
+		base = (ei->addr + PAGE_SIZE - 1) & ~(PAGE_SIZE - 1);
+		if (paddr < ei->addr)
+			e820_mark_nosave_range(paddr, base);
+
+		paddr = (ei->addr + ei->size) & ~(PAGE_SIZE - 1);
+		if (ei->type != E820_RAM)
+			e820_mark_nosave_range(base, paddr);
+	}
 }
 
 /*
-
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/