Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

Looking good now. Thanks Ira Taylor On 05/25/16 08:40, Stefan Sperling wrote: On Wed, May 25, 2016 at 11:19:22AM +0200, Stefan Sperling wrote: A better diff was posted here: http://marc.info/?l=openbsd-tech=146384048501213=raw Can you please try this? This is now committed so upcoming

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

On Wed, May 25, 2016 at 11:19:22AM +0200, Stefan Sperling wrote: > A better diff was posted here: > http://marc.info/?l=openbsd-tech=146384048501213=raw > Can you please try this? This is now committed so upcoming snaps should include it. Let me know how it works out. Thanks.

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

On Mon, May 23, 2016 at 12:24:03PM -0500, Ira Taylor wrote: > iwm0: unhandled firmware response 0x7e/0xe004 rx ring 9[23] This message shows you were running a snapshot with a known bug. The bug is not related to this message; this message is just a debug message which my code trigge

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

right line this time: 12:28:40.097283 802.11 flags=0<>: beacon, timestamp 8853501030487, interval 100, caps=421, ssid (FiOS-94KM2-5G), rates 6M 9M 12M 18M 24M 36M 48M 54M, tim 0x0001, country 'US ', channel 36 limit 17dB, channel 40 limit 17dB, channel 44 limit

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

it drop when running 11n i reset the mode to 11a it seems to work then I have it set to 11a and the output is: tcpdump -n -i iwm0 -y IEEE802_11_RADIO -vv -s 1500 type mgt subtype beacon tcpdump: listening on iwm0, link-type IEEE802_11_RADIO 12:04:41.755288 802.11 flags=0<>: beacon, timestamp

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

On Sun, May 22, 2016 at 12:43:41PM -0500, Ira Taylor wrote: > I am having issues with wifi also, mine connection keeps dropping. Could you take some time to add more details to your problem report? What are you running exactly? Could you post a dmesg? Under which conditions does the connection

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

I am having issues with wifi also, mine connection keeps dropping. Ira Taylor On 05/21/16 09:47, Stuart Henderson wrote: On 2016/05/21 16:25, Peter N. M. Hansteen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/21/16 16:12, Stefan Sperling wrote: On Sat, May 21, 2016 at

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/21/16 16:47, Stuart Henderson wrote: >> But looking at my logs I don't seem to have sufficient info to >> be sure, perhaps I should put the interface into debug mode for a >> while to collect info. > > tcpdump -yIEEE802_11_RADIO -niiwm0 -l |

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

On 2016/05/21 16:25, Peter N. M. Hansteen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 05/21/16 16:12, Stefan Sperling wrote: > > On Sat, May 21, 2016 at 04:04:35PM +0200, Peter N. M. Hansteen > > wrote: > >> The main reason I reported this was that I also had an episode of >

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

On Sat, May 21, 2016 at 04:04:35PM +0200, Peter N. M. Hansteen wrote: > The main reason I reported this was that I also had an episode of lost > link for long enough for me to notice for the first time in quite a > while. Again, could be unrelated. Did your AP decide to switch channels when this

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/21/16 15:28, Stefan Sperling wrote: > No reason to worry. These are harmless debug messages from the iwm > firmware update diff I mailed out. See > http://marc.info/?l=openbsd-tech=146356530605833=2 > > This will be fixed in the next

Re: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23]

On Sat, May 21, 2016 at 01:10:13PM +0200, pe...@bsdly.net wrote: > >Synopsis: iwm0: unhandled firmware response 0x7e/0xe0000004 rx ring 9[23] > >followed by fatal firmware error, link loss > >Category:firmware / driver bug > >Environment: > System :