* 2.6.23-rc3 - CONFIG_VMI broken
@ 2007-08-14 15:39 Parag Warudkar
2007-08-14 15:44 ` Michal Piotrowski
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Parag Warudkar @ 2007-08-14 15:39 UTC (permalink / raw)
To: linux-kernel; +Cc: Linus Torvalds, zach, rusty
CONFIG_VMI seems to be broken, but I am not sure when - the last
kernel I was running was 2.6.22-rc4 which used to boot fine and use
VMI. Current git with same configuration causes the kernel to reboot
early. Logs below.
Deselecting CONFIG_VMI and rebuilding allows the kernel to boot normally.
(I am running it on VMWare workstation 6 latest release.)
Thanks
Parag
Linux version 2.6.23-rc3 (root@ubuntu) (gcc version 4.1.2 (Ubuntu
4.1.2-0ubuntu4)) #4 Mon Aug 13 21:50:06 EDT 2007
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data)
BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS)
BIOS-e820: 000000001ff00000 - 0000000020000000 (usable)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
console [earlyser0] enabled
0MB HIGHMEM available.
512MB LOWMEM available.
found SMP MP-table at 000f6c90
VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0
Reserving virtual address space above 0xfc000000
Int 14: CR2 fc37e260 err 00000000 EIP fc37e260 CS 00000062 flags 00010006
Stack: c0490ec7 c04913cb 00000001 00000000 fc001340 c047fff4 c04a6080 c047aa00
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: 2.6.23-rc3 - CONFIG_VMI broken
2007-08-14 15:39 2.6.23-rc3 - CONFIG_VMI broken Parag Warudkar
@ 2007-08-14 15:44 ` Michal Piotrowski
2007-08-14 17:08 ` Parag Warudkar
2007-08-14 21:26 ` Zachary Amsden
2007-08-23 0:05 ` Zachary Amsden
2 siblings, 1 reply; 6+ messages in thread
From: Michal Piotrowski @ 2007-08-14 15:44 UTC (permalink / raw)
To: Parag Warudkar; +Cc: linux-kernel, Linus Torvalds, zach, rusty
Hi Parag,
On 14/08/07, Parag Warudkar <parag.warudkar@gmail.com> wrote:
> CONFIG_VMI seems to be broken, but I am not sure when - the last
> kernel I was running was 2.6.22-rc4 which used to boot fine and use
> VMI.
Please check the latest -stable and let me know if it is a regression.
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.23-rc3 - CONFIG_VMI broken
2007-08-14 15:39 2.6.23-rc3 - CONFIG_VMI broken Parag Warudkar
2007-08-14 15:44 ` Michal Piotrowski
@ 2007-08-14 21:26 ` Zachary Amsden
2007-08-14 21:49 ` Parag Warudkar
2007-08-23 0:05 ` Zachary Amsden
2 siblings, 1 reply; 6+ messages in thread
From: Zachary Amsden @ 2007-08-14 21:26 UTC (permalink / raw)
To: Parag Warudkar; +Cc: linux-kernel
Parag Warudkar wrote:
> CONFIG_VMI seems to be broken, but I am not sure when - the last
> kernel I was running was 2.6.22-rc4 which used to boot fine and use
> VMI. Current git with same configuration causes the kernel to reboot
> early. Logs below.
>
> Deselecting CONFIG_VMI and rebuilding allows the kernel to boot normally.
>
> (I am running it on VMWare workstation 6 latest release.)
>
> Thanks
>
> Parag
>
> Linux version 2.6.23-rc3 (root@ubuntu) (gcc version 4.1.2 (Ubuntu
> 4.1.2-0ubuntu4)) #4 Mon Aug 13 21:50:06 EDT 2007
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
> BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
> BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data)
> BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS)
> BIOS-e820: 000000001ff00000 - 0000000020000000 (usable)
> BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
> console [earlyser0] enabled
> 0MB HIGHMEM available.
> 512MB LOWMEM available.
> found SMP MP-table at 000f6c90
> VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0
> Reserving virtual address space above 0xfc000000
> Int 14: CR2 fc37e260 err 00000000 EIP fc37e260 CS 00000062 flags 00010006
> Stack: c0490ec7 c04913cb 00000001 00000000 fc001340 c047fff4 c04a6080 c047aa00
>
>
Can you send me your kernel config?
Thanks,
Zach
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.23-rc3 - CONFIG_VMI broken
2007-08-14 21:26 ` Zachary Amsden
@ 2007-08-14 21:49 ` Parag Warudkar
0 siblings, 0 replies; 6+ messages in thread
From: Parag Warudkar @ 2007-08-14 21:49 UTC (permalink / raw)
To: Zachary Amsden; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
Attached.
Thanks
Parag
On 8/14/07, Zachary Amsden <zach@vmware.com> wrote:
> Parag Warudkar wrote:
> > CONFIG_VMI seems to be broken, but I am not sure when - the last
> > kernel I was running was 2.6.22-rc4 which used to boot fine and use
> > VMI. Current git with same configuration causes the kernel to reboot
> > early. Logs below.
> >
> > Deselecting CONFIG_VMI and rebuilding allows the kernel to boot normally.
> >
> > (I am running it on VMWare workstation 6 latest release.)
> >
> > Thanks
> >
> > Parag
> >
> > Linux version 2.6.23-rc3 (root@ubuntu) (gcc version 4.1.2 (Ubuntu
> > 4.1.2-0ubuntu4)) #4 Mon Aug 13 21:50:06 EDT 2007
> > BIOS-provided physical RAM map:
> > BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> > BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> > BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
> > BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
> > BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
> > BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data)
> > BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS)
> > BIOS-e820: 000000001ff00000 - 0000000020000000 (usable)
> > BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> > BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> > BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
> > console [earlyser0] enabled
> > 0MB HIGHMEM available.
> > 512MB LOWMEM available.
> > found SMP MP-table at 000f6c90
> > VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0
> > Reserving virtual address space above 0xfc000000
> > Int 14: CR2 fc37e260 err 00000000 EIP fc37e260 CS 00000062 flags 00010006
> > Stack: c0490ec7 c04913cb 00000001 00000000 fc001340 c047fff4 c04a6080 c047aa00
> >
> >
>
> Can you send me your kernel config?
>
> Thanks,
>
> Zach
>
[-- Attachment #2: .config --]
[-- Type: application/xml, Size: 44069 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: 2.6.23-rc3 - CONFIG_VMI broken
2007-08-14 15:39 2.6.23-rc3 - CONFIG_VMI broken Parag Warudkar
2007-08-14 15:44 ` Michal Piotrowski
2007-08-14 21:26 ` Zachary Amsden
@ 2007-08-23 0:05 ` Zachary Amsden
2 siblings, 0 replies; 6+ messages in thread
From: Zachary Amsden @ 2007-08-23 0:05 UTC (permalink / raw)
To: Parag Warudkar
Cc: linux-kernel, Linus Torvalds, rusty, Chris Wright, Andi Kleen
Parag Warudkar wrote:
> CONFIG_VMI seems to be broken, but I am not sure when - the last
> kernel I was running was 2.6.22-rc4 which used to boot fine and use
> VMI. Current git with same configuration causes the kernel to reboot
> early. Logs below.
>
> Deselecting CONFIG_VMI and rebuilding allows the kernel to boot normally.
>
> (I am running it on VMWare workstation 6 latest release.)
>
> Thanks
>
> Parag
>
> Linux version 2.6.23-rc3 (root@ubuntu) (gcc version 4.1.2 (Ubuntu
> 4.1.2-0ubuntu4)) #4 Mon Aug 13 21:50:06 EDT 2007
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
> BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
> BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data)
> BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS)
> BIOS-e820: 000000001ff00000 - 0000000020000000 (usable)
> BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
> console [earlyser0] enabled
> 0MB HIGHMEM available.
> 512MB LOWMEM available.
> found SMP MP-table at 000f6c90
> VMI: Found VMware, Inc. Hypervisor OPROM, API version 3.0, ROM version 1.0
> Reserving virtual address space above 0xfc000000
> Int 14: CR2 fc37e260 err 00000000 EIP fc37e260 CS 00000062 flags 00010006
> Stack: c0490ec7 c04913cb 00000001 00000000 fc001340 c047fff4 c04a6080 c047aa00
>
I reproduced this, slightly different EIP, but I notice that all
paravirt-ops function calls are to bogus addresses; the first byte
appears correct (0xfc00XXXX is in the VMI ROM range), and the extracted
function addresses in the paravirt_ops struct are correct. However, it
looks like the patching of the call instructions went wrong. Does this
sound familiar to anyone?
In any case, I think the bug is already fixed.
Zach
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-08-23 0:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-14 15:39 2.6.23-rc3 - CONFIG_VMI broken Parag Warudkar
2007-08-14 15:44 ` Michal Piotrowski
2007-08-14 17:08 ` Parag Warudkar
2007-08-14 21:26 ` Zachary Amsden
2007-08-14 21:49 ` Parag Warudkar
2007-08-23 0:05 ` Zachary Amsden
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox