DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=xawC9EycfQGQZq9cdrnSMjcg2JeTR/JfgKLmlcNYqRXAo0OpZXt5zcWIpGSli0tsCxZ7A9ypDbThMa6xeBN0VDmjg2vEbx/upIkqHlKHQjx1+VOpBe2K3EibON0ZZsaN3bon0g1490Xj27OfYrrUb6PARCRL4dzRCjIQDqgqaBk=
Message-ID: <76366b180803032311g40593189o47f727e4bba52c43@mail.gmail.com>
Date: Tue, 4 Mar 2008 02:11:31 -0500
From: "Andrew Paprocki" <andrew@ishiboo.com>
To: linux-kernel@vger.kernel.org
Subject: Geode LX800 hanging at boot in vesa_store_edid() w/ CONFIG_FIRMWARE_EDID=y
Cc: "Jordan Crouse" <jordan.crouse@amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1410
Lines: 30

I have a LX800 board which hangs at boot time *only* if no monitor is
plugged into the VGA port. It hangs for about 20 minutes and then
continues booting.  If a monitor is plugged into the system while it
is hung, it recovers after a few minutes and continues booting.  I
added puts() debugging in the kernel main() and it is hanging in
vesa_store_edid() in the first asm() call:

        /* Note: The VBE DDC spec is different from the main VESA spec;
           we genuinely have to assume all registers are destroyed here. */

        asm("pushw %%es; movw %2,%%es; "INT10"; popw %%es"
            : "+a" (ax), "+b" (bx)
            :  "c" (cx), "D" (di)
            : "esi");

After waiting for a really long time, this int10 finishes and it
executes the second asm() call which returns right away.  I never
tried booting the system without a head, so I never noticed this
problem before.  Does this point to some kind of BIOS bug?  The system
boots fine when CONFIG_FIRMWARE_EDID is disabled (I'm not even sure if
it should have been enabled in the first place), but I want to make
sure the manufacturer is alerted if there is a BIOS problem.

Thanks,
-Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/