From owner-freebsd-current@FreeBSD.ORG Fri Jul 8 14:43:53 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C82F416A41C for ; Fri, 8 Jul 2005 14:43:53 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27DA743D45 for ; Fri, 8 Jul 2005 14:43:51 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[65.202.103.25]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Fri, 08 Jul 2005 10:57:43 -0400 From: John Baldwin To: Mike Tancsa Date: Fri, 8 Jul 2005 10:06:42 -0400 User-Agent: KMail/1.8 References: <70e8236f05070208212e36c375@mail.gmail.com> <200507071658.27361.jhb@FreeBSD.org> <6.2.1.2.0.20050707220038.08329918@64.7.153.2> In-Reply-To: <6.2.1.2.0.20050707220038.08329918@64.7.153.2> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507081006.43609.jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: 6.0-CURRENT SNAP004 hangs on amr 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: Fri, 08 Jul 2005 14:43:53 -0000 On Thursday 07 July 2005 10:09 pm, Mike Tancsa wrote: > At 04:58 PM 07/07/2005, John Baldwin wrote: > >Crud, it's off in the weeds. :( Can you do a boot -v and get the lines > > after 'pcib3:'? > > Here you go Ok, I see why it is badly confused in the non-APIC and non-ACPI case though I don't know why it is panicing. (FWIW, it is trying to route all interrupts to IRQ 14 because your $PIR is all busted *sigh*). BIOS writers suck. Anyway, I still need a simple matrix of what works and what doesn't work first (if I got one earlier I lost it): ACPI/APIC - amr0 gets no interrupts, hangs after boot ACPI/no-APIC - amr0 gets no interrupts, hangs after boot? no-ACPI/APIC - ??? no-ACPI/no-APIC - busted $PIR causes the code to go off into the weeds Is that summary more or less correct? Can you test the missing case? Also, is there any difference between 5.4 and 6.0 in this table? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org