From owner-freebsd-stable@FreeBSD.ORG Fri Sep 14 08:17:53 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6891C106572B; Fri, 14 Sep 2012 08:17:53 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id DFC9D8FC1B; Fri, 14 Sep 2012 08:17:52 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 90FB46A6001; Fri, 14 Sep 2012 10:17:51 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id q8E8HpH9029824; Fri, 14 Sep 2012 10:17:51 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id q8E8Hp6A029688; Fri, 14 Sep 2012 10:17:51 +0200 (CEST) (envelope-from lars) Date: Fri, 14 Sep 2012 10:17:51 +0200 From: Lars Engels To: Alexander Motin Message-ID: <20120914081751.GA11773@e-new.0x20.net> References: <20120912113425.GK20762@e-new.0x20.net> <50508606.4040704@FreeBSD.org> <20120912172525.GU20762@e-new.0x20.net> <5050C6BC.8000307@FreeBSD.org> <20120912174649.GV20762@e-new.0x20.net> <5050DB57.90903@FreeBSD.org> <20120912195821.GW20762@e-new.0x20.net> <5050EBB9.7040202@FreeBSD.org> <20120913074437.GX20762@e-new.0x20.net> <505210A3.8000105@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: <505210A3.8000105@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org, Andriy Gapon Subject: Re: Thinkpad X61s cannot boot 9.1-BETA1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 08:17:53 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 13, 2012 at 07:58:11PM +0300, Alexander Motin wrote: > On 13.09.2012 10:44, Lars Engels wrote: > > On Wed, Sep 12, 2012 at 11:08:25PM +0300, Alexander Motin wrote: > >> On 12.09.2012 22:58, Lars Engels wrote: > >>> On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote: > >>>> On 12.09.2012 20:46, Lars Engels wrote: > >>>>> On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote: > >>>>>> on 12/09/2012 20:25 Lars Engels said the following: > >>>>>>> On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote: > >>>>>>>> Could you try to play with different eventtimer settings (prefer= ably in current) ? > >>>>>>>> You can use this thread / PR as a guide: > >>>>>>>> http://thread.gmane.org/gmane.os.freebsd.devel.amd64/14480/focus= =3D14495 > >>>>>>>> > >>>>>>>> The place where boot stop looks suspiciously close to the place = where timer > >>>>>>>> interrupts should start driving the system. > >>>>>>> > >>>>>>> Yes, that's it! > >>>>>>> Setting kern.eventtimer.timer=3D"i8254" let's the Thinkpad boot = on > >>>>>>> CURRENT with the AC cable inserted. > >>>>>>> > >>>>>> > >>>>>> Please share your sysctl kern.eventtimer output with Alexander. > >>>>>> He will probably ask for some additional information :-) > >>>> > >>>> Sorry if I've missed, but it would be useful to see verbose dmesg in > >>>> situation where system couldn't boot without switching eventtimer. > >>> > >>> No problem. See: http://bsd-geek.de/FreeBSD/IMAG0190.jpg > >> > >> No, I've seen that one and I don't mean it. I mean full verbose dmesg = of > >> successful boot in conditions where system was not booting before > >> without setting kern.eventtimer.timer=3D"i8254". > > > > Ok, sorry. > > Here's a verbose dmesg booting CURRENT without AC power: > > http://bsd-geek.de/FreeBSD/T61_dmesg.boot.works >=20 > Hmm. I see nothing suspicious. HPET driver output is typical for ICH8M=20 > chipset, many of which are working fine in different systems, including= =20 > several mine. There was no significant changes in HPET after 9.0-RELASE= =20 > except r231161. It changed device probe order that increased chance of=20 > interrupt sharing. It should not be a problem, but who knows. You can=20 > try to hint HPET driver specific IRQ 23 (that looks unused) to avoid=20 > sharing by setting hint.hpet.0.allowed_irqs=3D"0x00800000". Setting that didn't change anything. > You've told that problem related to AC power state. Have you compared=20 > dmesg outputs with and without it? Here's are some more dmesgs: http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9.works # PCBSD 9.1-RC1 success= uful boot on AC power http://bsd-geek.de/FreeBSD/T61_dmesg.boot.10.works # FreeBSD 10-CURRENT su= ccessful boot on battery http://bsd-geek.de/FreeBSD/T61_dmesg.boot.9_10.diff # Their diff --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBS6C8ACgkQKc512sD3afgP4QCgqv3/XtmWgqoexydOkChSTHqy djgAn2+q92h/P4ePxGcErzeKXB1fqZti =0BCO -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp--