From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: pxeboot broken by commit "x86 setup: handle boot loaders which set up the stack incorrectly"
Date: Tue, 6 Nov 2007 16:18:32 -0800 [thread overview]
Message-ID: <86802c440711061618j5fdd7fbcv25be9a2065aa31eb@mail.gmail.com> (raw)
commit 6b6815c6d5d1dc209701d1661a7a0e09a295db2f
Author: H. Peter Anvin <hpa@zytor.com>
Date: Thu Oct 25 16:11:33 2007 -0700
x86 setup: handle boot loaders which set up the stack incorrectly
Apparently some specific versions of LILO enter the kernel with a
stack pointer that doesn't match the rest of the segments. Make our
best attempt at untangling the resulting mess.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
with that commit:
Linux version 2.6.24-rc1-smp-g2655e2ce-dirty
(yhlu@mpk12-office-77-204) (gcc version 4.2.1 (SUSE Linux)) #15 SMP
Tue Nov 6 15:42:01 PST 2007
Command line: console=uart8250,io,0x3f8,9600n8
initrd=kernel.org/mydisk10.3_x86_64.gz rw root=/dev/ram0 debug
apic=debug acpi.debug_level=0x0000000f p
without the commit:
Linux version 2.6.24-rc1-smp-g2655e2ce-dirty
(yhlu@mpk12-office-77-204) (gcc version 4.2.1 (SUSE Linux)) #15 SMP
Tue Nov 6 15:42:01 PST 2007
Command line: console=uart8250,io,0x3f8,9600n8
initrd=kernel.org/mydisk10.3_x86_64.gz rw root=/dev/ram0 debug
apic=debug acpi.debug_level=0x0000000f pci=routeirq ip=dhcp
load_ramdisk=1 ramdisk_size=131072
BOOT_IMAGE=kernel.org/bzImage_2.6.24_k8.7
pxeboot entry:
label k
kernel kernel.org/bzImage_2.6.24_k8.7
append console=uart8250,io,0x3f8,9600n8
initrd=kernel.org/mydisk10.3_x86_64.gz rw root=/dev/ram0 debug
apic=debug acpi.debug_level=0x0000000f pci=routeirq ip=dhcp
load_ramdisk=1 ramdisk_size=131072
YH
next reply other threads:[~2007-11-07 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 0:18 Yinghai Lu [this message]
[not found] <200711070708.lA778VtP029664@terminus.zytor.com>
2007-11-07 17:49 ` Yinghai Lu
2007-11-07 17:53 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86802c440711061618j5fdd7fbcv25be9a2065aa31eb@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®