From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 13:48: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 2569A1065697; Wed, 29 Sep 2010 13:48: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 7FF018FC15; Wed, 29 Sep 2010 13:48:11 +0000 (UTC) Received: by wwb17 with SMTP id 17so1015301wwb.31 for ; Wed, 29 Sep 2010 06:48: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=+LUREmvxuw2qfOI2Evx+Q35YeOgUAGZr7Uv9AKuBok4=; b=pTnST+EIqTyyR1aG+Urw/QbEksZa8EiKy5/iEzJbimlDd+BN5wzXr58XDixk9PVwXc Y21TdJKfQTtMyfMp0YyUQocUOdvdLpKEVDfsY4zze8s22/MztX1T+oqms8X6PpUM243G gMfhLgip8zOQ6YW61A5mfFAJSNLudCuqAbVQI= 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=phw20MhGuuG3Vuby+guH5Ts/WeorfrhXmWsOE3UOscolTxKsEV6rLuMy/y5RsEjaY+ 3DeavIkpBxC1vHRv4IBGihFFHEdvaB3ZQRsWf7DgRldskt/8Iqi565NRQNBmrVdzUOJr lJcyA0nxAEyjr7RCmUq7qkueFXV+2+yhn9B04= Received: by 10.216.20.18 with SMTP id o18mr1469223weo.31.1285768090249; Wed, 29 Sep 2010 06:48: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 w1sm5408149weq.25.2010.09.29.06.48.06 (version=SSLv3 cipher=RC4-MD5); Wed, 29 Sep 2010 06:48:09 -0700 (PDT) From: David Naylor Organization: Private To: John Baldwin Date: Wed, 29 Sep 2010 15:47:59 +0200 User-Agent: KMail/1.13.5 (FreeBSD/9.0-CURRENT; KDE/4.4.5; amd64; ; ) References: <201009291207.53146.naylor.b.david@gmail.com> <4CA324EB.4040500@icyb.net.ua> <201009290914.08513.jhb@freebsd.org> In-Reply-To: <201009290914.08513.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1479662.XOgHVrXr09"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201009291548.03752.naylor.b.david@gmail.com> Cc: Alexander Motin , freebsd-current@freebsd.org, Andriy Gapon 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 13:48:12 -0000 --nextPart1479662.XOgHVrXr09 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 with > > >> ``panic: No usable event timer found!''. This occurs on two (all my) > > >> 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 controllers. > > >=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. Is APIC and ACPI disabled in safe-mode on amd64? =20 This is using GENERIC, perhaps atpic should be added to the config file, or= made=20 mandatory for amd64 systems? =20 > > It's interesting to see what the "Safe Mode" really is: > > dup bootsafekey @ =3D if > >=20 > > s" arch-i386" environment? if > > =20 > > drop > > s" acpi_load" unsetenv > > s" 1" s" hint.acpi.0.disabled" setenv > > s" 1" s" loader.acpi_disabled_by_user" setenv > > s" 1" s" hint.apic.0.disabled" setenv > > =20 > > then > > s" 0" s" hw.ata.ata_dma" setenv > > s" 0" s" hw.ata.atapi_dma" setenv > > s" 0" s" hw.ata.wc" setenv > > s" 0" s" hw.eisa_slots" setenv > > s" 1" s" hint.kbdmux.0.disabled" setenv > > 0 boot > >=20 > > Not sure if disabling ACPI on modern hardware is a good idea. > > Even more unsure about disabling APIC. > >=20 > > Makes me wonder what this could be useful for. > > Perhaps, these are just leftovers from times were ACPI, APIC (and ATA > > DMA) were all new and unproven things. >=20 > Yes, on modern machines I think disabling ACPI and APIC is less safe > actually. --nextPart1479662.XOgHVrXr09 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) iEYEABECAAYFAkyjQ5MACgkQUaaFgP9pFrKR4ACgiAEqZNi3BuJUp53ynSzVGulc 07QAn3I4Yl3Cm7VUSEz0UyVoCjGzFsG6 =0tah -----END PGP SIGNATURE----- --nextPart1479662.XOgHVrXr09--