Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Nov 2001 08:06:53 -0700 (MST)
From:      Rudolfo Munguia <rudog@primenet.com>
To:        freebsd-mobile@freebsd.org
Subject:   4.4 pccard insanity
Message-ID:  <Pine.BSI.3.96.1011119071616.9581B-100000@usr01.primenet.com>

next in thread | raw e-mail | index | archive | help
Hello again,

I have taken the time now to re-install bsd and test using both my NP10T
and an addtron 802.11b card.

I set the "hw.pcic.intr_path="1" for ISA routing, and left the pcic in
polling mode,

The messages now vary slightly from before, but both cards hang the
system.

I tried with -h in boot to monitor over a serial connection, then found
that I cannot get my main freebsd workstation to display the input from
the mobile.

Failing that, I tried booting with "pccard_enable=YES" and
"pccard_flags=-i 11" and then inserting the card after boot, this yields:

card inserted slot 0

after which I sometimes have enough time to enter "pccardc dumpcis"
before it hangs and I have to remove the battery,

Debug does not come up though,

I decided to try and force a panic to get debug up by pulling the NP10T
out after entering the "pccardc dumpcis" command and get the following:

Tuple #1, code 0xff (Terminator, length = 0
1 slots found
No card in database for "(null)"("(null)")

and I am returned to a working prompt.

I thought then that maybe the NP10T was bad and tried it out on a fujitsu
lifebook, and it was recognized and installed by Windows ME without 
problems.

pccardc is obviously trying to read the CIS before the system Hangs,

however if I wait longer than 4-5 seconds before pulling the card (hoping
that dumpcis will yield more info) then I get debug:

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0xff90afa1
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc0159883
stack pointer		= 0x10:0xc2173ea0
frame pointer		= 0x10:0xc2173eb0
code segment		= base 0x0, limit 0xfffff, type x1b
			= DPL 0, pres 1, def32 1, gran 1
processor ef lags	= interrupt enabled, resume, IOPL = 0
current process		= 203 (pccardc)
interupt mask		=
kernel: type 12 trap, code=0
stopped at	lockmgr+0x27:	orl	0x4(%ebx),%esi

This message is consistent across reboots (excepting process id)

can anyone interpret this to determine if this is the actual system
problem, or is this just complaining about the card being removed?

rudog@primenet.com
'If you're not living on the edge, then you're taking up too much space'


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.96.1011119071616.9581B-100000>