right, it does mention IRQ, but I fail to see any IRQ problem - here's what
my /proc/interrupts says :
CPU0
0: 8012525 XT-PIC timer
1: 47285 XT-PIC keyboard
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 317729 XT-PIC eth0
10: 34 XT-PIC HiSax
11: 71619 XT-PIC usb-uhci, usb-uhci
12: 4375723 XT-PIC HiSax
13: 1 XT-PIC fpu
14: 3202602 XT-PIC ide0
15: 2 XT-PIC ide1
NMI: 0
and we see HiSax gets both IRQ 10 and 12, which is exactly what I get from
grepping my messages :
Oct 29 01:15:17 ariadna kernel: HiSax: TA XXX config irq:12 I/O:7400
Oct 29 01:15:18 ariadna kernel: HiSax: TA XXX config irq:10 I/O:7800
and it all fits nicely with what my BIOS reports on boot :-)
like I said, these are PCI cards.
I would love to hear any more suggestions that you may have...
TIA
Oded
..
Murphy's Law, that brash proletarian restatement of Godel's Theorem.
-- Thomas Pynchon, "Gravity's Rainbow"
----- Original Message -----
From: "Shaul Karl" <[EMAIL PROTECTED]>
To: "Oded Arbel" <[EMAIL PROTECTED]>
Cc: "Linux-Il Mailing List" <[EMAIL PROTECTED]>
Sent: Saturday, October 28, 2000 8:39 PM
Subject: Re: Problems with ISDN
> > I managed to get some more logging from the hisax module, but it's (a)
way
> > to long (something like a few pages worth every second) and (b) boring -
I
> > don't understand a thing out of it, and I'm not sure which parts are
> > important. I would have attached the entire log file (or at least part
of
> > it), but I know the list frowns upon attachments, so I'd just leave it
be..
> > I think that maybe the post was just too detailed, so here's a skinny
(if
> > you need indepth knowledge of my system, just read on) -
> > why do I get a message 'W6692 IRQ LOOP' broadcasted to all ttys and in
the
> > messages log file when using my MultiTech winbond 6692 based ISDN card
with
> > the hisax module, just before the connection freezes, and how can I stop
> > that from happening ?
> > if it's a hardware problem (which I think it might be), and I want to
> > replace my ISDN cards, which passive ISDN cards would you recomend me to
get
> > instead ?
> >
>
>
> Perhaps this is an IRQ problem? After all, the message quoted does
mentions
> IRQ.
> Maybe /proc/interrupts can show something?
> My logs shows this info:
> [20:37:46 /tmp]$ dmesg |grep "config irq"
> HiSax: AVM Fritz!PCI config irq:11 base:0x6100
> [20:38:01 /tmp]$
> Are those ISA/ISA-PNP cards?
>
>
> > TIA
> >
> > Oded
> >
> > ..
> > VAXORCIST: Everything looks okay to me.
> > SYSMGR: Maybe it's hibernating.
> > VAXORCIST: Unlikely. It's probably trying to lure us into a false sense
of
> > security.
> > SYSMGR: Sounds like VMS alright. (VAXORCIST gives him a dirty look)
> > -- from The Vaxorcist , (C) 1991 by Christopher Russell
> >
> > ----- Original Message -----
> > From: "Shaul Karl" <[EMAIL PROTECTED]>
> > To: "Oded Arbel" <[EMAIL PROTECTED]>
> > Cc: "Linux-Il Mailing List" <[EMAIL PROTECTED]>
> > Sent: Friday, October 27, 2000 3:23 PM
> > Subject: Re: Problems with ISDN
> >
> >
> > > What about log files (syslog, messages, debug)? Both boot messages and
> > making
> > > the connection are worth looking into.
> > > I suppose enable more debugging level in the config files is necessary
in
> > this
> > > case.
> > >
> > >
> > >
> > > > Hello list.
> > > >
> > > > I seem to have a problem with my ISDN connection - it doesn't stay
> > connected
> > > > very long, and I think that may be a problem on my side - here's the
> > deal :
> > > >
> > > > I have two MultiTech PCI128 passive ISDNs card - they are supported
> > using
> > > > the HiSax module as type 36 (it's a 6692 winbond chip based) When
I've
> > tried
> > > > to install them both on my computer (an old P2-266) they refused to
work
> > and
> > > > generated an E001B error message whenever I dialed. when I instaled
> > windows
> > > > to see if that could dial both modems, it did. I concluded that it
must
> > be
> > > > some wierd hardware problem that makes linux unable to use both
modems
> > (I
> > > > went over my configuration hundreds of times, and it must be a
hardware
> > > > problem - I have a really really old and cranky motherboard), so I
took
> > one
> > > > out and used just one for a 128Kbit connection. it worked great, but
I
> > > > wanted to use both, so I ordered me a new motherboard . while
Plonter
> > were
> > > > busy getting me the board (my first choise wasn't in stock and wasnt
> > > > produced any more, so was my second choise, and it didn't help me
being
> > in
> > > > 'miluim' a few days too), all in all it worked for about two weeks
> > without a
> > > > glitch - I use that computer to masquarade for my local home LAN
(which
> > > > includes two more computers) and the connection was on 24/7 .
> > > > Then I got the new board. after moving everything to then new board
and
> > case
> > > > (the old one was an AT computer, and the new is an ATX, so I needed
a
> > new
> > > > case too), I happily plugged in both ISDN cards, configured them
(it's a
> > > > pain to get any pre written script to support a multi link using one
> > slave,
> > > > let alone 3 slaves ...) and dialed - lo and behold : it works !
> > > > well, not exactly.. if I use all 4 devices, after a while of being
> > connected
> > > > (let's say, about two minutes) I get this error message printed to
the
> > > > screen (it isnt stored in any of the logs.. wierd..) :
> > > > W6692 IRQ LOOP
> > > > (w6692 is the id of my card's chip)
> > > > and then the connection just stops responding. hanging up and
redialing
> > > > doenst seem to work, it just dials, timesout (with no error
message),
> > dials
> > > > again, and so on until it runs out of dialing attempts. I have to
stop
> > and
> > > > remove all the isdn things (ipppd, hisax, etc) and then restart
> > everything
> > > > to get it going.
> > > > if I dial less devices (all are configured, I just don't dial them),
I
> > still
> > > > get that message , but after longer time (even if I use only the
master
> > > > device !).
> > > > so I gave up and took one card out of the box, leaving just one in
and
> > > > dialing with two devices... but - it still doesn't work as good as
it
> > used
> > > > too on the old board. it still disconnects unexpectedly, that is -
the
> > > > connection doesnt drop, it just stops responding, and I don't know
why -
> > it
> > > > does so when I'm not looking, and I couldn't find anything in the
logs .
> > > > also hanging up and redialing doesn't help, and last time it
happened,
> > > > restarting the isdn scripts and daemons didn't either - I think it
> > because
> > > > it couldn't unload the hisax module, claiming it was busy, and I
> > couldn't
> > > > manually either, so I had to reboot (!!!!!) to get back my
connection.
> > > > also, after I get the connection back, and the IP has changed, the
> > > > masquarding does not work, and I need to flush the chains and
reapply
> > the
> > > > MASQ rule to get it to work (though the rule isn't related to the
> > outgoing
> > > > IP at all).
> > > > one more thing - after I get connected, about a minute and a half, I
get
> > > > this message in the logs -
> > > > Oct 27 11:32:27 ariadna kernel: HiSax: W6692 XDUN/XCOL
> > > > I don't know what it means.
> > > >
> > > > here's my setup -
> > > > hard:
> > > > P2-266 chip on a 66MHz bus
> > > > Aopen AX64 board (4 PCIs , onbaord sound - I disabled it , coz it
shares
> > an
> > > > IRQ line with the 3rd PCI slots where I put my NIC, and it messes
things
> > up)
> > > > 128MB ram
> > > > RTL8139 NIC
> > > > 2x MultiTech ISDN PCI128 (only one installed currently)
> > > > ATI rageIIc on AGP
> > > > soft:
> > > > Redhat 7.0
> > > > isdn4net scripts (which I got as an RPM from freshmeat, and then
heavily
> > > > patched, and not in a nice way)
> > > > { the script came with a program called 'iprofd' - what does it
needs it
> > for
> > > > ? }
> > > > basicly, these are the commands that are being issued to make my
ISDN
> > card
> > > > dial out to my ISP:
> > > > # /sbin/modprobe hisax type=36,36 id=w6692 protocol=2,2
> > > > # echo 1 > /proc/sys/net/ipv4/ip_dynaddr
> > > > # isdnctrl readconf /etc/isdn/ctrl.conf.new
> > > > # isdnctrl pppbind ippp0
> > > > # /usr/sbin/ipppd 0.0.0.0:0.0.0.0 deldefaultroute user
<myloginname>
> > > > ipparam ippp0 ipcp-accept-local ipcp-accept-remote
> > > > defaultroute -vj -vjccomp -ac -pc -bsdcomp -chap ms-get-dns
/dev/ippp0
> > > > /dev/ippp1 /dev/ippp2 /dev/ippp3 +mp
> > > > # isdnctrl dial ippp0
> > > >
> > > > P.S.
> > > > while I was writing this, the connection just died again - it didnt'
> > drop,
> > > > just stoped responding. no message in the logs. hanging up and
redialing
> > did
> > > > the trick and I got this message afterwards :
> > > > Oct 27 11:55:44 ariadna kernel: IP_MASQ:ip_fw_masquerade(): change
> > masq.addr
> > > > from 212.150.99.2 to 212.150.97.72
> > > > but still had to flush and reapply the masq rule.
> > > > also - is there a way that I can make a script run whenever the
> > connection
> > > > drops (really drops) ?
> > > >
> > > > TIA , and sorry for the long message, I thought that supplying some
> > details
> > > > will get me a better and faster response..
> > > >
> > > > Oded
> > > >
> > > > ..
> > > > "I have the terrible feeling that, because I have a white beard and
am
> > > > sitting
> > > > in the back of the theater, you expect me to tell you the truth
about
> > > > something.
> > > > These are the cheap seats, not Mount Sinai."
> > > > --Orson Welles, "Someone to Love."
> > > >
> > > >
> > > >
> > > > =================================================================
> > > > To unsubscribe, send mail to [EMAIL PROTECTED] with
> > > > the word "unsubscribe" in the message body, e.g., run the command
> > > > echo unsubscribe | mail [EMAIL PROTECTED]
> > > >
> > >
> > > --
> > >
> > > Shaul Karl <[EMAIL PROTECTED]>
> > >
> > >
> > >
> > > =================================================================
> > > To unsubscribe, send mail to [EMAIL PROTECTED] with
> > > the word "unsubscribe" in the message body, e.g., run the command
> > > echo unsubscribe | mail [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > =================================================================
> > To unsubscribe, send mail to [EMAIL PROTECTED] with
> > the word "unsubscribe" in the message body, e.g., run the command
> > echo unsubscribe | mail [EMAIL PROTECTED]
> >
>
> --
>
> Shaul Karl <[EMAIL PROTECTED]>
>
>
>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
