Matthew Garrett ([personal profile] mjg59) wrote2013-07-02 15:50
Entry tags:

Explaining Intel Rapid Start Technology

Recent Intel-based systems often implement something called Intel Rapid Start Technology. Like many things with the word "Technology" in the name, there's a large part of this that's marketing. The relatively small amount of technical documentation available implies that it's tied to your motherboard chipset and CPU, but as far as I can tell it's entirely implemented in firmware and could work just as well on, say, a Cyrix on a circa 1996 SIS-based motherboard if someone wrote the BIOS code[1]. But since nobody has, we're stuck with the vendors who've met Intel's requirements and licensed the code.

The concept of IRST is pretty simple. There's a firmware mechanism for setting a sleep timeout. If you suspend your computer and this timeout expires, it'll resume. However, instead of handing control back to the OS, the firmware just copies the entire contents of RAM to a special partition and turns the computer off. Next time you hit the power button, the firmware dumps the partition contents back into RAM and resumes as if nothing had changed. This takes a few seconds longer than resume from S3 but is far faster than resume from hibernation since it starts the moment the system gets power.

At a more technical level, it's a little more complicated. The first thing to know about this feature is that it's entirely invisible unless your hard drive is set up correctly. There needs to be a partition that's at least the size of your system's physical RAM. For GPT systems, this needs to have a type GUID of D3BFE2DE-3DAF-11DF-BA-40-E3A556D89593. For MBR systems, you need a partition type of 0x84[2]. If the firmware doesn't find an appropriate partition then the OS will get no indication that the firmware supports it. Boo.

(The second thing is that it seems like it really does have to be on an SSD, and if you try to do this on spinning media your firmware will ignore it anyway)

If all the prerequisites are in place, an ACPI device with an HID of INT3392 will exist. It has four methods associated with it: GFFS, SFFS, GFTV and SFTV. GFFS returns an integer representing the events that will cause the system to wake up from S3 and suspend to SSD. The system will wake after the timeout expires if bit 0 is set, and will wake when the battery becomes critically low if bit 1 is set. The other bits appear to be unused at the moment[3]. SFFS sets the wakeup events, using the same bit values as GFFS. GFTV returns an integer containing the current wakeup timeout in minutes. SFTV sets it. Values above 1440 (ie, 24 hours) seem to be considered invalid - if I set them the value instead ends up as 10 and the timeout flag gets cleared from the wakeup events field.

I've submitted a patch that adds a sysfs interface for setting these values, and unless anyone objects it'll probably end up in 3.11. There's still the remaining question of how userspace should make use of these, and also how installers should behave when it comes to systems that support IRST. As previously mentioned, there's no obvious indication to the OS that the feature is supported unless the appropriate partition already exists. The easiest way to deal with this is for installers to default to retaining any partitions with the magic IDs, but I'm still looking into whether it's possible to get the firmware to cough up some more information so it can be created automatically even if the drive's entirely blank.

And now, having got this working on a test machine, I just need to split my Thinkpad's swap partition in half and make sure it works here as well. Woo.

[1] Note: I am not going to do this.
[2] Conveniently, the same as the partition type that APM systems used for suspend to disk back when dubstep hadn't been invented yet
[3] At least, if you attempt to set them they get ignored.

Threat to dm-crypt

(Anonymous) 2013-07-03 18:31 (UTC)(link)
What if you had encrypted volumes or swap open when your computer did this? Your keys get written out to disk in plaintext I would imagine. Along with other stuff from mlock()d RAM like unlocked keyrings for GNOME or GPG, your browser's memory cache and session cookies, open documents, ...

Re: Threat to dm-crypt

(Anonymous) - 2013-07-03 19:26 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-03 20:07 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-05 00:02 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-05 11:55 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-08 03:03 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-03 20:14 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-04 01:08 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) - 2013-07-04 10:13 (UTC) - Expand

Re: Threat to dm-crypt

(Anonymous) 2013-07-04 17:13 (UTC)(link)
You should test it to see, but it might not write the data out unencrypted.

Also, many SSDs these days have strong encryption tied to your BIOS disk password. Not as safe as dm-crypt, but still decent.

What goes around comes around

[identity profile] mas90.livejournal.com 2013-07-03 19:12 (UTC)(link)
My family's IBM PS/1 circa 1994 had something very similar ("Rapid Resume").

Re: What goes around comes around

(Anonymous) 2013-07-04 05:56 (UTC)(link)
Except without the mandatory SSD requirement (I guess)
ext_34812: (Default)

