[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440705080941y69ddd5d6lab170c5f3967f148@mail.gmail.com>
Date: Tue, 8 May 2007 09:41:09 -0700
From: yhlu <yhlu.kernel@...il.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: vgoyal@...ibm.com, "H. Peter Anvin" <hpa@...or.com>,
"Jeremy Fitzhardinge" <jeremy@...p.org>,
"Gerd Hoffmann" <kraxel@...hat.com>,
"Jeff Garzik" <jeff@...zik.org>, patches@...-64.org,
linux-kernel@...r.kernel.org,
virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
On 5/2/07, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> Vivek Goyal <vgoyal@...ibm.com> writes:
>
> > On Wed, May 02, 2007 at 02:59:11PM -0700, H. Peter Anvin wrote:
> >> Jeremy Fitzhardinge wrote:
> >> >
> >> > So the bzImage structure is currently:
> >> >
> >> > 1. old-style boot sector
> >> > 2. old-style boot info, followed by 0xaa55 at the end of the sector
> >> > 3. the HdrS boot param block
> >> > 4. setup.S boot code
> >> > 5. the self-decompressing kernel
> >> >
Eric,
With the latest change that make vmlinux to be elf64 and make bzImage
do switch to 64bit long mode, the kernel started via kexec can not get
VGA console. but the serial console works well. I wonder if the
setup.S is skipped in bzImage via kexec path.
or i missed sth?
#!/bin/bash
./kexec -t bzImage -l bzImage_2.6.22_k8.1 --command-line="apic=debug
acpi_dbg_level=0x00000007 pci=routeirq snd-hda-intel.enable_msi=1
ramdisk_size=65536 root=/dev/ram0 rw ip=dhcp console=tty0
console=ttyS0,9600n8" --ramdisk=mydisk8_x86_64.gz
YH
-
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/
Powered by blists - more mailing lists