From owner-svn-src-all@freebsd.org Thu Sep 1 20:42:24 2016 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99FDABCC705; Thu, 1 Sep 2016 20:42:24 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp003.me.com (st13p35im-asmtp003.me.com [17.164.199.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7260894A; Thu, 1 Sep 2016 20:42:24 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp003.me.com by st13p35im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OCU00500BZEF500@st13p35im-asmtp003.me.com>; Thu, 01 Sep 2016 19:42:17 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1472758936; bh=ZGOXssms4NlPkq5BDa2TqWHENV9lwdpONPn0ZSgjgHY=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=HRHjq1T8U79xigtfqroyyDVTCC7xfcrXPyYnseHTlHG1+eSSpq5Wc7MhuhXFCOZqi SbiZlJy5j3wjntryUVJerWZFJQm6M1IcxRd7GNHRnZp//l64jN9qFUcqEu1b/RCD+e CfJlVY1gW42vRYQJNEW49ZXMzYjkOgtKLbXG27rRcqRnsi1Pt2c6/VbRqM56m25dYG LJmCy63rtcjeMQwg8YitmbT5lwjLnkniMk6Vg2HqhiB4L652Vm/FgT/rA2HZRWOWGU oho1wAElLPZ7dyhE+Rd6cIdzeYzvV/7U2BnYlPOhIQzfngvYQ6iyl1TQj7sLuW8lUd awAL1BxCoESXA== Received: from nazgul.lan (220-90-235-80.dyn.estpak.ee [80.235.90.220]) by st13p35im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OCU008IIC2DAN10@st13p35im-asmtp003.me.com>; Thu, 01 Sep 2016 19:42:16 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-09-01_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1609010226 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: svn commit: r305178 - head/sys/boot/i386/libi386 From: Toomas Soome In-reply-to: <1604880.G26KHQlAxI@ralph.baldwin.cx> Date: Thu, 01 Sep 2016 22:42:12 +0300 Cc: Toomas Soome , src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <418639CF-EA43-4082-8A53-E085BC82F8E4@me.com> References: <201609010635.u816ZDlc025340@repo.freebsd.org> <1604880.G26KHQlAxI@ralph.baldwin.cx> To: John Baldwin X-Mailer: Apple Mail (2.3124) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 20:42:24 -0000 > On 1. sept 2016, at 21:28, John Baldwin wrote: >=20 > On Thursday, September 01, 2016 06:35:13 AM Toomas Soome wrote: >> Author: tsoome >> Date: Thu Sep 1 06:35:13 2016 >> New Revision: 305178 >> URL: https://svnweb.freebsd.org/changeset/base/305178 >>=20 >> Log: >> bd_int13probe() should check extended info if sector info is bad >>=20 >> In some Dell systems and usb stick combinations, it is found that >> int13 AH=3D08 is reporting back bad sector information, preventing = the >> boot. >>=20 >> This update is allowing bd_int13probe() to use extended info call to >> build disk properties. >>=20 >> It also can happen the total sectors count from extended info may be >> wrong, in such case, the CHS data is used to calculate total = sectors. >>=20 >> Reviewed by: allanjude >> Approved by: allanjude (mentor) >> Differential Revision: https://reviews.freebsd.org/D7718 >=20 > Hmm, can you see if this fixes > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176748 ? >=20 > --=20 > John Baldwin eh=E2=80=A6 well. as he was reporting about bad sector size - my patch = does not check it.. so apparently that would be good check as well=E2=80=A6= . unfortunately I don=E2=80=99t have any of such broken BIOSes handy to = verify what kind of breakage it is - are they just filling EDD with = garbage or is there any kind of logic.=20 rgds, toomas