2012-01-15 15:50:56

by Justin P. Mattock

[permalink] [raw]
Subject: ath9k timeouts with the current Mainline

not sure if the Internet provider just sucks, or I am hitting a wireless
issue. basically my connection times out after a few mins of being
up.(streaming radio is not solid).

dmesg shows:

[ 3322.827549] wlan1: authenticate with d8:c7:c8:a2:0f:40 (try 1)
[ 3322.831778] wlan1: d8:c7:c8:a2:0f:40 denied authentication (status 17)
[ 3386.310128] wlan1: authenticate with d8:c7:c8:a2:0d:80 (try 1)
[ 3386.312010] wlan1: d8:c7:c8:a2:0d:80 denied authentication (status 17)
[ 3389.481771] wlan1: direct probe to 00:18:0a:02:19:c3 (try 1/3)
[ 3389.681095] wlan1: direct probe to 00:18:0a:02:19:c3 (try 2/3)
[ 3389.881094] wlan1: direct probe to 00:18:0a:02:19:c3 (try 3/3)
[ 3390.081092] wlan1: direct probe to 00:18:0a:02:19:c3 timed out
[ 3458.618065] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 1/3)
[ 3458.818079] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 2/3)
[ 3459.018080] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 3/3)
[ 3459.218058] wlan1: direct probe to d8:c7:c8:a2:0d:80 timed out
[ 3466.518579] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 1/3)
[ 3466.718111] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 2/3)
[ 3466.918074] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 3/3)
[ 3467.118077] wlan1: direct probe to d8:c7:c8:a2:0d:80 timed out
[ 3474.424860] wlan1: authenticate with d8:c7:c8:a2:0d:80 (try 1)
[ 3474.449681] wlan1: authenticated
[ 3474.457133] wlan1: associate with d8:c7:c8:a2:0d:80 (try 1)
[ 3474.471059] wlan1: RX AssocResp from d8:c7:c8:a2:0d:80 (capab=0x421
status=0 aid=13)
[ 3474.471067] wlan1: associated
[ 3474.471075] wlan1: moving STA d8:c7:c8:a2:0d:80 to state 1
[ 3474.471080] wlan1: moving STA d8:c7:c8:a2:0d:80 to state 2
[ 3474.473809] wlan1: moving STA d8:c7:c8:a2:0d:80 to state 3
[ 3484.546077] wlan1: no IPv6 routers present


card is:
03:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless
Network Adapter (rev 01)

has anybody else seen/experienced anything like this?

Justin P. Mattock


2012-03-10 14:16:56

by Andreas Hartmann

[permalink] [raw]
Subject: Re: ath9k timeouts with the current Mainline

Oskar Stenman wrote:
> I'm having a similar or the same problem, it's been nagging me for at
> least 1.5years.
>
> If I'm able to connect I get frequent dropouts from any wireless network
> I'm connected to. It gets sluggish and after a little while disconnects,
> and once it has disconnected it just keeps reconnecting and failing.
> sometimes a reboot helps, but most of the time it wont help anymore than
> a couple of seconds to a minute. It's also impossible to connect to my
> wireless hotspot on my Xperia Mini Pro and it seems ad-hoc networks are
> also impossible.
>
> I'm running ubuntu 11.10 with latest patches applied as of today. Since
> i've not seen anything being solved during this time i doubt anyone has
> been trying to, or has been able to solve the problem recently.

I'm running exactly the same chip (according lspci) without any problem.
But I'm using slightly different environment:

1. 64 bit
2. kernel 3.1 (some time ago, I run 3.0, too, but cannot remember
having any problems related ar9285).
3. no network manager - just plain wpa_supplicant.
4. wpa_supplicant 0.7.3


If you like to, you could just check, if the problem is network manager
related. Try to stop it and run wpa_supplicant manually as root like
this (ensure, that no other wpa_supplicant process is running at the
same time):

wpa_supplicant -t -c /etc/wpa_supplicant/wpa_supplicant.conf -Dnl80211
-i wlan0

