Date: Wed, 06 Jul 2005 10:01:48 +0200 From: Martin Nilsson <martin@gneto.com> To: Joao Barros <joao.barros@gmail.com> Cc: freebsd-current@freebsd.org, Mike Tancsa <mike@sentex.net> Subject: Re: 6.0-CURRENT SNAP004 hangs on amr Message-ID: <42CB8FEC.7060508@gneto.com> In-Reply-To: <70e8236f050706002655cd9a0c@mail.gmail.com> References: <70e8236f05070208212e36c375@mail.gmail.com> <42C6DA5F.9070303@gneto.com> <6.2.1.2.0.20050703212843.07889088@64.7.153.2> <20050705011650.R80892@lexi.siliconlandmark.com> <70e8236f050706002655cd9a0c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Joao Barros wrote: > One thing I noticed: I can press scroll lock and move around through > the console text. I suppose a hanged kernel wouldn't allow this?! I had the following conversation with Scott Long, but I never had time to follow it up and the box I was using had other problems with FreeBSD CURRENT. See if the below is also true for your box. Regards, Martin > Scott Long wrote / skrev: > >> I wonder if there is an interrupt routing problem. Can you compile in KDB and DDB? When the hang occurs, note the irq that was assigned to the amr driver (it'll be printed on the console), and then drop into DDB and do 'show intrcnt'. > > > > amr0 gets irq25 but there is no such entry in the "show intrcnt" table. > > I tried to boot the system without ACPI but it panics with: > Multiple IRQs for PCI interrupt 0.31.INTA: 18 and 16 > Yep, it's an interrupt routing problem. Contact John Baldwin and Nate Lawson. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42CB8FEC.7060508>