FreeBSD_HEAD-tests - Build #1263 - Still Unstable:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1263/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1263/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1263/console
Change su
On Sun, Aug 9, 2015 at 6:36 AM, Gleb Smirnoff wrote:
> On Sun, Aug 09, 2015 at 12:28:22PM +0200, Kristof Provost wrote:
> K> Hi,
> K>
> K> I’ve run into a reproducible panic on a VIMAGE kernel with ‘sysctl -a’.
> K>
> K> Relevant backtrace bits:
> K> #8 0x80e7dd28 in trap (frame=0xfe
> On Aug 9, 2015, at 11:10 AM, Konstantin Belousov wrote:
>
> On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
>>
>> I suspect the LOR is new.
>>
>> It looks like the panic is occurring when WITNESS tries to print the
>> backtrace for the LOR. I???m not familiar with that code;
On Sun, Aug 09, 2015 at 08:08:21PM +, jenkins-ad...@freebsd.org wrote:
> FreeBSD_HEAD-tests - Build #1262 - Still Unstable:
> Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1262/
> Full change log:
> https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1262/changes
> Full
On Sun, Aug 09, 2015 at 08:32:15PM +0100, Gavin Atkinson wrote:
G> On Thu, 6 Aug 2015, Gleb Smirnoff wrote:
G> > As part of the "opaque ifnet project" [1], all 802.11 (WiFi) drivers
G> > undergo change of not being an interface anymore. Historically in FreeBSD
G> > 802.11 stack, 802.11 devices ca
FreeBSD_HEAD-tests - Build #1262 - Still Unstable:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1262/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1262/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1262/console
Change su
On Thu, 6 Aug 2015, Gleb Smirnoff wrote:
> As part of the "opaque ifnet project" [1], all 802.11 (WiFi) drivers
> undergo change of not being an interface anymore. Historically in FreeBSD
> 802.11 stack, 802.11 devices called if_attach() and created an interface.
> Later this was generalized and
On Sun, Aug 09, 2015 at 08:25:56PM +0200, Kristof Provost wrote:
K> On 2015-08-09 13:36:35 (+0300), Gleb Smirnoff wrote:
K> > On Sun, Aug 09, 2015 at 12:28:22PM +0200, Kristof Provost wrote:
K> > K> The following fixes it for me:
K> > K>
K> > K> diff --git a/sys/netinet/tcp_reass.c b/sys/netinet/
On 2015-08-09 13:36:35 (+0300), Gleb Smirnoff wrote:
> On Sun, Aug 09, 2015 at 12:28:22PM +0200, Kristof Provost wrote:
> K> The following fixes it for me:
> K>
> K> diff --git a/sys/netinet/tcp_reass.c b/sys/netinet/tcp_reass.c
> K> index 77d8940..3913ef3 100644
> K> --- a/sys/netinet/tcp_reass.
On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
>
> I suspect the LOR is new.
>
> It looks like the panic is occurring when WITNESS tries to print the
> backtrace for the LOR. I???m not familiar with that code; does it use the
> kernel linker?
>
It indeed locks the linker lock
> On Aug 8, 2015, at 11:47 PM, Konstantin Belousov wrote:
>
> On Sat, Aug 08, 2015 at 05:24:37PM -0700, Tim Kientzle wrote:
>> I???m seeing the following crash quite consistently on r286438. It looks
>> like the recent work on the kernel linker locking still has some issues.
>>
>> Any suggest
FreeBSD_HEAD-tests - Build #1261 - Still Unstable:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1261/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1261/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1261/console
Change su
FreeBSD_HEAD-tests - Build #1260 - Unstable:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1260/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1260/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1260/console
Change summarie
On Sun, Aug 09, 2015 at 12:28:22PM +0200, Kristof Provost wrote:
K> Hi,
K>
K> I’ve run into a reproducible panic on a VIMAGE kernel with ‘sysctl -a’.
K>
K> Relevant backtrace bits:
K> #8 0x80e7dd28 in trap (frame=0xfe01f16b26a0)
K> at /usr/src/sys/amd64/amd64/trap.c:426
K> #9 0x
Hi,
I’ve run into a reproducible panic on a VIMAGE kernel with ‘sysctl -a’.
Relevant backtrace bits:
#8 0x80e7dd28 in trap (frame=0xfe01f16b26a0)
at /usr/src/sys/amd64/amd64/trap.c:426
#9 0x80e5e6a2 in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:235
#10 0xfff
15 matches
Mail list logo