-c is the config file. -i is the device name.

sample config file for WPA2 PSK would be:

network={
ssid="your network name"
# scan_ssid=1
key_mgmt=WPA-PSK
psk="your psk"
proto=WPA2
}

If you see a line like this:
WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
you can go to another terminal and start dhclient or dhcpcd like this:

dhcpcd wlan0 (or whatever your device name is)


If this is all running fine, you most probably face a network manager
problem.


Hope that helps,
regards,
Andreas

2012-03-10 17:02:45

by Justin P. Mattock

[permalink] [raw]
Subject: Re: ath9k timeouts with the current Mainline

On 03/10/2012 06:13 AM, Andreas Hartmann wrote:
> Oskar Stenman wrote:
>> I'm having a similar or the same problem, it's been nagging me for at
>> least 1.5years.
>>
>> If I'm able to connect I get frequent dropouts from any wireless network
>> I'm connected to. It gets sluggish and after a little while disconnects,
>> and once it has disconnected it just keeps reconnecting and failing.
>> sometimes a reboot helps, but most of the time it wont help anymore than
>> a couple of seconds to a minute. It's also impossible to connect to my
>> wireless hotspot on my Xperia Mini Pro and it seems ad-hoc networks are
>> also impossible.
>>
>> I'm running ubuntu 11.10 with latest patches applied as of today. Since
>> i've not seen anything being solved during this time i doubt anyone has
>> been trying to, or has been able to solve the problem recently.
>
> I'm running exactly the same chip (according lspci) without any problem.
> But I'm using slightly different environment:
>
> 1. 64 bit
> 2. kernel 3.1 (some time ago, I run 3.0, too, but cannot remember
> having any problems related ar9285).
> 3. no network manager - just plain wpa_supplicant.
> 4. wpa_supplicant 0.7.3
>
>
> If you like to, you could just check, if the problem is network manager
> related. Try to stop it and run wpa_supplicant manually as root like
> this (ensure, that no other wpa_supplicant process is running at the
> same time):
>
> wpa_supplicant -t -c /etc/wpa_supplicant/wpa_supplicant.conf -Dnl80211
> -i wlan0
>
> -c is the config file. -i is the device name.
>
> sample config file for WPA2 PSK would be:
>
> network={
> ssid="your network name"
> # scan_ssid=1
> key_mgmt=WPA-PSK
> psk="your psk"
> proto=WPA2
> }
>
> If you see a line like this:
> WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
> you can go to another terminal and start dhclient or dhcpcd like this:
>
> dhcpcd wlan0 (or whatever your device name is)
>
>
> If this is all running fine, you most probably face a network manager
> problem.
>
>
> Hope that helps,
> regards,
> Andreas
>


The timeouts I have not see just yet; only the RX DMA thing which I am
monitoring and trying to recreate, so I can _possibly_ bisect. as for
the timeout(s) I have not see this with the current, there is a bug
report on this(2.6.37 or so) but I think the bug was closed due to no
participation or something.

also make sure you have power save off(iwconfig wlan* power off) because
from what I remember powersave on is what triggers the timeout(s)


Justin P. Mattock

2012-03-10 22:30:36

by Adrian Chadd

[permalink] [raw]
Subject: Re: ath9k timeouts with the current Mainline

Hi,

Please bisect the kernel to see if you can find a time where it worked.

And try disabling ANI and see if that helps.

ath9k seems to have a weird issue with the AR5008 series stuff
(AR5416/AR5418) with noise floor calibration + ANI == weird RX
deafness.

FreeBSD doesn't seem to have this issue with the AR5416. I don't (yet) know why.

Thanks,


Adrian

