Date: Fri, 14 May 2010 01:24:39 -0500 From: Scott Lambert <lambert@lambertfam.org> To: mobile@freebsd.org Subject: ACPI issue with minipci slot on Acer TravelMate 5720? Message-ID: <20100514062439.GA17367@sysmon.tcworks.net>
next in thread | raw e-mail | index | archive | help
I originally thought there was a problem with the iwn driver on resume.
However, I swapped the wireless card with an Atheros piece, and still
have issues on resume.
The symptoms common to both cards are that the driver can see the card
on resume but cannot use it. The iwn driver says it "could not lock
memory" and "could not load boot firmware." The ath driver says "unable
to attach hardware; HAL status 3."
pci4: driver added
found-> vendor=0x168c, dev=0x001c, revid=0x01
domain=0, bus=4, slot=0, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0507, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=17
powerspec 2 supports D0 D3 current D0
MSI supports 1 message
MSI-X supports 1 message in map 0x10
pci0:4:0:0: reprobing on driver added
ath0: <Atheros 5424/2424> mem 0xf8000000-0xf800ffff irq 17 at device 0.0 on pci4
pcib2: ath0 requested memory range 0xf8000000-0xf800ffff: good
ath0: [MPSAFE]
ath0: [ITHREAD]
ath0: unable to attach hardware; HAL status 3
device_attach: ath0 attach returned 6
I now suspect the real problem is in the ACPI layer.
Every other device on the laptop seems to work great. The wireless card
works well on initial boot. Once I suspend and resume, it's toast.
Unfortunately, I don't know what to try next.
This is pciconf -lbcv from a Feb 6, 2010 version of FreeBSD 8-STABLE on
initial boot:
ath0@pci0:4:0:0: class=0x020000 card=0x04281468 chip=0x001c168c rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'HDAUDIOFUNC_01&VEN_1095&DEV_1392&SUBSYS_10280242&REV_1000 (USBVID_147E&PID_20165&B71A446&0&1)'
class = network
subclass = ethernet
bar [10] = type Memory, range 64, base 0xf8000000, size 65536, enabled
cap 01[40] = powerspec 2 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message
cap 10[60] = PCI-Express 1 legacy endpoint max data 128(128) link x1(x1)
cap 11[90] = MSI-X supports 1 message in map 0x10
I recorded the pciconf output after boot and the on resume a couple of
minutes later. They were exactly the same.
This is pciconf -lbcv on initial boot and after resume for FreeBSD
8-STABLE built May 5th, 2010, the bar line is missing on resume:
Boot:
ath0@pci0:4:0:0: class=0x020000 card=0x04281468 chip=0x001c168c rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'AR5006 family 802.11abg Wireless NIC'
class = network
subclass = ethernet
bar [10] = type Memory, range 64, base 0xf8000000, size 65536, enabled
cap 01[40] = powerspec 2 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message
cap 10[60] = PCI-Express 1 legacy endpoint max data 128(128) link x1(x1)
cap 11[90] = MSI-X supports 1 message in map 0x10
Resume:
ath0@pci0:4:0:0: class=0x020000 card=0x04281468 chip=0x001c168c rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'AR5006 family 802.11abg Wireless NIC'
class = network
subclass = ethernet
cap 01[40] = powerspec 2 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message
cap 10[60] = PCI-Express 1 legacy endpoint max data 128(128) link x1(x1)
cap 11[90] = MSI-X supports 1 message in map 0x10
So, at least I have a difference I can point to now.
I've read through the ASL, but I didn't see anything that looks
pertinent. That may be due to my ignorance on the subject. It could
even be the wrong tree.
I would really appreciate if someone could direct me in gathering the
information needed to figure this out.
Thank you,
--
Scott Lambert KC5MLE Unix SysAdmin
lambert@lambertfam.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100514062439.GA17367>