From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.23-bk bogus edd changeset - Re: 2.4.23 compile error in edd
Date: Mon, 15 Dec 2003 19:52:32 +0000 (GMT) [thread overview]
Message-ID: <Pine.SOL.4.58.0312151949290.21523@green.csi.cam.ac.uk> (raw)
In-Reply-To: <20031210144842.A24414@lists.us.dell.com>
On Wed, 10 Dec 2003, Matt Domsch wrote:
> > The ds segment is not pointing to the correct segment AND/OR the offsets
> > into the segment used for the writes are bogus. You write straight into
> > ds and ds:si referenced memory but you never setup ds in the first
> > place. So the writes done by the EDD code corrupt the loaded compressed
> > kernel and the decompression fails.
>
> ds is set up already to point at the empty_zero_page, else none of
> what I'm doing is correct. But, it is very likely that something else
> is using 0x228 in empty_zero_page but isn't marked as using it in
> Documentation/i386/zero-page.txt.
>
> You've been patient, and thorough. As another test, could you change
> include/asm-i386/edd.h: DISK80_SIG_BUFFER from 0x228 to 0x2cc (the
> four bytes immediately before the e820 memory buffer), and see if that
> helps? If so, I'll submit a patch to use that instead, and another
> that markes 0x228 as in use by something else.
Hi Matt,
sorry for the delay but I am now on holidays until January because of my
impending wedding and I won't be back at work, where the affected PC lives
until 5th or 6th January (whichever is the Monday). I will try it then,
sorry to have to keep you waiting so long.
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2003-12-15 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 14:20 2.4.23 compile error in edd Meelis Roos
2003-12-04 14:58 ` Meelis Roos
2003-12-04 22:31 ` 2.4.23-bk bogus edd changeset - " Anton Altaparmakov
2003-12-05 15:52 ` Marcelo Tosatti
2003-12-05 17:36 ` Matt Domsch
2003-12-05 18:53 ` Matt Domsch
2003-12-05 19:07 ` Matt Domsch
2003-12-08 16:34 ` Anton Altaparmakov
2003-12-09 4:23 ` Matt Domsch
2003-12-09 16:29 ` Anton Altaparmakov
2003-12-10 20:48 ` Matt Domsch
2003-12-15 19:52 ` Anton Altaparmakov [this message]
2003-12-18 11:32 ` Meelis Roos
2003-12-18 14:02 ` Matt Domsch
2003-12-19 11:05 ` Meelis Roos
2003-12-19 14:49 ` Matt Domsch
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=Pine.SOL.4.58.0312151949290.21523@green.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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;
as well as URLs for NNTP newsgroup(s).