On 10 March 2012 09:02, Justin P. Mattock <[email protected]> wrote:
> On 03/10/2012 06:13 AM, Andreas Hartmann wrote:
>>
>> Oskar Stenman wrote:
>>>
>>> I'm having a similar or the same problem, it's been nagging me for at
>>> least 1.5years.
>>>
>>> If I'm able to connect I get frequent dropouts from any wireless network
>>> I'm connected to. It gets sluggish and after a little while disconnects,
>>> and once it has disconnected it just keeps reconnecting and failing.
>>> sometimes a reboot helps, but most of the time it wont help anymore than
>>> a couple of seconds to a minute. It's also impossible to connect to my
>>> wireless hotspot on my Xperia Mini Pro and it seems ad-hoc networks are
>>> also impossible.
>>>
>>> I'm running ubuntu 11.10 with latest patches applied as of today. Since
>>> i've not seen anything being solved during this time i doubt anyone has
>>> been trying to, or has been able to solve the problem recently.
>>
>>
>> I'm running exactly the same chip (according lspci) without any problem.
>> But I'm using slightly different environment:
>>
>> 1. 64 bit
>> 2. kernel 3.1 (some time ago, I run 3.0, too, but cannot remember
>> ? ?having any problems related ar9285).
>> 3. no network manager - just plain wpa_supplicant.
>> 4. wpa_supplicant 0.7.3
>>
>>
>> If you like to, you could just check, if the problem is network manager
>> related. Try to stop it and run wpa_supplicant manually as root like
>> this (ensure, that no other wpa_supplicant process is running at the
>> same time):
>>
>> wpa_supplicant -t -c /etc/wpa_supplicant/wpa_supplicant.conf -Dnl80211
>> -i wlan0
>>
>> -c is the config file. -i is the device name.
>>
>> sample config file for WPA2 PSK would be:
>>
>> network={
>> ? ? ? ? ssid="your network name"
>> ? ? ? ? # scan_ssid=1
>> ? ? ? ? key_mgmt=WPA-PSK
>> ? ? ? ? psk="your psk"
>> ? ? ? ? proto=WPA2
>> }
>>
>> If you see a line like this:
>> WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
>> you can go to another terminal and start dhclient or dhcpcd like this:
>>
>> dhcpcd wlan0 (or whatever your device name is)
>>
>>
>> If this is all running fine, you most probably face a network manager
>> problem.
>>
>>
>> Hope that helps,
>> regards,
>> Andreas
>>
>
>
> The timeouts I have not see just yet; only the RX DMA thing which I am
> monitoring and trying to recreate, so I can _possibly_ bisect. as for the
> timeout(s) I have not see this with the current, there is a bug report on
> this(2.6.37 or so) but I think the bug was closed due to no participation or
> something.
>
> also make sure you have power save off(iwconfig wlan* power off) because
> from what I remember powersave on is what triggers the timeout(s)
>
>
> Justin P. Mattock
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html

2012-03-10 10:14:23

by Oskar Stenman

[permalink] [raw]
Subject: Re: ath9k timeouts with the current Mainline

I'm having a similar or the same problem, it's been nagging me for at
least 1.5years.

If I'm able to connect I get frequent dropouts from any wireless network
I'm connected to. It gets sluggish and after a little while disconnects,
and once it has disconnected it just keeps reconnecting and failing.
sometimes a reboot helps, but most of the time it wont help anymore than
a couple of seconds to a minute. It's also impossible to connect to my
wireless hotspot on my Xperia Mini Pro and it seems ad-hoc networks are
also impossible.

I'm running ubuntu 11.10 with latest patches applied as of today. Since
i've not seen anything being solved during this time i doubt anyone has
been trying to, or has been able to solve the problem recently.

uname -a
Linux 1005PE 3.0.0-16-generic #29-Ubuntu SMP Tue Feb 14 12:49:42 UTC
2012 i686 i686 i386 GNU/Linux

