On 17 January 2017 at 12:25, Stefan Sperling <s...@stsp.name> wrote: > On Tue, Jan 17, 2017 at 11:56:09AM +0100, Stefan Sperling wrote: >> Without more details, all I can do is guess. >> I made one guess already (antennas) and sadly I guessed wrong. > > Another thing where your setup differs from mine is that you are > using a device with 3 antennas, whereas my devices only have 2. > > I have already ordered a 3 antenna device two days ago so I should > have one to test with soon. Perhaps I will see a problem then. > > Is anyone else reading this list using a 3 antenna device? > Please let us know whether it works. I'd actually recompiled the kernel using January 16th sources and it was working fine, until tonight. Brought up the glass console to see a panic
The following was photographed, then OCRd. I've given it a quick look to check it seems ok, but not a fine toothcomb. sfer overflow ddb> trace Debugger(d09e973d,13734d68,d09cf94e,f3734db8,b2000000) at Debugger+0x7 panic(d09cf9de,f3734d8c,d03c88c9,d1605008,13734df8) at panic.0x71 ieee80211_mira_update_stats(d169ab58,d1364030,4169a000,d03b9634,d0c6c980) at ieee80211 mira_update_siats+0x3bf ieee80211_mira_choose(d169ab58,d1364030,d169a000,0,d13be040) at ieee80.2.11_mira_choose+0x4e ar5008_tx_process (d1364009 ,0 , f3734edc,760f4a ,8354c175) at arS008_tx_process+0x1f2 ar5008_tx intr (d1364000,c0,f3734f0c, d03ba33f ,f3734ef4) at ar5008tx_intr+0x7c ar5008_intr (d1364000 , d135d380) at ar5008_intr+021b Xintrlegacy3() at Xintr_legacy3+0x81 --- interrupt --- cpu_idle_cycle(d0c6c960) at cpu_idlecycle+0xf I also have the ps lists, but I ran out of time to OCR them. Let me know if needed and I can forward the photos
