From owner-freebsd-ia64 Sun Nov 11 23:25:19 2001
Delivered-To: freebsd-ia64@freebsd.org
Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180])
by hub.freebsd.org (Postfix) with ESMTP id 11C2537B417
for <ia64@FreeBSD.ORG>; Sun, 11 Nov 2001 23:25:16 -0800 (PST)
Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3])
by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id fAC7PFM12144
for <ia64@FreeBSD.ORG>; Sun, 11 Nov 2001 23:25:15 -0800 (PST)
(envelope-from peter@wemm.org)
Received: from wemm.org (localhost [127.0.0.1])
by overcee.netplex.com.au (Postfix) with ESMTP
id DD68538FD; Sun, 11 Nov 2001 23:25:14 -0800 (PST)
(envelope-from peter@wemm.org)
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
To: Marcel Moolenaar <marcel@xcllnt.net>
Cc: ia64@FreeBSD.ORG
Subject: Re: Regressing...
In-Reply-To: <20011110143603.A10085@dhcp01.pn.xcllnt.net>
Date: Sun, 11 Nov 2001 23:25:14 -0800
From: Peter Wemm <peter@wemm.org>
Message-Id: <20011112072514.DD68538FD@overcee.netplex.com.au>
Sender: owner-freebsd-ia64@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ia64.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ia64>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ia64>
X-Loop: FreeBSD.org
Marcel Moolenaar wrote:
> On Sat, Nov 10, 2001 at 01:19:27PM -0800, Peter Wemm wrote:
> >
> > I've had this a few times before. I dont recall anything in particular
> > fixing it, but changing/building a kernel seemed to help.
>
> That doesn't seem to fix it, even if I remove the build directory.
> I updated the ia64 subtree with dated sources, but that didn't improve
> as well. I'm now updating my whole sys tree with Nov 2nd sources.
>
> I hope it's not a hardware problem...
For what its worth, I reproduce this exactly here.
I'm getting suspicious of the last acpica import now. I cant see anything
else that looks even remotely likely to cause a failure like this.
Look familiar?
Timecounter "IA64 ITC" frequency 800029008 Hz
acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5%
ata0-master: ata_command: timeout waiting for intr
ata0-master: ATAPI identify failed
ata1-master: ata_command: timeout waiting for intr
ata1-master: ATAPI identify failed
Waiting 2 seconds for SCSI devices to settle
isp0: Interrupting Mailbox Command (0x38) Timeout
isp0: Mailbox Command 'SET TARGET PARAMS' failed (TIMEOUT)
isp0: Interrupting Mailbox Command (0x38) Timeout
isp0: Mailbox Command 'SET TARGET PARAMS' failed (TIMEOUT)
isp0: Interrupting Mailbox Command (0x28) Timeout
I'm guessing that the interrupt routing is hosed.
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message
From owner-freebsd-ia64 Sun Nov 11 23:38:34 2001
Delivered-To: freebsd-ia64@freebsd.org
Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226])
by hub.freebsd.org (Postfix) with ESMTP id D259E37B405
for <ia64@FreeBSD.ORG>; Sun, 11 Nov 2001 23:38:30 -0800 (PST)
Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3])
by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id fAC7cUQ24840;
Sun, 11 Nov 2001 23:38:30 -0800 (PST)
(envelope-from marcel@kayak.pn.xcllnt.net)
Received: (from marcel@localhost)
by athlon.pn.xcllnt.net (8.11.6/8.11.5) id fAC7cJA14182;
Sun, 11 Nov 2001 23:38:19 -0800 (PST)
(envelope-from marcel)
Date: Sun, 11 Nov 2001 23:38:19 -0800
From: Marcel Moolenaar <marcel@xcllnt.net>
To: Peter Wemm <peter@wemm.org>
Cc: ia64@FreeBSD.ORG
Subject: Re: Regressing...
Message-ID: <20011111233819.B14074@athlon.pn.xcllnt.net>
References: <20011110143603.A10085@dhcp01.pn.xcllnt.net> <20011112072514.DD68538FD@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011112072514.DD68538FD@overcee.netplex.com.au>
User-Agent: Mutt/1.3.21i
Sender: owner-freebsd-ia64@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ia64.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ia64>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ia64>
X-Loop: FreeBSD.org
On Sun, Nov 11, 2001 at 11:25:14PM -0800, Peter Wemm wrote:
> Marcel Moolenaar wrote:
> > On Sat, Nov 10, 2001 at 01:19:27PM -0800, Peter Wemm wrote:
> > >
> > > I've had this a few times before. I dont recall anything in particular
> > > fixing it, but changing/building a kernel seemed to help.
> >
> > That doesn't seem to fix it, even if I remove the build directory.
> > I updated the ia64 subtree with dated sources, but that didn't improve
> > as well. I'm now updating my whole sys tree with Nov 2nd sources.
> >
> > I hope it's not a hardware problem...
>
> For what its worth, I reproduce this exactly here.
I wasted a whole weekend on this, but I think in the end it's my
own damn fault. I just committed fixes for both the UP and MP
configurations.
This is what I think was wrong:
The UP configuration was broken because we didn't probe the MADT
at all (it was done in cpu_mp_probe). We create IOSAPIC devices
for every IOSAPIC we find. This seems to have caused the INTR
failures for UP configurations. I wasn't aware it was broken to
this extend, but it must have been.
MP configurations were broken because the AP ended up in trap()
before it was even properly initialized. This didn't happen
before (ie page faults were always handled by the low-level
trap code). I smacked myself on the head and told myself to not
try to make it perfect the first time, because I can't. I don't
have the experience...
> I'm getting suspicious of the last acpica import now. I cant see anything
> else that looks even remotely likely to cause a failure like this.
It may have emphasized the effect, because it appeared to be working
before and then suddency failed to work at all.
> Timecounter "IA64 ITC" frequency 800029008 Hz
> acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5%
> ata0-master: ata_command: timeout waiting for intr
> ata0-master: ATAPI identify failed
> ata1-master: ata_command: timeout waiting for intr
> ata1-master: ATAPI identify failed
> Waiting 2 seconds for SCSI devices to settle
> isp0: Interrupting Mailbox Command (0x38) Timeout
> isp0: Mailbox Command 'SET TARGET PARAMS' failed (TIMEOUT)
> isp0: Interrupting Mailbox Command (0x38) Timeout
> isp0: Mailbox Command 'SET TARGET PARAMS' failed (TIMEOUT)
> isp0: Interrupting Mailbox Command (0x28) Timeout
Oh yeah... I've been seeing this 6 times an hour over the last
30 hours :-)
Anyway: cvsup and see how it goes. I'm going to drink heavily
for the rest of the evening, because I need a stiff drink...
--
Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message
From owner-freebsd-ia64 Mon Nov 12 10: 7:43 2001
Delivered-To: freebsd-ia64@freebsd.org
Received: from mass.dis.org (mass.dis.org [216.240.45.41])
by hub.freebsd.org (Postfix) with ESMTP id A4E6337B418
for <ia64@FreeBSD.ORG>; Mon, 12 Nov 2001 10:07:41 -0800 (PST)
Received: from mass.dis.org (localhost [127.0.0.1])
by mass.dis.org (8.11.6/8.11.3) with ESMTP id fACI9Nn01044;
Mon, 12 Nov 2001 10:09:27 -0800 (PST)
(envelope-from msmith@mass.dis.org)
Message-Id: <200111121809.fACI9Nn01044@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Peter Wemm <peter@wemm.org>
Cc: Marcel Moolenaar <marcel@xcllnt.net>, ia64@FreeBSD.ORG
Subject: Re: Regressing...
In-reply-to: Your message of "Sun, 11 Nov 2001 23:25:14 PST."
<20011112072514.DD68538FD@overcee.netplex.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 12 Nov 2001 10:09:23 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-ia64@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ia64.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ia64>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ia64>
X-Loop: FreeBSD.org
>
> I'm getting suspicious of the last acpica import now. I cant see anything
> else that looks even remotely likely to cause a failure like this.
What interrupt is actually being assigned to the driver?
There should be another ACPI CA drop shortly; the acpi-jp folks found a
couple of killer bugs in the most recent one (which I have not
integrated).
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message