From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Missing interrupts in 9pxeload?
Date: Sat, 6 Jun 2009 11:00:39 -0400 [thread overview]
Message-ID: <7c3ba90a8c4a8982933e4701243e4b84@quanstro.net> (raw)
In-Reply-To: <aa7e41150906052357n734241f9m200d31a8dad4ce43@mail.gmail.com>
> Longer analysis: Based on your advice, I started playing around in
> 9pxeload to disable things and see if I could run with just the clock
> enabled. That worked. Then, I started to put things back in; I got
> to the point where I realized that the rtl8169init() function wasn't
> returning correctly. Looking at it, I saw that the likely culprit was
> the switch statement testing ctlr->macv; sure enough, my macv
> (0x24800000 - I guess I was a little wrong about exactly what chipset
> it is) didn't have a case associated with it. So, I added one (that
> just did break;). Voila the kernel loaded (and so did the plan9.ini
> from /cfg/pxe).
that's good work. i put out a 9load-e820 with a revised rtl8169
driver that should complain if the mac is not recognized but the
vid/did are rather than putting the 8169 into this state.
if this works, i'll put similar changes into a 8169 kernel driver.
i believe several other people have seen this problem with
similar hardware.
- erik
next prev parent reply other threads:[~2009-06-06 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 20:38 Dan Cross
2009-06-05 18:28 ` erik quanstrom
2009-06-05 20:49 ` Dan Cross
2009-06-05 21:30 ` balaji
2009-06-05 22:18 ` Dan Cross
2009-06-06 2:18 ` erik quanstrom
2009-06-06 6:57 ` Dan Cross
2009-06-06 15:00 ` erik quanstrom [this message]
2009-06-06 2:19 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c3ba90a8c4a8982933e4701243e4b84@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).