On Fri, Mar 06, 2015 at 11:24:27PM +0100, Martin Pieuchot wrote:
> On 06/03/15(Fri) 22:06, Remi Locherer wrote:
> > On Fri, Mar 06, 2015 at 09:15:23AM +0100, Stefan Sperling wrote:
> > > On Fri, Mar 06, 2015 at 08:45:20AM +0100, Remi Locherer wrote:
> > > > Hi,
> > > >
> > > > Since about fall 201
On 7 March 2015 at 01:18, Michael wrote:
>> I think this is how a null-pointer call shows up in ddb.
>>
>> Does the diff below help?
>>
>
>
> Perfect! That stopped the uvm_fault occuring, scanning now works well;
> however when actually connecting to an AP I get a number of
> bwi0: watchdog timeo
On Sat, Mar 07, 2015 at 03:35:29PM -0330, Michael wrote:
> So here is the mentioned bootup/dmesg output with Stefans debug patch,
> where the in this output is, is just me typing in the command
> to shutdown as it is quite hard to work with the system with the
> number of messages being printed. A
umsm0 at uhub3 port 3 configuration 1 interface 0 "HUAWEI HUAWEI Mobile" rev
2.00/1.02 addr 4
ucom0 at umsm0
umsm1 at uhub3 port 3 configuration 1 interface 1 "HUAWEI HUAWEI Mobile" rev
2.00/1.02 addr 4
ucom1 at umsm1
umsm2 at uhub3 port 3 configuration 1 interface 2 "HUAWEI HUAWEI Mobile" rev
2
> I can't find anything inherently bad in there.
>
> The interrupts you're getting are receive interrupts. So it seems receive
> is working, but transmit is broken (watchdog timeout triggers if attempts
> to transmit time out). I don't know why this is happenning.
>
> Does anything change if you mo
On Sat, Mar 07, 2015 at 04:29:40PM -0330, Michael wrote:
> > I can't find anything inherently bad in there.
> >
> > The interrupts you're getting are receive interrupts. So it seems receive
> > is working, but transmit is broken (watchdog timeout triggers if attempts
> > to transmit time out). I do
