From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O20D2-0001hY-CU for qemu-devel@nongnu.org; Wed, 14 Apr 2010 06:52:40 -0400 Received: from [140.186.70.92] (port=41081 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O20Cz-0001gN-18 for qemu-devel@nongnu.org; Wed, 14 Apr 2010 06:52:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O20Cp-0002e5-30 for qemu-devel@nongnu.org; Wed, 14 Apr 2010 06:52:30 -0400 Received: from canardo.mork.no ([148.122.252.1]:51269) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O20Co-0002dX-Mj for qemu-devel@nongnu.org; Wed, 14 Apr 2010 06:52:27 -0400 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= References: <20100221040555.GA16455@morn.localdomain> <20100228193904.GA15352@morn.localdomain> <20100228204137.GA23442@redhat.com> <87d3y3p4sc.fsf@nemi.mork.no> <20100414012749.GB29097@morn.localdomain> Date: Wed, 14 Apr 2010 12:51:57 +0200 In-Reply-To: <20100414012749.GB29097@morn.localdomain> (Kevin O'Connor's message of "Tue, 13 Apr 2010 21:27:49 -0400") Message-ID: <87ochmmhma.fsf@nemi.mork.no> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: SeaBIOS error with Juniper FreeBSD kernel List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: Brandon Bennett , seabios@seabios.org, qemu-devel@nongnu.org, Gleb Natapov "Kevin O'Connor" writes: > It looks like memory layout changes in the f-segment is tickling the > underlying bug. I don't think SMBIOS, the above commit, or the other > commit identified earlier are the root cause of the problem. Instead, > I'd guess these commits just change the memory layout enough to avoid > the root cause. Sounds like a reasonable explanation. Is there anything I can do to try to pin down the problem? > This looks like it is going to require some careful study with a > debugger and some execution traces. Unfortunately, since this image > isn't available for download it makes it difficult to track down. I understand that. But I'm afraid I can't provide any such image. I don't think Juniper has done anything extra-ordinary at this point however, so I'll try to see if I can create a freely distributable image triggering the bug using the same tools as them. Will let you know if I succeed.=20 Bj=C3=B8rn