Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Aug 2001 12:03:48 -0600
From:      Nate Williams <nate@yogotech.com>
To:        Warner Losh <imp@harmony.village.org>
Cc:        nate@yogotech.com (Nate Williams), mobile@FreeBSD.ORG
Subject:   Re: HEADS UP: pcic pci attachments merged from current 
Message-ID:  <15228.2820.792698.491952@nomad.yogotech.com>
In-Reply-To: <200108161753.f7GHrZW34243@harmony.village.org>
References:  <15228.1694.871200.901582@nomad.yogotech.com> <15227.21642.728459.378078@nomad.yogotech.com> <15226.52618.594233.704448@nomad.yogotech.com> <200108150433.f7F4X1W20487@harmony.village.org> <200108160317.f7G3HHW28812@harmony.village.org> <200108160533.f7G5XWW29552@harmony.village.org> <15227.65384.819476.423333@nomad.yogotech.com> <200108161753.f7GHrZW34243@harmony.village.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> : I'm working on tracking down new hangs as to which commit is causing
> : this.
> 
> Cool.  I'm getting ready to spend some time out in the Big Blue Room.

What's that?  Is that the room that makes your skin turn brown, instead
of that wonderful sickly green color. *grin*

> To be honest, I'd suspect one of two things is going on:
> 
> First, one of the bits in the config registers that you sent me that
> are different is hozing you.  The interrupt is routed in a funky way
> that the pcic interrupt isn't seeing since it is coming out a
> different IRQ than is attached to the PCI line.  Likely due to one bit
> in one of the config registers saying "route this via comsat and map
> it" or maybe it might be the INTRTIE bit isn't needed on that card.
> Could be either one.

Ok.

> Or, Maybe we do see it once, and fail to properly handle the
> interrupt, so when we exit our interrupt handler, we go right back in.
> I consider this less likely since you didn't say you saw any pcic0:
> Event mask 0xX in your failing dmesg.

I don't remember seeing anything like that, and in reviewing the boot
message, I didn't see anything. :)

In any case, here's my latest update:

# cd /usr/src/sys
# cvs update -Pdr RELENG_4 -D'August 5, 2001'
[ Build new kernel, install, reboot ]

This works fine.  So, sometime after August 5 it's broken.  I noticed a
change on the 6th, so I'll update to the 7th and see what happens.



Nate

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15228.2820.792698.491952>