Re: What goes around comes around

[identity profile] boggyb.livejournal.com 2013-07-09 19:24 (UTC)(link)
I used to have an IBM Aptiva with this feature, which as it happens was indeed a circa 1996 SIS-based system (though not with a Cyrix processor).

Re: What goes around comes around

(Anonymous) - 2013-07-09 19:27 (UTC) - Expand

Requires SSD?

[personal profile] steveriley 2013-07-03 23:08 (UTC)(link)
Matthew writes...
(The second thing is that it seems like it really does have to be on an SSD, and if you try to do this on spinning media your firmware will ignore it anyway)

Sounds like an effort to goose the sales of SSDs. I can't think of any technical reason that IRST wouldn't work on a spining disk. I can think of a marketing reason, though -- it won't feel so rapid any more.

Re: Requires SSD?

(Anonymous) - 2013-07-04 10:34 (UTC) - Expand

Re: Requires SSD?

(Anonymous) 2013-07-04 09:07 (UTC)(link)
One marginally technical reason is that the write-to-disk operation will occur when the user thinks the system is off. It is less risky to write to an SSD in a moving backpack than spinning up a hard drive.

Interesting post

(Anonymous) 2013-07-04 00:15 (UTC)(link)
Interesting post, you're great at writing about these hardware/BIOS related things.

You brought up a point relating to trusting your firmware. Since it's probably proprietary, and since it's not possible to trust proprietary stuff, maybe you can get in on the coreboot team and give the world a Free Software BIOS? Wouldn't that be awesome?

The bonus is that you wouldn't have to fight with arbitrary binary code, and you could implement awesome things!

Cheers,
James

Quirks?

(Anonymous) 2013-07-04 00:33 (UTC)(link)
What does IRST do about video cards and other devices that need some kind of re-initialization on resume?

Intel Rapid Start Technology

(Anonymous) 2013-07-04 06:28 (UTC)(link)
Facing a problem with my Fujitsu UH572 and it is pretty related with this (great) post. After a board replacement intel controller is refusing to see the disk as hybrid and especially the SSD partition. Intel was using a 8G volume inside this 30G SSD partition for fastboot - but i dont use windows so i've encrypted the SSD partition and installed linux.

The fujitsu service is telling me that the disk is OK! but they are working on found out why the SSD partition has been disappeared.

Is it possible that this feature (intel rapid start technology) is being glued with the specific board or is it possible that a UEFI setting exist that tells the board the specs of the disk ?

It seems idiotic to me to exist such a connection but its being 3 weeks now and none of the fujitsu technicians cant reply to me on this.

btw This is my second UH572. I had the same problem with the board on the first but they have replaced it as the problem occurred 3 days after the purchase of it

Thanks for this!

(Anonymous) 2013-07-04 06:54 (UTC)(link)
I don't know that I will actually use it, but I have wanted to see if I could get this working for some time now. I had tried before after finding a blog post of someone else who had gotten this to work. But I failed at that time since I didn't understand that gdisk's 8300 was actually representative of a type GUID.

I have an SSD in my machine that is currently blank while I try to figure out what to use it for. So I think I will leave this enabled for a bit and see how it goes. So far so good.

Unfortunately, the firmware only allows for up to 3 hours before the IRST kicks in. You say that 24 hours is invalid, but does adjustment with your patch allow you to go over the bios listed max at all?

PS D'oh, I got the anti-spam question wrong...

Re: Thanks for this!

(Anonymous) - 2013-07-04 19:56 (UTC) - Expand

Re: Thanks for this!

(Anonymous) - 2013-07-04 21:43 (UTC) - Expand

Critical level

(Anonymous) 2013-07-05 03:00 (UTC)(link)
So I understand that a value of 3 in wakeup_events will enable transition into hibernation from both timer events as well as reaching a "critical level".

But what is the "critical level"? Can I set this myself, or is it hard coded into the firmware?

Re: Critical level

(Anonymous) - 2013-07-05 23:24 (UTC) - Expand

sysfs Patches

(Anonymous) 2013-07-05 07:42 (UTC)(link)
Any patches yet? Would love to backport them to my distro kernel to configure and test this. The Windows GUI is horrible.

Re: sysfs Patches

(Anonymous) 2013-07-05 15:08 (UTC)(link)
There is a link to the patches in the blog post. They work just fine as far as I can tell so far. But yu should be aware that this is really just adding Linux userspace configuration ability. The patches are not required at all to get this functioanlity going. It just makes it much nicer to deal with.

