From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 16:20:12 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 351821065670; Wed, 29 Sep 2010 16:20:12 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 682528FC17; Wed, 29 Sep 2010 16:20:11 +0000 (UTC) Received: by wwb17 with SMTP id 17so1238405wwb.31 for ; Wed, 29 Sep 2010 09:20:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:organization:to:subject :date:user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=NO+f7bS/h9TGFmzH5ong41evUlZU6jqFaIM9IvgsaTY=; b=YQH4geSAC8jS6tKTQ956yllMLl5iWkxMRY4ISiS62hsmP30FzDUTKaPLn2noShPPdQ k/r3coln40+TCEBBabn6k5fuIwl/rPyeAOCkOv6CO94PeWOuUy3qsmiYIn/MmWvbCEvj RV7VQfqSv1aWhPt3BgyDmpUyUi9/RLQFTeO9g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:organization:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; b=CPK3RlvxFnh9VV8mJT/e+CJLWl4MHkYRwJ1aZ0xVymTfLfFTdrBtggKp1QXpTzU4Ev 41UQSR73ivHyMn5sSTyLIrBcdrc/MuDzMnz3gT/9FvhNIt2w1aHEWl/yx2nyZr0awbOa KNiK5mIhi+OfIrss/7QcZsD0J/3fZ0vLpkBiw= Received: by 10.227.155.3 with SMTP id q3mr1661278wbw.130.1285777210389; Wed, 29 Sep 2010 09:20:10 -0700 (PDT) Received: from dragon.dg (41-132-25-181.dsl.mweb.co.za [41.132.25.181]) by mx.google.com with ESMTPS id k7sm5522365wej.2.2010.09.29.09.20.06 (version=SSLv3 cipher=RC4-MD5); Wed, 29 Sep 2010 09:20:09 -0700 (PDT) From: David Naylor Organization: Private To: Andriy Gapon Date: Wed, 29 Sep 2010 18:19:57 +0200 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.4.5; amd64; ; ) References: <201009291207.53146.naylor.b.david@gmail.com> <201009291548.03752.naylor.b.david@gmail.com> <4CA34ADC.40309@icyb.net.ua> In-Reply-To: <4CA34ADC.40309@icyb.net.ua> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9056537.7SONuKrAe5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201009291820.02401.naylor.b.david@gmail.com> Cc: Alexander Motin , freebsd-current@freebsd.org Subject: Re: Safe-mode on amd64 broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2010 16:20:12 -0000 --nextPart9056537.7SONuKrAe5 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Wednesday 29 September 2010 16:19:08 Andriy Gapon wrote: > on 29/09/2010 16:47 David Naylor said the following: > > On Wednesday 29 September 2010 15:14:08 John Baldwin wrote: > >> On Wednesday, September 29, 2010 7:37:15 am Andriy Gapon wrote: > >>> on 29/09/2010 13:40 Alexander Motin said the following: > >>>> Hi. > >>>>=20 > >>>> David Naylor wrote: > >>>>> Trying to boot a recent (sep 23) amd64 kernel in safe-mode fails wi= th > >>>>> ``panic: No usable event timer found!''. This occurs on two (all m= y) > >>>>> machines. This has been a persistent problem since the introduction > >>>>> of the event timer code. > >>>>=20 > >>>> I've reproduced the problem. > >>>>=20 > >>>> The reason is that all (or at least most) of devices (both PCI and > >>>> ISA), including only available in that mode i8254 and RTC timers, > >>>> failed to allocate their interrupts. While reported message is indeed > >>>> related to event timer code, problem IMHO doesn't. While without this > >>>> panic system could boot without any alive timer, I have doubts that = it > >>>> would be functional without timers, USB, network and disk controller= s. > >>>>=20 > >>>> Problems seems to be the same if I am trying to boot without ACPI. > >>=20 > >> Probably the kernel doesn't have 'device atpic' so disabling APIC > >> probably breaks all interrupts. A newer system might only describe > >> APICs via the ACPI MADT table and not provide an MP Table. In that > >> case disabling ACPI would effectively disable APIC leading to the same > >> result. > >=20 > > Is APIC and ACPI disabled in safe-mode on amd64? >=20 > Did you notice the code snippet below? Yes, and it managed to confuse me. =20 > Specifically hint.acpi.0.disabled and hint.apic.0.disabled. > Don't let "arch-i386" confuse you, it means "x86" in that context. >=20 > > This is using GENERIC, perhaps atpic should be added to the config file, > > or made mandatory for amd64 systems? >=20 > I don't think so. Especially given that hardware might not support !APIC > case at all, even if you have atpic in your kernel. Perhaps safe-mode is no longer a viable option and should be removed from t= he=20 boot menu, or renamed to "unsafe-mode"? =20 =20 > Alternatively, perhaps just don't use this "Safe Mode"? > What do you try to actually achieve? I was trying to boot a system and it was panicking due to stray interrupts.= =20 It turned out to be caused by HPET. I found `hint.hpet.0.clock=3D0' which = fixed=20 the problem. =20 This means HPET does not work on any of my machines. The other one's sympt= oms=20 are hda losing interrupts after a period of up-time. =20 --nextPart9056537.7SONuKrAe5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEABECAAYFAkyjZzIACgkQUaaFgP9pFrIg1ACfZw+/o3Qxa5lEAb8xUAk6NaTK w58AnAm48Je2BY2gOkrIwb8XEIAK+phn =Ogw3 -----END PGP SIGNATURE----- --nextPart9056537.7SONuKrAe5--