On Sat, Jan 21, 2017 at 08:07:53PM +1300, Richard Procter wrote:
> Hi,
>
> On 18/01/2017, Stefan Sperling wrote:
> > I managed to trigger the following uvm fault by continously switching an
> > iwm(4) client between two APs on different channels, i.e. a loop that runs:
> >
Hi,
On 18/01/2017, Stefan Sperling wrote:
> I managed to trigger the following uvm fault by continously switching an
> iwm(4) client between two APs on different channels, i.e. a loop that runs:
> ifconfig iwm0 chan X; sleep 10; ifconfig iwm chan Y; sleep 10;
>
>
Anyone?
This could crash all your iwm(4) machines any time you run ifconfig...
On Tue, Jan 17, 2017 at 08:22:27PM +0100, Stefan Sperling wrote:
> I managed to trigger the following uvm fault by continously switching an
> iwm(4) client between two APs on different channels, i.e. a loop that runs:
I managed to trigger the following uvm fault by continously switching an
iwm(4) client between two APs on different channels, i.e. a loop that runs:
ifconfig iwm0 chan X; sleep 10; ifconfig iwm chan Y; sleep 10;
uvm_fault(0x819614a0, 0x7, 0, 2) -> e
kernel: page fault trap, code=0