[PATCH 1/2] x86: make e820 output consistent with other resource printks
This tidies e820 output by adding an "e820" prefix and printing ranges similarly to the way we print struct resource with %pR, e.g.: - BIOS-e820: 0000000000000000 - 000000000009f400 (usable) + BIOS-e820: [mem ...Message posted on the February 13th, 2012 - 7:10 PM ET
[PATCH 1/2] x86: change names of e820 memory map type
E820_RAM -> E820_TYPE_RAM E820_ACPI-> E820_TYPE_ACPI ... names like E820_RAM is conflict-prone, because user is more likely to define a macro like this if did not strongly aware this name have been defined by e820.h Signed-off-by: liguang ...Message posted on the March 1st, 2013 - 12:30 AM ET
early microcode on amd is broken when no initramfs provided
When CONFIG_MICROCODE_EARLY is enabled on AMD but no initramfs is provided in the bootmanager (grub2), the system hangs here: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing ...Message posted on the July 9th, 2013 - 12:50 PM ET
Use of memmap= to forcibly recover memory in 3GB-4GB range - is this safe?
I have a Foxconn mainboard that supports 64-bit CPUs and DDR2 memory up to 4GB. Two days ago I bought memory to max out the memory capacity. When I booted up the system with my new memory sticks, I found out that the system only presented around ...Message posted on the January 15th, 2013 - 8:50 PM ET
Bug#685047: Debian Wheezy B1 installer for amd64 fails during base system install reporting unmet (awk) dependencies.
Package: installation-reports Boot method: netinst running from USB thumbdrive Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta1/amd64/iso-cd/debian-wheezy-DI-b1-amd64-netinst.iso ...Message posted on the August 16th, 2012 - 1:10 AM ET
x86: early boot crash: "alloc_low_page: ran out of memory" (bisected)
I'm getting a 100% reproducible panic early in boot: [ 0.000000] Kernel panic - not syncing: alloc_low_page: ran out of memory I'm not sure why I didn't run in to this until now. I think there are a couple of config options that need to get ...Message posted on the August 9th, 2013 - 7:20 PM ET
[BUG?] mtrr sanitizer fails on Latitude E6230
I recently got a Dell Latitude E6230 (Ivy Bridge i7-3540M) and noticed that the mtrr sanitizer failed on it: snip ==Linux version 3.12.0 (mikpe@barley) (gcc version 4.8.3 20131017 (prerelease) (GCC) ) #1 SMP Wed Nov 6 09:46:02 CET 2013 Command ...Message posted on the November 6th, 2013 - 4:20 AM ET
x86: Regression in 3.6.4, bisected to "Exclude E820_RESERVED regions..."
Hello, I've just bisected a problem with 3.6.4. I had to revert commit 54ce8ce298f382a06186cb4672ad6aa090b050b6 (1bbbbe779aabe1f0768c2bf8f8c0a5583679b54a in mainline), otherwise my box didn't boot. I can't provide any output, because I don't see ...Message posted on the October 29th, 2012 - 5:30 AM ET
Bootup regression introduced by 7bd0b0f0da3b1ec11cbcc798eb0ef747a1184077 ("memblock: Reimplement memblock allocation using reverse free area iterato") in v3.3-rc0
Hey, With that patch I get this when trying to launch a 4GB xen guest: kernel="/mnt/lab/latest/vmlinuz" ramdisk="/mnt/lab/latest/initramfs.cpio.gz" extra="console=hvc0 debug earlyprintk=xen" memory@96 maxmem92 ...Message posted on the January 10th, 2012 - 3:40 PM ET
[GIT PULL] x86/mm changes for v3.3
Linus, Please pull the latest x86-mm-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus out-of-topic modifications in x86-mm-for-linus: include/linux/mm.h # 54c29c6: mm, x86: ...Message posted on the January 5th, 2012 - 10:20 AM ET
[PATCH] To crash dump, we need keep other memory type except E820_RAM, because other type come from BIOS or firmware is used by other code(for example: PCI_MMCONFIG).
From aebc336baa7ec2d4ccb6f21166770c7d2ee26cba Mon Sep 17 00:00:00 2001 From: jzha144 <email@example.com> Date: Wed, 31 Oct 2012 08:51:18 +0800 Subject: [PATCH] To crash dump, we need keep other memory type except E820_RAM, because other type ...Message posted on the October 30th, 2012 - 8:30 PM ET
[GIT PULL] x86/uapi for 3.8
Hi Linus, This is the arch/x86 portion of David Howell's user API splitup. Since this is a "build or fail" type patchset, I consider it to be very low risk. My test merge shows a single merge conflict in arch/x86/include/asm/mce.h; the ...Message posted on the December 12th, 2012 - 5:20 PM ET
[ 00/69] 3.10.17-stable review
This is the start of the stable review cycle for the 3.10.17 release. There are 69 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. You might notice a ...Message posted on the October 16th, 2013 - 2:30 PM ET
[PATCH 00/35] x86, boot, 64bit: Add support for loading ramdisk and bzImage above 4G
Now we have limit kdump reseved under 896M, because kexec has the limitation. and also bzImage need to stay under 4g. To make kexec/kdump could use range above 4g, we need to make bzImage and ramdisk could be loaded above 4g. During booting bzImage ...Message posted on the January 24th, 2013 - 3:30 PM ET