From: Matt Domsch <Matt_Domsch@dell.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Anton Altaparmakov <aia21@cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-bk bogus edd changeset - Re: 2.4.23 compile error in edd
Date: Thu, 18 Dec 2003 08:02:16 -0600 [thread overview]
Message-ID: <20031218080216.A30913@lists.us.dell.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0312181330150.5204-100000@math.ut.ee>; from mroos@linux.ee on Thu, Dec 18, 2003 at 01:32:20PM +0200
> Same here - instant reboot when EDD is enabled. Do you need my config
> also? The mainboard is Intel D815EEA2 with latest BIOS
> (EA81520A.86A.0039.P21.0211061753).
Ok, 2 reports now. With Anton off getting married, can you assist
with debugging this (I've tried, and can't reproduce it on any systems
available to me) ?
In include/asm-i386/edd.h, change:
#define DISK80_SIG_BUFFER 0x228
to
#define DISK80_SIG_BUFFER 0x2cc
and see if that helps. What I'm thinking right now is that 0x228 is
being used by a boot loader somehow (what's your boot loader?) though I can't
yet prove it, and it isn't listed in
Documentation/i386/zero-page.txt. But Anton showed that the int13
calls the EDD code makes (or even if you remove those) succeeds, but
by writing something into 0x228 the kernel uncompress fails. I'm
hoping that by moving the buffer to 0x2cc (immediately before the e820
memory map reserved space) that it will succeed.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2003-12-18 14:02 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
2003-12-18 11:32 ` Meelis Roos
2003-12-18 14:02 ` Matt Domsch [this message]
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=20031218080216.A30913@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mroos@linux.ee \
/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).