From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a670439cab10dcc08e8db1ab3e3b5ac2@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri,  5 Jun 2009 14:28:08 -0400
To: 9fans@9fans.net
In-Reply-To: <aa7e41150906041338u66c43391o4fcd16e44a822f6b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Missing interrupts in 9pxeload?
Topicbox-Message-UUID: 0549b424-ead5-11e9-9d60-3106f5b1d025

> below).  The machine has no mass storage device of any kind, nor an
> optical drive.  It does have a VGA interface and is connected to a
> keyboard and mouse by the onboard PS/2 connectors.  It is not using
> USB at all.  I have disabled pretty much everything except the
> graphics adapter and ethernet in the BIOS.
>
> I am attempting to PXE boot it from my file/auth/boot/cpu server (the
> aforementioned machine that is having some problems).  The machine
> DHCP's fine, and will load 9pxeload via TFTP, but then hangs.  I
> started playing around with 9pxeload to see what was going on,
> including updating the driver in /sys/src/boot/pc using Erik's latest
> from his directory on sources, but still no go.  I finally traced
> through the code far enough to see that it is getting stuck in the
> wait() routine in ether.c; that is defined in l.s, and just calls
> 'HLT' and 'RET'.  Ie, do nothing until you receipt of an interrupt and
> return.  However, no interrupts ever arrive; modifying wait() to
> comment out the call to idle() and then printing m->ticks every
> million or so iterations through the loop shows that m->ticks doesn't
> change.  It's as if all interrupts somehow got turned off prior to the
> call to wait().  Has anyone else seen this?  Could there be something
> somewhere that's disabling interrupts that I should look into?  Could
> things be being routed weirdly on an Atom processor?

how are you verifying that this machine isn't getting any
interrupts?  the wait loop will loop if an interrupt is rx'd
unless ring->owner != owner or it times out.  are you saying
that wait doesn't even timeout?

or do you mean that it's not getting any ethernet interrupts?
what irq is being enabled by ether8269.c?

- erik