Working only with UEFI?

(Anonymous) 2013-07-11 11:35 (UTC)(link)
Hi there,

Sorry if this is a stupid question. Does this stuff only work when you boot in UEFI mode, or also with legacy BIOS? Asking because I am using a Samsung laptop, and I am forced booting with legacy BIOS if I want to load the samsung-laptop-module.

Second question, should I create some filesystem on the partition, or it does not matter?

Cheers,
Alessandro

Re: Working only with UEFI?

(Anonymous) - 2013-07-11 11:58 (UTC) - Expand

Re: Working only with UEFI?

(Anonymous) - 2013-07-11 20:55 (UTC) - Expand

Just Works

(Anonymous) - 2013-07-13 14:50 (UTC) - Expand

Re: Just Works

[identity profile] psusi [launchpad.net] - 2013-09-26 17:24 (UTC) - Expand

Was working with a Medion Akoya i7

(Anonymous) 2013-07-15 08:49 (UTC)(link)
First I wasn't sure what that iFFS entry was in my BIOS until I detected this website http://blog.adios.tw/2012/10/funtoo-linux-and-intel-rapid-start.html which explains it pretty well.

The good thing about it is that it is working totally separate from the OS. The bad thing - if you change your RAM size you have to grow the partition!

I have tested it but it wasn't really quicker as normal hibernate and hibernating 8 Gig or more takes a while (~20 seconds). Booting the system from scratch is faster (~10 seconds). So I stick with suspend-to-ram (~1 sec) or just plain boot on SSD anyway.

HP

Testing in other kernels than mainline

(Anonymous) 2013-07-21 22:46 (UTC)(link)
Hi,

I was anxiously waiting for someone with some insight on this tech to develop some way of setting up the timeout value on linux, thanks a lot!

Since I didn't want to build the whole kernel to test the module, I isolated it and set up a dkms script for it along with some upstart script to set values on boot.

https://kassick@bitbucket.org/kassick/intel-rst.git
(clone and run setup.sh )

I've just installed it on Quantal/3.5.0-31-generic, seems to work fine; I'll keep you posted.

Kassick.

Re: Testing in other kernels than mainline

(Anonymous) 2013-07-21 23:06 (UTC)(link)
https://bitbucket.org/kassick/intel-rst/

Re: Testing in other kernels than mainline

(Anonymous) - 2013-07-22 14:21 (UTC) - Expand

How is this anything new?

[identity profile] psusi [launchpad.net] 2013-09-26 17:36 (UTC)(link)
The OS can already do a hybrid suspend and set an ACPI wakeup timer and transition to S5 when it fires. Personally I'd rather the data be written to the disk at suspend time rather than while the laptop is in your backpack, and not have to have a separate partition dedicated only to hibernation.

Re: How is this anything new?

[identity profile] psusi [launchpad.net] 2013-09-27 15:20 (UTC)(link)
So they basically violate the standard and transition to S4 without telling the OS, then jump to the S3 wakeup vector, so it thinks the system was in S3 the whole time?

This other document I found here: http://software.intel.com/en-us/articles/what-is-intel-rapid-start-technology

Says that the software takes steps to reduce the set of pages that must be saved. Is there an as yet undescribed acpi method to send the bios a memory usage map before entering S3, and it defaults to saving all of system ram under Linux, which would make it slower than software hibernate?

Re: How is this anything new?

(Anonymous) - 2013-10-21 20:28 (UTC) - Expand

Works with rotary disc

[personal profile] loic2105 2014-03-07 11:21 (UTC)(link)
Hi,

I'm rather happy to say that on my brand new laptop, IRST works with a rotating disk. I'm less happy to say that my bios+disk need 80s to save and restore the RAM. I hope I'll find, as PSUSI says above, an as yet undescribed acpi method to send the bios a memory usage map before entering S3. The idea is to suspend to disk using (u)swsusp or TuxOnIce and instead of turning off the computer, just writing the kernel image and a few MB (kB ?) of memory to disk using IRST.

Loïc

Re: Works with rotary disc

[personal profile] loic2105 2014-03-07 13:25 (UTC)(link)
A couple of observations: 1) 80s is at the end of the disc, it will be better once I get the partition at the beginning of the disc. 2) The partition is certainly not zeroed out, this means that it is done with "trim" for SSD.

Loïc