Hi all,
The attached thread (apologies for the volume of text, but it is all
relevant) came up on freebsd-xircom last week. Jose Alcaide actually
posted to -mobile on the same subject a week or so before, but got no
response. We figure it's definitely nothing to do with the Xircom driver
in particular and probably nothing to do with pccard, so I'm bouncing it to
any interested kernel gurus.
Essentially, the irq line to which clk0 interrupts are accounted (in the
output from vmstat -i) changes when pccards are inserted/removed. The same
effect has been seen with cards using the xe0 and ed0 drivers.
Any ideas?
Scott
--
===
Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just
Cambridge, England | 0x54B171B9 | like a dried up piece of roast goat"
[EMAIL PROTECTED] | 0xAA775B8B | -- J. S. Bach.
Hello,
I have just purchased a Xircom RE-100BTX. It works fine, but I found
something very strange. After booting the system (with no pccard inserted),
"vmstat -i" shows:
interrupt total rate
clk0 irq0 718701 100
...
But, just after I insert the Xircom card and it is detected and enabled,
another "vmstat -i" shows:
interrupt total rate
clk0 irq3 732248 110
(IRQ3 is the first available interrupt in my system, and it is assigned
to the Xircom card by the pccardd daemon. I am running FreeBSD 3.4-RELEASE,
no PAO.)
After inserting the card, the clk0 interrupts are accounted to the
interrupt level used by the Xircom card (I have tried other IRQ levels
with the same result). The 100 interrupts/second generated by the
timer are added to the interrupts generated by the Ethernet adapter.
Since I don't have any other PCMCIA cards, I don't know whether this
"problem" only happens with the xe driver or, on the contrary, it is
a general problem of the FreeBSD's pccard driver.
Did anybody find this same behavior?
-- JMA
---
José Mª Alcaide | mailto:[EMAIL PROTECTED]
Universidad del País Vasco | mailto:[EMAIL PROTECTED]
Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose
Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479
48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071
---
"Beware of Programmers who carry screwdrivers" -- Leonard Brandwein
After inserting the card, the clk0 interrupts are accounted to the
interrupt level used by the Xircom card (I have tried other IRQ
levels
with the same result). The 100 interrupts/second generated by the
timer are added to the interrupts generated by the Ethernet adapter.
Since I don't have any other PCMCIA cards, I don't know whether this
"problem" only happens with the xe driver or, on the contrary, it is
a general problem of the FreeBSD's pccard driver.
Hmmm taking a quick look at my 'vmstat -i' output I see the same
thing:
clk0 irq10 2667404102
bunch of others deleted
IRQ10 is the IRQ I hooked to my RealPort.
I'll give the ed0 card I have at home a shot tonight.
DocWilco
On Tue, Jan 25, 2000 at 05:31:08PM +0100, ROGIER MULHUIJZEN wrote:
After inserting the card, the clk0 interrupts are accounted to the
interrupt level used by the Xircom card (I have tried other IRQ
levels
with the same result). The 100 interrupts/second generated by the
timer are added to the interrupts generated by the Ethernet adapter.
Since I don't have any other PCMCIA cards, I don't know whether this
"problem" only happens with the xe driver or, on the contrary, it is
a general problem of the FreeBSD's pccard driver.
Hmmm taking a quick look at my 'vmstat -i' output I see the same
thing:
clk0 irq10 2667404102
bunch of others deleted
IRQ10 is the IRQ I hooked to my RealPort.
I'll give the ed0 card I have at home a shot tonight.
Another data point:
Script started on Wed Jan 26 21:18:22 2000
orac 78 ~ vmstat -i
interrupt total rate
clk0 irq3 23175 99
rtc0 irq8 29662 127
fdc0 irq6 10
wdc0 irq14 19348
atkbd0 irq1 4682
psm0 irq12 90
Total 55249 238
[xe0 inserted here]
orac 79 ~ vmstat -i
interrupt total rate
clk0 irq10 33303 100
rtc0 irq8 42600 127
fdc0 irq6 10
wdc0 irq14 20886
atkbd0 irq1 5011
psm0 irq12 90
Total 78502 235
orac 80 ~ exit
irq3 is where my pccard controller typically lives; irq10 is (of course)
the line occupied by xe0. I'll be interested to see what happens with
Rogier's ed0 (I should probably borrow a 3Com card from work and try the
same thing) but I suspect this is a case of the generic pccard code being
weird
