linux-kernel - Data corruption in some BIOSes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <eb0b59820811190101i50a18bd6m39bd8313d5b31dd4@mail.gmail.com>
Date:	Wed, 19 Nov 2008 11:01:18 +0200
From:	"Сергій Стецькович" 
	<patriotyk@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Data corruption in some BIOSes

Hello,

I am working on some project where I need to boot winxp from linux,
and I am using kexec for it, but in some computers it doesn't work.
When kexec jumps to my kernel, in kernel  I am switching to real mode
and try to call int13h to read mbr sector. But I have one
computer(with AMI BIOS and this computer is newer than others) where
this BIOS call doesn't work.
I think it is the problem with data corruption of BIOS memory, and I
also have compiled 2.6.27.6 kernel(where is applied patch
X86_RESERVE_LOW_64K), but it didn't help.
I think maybe I'm doing something wrong, maybe I need to do restoring
reserved BIOS memory in kexec kernel function before loading new
kernel?

Please help me!

Thanks, Serhiy
--
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/