Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Jan 98 18:37:56 -0700
From:      "Sean J. Schluntz" <schluntz@pinpt.com>
To:        "Mike Smith" <mike@smith.net.au>
Cc:        "Goeringer,    Michael" <goeringerm@keywest.ird.rl.af.mil>, <freebsd-mobile@FreeBSD.ORG>
Subject:   Re: Ach! Slot 0, unfielded interrupt 0 (unbreakable loop) 
Message-ID:  <199802010232.SAA14584@gromit.pinpt.com>

next in thread | raw e-mail | index | archive | help
*From the fingers of Mike Smith
>> >Make sure pccardd is *NOT* running.  Insert the card and say 
>> >"pccardc dumpcis".  Look through the output for an entry like this:
>> 
>> Does killing it after it launches ok?  I found that I got strange errors 
>> if I turned off pccard in rc.conf but was able to get the info you 
>> mentioned when I let the system load it on boot and then killed it.
>
>The fact that things don't work unless you have run pccardd are 
>strange; it certainly *should* work.  I am beginning to suspect that 
>there is something very odd with your pcic/laptop.

Heh, now you tell me *grin*.  You see, when I purchased it I was told by 
the sales person at Dell that it would work fine with NT.  I got it and 
when I went to load NT on it I found there were no video drivers for it 
anywhere to be found.  Upon calling Dell tech support I was informed that 
they did not support my laptop with NT. :(  (Luckily I've been working 
with NT for a while so I was able to dredge up what I needed with out 
their help.)


>> I actually got two?: ('scuze any typos, it's on the laptop and I'm 
>> writing from the PMac.)
>> 
>> Tuple #7, code 0x1b (Configuration entry), length = 15
>>    000: 03 01 71 55 26 26 54
>>        Config index = 0x1(default)
>> 
>> and 
>> 
>> Tuple #8, code 0x1b (Configuration entry), length = 7
>>    000:  03 01 71 55 26 26 54
>>        Config index = 0x3
>
>OK, so the only two valid configuration indices are 0x1 and 0x3.  What 
>are the I/O addresses associated with them? (There should be extra data 
>in thost tuples, but I can't read them 8)

Ah, sorry ;)  Here they are:

Tuple #7, code 0x1b (Configuration entry), length = 15
    000: 03 01 71 55 26 26 54
        Config index = 0x1(default)
        Interface byte = 0x1 (I/O)
        Vcc pwd:
               Nominal operating supply voltage: 5 x 1V
               Max current average over 1 second: 3 x 10mA
               Max current average over 10 ms: 5 x 10mA
               Power down supply current: 5 x 1mA
        Wait scale Speed = 7.0 x 100 ns
        RDY/BSY scale Speed = 7.0 x 100 ns
        Card decodes 18 address lines, full 8/16 Bit I/O
               IRQ modes: Level, Pulse
               IRQs:  IOCK 1 4 5 6 8 10 11 12 14
Tuple #8, code 0x1b (Configuration entry), length = 7
    000:  03 01 71 55 26 26 54
        Config index = 0x3
        Vcc pwd:
               Nominal operating supply voltage: 5 x 1V
               Max current average over 1 second: 2 x 100mA
               Max current average over 10 ms: 2 x 100mA
               Power down supply current: 5 x 1mA
     

>
>> Ok, here is what happens:
>> 
>> config 0x1 "ep0" 10 
>>      Card inserted, slot 0         # 30-45 second delay
>>      Slot0, unfielded interrupt (0)
>
>This is indicative of a serious problem; something is generating 
>interrupts even though the slot has not been configured yet.  I am 
>concerned that your pcic may not be correctly configured.  I'm sure 
>you've mentioned before what your laptop is, but could you tell me 
>again?]

It's a Dell Inspiron 3000 model TS30H
A 200mzh Pentium with 80 megs of RAM and a 3gig HD.  NeoMagic video 
chipset.
According to Windows NT (so I take this with a grain of salt since it 
also currently thinks I have a different version of the NeoMagic chipset 
than I do ;) the PCCard chipset is "Intel Compatible" using 3E0-3E1. Lot 
of help that is. Dell's web site is less informative.


>> config 0x300 "ep0" 10
>>      Card inserted, slot 0         # 10-20 second delay
>>      Jan 31 16:45:24 quarry cardd[249]: Resource allocation failure for 
>> 3Com Corporation.
>
>This obviously can't work; you have specified a configuration index of 
>0x300, but only 0x1 and 0x3 exist in the CIS. 

Ah, see that is one of the places where I was confused.  I was under the 
assumtion that the 0xXX was for the 300h the system spoke to the card 
with.  


>> I went ahead and made the changes (even though this is a resource error 
>> not a driver error) and added a printf to the two ENXIO exits that 
>> didn't' supply an error but still nothing. Should I do the same to 
>> another area of the code to find the problem with the resource allocation?
>
>No.  The resource error is configuration-file related.  The endless 
>unfielded interrupt errors, on the other hand, appear to be a problem 
>with the way that cards are probed/attached.
>
>Are you doing this on 2.2.5 or on -current?

I'm running 2.2.5 with out any of the security patches sent out (I was 
trying to get things running first.)


-Sean

----------------------------------------------------------------------
Sean J. Schluntz                                    schluntz@pinpt.com
Systems Engineer                                   (408) 997-6900 x222
PinPoint Software Corporation                     http://www.pinpt.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802010232.SAA14584>