Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Nov 2011 12:21:06 +0400
From:      Ruslan Mahmatkhanov <cvs-src@yandex.ru>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        freebsd-mobile@freebsd.org
Subject:   Re: other bwn panic
Message-ID:  <4EBCDAF2.5020605@yandex.ru>
In-Reply-To: <CAJ-Vmok%2BUcGUS8fVm6WehyEZBUJKr5TmL3RnKwOQbiMdcpb6Mw@mail.gmail.com>
References:  <4EBBD13C.2010705@yandex.ru> <CAJ-Vmok%2BUcGUS8fVm6WehyEZBUJKr5TmL3RnKwOQbiMdcpb6Mw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Adrian Chadd wrote on 11.11.2011 11:34:
> On 10 November 2011 05:27, Ruslan Mahmatkhanov <cvs-src@yandex.ru> wrote:
>> Good day!
>>
>> I just got yet another panic with bwn driver on fresh -CURRENT. And
>> still have debugging options turned off, so dunno if this ("unexpected
>> NULL ni") can help anyhow to understand the problem. Since switching
>> to 10.0 i constantly get those "HW reset: PHY TX errors", but till
>> today this wasn't a problem:
> 
> Was there ever a version where the HW reset issues weren't happening?

Yes, but i'm not sure what exact version it was. Firmware version is
still the same as it was on 9-CURRENT, but after some recent if_bwn or
wireless stack changes this errors now happens constantly, but this
panic was for the first time.

> We'll need a backtrace to figure out why the node is null.
> 
> Adrian

Understood, i'll turn debug on and come with stacktrace next time.

-- 
Regards,
Ruslan

Tinderboxing kills... the drives.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EBCDAF2.5020605>