lspci -vvv
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
Network Adapter (PCI-Express) (rev 01)
Subsystem: AzureWave Device 1089
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fbff0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
PME(D0+,D1+,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000 Data: 0000
Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <512ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 00-15-17-ff-ff-24-14-12
Capabilities: [170 v1] Power Budgeting <?>
Kernel driver in use: ath9k
Kernel modules: ath9k

after having network-manager trying to connect to my hotspot for a while
dmesg shows a lot of:
[ 1475.249446] wlan0: direct probe to 84:00:d2:20:0d:3a (try 1/3)
[ 1475.448077] wlan0: direct probe to 84:00:d2:20:0d:3a (try 2/3)
[ 1475.648107] wlan0: direct probe to 84:00:d2:20:0d:3a (try 3/3)
[ 1475.848085] wlan0: direct probe to 84:00:d2:20:0d:3a timed out

complete dmesg and lsmod is attached.

What i've found that seems relevant on a quick google-run:
https://bugzilla.kernel.org/show_bug.cgi?id=42092
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773154

No solution in sight though.

If there's any way that i can help solve this please let me know!

Oskar Stenman


On 01/15/2012 04:50 PM, Justin P. Mattock wrote:
> not sure if the Internet provider just sucks, or I am hitting a
> wireless issue. basically my connection times out after a few mins of
> being up.(streaming radio is not solid).
>
> dmesg shows:
>
> [ 3322.827549] wlan1: authenticate with d8:c7:c8:a2:0f:40 (try 1)
> [ 3322.831778] wlan1: d8:c7:c8:a2:0f:40 denied authentication (status 17)
> [ 3386.310128] wlan1: authenticate with d8:c7:c8:a2:0d:80 (try 1)
> [ 3386.312010] wlan1: d8:c7:c8:a2:0d:80 denied authentication (status 17)
> [ 3389.481771] wlan1: direct probe to 00:18:0a:02:19:c3 (try 1/3)
> [ 3389.681095] wlan1: direct probe to 00:18:0a:02:19:c3 (try 2/3)
> [ 3389.881094] wlan1: direct probe to 00:18:0a:02:19:c3 (try 3/3)
> [ 3390.081092] wlan1: direct probe to 00:18:0a:02:19:c3 timed out
> [ 3458.618065] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 1/3)
> [ 3458.818079] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 2/3)
> [ 3459.018080] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 3/3)
> [ 3459.218058] wlan1: direct probe to d8:c7:c8:a2:0d:80 timed out
> [ 3466.518579] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 1/3)
> [ 3466.718111] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 2/3)
> [ 3466.918074] wlan1: direct probe to d8:c7:c8:a2:0d:80 (try 3/3)
> [ 3467.118077] wlan1: direct probe to d8:c7:c8:a2:0d:80 timed out
> [ 3474.424860] wlan1: authenticate with d8:c7:c8:a2:0d:80 (try 1)
> [ 3474.449681] wlan1: authenticated
> [ 3474.457133] wlan1: associate with d8:c7:c8:a2:0d:80 (try 1)
> [ 3474.471059] wlan1: RX AssocResp from d8:c7:c8:a2:0d:80 (capab=0x421
> status=0 aid=13)
> [ 3474.471067] wlan1: associated
> [ 3474.471075] wlan1: moving STA d8:c7:c8:a2:0d:80 to state 1
> [ 3474.471080] wlan1: moving STA d8:c7:c8:a2:0d:80 to state 2
> [ 3474.473809] wlan1: moving STA d8:c7:c8:a2:0d:80 to state 3
> [ 3484.546077] wlan1: no IPv6 routers present
>
>
> card is:
> 03:00.0 Network controller: Atheros Communications Inc. AR5008
> Wireless Network Adapter (rev 01)
>
> has anybody else seen/experienced anything like this?
>
> Justin P. Mattock
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>


Attachments:
lsmod.txt (2.15 kB)
dmesg.txt (91.97 kB)
Download all attachments

2012-03-12 05:22:54

by Justin P. Mattock

[permalink] [raw]
Subject: Re: ath9k timeouts with the current Mainline

