From owner-freebsd-current@FreeBSD.ORG Wed Jul 8 00:28:56 2009 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 034A4106566C for ; Wed, 8 Jul 2009 00:28:56 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by mx1.freebsd.org (Postfix) with ESMTP id A92E98FC08 for ; Wed, 8 Jul 2009 00:28:55 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: by yxe11 with SMTP id 11so7532176yxe.3 for ; Tue, 07 Jul 2009 17:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=enXlZRnmA4oZ5tWhJZyTipwKyG0po2Mkck9y4CTE63o=; b=UIkqxWqQQEivFpasE1j5cnpSVQ68r72Q0Cd5K0ebi+NzTfDyOZ1C0IF2HOF/b1qKTm 82CpxBsOgD4gzi5uYhNacqDDlsM1ieXIH01lq6MvZ8Y6dgUaYY8Rf2vMN9qlh/B88AuY //suF8JLyd14A8J3sb+XaEFJD7HkrIx+4zkI0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=kqMdepvGVjUw0JTakMW2DJuLNTPWc5xz8BKoex9CMYWii468hbAI+4INohRYVy/FgO f+zZXrWuicCBAMWR7TyrWHnRdrk3tODaCqpuac2sjTkEyWzwL/y40cNs9o4cvOXNccXZ 7u0rYFBRGiqd50/CNWpPFZ1yCz1x3aA15ILrc= Received: by 10.90.86.10 with SMTP id j10mr5586422agb.97.1247012934719; Tue, 07 Jul 2009 17:28:54 -0700 (PDT) Received: from ?192.168.1.100? ([190.177.209.40]) by mx.google.com with ESMTPS id 8sm1126115agd.37.2009.07.07.17.28.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 07 Jul 2009 17:28:54 -0700 (PDT) From: Gonzalo Nemmi To: Gavin Atkinson Date: Tue, 7 Jul 2009 21:29:01 -0300 User-Agent: KMail/1.9.10 References: <19e9a5dc0907062254u528c4a8ahea2a605e80b1feea@mail.gmail.com> <1246963840.48637.44.camel@buffy.york.ac.uk> In-Reply-To: <1246963840.48637.44.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907072129.01232.gnemmi@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 9 on -BETA1 on boot "with ACPI disabled" or "Safe Mode": 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, 08 Jul 2009 00:28:56 -0000 On Tuesday 07 July 2009 7:50:40 am Gavin Atkinson wrote: > On Tue, 2009-07-07 at 02:54 -0300, Gonzalo Nemmi wrote: > > Can reproduce it on -CURRENT-200906 and -BETA1 whenever I try to > > boot "with ACPI disabled" or "Safe Mode": > > > > Fatal trap 9: general protection fault while in kernel mode > > cpuid = 0; acpic id = 00 > > instruction pointer = 0x70:0xbfe4 > > stack pointer = 0x28:0xfa4 > > frame pointer = 0x28:0xfd4 > > code segment = base 0xc00f0000, limit 0xffff, type 0x1b > > = DPL 0, pres 1, def32 0, gran 0 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 0 (swapper) > > [thread pid 0 tid 100000 ] > > Stopped at 0xbfe4: *** error reading from address bfe4 *** > > db> bt > > Tracing pid 0 tid 100000 td 0x0da9b50 > > uart_z8530_class(780001,0,b0202,ffe,0,...) at 0xbfe4 > > db> > > This may well be a known problem that has affected certain Intel > motherboards since around 5.x. Although this problem may well be > solvable, perhaps the better approach is to fix whatever is stopping > you from booting with ACPI enabled? Hello Gavin :) Actually I can boot with ACPI enabled (default boot), what I can't boot is "with ACPI disabled" or in "Safe Mode" since both of them throw a Fatal trap 9. > If for some reason you cannot have ACPI enabled, I guess knowing more > output than the above would be useful. For example, when booting > verbose and with ACPI disabled, what lines are printed before the > above? > > (to do this, break to the loader prompt, and: > > setenv hint.acpi.0.disabled=1 > setenv hint.apic.0.disabled=1 > boot -v setenv hint.acpi.0.disabled=1 and setenv hint.apic.0.disabled=1 yielded a stack overflow each one, so I tried booting to the loader (#6) and then: OK set hint.acpi.0.disabled=1 OK set hint.apic.0.disabled=1 OK boot -v That resulted in the very same Fatal trap 9 described above :s The lines before I get the Fatal trap are: pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete ex_isa_identify() pnpbios: 13 devices, largest 146 bytes PNP0a3: adding io range 0xcf8-0xcff, size=0x8, align=0x2 pnpbios: handle 0 device ID PNP0a03 (030ad041) Fatal trap 9: general protection fault while in kernel mode ... > it's also worth trying just with the first one to just disable ACPI, > then just trying the APIC option, to see which of those two are > causing you problems) > > By the way, is this i386 or amd64? CPU: Intel(R) Celeron(R) CPU 560 @ 2.13GHz (2128.02-MHz 686-class CPU) You'll fin my boot -v in here should you like to take a look at it: http://pastebin.com/f604c1399 > Gavin Thanks for your concern :) -- Blessings Gonzalo Nemmi