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 but it seems to trigger during > > a large download (3-4GB or so). > > > > Anything I should try to make diagnosing this easier? > > This is very odd. > The response code (before the slash) is supposed to match the ID of the > command the firmware is responding to. But many of the response codes in > your output don't match any of the commands we send to the firmware. > > I've never seen this before. > Can you provide me with a URL that will trigger this when downloaded?
Actually I triggered it by streaming a film over NFS. The NFS options that I use are: -i,-r=32768,noauto,ro 0 0
