From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52601) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WAeEa-0004Pd-Qc for qemu-devel@nongnu.org; Tue, 04 Feb 2014 06:32:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WAeET-00032a-4a for qemu-devel@nongnu.org; Tue, 04 Feb 2014 06:32:08 -0500 Received: from isrv.corpit.ru ([86.62.121.231]:41543) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WAeES-00032R-Tu for qemu-devel@nongnu.org; Tue, 04 Feb 2014 06:32:01 -0500 Message-ID: <52F0CFAF.9090200@msgid.tls.msk.ru> Date: Tue, 04 Feb 2014 15:31:59 +0400 From: Michael Tokarev MIME-Version: 1.0 References: <1391438755-30975-1-git-send-email-kraxel@redhat.com> <52F09936.9090407@msgid.tls.msk.ru> <1391501856.15480.4.camel@nilsson.home.kraxel.org> In-Reply-To: <1391501856.15480.4.camel@nilsson.home.kraxel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL 0/3] Update seabios to 1.7.4 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel@nongnu.org 04.02.2014 12:17, Gerd Hoffmann wrote: > On Di, 2014-02-04 at 11:39 +0400, Michael Tokarev wrote: >> FWIW, we updated seabios in Debian testing (with qemu 1.7), and >> now there are several bugs filed in Debian BTS, at least: >> >> http://bugs.debian.org/737142 >> http://bugs.debian.org/736902 > Dunno what 737142 is. 736902 looks like something with ram detection. > > Would be interesting to know whenever the blobs from this pull request > are failing too. If so a seabios log would be helpful. It looks like this mess is entirely due to my brown-paper-bag error. I updated multiboot.S (which we have to carry in seabios source for debian, a long story) from a wrong qemu branch (but at the same time stating in the README that it is from the right commit). Hence it broke. I'm now trying to verify 737142 (PC-BSD is unable to boot), but since it also uses multiboot, it is highly likely that it is the same issue. I'm sorry for the noize. Thanks, /mjt