From owner-freebsd-current@FreeBSD.ORG  Tue Nov  4 07:49:30 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 3A01216A4CE; Tue,  4 Nov 2003 07:49:30 -0800 (PST)
Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DAE7643FD7; Tue,  4 Nov 2003 07:49:26 -0800 (PST)
	(envelope-from l.ertl@univie.ac.at)
Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177])
	hA4FnIwN436354;	Tue, 4 Nov 2003 16:49:20 +0100
Date: Tue, 4 Nov 2003 16:49:18 +0100 (CET)
From: Lukas Ertl <l.ertl@univie.ac.at>
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <XFMail.20031104103918.jhb@FreeBSD.org>
Message-ID: <20031104164627.Y22613@pcle2.cc.univie.ac.at>
References: <XFMail.20031104103918.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-DCC-ZID-Univie-Metrics: imap 4243; Body=0 Fuz1=0 Fuz2=0
cc: current@FreeBSD.org
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 15:49:30 -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.

Sorry for the noise, I think I found the problem: I had to put "options
SMP" and "device apic" into the kernel, now everythings seems to run fine.
I thought they were only needed for SMP kernels, that's at least what
the comment in GENERIC says...  If you still want the dmesg, I can send it
to you.

sorry,
regards.
le

-- 
Lukas Ertl                             eMail: l.ertl@univie.ac.at
UNIX Systemadministrator               Tel.:  (+43 1) 4277-14073
Vienna University Computer Center      Fax.:  (+43 1) 4277-9140
University of Vienna                   http://mailbox.univie.ac.at/~le/