From owner-freebsd-current@FreeBSD.ORG  Tue Nov  4 09:48:13 2003
Return-Path: <owner-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 E48DC16A4CE; Tue,  4 Nov 2003 09:48:13 -0800 (PST)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3118243F75; Tue,  4 Nov 2003 09:48:12 -0800 (PST)
	(envelope-from bde@zeta.org.au)
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id EAA26820;
	Wed, 5 Nov 2003 04:48:09 +1100
Date: Wed, 5 Nov 2003 04:48:08 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <XFMail.20031104103918.jhb@FreeBSD.org>
Message-ID: <20031105043233.G840@gamplex.bde.org>
References: <XFMail.20031104103918.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@FreeBSD.org
cc: Lukas Ertl <l.ertl@univie.ac.at>
Subject: Re: new interrupt code: panic when going multiuser
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2003 17:48:14 -0000

On Tue, 4 Nov 2003, John Baldwin wrote:

> On 04-Nov-2003 Lukas Ertl wrote:
> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
> >
> >> I somehow can't get at a good vmcore :-(.  But I found out that the
> >> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned off.
> >
> > Ok, if I set hw.ata.ata_dma=0 in loader.conf, it boots fine.  Could there
> > be some issue with ATAng + new interrupt code?
>
> Can you provide a dmesg please?  There may be a weird issue with
> some PPro's for example that I haven't been able to test.

I have noticed the following problems with the new interrupt code so far:
- it conflicts with a few thousand lines of local changes.
- yesterday's backup kernels which I preserved to run benchmarks with
  all hang at boot time while probing atapicam devices.  Backing out
  rev.1.23 of ata-lowlevel.c fixes the hang, but I didn't back up
  yesterday's sources so it will take some work to regenerate working
  versions of yesterday's kernels.

The following is without the local changes:
- cyintr(int unit) panics becauase it is passed a pointer to somewhere.
  I think all compat_isa devices are broken for unit 0 because unit 0
  is represented by a null pointer.
- on a BP6, UP kernels without apic work except for cyintr(), but SMP
  kernels have problems with missing interrupts for ata devices and hang
  at boot time.

Bruce