On 03/10/2012 02:30 PM, Adrian Chadd wrote:
> Hi,
>
> Please bisect the kernel to see if you can find a time where it worked.
>
> And try disabling ANI and see if that helps.
>
> ath9k seems to have a weird issue with the AR5008 series stuff
> (AR5416/AR5418) with noise floor calibration + ANI == weird RX
> deafness.
>
> FreeBSD doesn't seem to have this issue with the AR5416. I don't (yet) know why.
>
> Thanks,
>
>
> Adrian
>
> On 10 March 2012 09:02, Justin P. Mattock<[email protected]> wrote:
>> On 03/10/2012 06:13 AM, Andreas Hartmann wrote:
>>>
>>> Oskar Stenman wrote:
>>>>
>>>> I'm having a similar or the same problem, it's been nagging me for at
>>>> least 1.5years.
>>>>
>>>> If I'm able to connect I get frequent dropouts from any wireless network
>>>> I'm connected to. It gets sluggish and after a little while disconnects,
>>>> and once it has disconnected it just keeps reconnecting and failing.
>>>> sometimes a reboot helps, but most of the time it wont help anymore than
>>>> a couple of seconds to a minute. It's also impossible to connect to my
>>>> wireless hotspot on my Xperia Mini Pro and it seems ad-hoc networks are
>>>> also impossible.
>>>>
>>>> I'm running ubuntu 11.10 with latest patches applied as of today. Since
>>>> i've not seen anything being solved during this time i doubt anyone has
>>>> been trying to, or has been able to solve the problem recently.
>>>
>>>
>>> I'm running exactly the same chip (according lspci) without any problem.
>>> But I'm using slightly different environment:
>>>
>>> 1. 64 bit
>>> 2. kernel 3.1 (some time ago, I run 3.0, too, but cannot remember
>>> having any problems related ar9285).
>>> 3. no network manager - just plain wpa_supplicant.
>>> 4. wpa_supplicant 0.7.3
>>>
>>>
>>> If you like to, you could just check, if the problem is network manager
>>> related. Try to stop it and run wpa_supplicant manually as root like
>>> this (ensure, that no other wpa_supplicant process is running at the
>>> same time):
>>>
>>> wpa_supplicant -t -c /etc/wpa_supplicant/wpa_supplicant.conf -Dnl80211
>>> -i wlan0
>>>
>>> -c is the config file. -i is the device name.
>>>
>>> sample config file for WPA2 PSK would be:
>>>
>>> network={
>>> ssid="your network name"
>>> # scan_ssid=1
>>> key_mgmt=WPA-PSK
>>> psk="your psk"
>>> proto=WPA2
>>> }
>>>
>>> If you see a line like this:
>>> WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=CCMP]
>>> you can go to another terminal and start dhclient or dhcpcd like this:
>>>
>>> dhcpcd wlan0 (or whatever your device name is)
>>>
>>>
>>> If this is all running fine, you most probably face a network manager
>>> problem.
>>>
>>>
>>> Hope that helps,
>>> regards,
>>> Andreas
>>>
>>
>>
>> The timeouts I have not see just yet; only the RX DMA thing which I am
>> monitoring and trying to recreate, so I can _possibly_ bisect. as for the
>> timeout(s) I have not see this with the current, there is a bug report on
>> this(2.6.37 or so) but I think the bug was closed due to no participation or
>> something.
>>
>> also make sure you have power save off(iwconfig wlan* power off) because
>> from what I remember powersave on is what triggers the timeout(s)
>>
>>
>> Justin P. Mattock
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>


please no top-posting!

Anyway a bisect is easy just would like a way to recreate this?(so that
I am not wasting my precious time) does anybody know how to do this? any
kind of C code to trigger this? any tweaking with NM etc.. to trigger
this? reading through
http://www.mail-archive.com/[email protected]/msg05051.html
hostapd was able to trigger this for one, but over here still no luck.

If no re-creation is possible I suppose the bisect might take a few
weeks(since I seem to be hitting this once a week),but then again I
could be wrong.

Justin P. Mattock