Bug 69001 - "Failed to alloc lowmem for boot params" in EFI boot stub
Summary: "Failed to alloc lowmem for boot params" in EFI boot stub
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: EFI
Classification: Unclassified
Component: Boot (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: EFI Virtual User
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-19 18:54 UTC by Matt Fleming
Modified: 2014-09-19 09:44 UTC (History)
2 users (show)

See Also:
Kernel Version: v3.12.7
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lowmem patch (1.19 KB, patch)
2014-01-19 18:54 UTC, Matt Fleming
Details | Diff

Description Matt Fleming 2014-01-19 18:54:18 UTC
Created attachment 122641 [details]
lowmem patch

Bastian Beischer is hitting the following error message when using the EFI boot stub on his Lenovo Thinkpad W520,


        status = low_alloc(0x4000, 1, (unsigned long *)&boot_params);
        if (status != EFI_SUCCESS) {
                efi_printk("Failed to alloc lowmem for boot params\n");
                return NULL;
        }

which the attached patch may fix.

Bastian, if could provide a dmesg from a working kernel boot and describe how you built the kernels you've tested that would be very helpful.
Comment 1 Bastian Beranek 2014-01-19 19:04:18 UTC
Hey Matt,

to be clear:

I got the "Failed to alloc lowmem for boot params" message with 9c612a77032a98b264d12fd6e3df2ca530d968d2, but I didn't get it with any of the other bad kernel builds I tried in my bisect.

Whether or not the error message appears sporadically or just with 9c612a7 requires further testing.

However, I did see other people in the Arch bug report at

https://bugs.archlinux.org/task/33745?project=1&order=lastedit&sort=desc

mention that error message with earlier kernel versions.
Comment 2 Matt Fleming 2014-09-19 09:30:07 UTC
Bastian, is this still occuring?
Comment 3 Bastian Beranek 2014-09-19 09:42:00 UTC
No I don't think so. Haven't seen this for a long while.
Comment 4 Matt Fleming 2014-09-19 09:44:16 UTC
Cool. Closing this report then. Feel free to re-open if it ever comes back.

Note You need to log in before you can comment on or make changes to this bug.