On Mon, Jan 23, 2017 at 08:23:41PM +, Dimitris Papastamos wrote:
> On Mon, Jan 23, 2017 at 02:56:10PM +0100, Stefan Sperling wrote:
> > On Mon, Jan 23, 2017 at 10:17:51AM +, Dimitris Papastamos wrote:
> > > Hi,
> > >
> > > iwm seems to produce "unhandled firmware response" messages.
On Mon, Jan 23, 2017 at 02:56:10PM +0100, Stefan Sperling wrote:
> On Mon, Jan 23, 2017 at 10:17:51AM +, Dimitris Papastamos wrote:
> > Hi,
> >
> > iwm seems to produce "unhandled firmware response" messages. Network
> > connectivity is really bad during this period and eventually ceases
> >
trimmed
> it.
This looks like memory corruption. There is garbage in memory.
Not sure what to do about this.
Can you tell us which snapshot was still working?
> iwm0: unhandled firmware response 0xf2/0x12a84a5c rx ring 114[34]
> iwm0: unhandled firmware response 0xff/0x80 rx ring 127[255]
> iwm0:
On Tue, Jul 05, 2016 at 07:43:57PM +0200, Stefan Sperling wrote:
> On Tue, Jul 05, 2016 at 06:22:00PM +0100, Dimitris Papastamos wrote:
> > Hi,
> >
> > I am have some issues with iwm(4). I think this started happening
> > around the 22nd-23rd of June.
> >
> > I cannot reproduce it very easily
firmware.
I've never seen this before.
Can you provide me with a URL that will trigger this when downloaded?
> iwm0: unhandled firmware response 0xc2/0xfcb60ac2 rx ring 124[182]
> iwm0: unhandled firmware response 0x6/0xfcb60d06 rx ring 124[182]
> iwm0: unhandled firmware response 0x9
ntegrated
Camera" rev 2.00/10.19 addr 6
video0 at uvideo0
uhub2 at uhub1 port 1 "Intel Rate Matching Hub" rev 2.00/0.03 addr 2
ugen0 detached
umb0 at uhub0 port 4 configuration 1 interface 0 "Sierra Wireless Inc. Sierra
Wireless EM7345 4G LTE" rev 2.00/17.29 addr 2
umodem0 at
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
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.
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
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
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
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
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
-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 |
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
>
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
-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
On Sat, May 21, 2016 at 01:10:13PM +0200, pe...@bsdly.net wrote:
> >Synopsis: iwm0: unhandled firmware response 0x7e/0xe004 rx ring 9[23]
> >followed by fatal firmware error, link loss
> >Category:firmware / driver bug
> >Environment:
> System :
18 matches
Mail list logo