On Sat, Sep 11, 2010 at 08:42:17PM -0000, Jaap-Jan van der Veen wrote:
> Maybe this will shed some light on it. ;) I happen to have a suitable
> docking station for my Precision M4500.
[...]
> [ 0.243608] Call Trace:
> [ 0.246050] [<ffffffff81031fd6>] ? efi_call4+0x46/0x80
> [ 0.251271] [<ffffffff81afea91>] ? efi_enter_virtual_mode+0x15b/0x284
> [ 0.257786] [<ffffffff81aedc26>] start_kernel+0x310/0x390
> [ 0.263260] [<ffffffff81aed341>] x86_64_start_reservations+0x12c/0x130
> [ 0.269857] [<ffffffff81aed43f>] x86_64_start_kernel+0xfa/0x109
> [ 0.275854] Code: Bad RIP value.
> [ 0.279212] RIP [<ffffffffcccafed0>] 0xffffffffcccafed0
Thanks, that's interesting. Sort of similar to what Mario found on a
different machine, although the symptom is very slightly different.
I think it will be easiest to debug this when I can iteratively install
new test kernels and GRUB images on my machine and observe the output.
In the meantime, I can confirm that the fault is at
arch/x86/kernel/efi.c:167, matching Mario's log:
status = efi_call_phys4(efi_phys.set_virtual_address_map,
memory_map_size, descriptor_size,
descriptor_version, virtual_map);
It is interesting that 0xffffffffcccafed0 is way up in the kernel module
mapping area, not in anything that seems a plausible physical address,
and it doesn't match anything in the EFI memory map either (which seems
to tentatively rule out the idea that GRUB might just be constructing
the E820 map wrongly). I would have expected this function to be in one
of the EfiRuntimeServicesCode ranges, namely:
[ 0.000000] EFI: mem355: type=5, attr=0x800000000000000f,
range=[0x00000000cf5df000-0x00000000cf636000) (0MB)
[ 0.000000] EFI: mem356: type=5, attr=0x800000000000000f,
range=[0x00000000cf636000-0x00000000cf65f000) (0MB)
I smell a rat, but as yet I'm not sure what kind. In-kernel memory
corruption, or are we failing to mark the EFI system table as reserved
so it gets overwritten? Or something else?
> Off-topic:
> I don't know if it's just my machine, but does yours also take a long
> time to show the boot menu when pressing F12? On my machine takes a
> second or 15 between the BIOS screen disappearing and (for now)
> Windows 7 boot screen appearing when booting normally. In between
> there seems to be some hard disk activity, as if the BIOS scans all
> partitions for boot loaders.
Yes, I suspect that's pretty much what it's doing. I haven't been
worrying about it too much as yet ...
--
No UEFI boot on Dell Precision M4500
https://bugs.launchpad.net/bugs/635439
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
