From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Bogus shared IRQ on Dell D610
Date: Sun, 12 Feb 2006 18:56:17 -0800 [thread overview]
Message-ID: <C09C0449-CF15-4AE9-8C6D-33D870AC5DCF@orthanc.ca> (raw)
A bit more info on the 3C589 problems I'm having on my D610 laptop.
During boot the kernel says:
...
ELCR: 0E80
#y0: 2 slot Intel 82365SL: port 0x3E0 IRQ 5
#y1: 2 slot Intel 82365SL: port 0x3E0 IRQ 5
8259enable: irq 5 shared but not level
intrenable: couldn't enable irq 5, tbdf 0xFFFFFFFF for i82365.1
#I0: xcvr10BaseT 3C589
I0: 3C589: 10 Mbps port 0x240 irq 10: 00104bdf06a8
...
The kernel is getting confused about #y1, which makes sense, because
there is no #y1. This laptop only has a single card slot. The 589
card is visible, and both /net/ether0/stats and ifstats are reporting
traffic in both directions (provoked by trying the DHCP dance with ip/
ipconfig), it just seems as though the received data isn't being
handed up to the user mode process.
I'm puzzled whether this is because of the irq 5 confusion. The card
claims it's interrupting on irq 10, and the driver claims to be
receiving (good) frames. Should irq 5 even matter after the kernel
finds the device and (apparently successfully) maps it's memory and
sets up the interrupt routing?
--lyndon
next reply other threads:[~2006-02-13 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 2:56 Lyndon Nerenberg [this message]
2006-02-13 7:57 ` Lyndon Nerenberg
2006-02-13 8:14 ` Lyndon Nerenberg
2006-02-13 17:40 ` Dave Eckhardt
2006-02-13 18:47 ` Lyndon Nerenberg
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=C09C0449-CF15-4AE9-8C6D-33D870AC5DCF@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
/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).