archive mirror
 help / color / mirror / Atom feed
From: Matt Domsch <>
To: Anton Altaparmakov <>
Cc: Marcelo Tosatti <>,
	LKML <>
Subject: Re: 2.4.23-bk bogus edd changeset - Re: 2.4.23 compile error in edd
Date: Mon, 8 Dec 2003 22:23:22 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1070901250.4508.1.camel@imp>; from on Mon, Dec 08, 2003 at 04:34:10PM +0000

> With latest 2.4-BK which includes your compile fix, compiling the kernel
> with the attached .config, installing and attempting to boot the kernel
> causes immediate reboot on my workstation.
> Disabling EDD in the .config, recompiling and installing the kernel
> makes it boot just fine.
> Let me know if you want me to test any patches, need any more
> information, etc...

Ok, I'm betting that your BIOS doesn't like the int13 call in setup.S for some

#if defined(CONFIG_EDD) || defined(CONFIG_EDD_MODULE)
# Read the first sector of device 80h and store the 4-byte signature
        movl    $0xFFFFFFFF, %eax
        movl    %eax, (DISK80_SIG_BUFFER)       # assume failure
        movb    $READ_SECTORS, %ah
        movb    $1, %al                         # read 1 sector
        movb    $0x80, %dl                      # from device 80
        movb    $0, %dh                         # at head 0
        movw    $1, %cx                         # cylinder 0, sector 0
        pushw   %es
        pushw   %ds
        popw    %es
        movw    $EDDBUF, %bx
        int     $0x13
        jc      disk_sig_done
        movl    (EDDBUF+MBR_SIG_OFFSET), %eax
        movl    %eax, (DISK80_SIG_BUFFER)       # store success
        popw    %es

To test this, would you mind #if 0'ing everything starting with
movb $READ_SECTORS, %ah   through the popw %es at the end?  That
should leave you with a file in /proc/bios/int13_dev80/mbr_signature
that says 0xFFFFFFFF, but a booting system.

I'm wondering if %eax shouldn't be zeroed before the int13.  The
bottom word gets set properly, but the top word is 0xFFFF which your
BIOS may not like?  That would be another test, add an

 xor %eax, %eax

before the movb $READ_SECTORS, %ah.

My BIOSs I've seen this on work, so it could be BIOS-dependent;
clearing eax before setting the lower bytes would be OK if that fixes

I'm travelling Monday and Tuesday, but will respond ASAP.


Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions
Linux on Dell mailing lists @

  reply	other threads:[~2003-12-09  4:23 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).