Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Works fine.
Thank you, Adrian

On Friday 19 April 2013 14:57:12 Adrian Chadd wrote:
> Hi!
> 
> Ok, please update to -HEAD and retest!
> 
> 
> 
> adrian
> 
> On 19 April 2013 06:26, Adrian Chadd  wrote:
> > oo good to know! let me setup the chainmask info whether or not
> > the 11n option is set.
> >
> > thanks!
> >
> >
> > adrian
> >
> > On 19 April 2013 04:08, Artyom Mirgorodskiy
> >  wrote:
> >> Adrian, I found the problem.
> >>
> >> I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define
> >> ATH_ENABLE_11N - everything work.
> >>
> >>
> >>
> >>
> >>
> >> Artyom Mirgorodskiy
> >>
> >>
> >>
> >> On Friday 19 April 2013 13:27:21 wrote:
> >>
> >> Updated. However I did not see chainmask information.
> >>
> >> See attached
> >>
> >>
> >>
> >> On Friday 19 April 2013 00:57:12 Adrian Chadd wrote:
> >>
> >>> Hi,
> >>
> >>>
> >>
> >>> I've just committed some changes to -HEAD. Please update to the latest
> >>
> >>> -HEAD and paste me the ath0 dmesg output.
> >>
> >>> It will include the chainmask information.
> >>
> >>>
> >>
> >>> Thanks,
> >>
> >>>
> >>
> >>>
> >>
> >>> Adrian
> >>
> >> --
> >>
> >> Artyom Mirgorodskiy
> >>
> >>
> >> --
> >>
> >> Artyom Mirgorodskiy
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Hi!

Ok, please update to -HEAD and retest!



adrian

On 19 April 2013 06:26, Adrian Chadd  wrote:
> oo good to know! let me setup the chainmask info whether or not
> the 11n option is set.
>
> thanks!
>
>
> adrian
>
> On 19 April 2013 04:08, Artyom Mirgorodskiy
>  wrote:
>> Adrian, I found the problem.
>>
>> I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define
>> ATH_ENABLE_11N - everything work.
>>
>>
>>
>>
>>
>> Artyom Mirgorodskiy
>>
>>
>>
>> On Friday 19 April 2013 13:27:21 wrote:
>>
>> Updated. However I did not see chainmask information.
>>
>> See attached
>>
>>
>>
>> On Friday 19 April 2013 00:57:12 Adrian Chadd wrote:
>>
>>> Hi,
>>
>>>
>>
>>> I've just committed some changes to -HEAD. Please update to the latest
>>
>>> -HEAD and paste me the ath0 dmesg output.
>>
>>> It will include the chainmask information.
>>
>>>
>>
>>> Thanks,
>>
>>>
>>
>>>
>>
>>> Adrian
>>
>> --
>>
>> Artyom Mirgorodskiy
>>
>>
>> --
>>
>> Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

oo good to know! let me setup the chainmask info whether or not
the 11n option is set.

thanks!


adrian

On 19 April 2013 04:08, Artyom Mirgorodskiy
 wrote:
> Adrian, I found the problem.
>
> I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define
> ATH_ENABLE_11N - everything work.
>
>
>
>
>
> Artyom Mirgorodskiy
>
>
>
> On Friday 19 April 2013 13:27:21 wrote:
>
> Updated. However I did not see chainmask information.
>
> See attached
>
>
>
> On Friday 19 April 2013 00:57:12 Adrian Chadd wrote:
>
>> Hi,
>
>>
>
>> I've just committed some changes to -HEAD. Please update to the latest
>
>> -HEAD and paste me the ath0 dmesg output.
>
>> It will include the chainmask information.
>
>>
>
>> Thanks,
>
>>
>
>>
>
>> Adrian
>
> --
>
> Artyom Mirgorodskiy
>
>
> --
>
> Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Adrian, I found the problem.
I'm use ath as module, so ATH_ENABLE_11N is not defined.  When I define 
ATH_ENABLE_11N - everything work.


Artyom Mirgorodskiy

On Friday 19 April 2013 13:27:21  wrote:


Updated. However I did not see chainmask information.
See attached

On Friday 19 April 2013 00:57:12 Adrian Chadd wrote:
> Hi,
> 
> I've just committed some changes to -HEAD. Please update to the latest
> -HEAD and paste me the ath0 dmesg output.
> It will include the chainmask information.
> 
> Thanks,
> 
> 
> Adrian
-- 
Artyom Mirgorodskiy


