Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Aug 2001 13:40:30 -0400
From:      Allen Landsidel <all@biosys.net>
To:        freebsd-mobile@freebsd.org
Subject:   My very own pcic bad experiences
Message-ID:  <5.1.0.14.0.20010824133207.00c128a0@rfnj.org>

next in thread | raw e-mail | index | archive | help
I've been running RELENG_4 on my laptop for a while (it functions as my 
firewall) and decided to updated it recently.. bad idea because I wasn't 
paying a lot of attention to this list.  This Cvsup was performed from 
cvsup4.freebsd.org just a few hours ago.

Updating the maching from 4.3-STABLE to 4.4-PRERELASE and 4.4-RC results in 
the pcic becoming unusable.  Here is the dmesg (relevant parts anyway.. if 
anyone wants the whole thing, let me know) from the machine:

...   ( pcic on this machine, Twinhead 9133TV, is on 0xfcfc) ...
config> en pcic0
config> po pcic0 0xfcfc
config> ir pcic0 0
config> iom pcic0 0xd0000
config> f pcic0 0
config> q

... (something weird is going on here I think.. why is pci0 detected twice 
as different devices?) ...
pci0: <PCI bus> on pcib0
isab0: <SiS 85c503 PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Generic PCI ATA controller> port 
0x3f4-0x3f7,0x374-0x377,0x1f4-0x1f7,0x174-0x177 irq 14 at device 1.1 on pci0
atapci0: Busmastering DMA not supported
pci0: <Trident model 9660 VGA-compatible display device> at 17.0
pci_cfgintr: can't route an interrupt to 0:19 INTA
pcic0: <Cirrus Logic PD6729/6730 PC-Card Controller> port 0xfcfc-0xfcff at 
device 19.0 on pci0
pcic0: I/O mapped device, might not work.
pci_cfgintr: can't route an interrupt to 0:19 INTA
pcic0: Failed to allocate managment irq
device_probe_and_attach: pcic0 attach returned 5
....

That's basically all.  Some stuff is output on stderr (apparently) about 
"/dev/pccard0 device not configured" or something but it didn't capture in 
dmesg > dmesg.txt which is how I grabbed this.

As it is now, I'm booted on a 4.4-RC world, with a 4.3-RELEASE (generic) 
kernel.  I'd give you a dmesg of the working system, but alas I can't since 
the dmesg interface was changed in there somewhere and I get "dmesg: sysctl 
kern.msgbuf: No such file or directory"

Anyway Warner.. I hope you can do something for me here too. ;)

-Allen


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?5.1.0.14.0.20010824133207.00c128a0>