-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/05/2014 12:24, Gleb Smirnoff wrote:
> On Fri, Sep 05, 2014 at 08:38:10AM -0700, Mark Atkinson wrote: M>
> r271093 GENERIC amd64. Received this panic in the tcp reassembly
> code: M> Unread portion of the kernel message b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r271093 GENERIC amd64. Received this panic in the tcp reassembly code:
Unread portion of the kernel message buffer:
panic: m_demote: m_nextpkt not NULL
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mounted a drive with -o sync this morning on r266123 and got a LOR I
had not seen before (ufs/soft updates)
lock order reversal:
1st 0xf8005904db78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2101
2nd 0xfe00efe72080 bufwait (bufwait) @
/usr/src
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2014 04:52, Aleksandr Rybalko wrote:
> On Wed, 14 May 2014 08:29:32 -0700 Mark Atkinson
> wrote:
>
> I updated -current to r265915 w/ amd64 kernel and I get a panic
> when I startx instantly (no video output of panic). T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I updated -current to r265915 w/ amd64 kernel and I get a panic
when I startx instantly (no video output of panic). There is a LOR
right before the panic.
This is built using the VT kernel definition.
loading the old kernel built @ r264316 continue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/2013 12:23, Konstantin Belousov wrote:
> On Fri, Jan 04, 2013 at 08:06:02PM +0100, Stefan Farfeleder wrote:
>> On Fri, Jan 04, 2013 at 08:14:38PM +0200, Konstantin Belousov
>> wrote:
>>> On Fri, Jan 04, 2013 at 04:49:41PM +0100, Stefan Farfele
On 1/1/2013 2:22 AM, Gleb Smirnoff wrote:
> Manfred,
>
> On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote:
> M> For the past few days the loopback interface 127.0.0.1 is broken on
> current.
> M> The last good kernel that works for me is r244662: Mon Dec 24 06:43:07
> PST 2012
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 12:45, Mark Atkinson wrote:
> On 12/10/2012 12:33, Konstantin Belousov wrote:
>
>> Hmm. Since I took out -O2 and added -g in rebuilding
>> libthr/libc/rtld, I figured I needed to reproduce a new
>> segfau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 12:33, Konstantin Belousov wrote:
> Hmm. Since I took out -O2 and added -g in rebuilding
> libthr/libc/rtld, I figured I needed to reproduce a new segfault,
> but the rtld side of things seems broken:
>> Use e.g. cd src/libexec/rtld-el
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/2012 10:25, Konstantin Belousov wrote:
> On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote: On
> 12/07/2012 09:29, Dimitry Andric wrote:
>>>> On 2012-12-07 17:43, Mark Atkinson wrote:
>>>>> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2012 09:29, Dimitry Andric wrote:
> On 2012-12-07 17:43, Mark Atkinson wrote:
>> On 12/7/2012 6:08 AM, Dimitry Andric wrote:
> ...
>>> With this patch (placed in /usr/ports/devel/dbus-qt4/files),
>>> qdbus start
On 12/7/2012 6:08 AM, Dimitry Andric wrote:
> On 2012-12-07 13:59, Dimitry Andric wrote:
>> On 2012-12-06 18:12, Mark Atkinson wrote:
>>> Short backstory, I had recently upgraded my workstation to the latest
>>> current which included clang as default cc now.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Short backstory, I had recently upgraded my workstation to the latest
current which included clang as default cc now.
Compiling chromium failed for want of SSE2, which led me to recompile
world with CPUTYPE?=core2. The original flag for world/ports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/2010 11:04, Mark Murray wrote:
> Hi
>
> IPv6 gurus: what are the CURRENT /etc/rc.conf incantations to do the
> following (which works):
>
> $ ifconfig gif0 create
> $ ifconfig gif0 tunnel 192.168.0.2 11.22.33.44
> $ ifconfig gif0 inet6 2001:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/06/2010 08:04, Mark Atkinson wrote:
>>> On 10/05/2010 11:39, Mark Atkinson wrote:
> kern.eventtimer.periodic: 0
*sigh* Although I misspelled eventtimer as 'eventtimers' in loader.conf
it still fails to boot without manual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/10 09:09, Mark Atkinson wrote:
> I had problems building world this morning, and noticed the following
> error had occurred that caused svn update to exit:
>
> $ svn update
> svn: No such revision 207561
>
> I keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I had problems building world this morning, and noticed the following
error had occurred that caused svn update to exit:
$ svn update
svn: No such revision 207561
I keep a local svn mirror to update all my clients to, but I couldn't
grab this revisio
On 5/3/2010 6:23 PM, Mark Atkinson wrote:
> On 5/3/2010 1:33 PM, Chris Ruiz wrote:
>> On Mon, May 3, 2010 at 9:16 AM, Mark Atkinson wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> I updated a border gateway yesterday from a Feb
On 5/3/2010 1:33 PM, Chris Ruiz wrote:
> On Mon, May 3, 2010 at 9:16 AM, Mark Atkinson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> I updated a border gateway yesterday from a Feb 23 kernel to a May 2
>> version kernel/world, and lost my
On 5/3/2010 12:55 PM, Pyun YongHyeon wrote:
> On Mon, May 03, 2010 at 07:01:56AM -0700, Mark Atkinson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> I updated to current yesterday and got the following 'witness_warn'
>> panic upon execut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/03/10 12:38, Fabien Thomas wrote:
> Hi Jeff,
>
> I'm with r207548 now and since some days i've system deadlock.
> It seems related to SUJ with process waiting on suspfs or ppwait.
I've also seen it stalled in suspfs, but this information is way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I updated a border gateway yesterday from a Feb 23 kernel to a May 2
version kernel/world, and lost my connectivity to my gif0 HE tunnel.
I've been using the following in /etc/rc.conf successfully for some time
to establish the tunnel:
# Hurricane El
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I updated to current yesterday and got the following 'witness_warn'
panic upon executing 'reboot':
suspending ithread with the following locks held:
exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @
/usr/src/sys/dev/msk/if_msk.c
On 03/02/10 09:21, Mark Atkinson wrote:
> On 03/02/10 09:03, John Baldwin wrote:
>> On Tuesday 02 March 2010 11:38:57 am Mark Atkinson wrote:
>>> Hi,
>>>
>>> I updated my kernel/world yesterday and thunderbird 3.0.2 started core
>>> dumping after I comp
On 03/02/10 09:03, John Baldwin wrote:
> On Tuesday 02 March 2010 11:38:57 am Mark Atkinson wrote:
>> Hi,
>>
>> I updated my kernel/world yesterday and thunderbird 3.0.2 started core
>> dumping after I completed the upgrade. It continued to do so on
>> previousl
Hi,
I updated my kernel/world yesterday and thunderbird 3.0.2 started core
dumping after I completed the upgrade. It continued to do so on
previously good operations after a full re-compile.
I noticed that some jemalloc changes went in and was wondering if anyone
else was noticing SEGV problems
stancy
across platforms.
Just FYI HP, linux, and solaris all include a wchar.h, but different
systems are missing different wcs* type functions.
---
Mark Atkinson
Checkpoint Technologies' Metaip Group
ma...@metaip.checkpoint.com
!(wired)?(coffee++):(wired)
To Unsubscribe: send mail to majord...
27 matches
Mail list logo