-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Hi,

I've just committed some changes to -HEAD. Please update to the latest
-HEAD and paste me the ath0 dmesg output.
It will include the chainmask information.

Thanks,


Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Ok. I'll add some tidyups to head tonight and then add some more verbose 
logging.

I don't have any 64 bit machines to test ar9287 on atm.

Sent from my Palm Pre on AT&T
On Apr 18, 2013 3:52 PM, Artyom Mirgorodskiy 
 wrote: 


Nothing :(
 
On Thursday 18 April 2013 15:22:49 Adrian Chadd wrote:
> Hm! I wonder..
> 
> Edit if_athvar.h - change sc_rxchainmask and sc_txchainmask in
> ath_softc to be uint32_t, rather than int.
> 
> See if that helps.
> 
> 
> 
> Adrian
> 
> On 18 April 2013 15:20, Artyom Mirgorodskiy
>  wrote:
> > See attached
> >
> >
> >
> > On Thursday 18 April 2013 15:08:36 Adrian Chadd wrote:
> >
> >> On 18 April 2013 15:07, Artyom Mirgorodskiy
> >
> >>  wrote:
> >
> >> > See attached
> >
> >> >
> >
> >>
> >
> >> What the hell? Those masks are really wrong.
> >
> >>
> >
> >> Try adding this line after it:
> >
> >>
> >
> >> ath_hal_printf(ah, "%s: pcap rx=0x%x, tx=0x%x; configured rx=0x%x,
> >
> >> tx=0x%x\n", __func__, pCap->halRxChainMask, 
pCap->halTxChainMask,
> >
> >> rx_chainmask, tx_chainmask);
> >
> > --
> >
> > Artyom Mirgorodskiy
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Nothing :(

On Thursday 18 April 2013 15:22:49 Adrian Chadd wrote:
> Hm! I wonder..
> 
> Edit if_athvar.h - change sc_rxchainmask and sc_txchainmask in
> ath_softc to be uint32_t, rather than int.
> 
> See if that helps.
> 
> 
> 
> Adrian
> 
> On 18 April 2013 15:20, Artyom Mirgorodskiy
>  wrote:
> > See attached
> >
> >
> >
> > On Thursday 18 April 2013 15:08:36 Adrian Chadd wrote:
> >
> >> On 18 April 2013 15:07, Artyom Mirgorodskiy
> >
> >>  wrote:
> >
> >> > See attached
> >
> >> >
> >
> >>
> >
> >> What the hell? Those masks are really wrong.
> >
> >>
> >
> >> Try adding this line after it:
> >
> >>
> >
> >> ath_hal_printf(ah, "%s: pcap rx=0x%x, tx=0x%x; configured rx=0x%x,
> >
> >> tx=0x%x\n", __func__, pCap->halRxChainMask, pCap->halTxChainMask,
> >
> >> rx_chainmask, tx_chainmask);
> >
> > --
> >
> > Artyom Mirgorodskiy
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

On 18 April 2013 15:54, Artyom Mirgorodskiy
 wrote:
> Nothing :(

Ok, so I wonder now whether we're actually getting the right chainmask
at startup.

edit if_ath.c, look for 'ath_hal_getrxchainmask()'

After the rx/tx chainmask is fetched,a dd this:

device_printf(sc->sc_dev, "%s: RX chainmask=0x%x, TX
chainmask=0x%x\n", sc->sc_rxchainmask, sc->sc_txchainmask);



Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Hm! I wonder..

Edit if_athvar.h - change sc_rxchainmask and sc_txchainmask in
ath_softc to be uint32_t, rather than int.

See if that helps.



Adrian

On 18 April 2013 15:20, Artyom Mirgorodskiy
 wrote:
> See attached
>
>
>
> On Thursday 18 April 2013 15:08:36 Adrian Chadd wrote:
>
>> On 18 April 2013 15:07, Artyom Mirgorodskiy
>
>>  wrote:
>
>> > See attached
>
>> >
>
>>
>
>> What the hell? Those masks are really wrong.
>
>>
>
>> Try adding this line after it:
>
>>
>
>> ath_hal_printf(ah, "%s: pcap rx=0x%x, tx=0x%x; configured rx=0x%x,
>
>> tx=0x%x\n", __func__, pCap->halRxChainMask, pCap->halTxChainMask,
>
>> rx_chainmask, tx_chainmask);
>
> --
>
> Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

On 18 April 2013 15:07, Artyom Mirgorodskiy
 wrote:
> See attached
>

What the hell? Those masks are really wrong.

Try adding this line after it:

ath_hal_printf(ah, "%s: pcap rx=0x%x, tx=0x%x; configured rx=0x%x,
tx=0x%x\n", __func__, pCap->halRxChainMask, pCap->halTxChainMask,
rx_chainmask, tx_chainmask);
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

On 18 April 2013 14:43, Artyom Mirgorodskiy
 wrote:
> Did not work.
>

Hm. Ok.

Let's add some debugging:

inside of ar5416SetChainMasks(), let's add a printf() at the -end- of
the function:

ath_hal_printf(ah, "%s: txchainmask=0x%x, rxchainmask=0x%x\n",
__func__, AH5416(ah)->ah_tx_chainmask, AH5416(ah)->ah_rx_chainmask);

Then recompile, reboot, and show me the output of 'dmesg'
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Did not work.

On Thursday 18 April 2013 13:58:23 Adrian Chadd wrote:
> On 18 April 2013 13:33, Artyom Mirgorodskiy
>  wrote:
> > Yes. I tested 247287 and it breaks.
> 
> Hm.
> 
> Well, not much changed there.
> 
> Try going to 247287 (ie, the broken revision), but revert
> head/sys/dev/ath/ath_hal/ar5416/ar5416_xmit.c to 247286.
> 
> See if that fixes it.
> 
> 
> 
> Adrian
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

On 18 April 2013 13:33, Artyom Mirgorodskiy
 wrote:
> Yes. I tested 247287 and it breaks.

Hm.

Well, not much changed there.

Try going to 247287 (ie, the broken revision), but revert
head/sys/dev/ath/ath_hal/ar5416/ar5416_xmit.c to 247286.

See if that fixes it.



Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Yes. I tested 247287 and it breaks.

On Thursday 18 April 2013 13:31:29 Adrian Chadd wrote:
> On 18 April 2013 11:58, Artyom Mirgorodskiy
>  wrote:
> > Yes, HEAD everything else except the wifi code (ath).
> >
> > Last working revision is 247286. So problem in revision 247287.
> 
> That's really odd. It behaves perfectly fine on my system.
> 
> You've tested 247287 and it breaks?
> 
> 
> Adrian
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

On 18 April 2013 11:58, Artyom Mirgorodskiy
 wrote:
> Yes, HEAD everything else except the wifi code (ath).
>
> Last working revision is 247286. So problem in revision 247287.

That's really odd. It behaves perfectly fine on my system.

You've tested 247287 and it breaks?


Adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[John Baldwin]

On Thursday, April 18, 2013 12:41:53 pm Adrian Chadd wrote:
> 
> ... Why would it differ for the same machine, different kernel?

I can't tell you why, but if you compare the full dmesg's you will see
that several devices all changed their BIOS-assigned IRQs because the BIOS
decided to shuffle the IRQs assigned to the PCI links around.  That should
all be moot since you are using the APIC anyway.

-- 
John Baldwin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Yes, HEAD everything else except the wifi code (ath).
Last working revision is 247286. So problem in revision 247287.


On Thursday 18 April 2013 10:42:15 Adrian Chadd wrote:
> Hm, so -HEAD everything else except the wifi code?
> 
> That's really odd. I updated to -HEAD this morning just to test the
> AR9287 for you and it was peachy!
> 
> 
> Adrian
> 
> On 18 April 2013 10:36, Artyom Mirgorodskiy
>  wrote:
> > Yes
> >
> >
> >
> > On Thursday 18 April 2013 10:30:33 Adrian Chadd wrote:
> >
> > On head?
> >
> >
> >
> > Adrian
> >
> >
> >
> > Sent from my Palm Pre on AT&T
> >
> > 
> >
> > Artyom MirgorodskiyOn Apr 18, 2013 10:06 AM, 
> > wrote:
> >
> > I tried to check out revision 245031 (only sys/dev/ath) and got a working
> > WiFi. I'll try to find a broken revision.
> >
> >
> >
> > On Thursday 18 April 2013 11:37:17 John Baldwin wrote:
> >
> >> On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> >
> >> > Ok, the relevant / interesting bit:s. John, any ideas?
> >
> >>
> >
> >> Only that this means absolutely nothing? These are the values the BIOS
> >> wrote
> >
> >> into the registers which we use as hints about whether or not ACPI lies
> >> about
> >
> >> which interrupts are used when APIC is disabled. The actually useful
> >> message
> >
> >> shows the same interrupts used in both cases:
> >
> >>
> >
> >> > HEAD:
> >
> >> >
> >
> >> > pcib2: slot 0 INTA hardwired to IRQ 18
> >
> >> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on
> >> > pci10
> >
> >> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> >
> >> >
> >
> >> > versus
> >
> >> >
> >
> >> > pcib2: slot 0 INTA hardwired to IRQ 18
> >
> >> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on
> >> > pci10
> >
> >> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> >
> >>
> >
> >>
> >
> > --
> >
> > Artyom Mirgorodskiy
> >
> >
> > --
> >
> > Artyom Mirgorodskiy
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Hm, so -HEAD everything else except the wifi code?

That's really odd. I updated to -HEAD this morning just to test the
AR9287 for you and it was peachy!


Adrian

On 18 April 2013 10:36, Artyom Mirgorodskiy
 wrote:
> Yes
>
>
>
> On Thursday 18 April 2013 10:30:33 Adrian Chadd wrote:
>
> On head?
>
>
>
> Adrian
>
>
>
> Sent from my Palm Pre on AT&T
>
> 
>
> Artyom MirgorodskiyOn Apr 18, 2013 10:06 AM, 
> wrote:
>
> I tried to check out revision 245031 (only sys/dev/ath) and got a working
> WiFi. I'll try to find a broken revision.
>
>
>
> On Thursday 18 April 2013 11:37:17 John Baldwin wrote:
>
>> On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
>
>> > Ok, the relevant / interesting bit:s. John, any ideas?
>
>>
>
>> Only that this means absolutely nothing? These are the values the BIOS
>> wrote
>
>> into the registers which we use as hints about whether or not ACPI lies
>> about
>
>> which interrupts are used when APIC is disabled. The actually useful
>> message
>
>> shows the same interrupts used in both cases:
>
>>
>
>> > HEAD:
>
>> >
>
>> > pcib2: slot 0 INTA hardwired to IRQ 18
>
>> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on
>> > pci10
>
>> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
>
>> >
>
>> > versus
>
>> >
>
>> > pcib2: slot 0 INTA hardwired to IRQ 18
>
>> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on
>> > pci10
>
>> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
>
>>
>
>>
>
> --
>
> Artyom Mirgorodskiy
>
>
> --
>
> Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

Yes

On Thursday 18 April 2013 10:30:33 Adrian Chadd wrote:


On head?



Adrian




Sent from my Palm Pre on AT&T


Artyom MirgorodskiyOn Apr 18, 2013 10:06 AM,   
wrote: 



I tried to check out revision 245031 (only sys/dev/ath) and got a working WiFi. 
I'll try to find a broken revision.

On Thursday 18 April 2013 11:37:17 John Baldwin wrote:
> On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> > Ok, the relevant / interesting bit:s. John, any ideas?
> 
> Only that this means absolutely nothing? These are the values the BIOS wrote 
> into the registers which we use as hints about whether or not ACPI lies about 
> which interrupts are used when APIC is disabled. The actually useful message
> shows the same interrupts used in both cases:
> 
> > HEAD:
> > 
> > pcib2: slot 0 INTA hardwired to IRQ 18
> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> > 
> > versus
> > 
> > pcib2: slot 0 INTA hardwired to IRQ 18
> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> 
> 
-- 
Artyom Mirgorodskiy


-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

On head?



Adrian



Sent from my Palm Pre on AT&T
On Apr 18, 2013 10:06 AM, Artyom Mirgorodskiy 
 wrote: 


I tried to check out revision 245031 (only sys/dev/ath) and got a working WiFi. 
I'll try to find a broken revision.
 
On Thursday 18 April 2013 11:37:17 John Baldwin wrote:
> On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> > Ok, the relevant / interesting bit:s. John, any ideas?
> 
> Only that this means absolutely nothing?  These are the values the BIOS 
wrote 
> into the registers which we use as hints about whether or not ACPI lies 
about 
> which interrupts are used when APIC is disabled.  The actually useful 
message
> shows the same interrupts used in both cases:
> 
> > HEAD:
> > 
> > pcib2: slot 0 INTA hardwired to IRQ 18
> > ath0:  mem 0xe050-0xe050 irq 18 at device 
0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> > 
> > versus
> > 
> > pcib2: slot 0 INTA hardwired to IRQ 18
> > ath0:  mem 0xe050-0xe050 irq 18 at device 
0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> 
> 
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

I tried to check out revision 245031 (only sys/dev/ath) and got a working WiFi. 
I'll try to find a broken revision.

On Thursday 18 April 2013 11:37:17 John Baldwin wrote:
> On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> > Ok, the relevant / interesting bit:s. John, any ideas?
> 
> Only that this means absolutely nothing?  These are the values the BIOS wrote 
> into the registers which we use as hints about whether or not ACPI lies about 
> which interrupts are used when APIC is disabled.  The actually useful message
> shows the same interrupts used in both cases:
> 
> > HEAD:
> > 
> > pcib2: slot 0 INTA hardwired to IRQ 18
> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> > 
> > versus
> > 
> > pcib2: slot 0 INTA hardwired to IRQ 18
> > ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> 
> 
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

... Why would it differ for the same machine, different kernel?


Adrian


Sent from my Palm Pre on AT&T
On Apr 18, 2013 8:40 AM, John Baldwin  wrote: 

On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:

> Ok, the relevant / interesting bit:s. John, any ideas?



Only that this means absolutely nothing?  These are the values the BIOS wrote 

into the registers which we use as hints about whether or not ACPI lies about 

which interrupts are used when APIC is disabled.  The actually useful message

shows the same interrupts used in both cases:



> HEAD:

> 

> pcib2: slot 0 INTA hardwired to IRQ 18

> ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 
on pci10

> ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60

> 

> versus

> 

> pcib2: slot 0 INTA hardwired to IRQ 18

> ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 
on pci10

> ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60



-- 

John Baldwin


___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[John Baldwin]

On Thursday, April 18, 2013 11:22:38 am Adrian Chadd wrote:
> Ok, the relevant / interesting bit:s. John, any ideas?

Only that this means absolutely nothing?  These are the values the BIOS wrote 
into the registers which we use as hints about whether or not ACPI lies about 
which interrupts are used when APIC is disabled.  The actually useful message
shows the same interrupts used in both cases:

> HEAD:
> 
> pcib2: slot 0 INTA hardwired to IRQ 18
> ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
> 
> versus
> 
> pcib2: slot 0 INTA hardwired to IRQ 18
> ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60

-- 
John Baldwin
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Ok, the relevant / interesting bit:s. John, any ideas?

HEAD:

pcib2:  irq 18 at device 28.2 on pci0
pcib0: allocated type 3 (0xe050-0xe05f) for rid 20 of pcib2
pcib2:   domain0
pcib2:   secondary bus 10
pcib2:   subordinate bus   10
pcib2:   memory decode 0xe050-0xe05f
pcib2:   no prefetched decode
pci10:  on pcib2
pci10: domain=0, physical bus=10
found-> vendor=0x168c, dev=0x002e, revid=0x01
domain=0, bus=10, slot=0, func=0
class=02-80-00, hdrtype=0x00, mfdev=0
cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=10

^-- notice how this is irq 10

powerspec 3  supports D0 D1 D3  current D0
MSI supports 1 message
map[10]: type Memory, range 64, base 0xe050, size 16, enabled
pcib2: allocated memory range (0xe050-0xe050) for rid 10 of pci0:10:0:0
pcib2: matched entry for 10.0.INTA
pcib2: slot 0 INTA hardwired to IRQ 18
ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
ath0: 2T2R
ath0: 11ng MCS 20MHz
ath0: MCS 0-7: 6.5Mbps - 65Mbps
ath0: MCS 8-15: 13Mbps - 130Mbps
ath0: AR9287 mac 384.2 RF5133 phy 15.15
ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0
ath0: Use hw queue 1 for WME_AC_BE traffic
ath0: Use hw queue 0 for WME_AC_BK traffic
ath0: Use hw queue 2 for WME_AC_VI traffic
ath0: Use hw queue 3 for WME_AC_VO traffic
ath0: Use hw queue 8 for CAB traffic
ath0: Use hw queue 9 for beacons
ath0: using multicast key search

versus

pcib2:  irq 18 at device 28.2 on pci0
pcib0: allocated type 3 (0xe050-0xe05f) for rid 20 of pcib2
pcib2:   domain0
pcib2:   secondary bus 10
pcib2:   subordinate bus   10
pcib2:   memory decode 0xe050-0xe05f
pcib2:   no prefetched decode
pci10:  on pcib2
pci10: domain=0, physical bus=10
found-> vendor=0x168c, dev=0x002e, revid=0x01
domain=0, bus=10, slot=0, func=0
class=02-80-00, hdrtype=0x00, mfdev=0
cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=7

^-- notice this is irq 7

powerspec 3  supports D0 D1 D3  current D0
MSI supports 1 message
map[10]: type Memory, range 64, base 0xe050, size 16, enabled
pcib2: allocated memory range (0xe050-0xe050) for rid 10 of pci0:10:0:0
pcib2: matched entry for 10.0.INTA
pcib2: slot 0 INTA hardwired to IRQ 18
ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
ath0: 2T2R
ath0: 11ng MCS 20MHz
ath0: MCS 0-7: 6.5Mbps - 65Mbps
ath0: MCS 8-15: 13Mbps - 130Mbps
ath0: AR9287 mac 384.2 RF5133 phy 15.15
ath0: Use hw queue 1 for WME_AC_BE traffic
ath0: Use hw queue 0 for WME_AC_BK traffic
ath0: Use hw queue 2 for WME_AC_VI traffic
ath0: Use hw queue 3 for WME_AC_VO traffic
ath0: Use hw queue 8 for CAB traffic
ath0: Use hw queue 9 for beacons
ath0: using multicast key search
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Sigh.

Someone's broken the bus or interrupt handling code between -9 and
-head. Or ACPI, for all I know. It may even be something to do with
RFKILL.

Can you please boot verbosely, both on -9 and -head? you don't have to
do anything - just capture the logfile /var/run/dmesg.boot and attach
them here.

Hopefully something glaringly different will stand out.

Thanks,



adrian

On 18 April 2013 07:05, Artyom Mirgorodskiy
 wrote:
> No interrupts at all:
>
>
>
> interrupt total rate
>
> irq1: atkbd0 474 1
>
> irq9: acpi0 95 0
>
> irq22: ehci1 504 1
>
> irq23: ehci0 1037 3
>
> irq256: hpet0:t0 8426 30
>
> irq257: hpet0:t1 1823 6
>
> irq258: hpet0:t2 1992 7
>
> irq259: hpet0:t3 2112 7
>
> irq264: hdac0 118 0
>
> irq265: ahci0 4026 14
>
> Total 20607 75
>
>
>
>
>
> On Thursday 18 April 2013 06:56:14 Adrian Chadd wrote:
>
>> I've just tested -HEAD on a WB197 (AR9287 + bluetooth.) It works fine.
>
>>
>
>> I think it's very likely something to do with the bus enumeration. Can
>
>> you do a vmstat -i, see if you've seen any ath interrupts?
>
>>
>
>>
>
>>
>
>> adrian
>
> --
>
> Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

No interrupts at all:

interrupt  total   rate
irq1: atkbd0 474  1
irq9: acpi0   95  0
irq22: ehci1 504  1
irq23: ehci01037  3
irq256: hpet0:t08426 30
irq257: hpet0:t11823  6
irq258: hpet0:t21992  7
irq259: hpet0:t32112  7
irq264: hdac0118  0
irq265: ahci0   4026 14
Total  20607 75


On Thursday 18 April 2013 06:56:14 Adrian Chadd wrote:
> I've just tested -HEAD on a WB197 (AR9287 + bluetooth.) It works fine.
> 
> I think it's very likely something to do with the bus enumeration. Can
> you do a vmstat -i, see if you've seen any ath interrupts?
> 
> 
> 
> adrian
-- 
Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

I've just tested -HEAD on a WB197 (AR9287 + bluetooth.) It works fine.

I think it's very likely something to do with the bus enumeration. Can
you do a vmstat -i, see if you've seen any ath interrupts?



adrian
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Ok, no obvious errors during scanning that would explain this.

Hm!

I'll stick an AR9287 in a test laptop today and give it a whirl.


Adrian

On 18 April 2013 06:41, Artyom Mirgorodskiy
 wrote:
> See attached
>
>
>
>
>
> Preloaded elf obj module "/boot/kernel/if_ath.ko" at 0x80d2aef8.
>
> Preloaded elf obj module "/boot/kernel/if_ath_pci.ko" at 0x80d2db10.
>
> ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
>
> ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>
> ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps
> 36Mbps 48Mbps 54Mbps
>
> ath0: 2T2R
>
> ath0: 11ng MCS 20MHz
>
> ath0: MCS 0-7: 6.5Mbps - 65Mbps
>
> ath0: MCS 8-15: 13Mbps - 130Mbps
>
> ath0: AR9287 mac 384.2 RF5133 phy 15.15
>
> ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0
>
> ath0: Use hw queue 1 for WME_AC_BE traffic
>
> ath0: Use hw queue 0 for WME_AC_BK traffic
>
> ath0: Use hw queue 2 for WME_AC_VI traffic
>
> ath0: Use hw queue 3 for WME_AC_VO traffic
>
> ath0: Use hw queue 8 for CAB traffic
>
> ath0: Use hw queue 9 for beacons
>
> ath0: using multicast key search
>
>
>
>
>
> On Thursday 18 April 2013 06:31:50 Adrian Chadd wrote:
>
>> Hm, paste the relevant dmesg lines from the boot into here?
>
>>
>
>> I'll reboot into an AR9287 today and see what happened.
>
>>
>
>> Thanks,
>
>>
>
>>
>
>>
>
>> Adrian
>
>>
>
>> On 18 April 2013 06:25, Artyom Mirgorodskiy
>
>>  wrote:
>
>> > Hi
>
>> > I just updated to FreeBSD-current and found that the WiFi does not work
>> > on my laptop.
>
>> > ifconfig wlan0 list scan response very quickly with empty result.
>> > Previous kernel (freebsd 9) works fine.
>
>> >
>
>> > What information do I need to give more to solve the problem?
>
>> >
>
>> >
>
>> > --
>
>> > Artyom Mirgorodskiy
>
>> >
>
>> > ___
>
>> > freebsd-wireless@freebsd.org mailing list
>
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>
>> > To unsubscribe, send any mail to
>> > "freebsd-wireless-unsubscr...@freebsd.org"
>
> --
>
> Artyom Mirgorodskiy
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Atheros 9287 - no carrier . revision 249623.

[Artyom Mirgorodskiy]

See attached


Preloaded elf obj module "/boot/kernel/if_ath.ko" at 0x80d2aef8.
Preloaded elf obj module "/boot/kernel/if_ath_pci.ko" at 0x80d2db10.
ath0:  mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 
36Mbps 48Mbps 54Mbps
ath0: 2T2R
ath0: 11ng MCS 20MHz
ath0: MCS 0-7: 6.5Mbps - 65Mbps
ath0: MCS 8-15: 13Mbps - 130Mbps
ath0: AR9287 mac 384.2 RF5133 phy 15.15
ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0
ath0: Use hw queue 1 for WME_AC_BE traffic
ath0: Use hw queue 0 for WME_AC_BK traffic
ath0: Use hw queue 2 for WME_AC_VI traffic
ath0: Use hw queue 3 for WME_AC_VO traffic
ath0: Use hw queue 8 for CAB traffic
ath0: Use hw queue 9 for beacons
ath0: using multicast key search


On Thursday 18 April 2013 06:31:50 Adrian Chadd wrote:
> Hm, paste the relevant dmesg lines from the boot into here?
> 
> I'll reboot into an AR9287 today and see what happened.
> 
> Thanks,
> 
> 
> 
> Adrian
> 
> On 18 April 2013 06:25, Artyom Mirgorodskiy
>  wrote:
> > Hi
> > I just updated to FreeBSD-current and found that the WiFi does not work on 
> > my laptop.
> > ifconfig wlan0 list scan response very quickly with empty result. Previous 
> > kernel (freebsd 9) works fine.
> >
> > What information do I need to give more to solve the problem?
> >
> >
> > --
> > Artyom Mirgorodskiy
> >
> > ___
> > freebsd-wireless@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
-- 
Artyom Mirgorodskiy
Table 'FACP' at 0xcafef000
Table 'SSDT' at 0xcaffd000
Table 'SSDT' at 0xcaffc000
Table 'SSDT' at 0xcaffb000
Table 'ASF!' at 0xcaff1000
Table 'HPET' at 0xcafee000
Table 'APIC' at 0xcafed000
APIC: Found table at 0xcafed000
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 1 ACPI ID 2: enabled
SMP: Added CPU 1 (AP)
MADT: Found CPU APIC ID 2 ACPI ID 3: enabled
SMP: Added CPU 2 (AP)
MADT: Found CPU APIC ID 3 ACPI ID 4: enabled
SMP: Added CPU 3 (AP)
MADT: Found CPU APIC ID 0 ACPI ID 5: disabled
MADT: Found CPU APIC ID 0 ACPI ID 6: disabled
MADT: Found CPU APIC ID 0 ACPI ID 7: disabled
MADT: Found CPU APIC ID 0 ACPI ID 8: disabled
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-CURRENT #1 r249620: Thu Apr 18 15:17:57 EEST 2013
r...@home.alkar.net:/usr/obj/usr/src/sys/Work amd64
FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221
Preloaded elf kernel "/boot/kernel/kernel" at 0x80d2a000.
Preloaded elf obj module "/boot/kernel/msdosfs.ko" at 0x80d2a950.
Preloaded elf obj module "/boot/kernel/if_ath.ko" at 0x80d2aef8.
Preloaded elf obj module "/boot/kernel/wlan.ko" at 0x80d2b6a0.
Preloaded elf obj module "/boot/kernel/if_re.ko" at 0x80d2bf08.
Preloaded elf obj module "/boot/kernel/miibus.ko" at 0x80d2c430.
Preloaded elf obj module "/boot/kernel/snd_hda.ko" at 0x80d2c998.
Preloaded elf obj module "/boot/kernel/uhid.ko" at 0x80d2cf40.
Preloaded elf obj module "/boot/kernel/usb.ko" at 0x80d2d4a8.
Preloaded elf obj module "/boot/kernel/if_ath_pci.ko" at 0x80d2db10.
Preloaded elf obj module "/boot/kernel/uhci.ko" at 0x80d2e040.
Preloaded elf obj module "/boot/kernel/ehci.ko" at 0x80d2e568.
Preloaded elf obj module "/boot/kernel/msdosfs_iconv.ko" at 0x80d2ea90.
Preloaded elf obj module "/boot/kernel/libiconv.ko" at 0x80d2ef40.
Preloaded elf obj module "/boot/modules/cuse4bsd.ko" at 0x80d2f570.
Preloaded elf obj module "/boot/kernel/ichsmb.ko" at 0x80d2fb20.
Preloaded elf obj module "/boot/kernel/smbus.ko" at 0x80d30048.
Calibrating TSC clock ... TSC clock: 2195067612 Hz
CPU: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (2195.07-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x206a7  Family = 0x6  Model = 0x2a  Stepping = 
7
  
Features=0xbfebfbff
  
Features2=0x1dbae3bf
  AMD Features=0x28100800
  AMD Features2=0x1
  TSC: P-state invariant, performance statistics
real memory  = 4294967296 (4096 MB)
Physical memory chunk(s):
0x0001 - 0x00099fff, 565248 bytes (138 pages)
0x0010 - 0x001f, 1048576 bytes (256 pages)
0x00d5 - 0xbfa37fff, 3201204224 bytes (781544 pages)
0x0001 - 0x00012fde7fff, 803110912 bytes (196072 pages)
avail memory = 3829268480 (3651 MB)
ACPI APIC Table: 
INTR: Adding local APIC 1 as a target
INTR: Adding local APIC 2 as a target
INTR: Adding local APIC 3 as a target
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1

Re: Atheros 9287 - no carrier . revision 249623.

[Adrian Chadd]

Hm, paste the relevant dmesg lines from the boot into here?

I'll reboot into an AR9287 today and see what happened.

Thanks,



Adrian

On 18 April 2013 06:25, Artyom Mirgorodskiy
 wrote:
> Hi
> I just updated to FreeBSD-current and found that the WiFi does not work on my 
> laptop.
> ifconfig wlan0 list scan response very quickly with empty result. Previous 
> kernel (freebsd 9) works fine.
>
> What information do I need to give more to solve the problem?
>
>
> --
> Artyom Mirgorodskiy
>
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"