TB --- 2012-12-11 06:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-11 06:40:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Mon, Dec 10, 2012 at 03:18:45PM -0800, m...@freebsd.org wrote:
m> On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd wrote:
m> > 9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
m> > after it's finalised/freed.
m> >
m> > I have a similar bug showing up on ath(4) RX. :(
m>
m> Co
Artyom,
can you please run route with attached patch and show output?
--
Totus tuus, Glebius.
Index: route.c
===
--- route.c (revision 244082)
+++ route.c (working copy)
@@ -325,6 +325,7 @@
goto fiboptlist_csv_ret;
}
s
Got bit by compiler not warning on some things.
Working on a fix.
-Alfred
On 12/10/12 10:36 PM, FreeBSD Tinderbox wrote:
TB --- 2012-12-11 03:32:04 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-11 03:32:04 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PR
TB --- 2012-12-11 03:32:04 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-11 03:32:04 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-11 03:24:20 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-11 03:24:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-12-11 04:09:25 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-11 04:09:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Dec 10, 2012, at 10:38 AM, Rick Macklem wrote:
> Adrian Chadd wrote:
>> .. what was the previous kernel version?
>>
> Hopefully Tim has it narrowed down more, but I don't see
> the hangs on a Sept. 7 kernel from head and I do see them
> on a Dec. 3 kernel from head. (Don't know the eact r
On Mon, Dec 10, 2012 at 07:11:59PM -0500, Rick Macklem wrote:
> Konstantin Belousov wrote:
> > On Mon, Dec 10, 2012 at 01:38:21PM -0500, Rick Macklem wrote:
> > > Adrian Chadd wrote:
> > > > .. what was the previous kernel version?
> > > >
> > > Hopefully Tim has it narrowed down more, but I don't
TB --- 2012-12-11 02:07:55 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-12-11 02:07:55 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Mon, Dec 10, 2012 at 05:37:17PM -0800, Garrett Cooper wrote:
> On Mon, Dec 10, 2012 at 3:21 PM, Adrian Chadd wrote:
> > On 10 December 2012 15:18, wrote:
> >> On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd wrote:
> >>> 9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
> >>
On Mon, Dec 10, 2012 at 3:21 PM, Adrian Chadd wrote:
> On 10 December 2012 15:18, wrote:
>> On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd wrote:
>>> 9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
>>> after it's finalised/freed.
>>>
>>> I have a similar bug showing up on a
Konstantin Belousov wrote:
> On Mon, Dec 10, 2012 at 01:38:21PM -0500, Rick Macklem wrote:
> > Adrian Chadd wrote:
> > > .. what was the previous kernel version?
> > >
> > Hopefully Tim has it narrowed down more, but I don't see
> > the hangs on a Sept. 7 kernel from head and I do see them
> > on a
On 10 December 2012 15:18, wrote:
> On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd wrote:
>> 9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
>> after it's finalised/freed.
>>
>> I have a similar bug showing up on ath(4) RX. :(
>
> Compile with DEBUG_MEMGUARD in the kernel co
On Mon, Dec 10, 2012 at 3:10 PM, Adrian Chadd wrote:
> 9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
> after it's finalised/freed.
>
> I have a similar bug showing up on ath(4) RX. :(
Compile with DEBUG_MEMGUARD in the kernel configuration, and then set
vm.memguard.desc to
9216 sounds like a jumbo frame mbuf. So the NIC is writing to an mbuf
after it's finalised/freed.
I have a similar bug showing up on ath(4) RX. :(
adrian
On 10 December 2012 14:22, Garrett Cooper wrote:
> I noticed this while checking the logs on one of my test boxes
> after restarting th
I noticed this while checking the logs on one of my test boxes
after restarting the network. Any idea where I should start looking
into this (has IPv6 enabled but wasn't using it, em/cxgbe/ixgbe
interfaces with the ixgbe interfaces lagged previously, but now not)?
It looks suspiciously like the
Hi,
The fact the initial probe/attach fails by returning 0x means
the chip isn't "right" on the bus.
It's either just not mapped in correctly, or it's "powered off."
If it were just asleep, it'd return 0xdeadc0de or 0xdeadbeef or
something similar like that.
Try AR_SCR (0x4004) and AR_P
On Mon, Dec 10, 2012 at 12:35 PM, Mark Atkinson wrote:
> vex x86->IR: unhandled instruction bytes: 0xF 0xB 0x90 0x90
> ==33074== valgrind: Unrecognised instruction at address 0x380434e9.
> ==33074==at 0x380434E9: ??? (in
> /usr/local/lib/valgrind/memcheck-x86-freebsd)
> ==33074==by 0x323C
On Thu, Dec 6, 2012 at 4:55 PM, Garrett Cooper wrote:
...
> (Removing bogus list)
>
> If I try and let it import the pool at boot it claims the pool is in a
> FAULTED state when I point mountroot to /dev/cd0 (one of gjb's
> snapshot CDs -- thanks!), run service hostid onestart, etc. If I
> expor
On Mon, Dec 10, 2012 at 01:13:23PM -0800, Mark Atkinson wrote:
> -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,
-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
>> segfault, but the rtld side of things
-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
On Mon, Dec 10, 2012 at 12:29:20PM -0800, Mark Atkinson wrote:
> -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-0
-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 12/7/2012 6:08 AM, Dimitry Andric wrot
On Friday, December 07, 2012 4:59:37 am hu...@hush.com wrote:
> Hello,
>
> thank you for your answer.
>
> Unfortunately, I'm unexperienced with FreeBSD, and am absolutely unfamiliar
with hardware specifics. During this mail conversion, I have heard abour BAR
for the first time, and therefore, I
On Mon, Dec 10, 2012 at 01:38:21PM -0500, Rick Macklem wrote:
> Adrian Chadd wrote:
> > .. what was the previous kernel version?
> >
> Hopefully Tim has it narrowed down more, but I don't see
> the hangs on a Sept. 7 kernel from head and I do see them
> on a Dec. 3 kernel from head. (Don't know th
Adrian Chadd wrote:
> .. what was the previous kernel version?
>
Hopefully Tim has it narrowed down more, but I don't see
the hangs on a Sept. 7 kernel from head and I do see them
on a Dec. 3 kernel from head. (Don't know the eact rNN.)
It seems to predate my commit (r244008), which was my fi
On Mon, Dec 10, 2012 at 09:35:29AM -0800, Mark Atkinson wrote:
> -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 /u
-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 starts up and exits normally for me.
Before calling fiboptlist_csv() the errno = EINVAL. I hope this help to solve
problem.
On Monday 10 December 2012 17:40:57 Gleb Smirnoff wrote:
> On Sat, Dec 08, 2012 at 01:00:57PM +0200, Artyom Mirgorodskiy wrote:
> A> I just upgraded to revision 244030. Unexpected route command is not
> workin
On Fri, 2012-12-07 at 16:11:37 -0600, Chuck Burns wrote:
> On 12/7/2012 3:50 PM, CeDeROM wrote:
> > Hello :-)
> >
> > I have tried to chceck for badblocks on my / but I did not find badblocks
> > program on LiveCD and there is no option to install it. This is very useful
> > utility, please add it
sysctl net.my_fibnum
net.my_fibnum: 0
On Monday 10 December 2012 17:40:57 Gleb Smirnoff wrote:
> On Sat, Dec 08, 2012 at 01:00:57PM +0200, Artyom Mirgorodskiy wrote:
> A> I just upgraded to revision 244030. Unexpected route command is not
> working:
> A>
> A> #route add default 192.168.1.1
> A>
On Sat, Dec 08, 2012 at 01:00:57PM +0200, Artyom Mirgorodskiy wrote:
A> I just upgraded to revision 244030. Unexpected route command is not working:
A>
A> #route add default 192.168.1.1
A> route: fiboptlist_csv failed.
What does 'sysctl net.my_fibnum' say?
--
Totus tuus, Glebius.
_
On Dec 6, 2012, at 1:28 AM, Garrett Cooper wrote:
> On Wed, Dec 5, 2012 at 3:51 PM, Damien Fleuriot wrote:
>
> ...
>
>> All trolling aside, I believe an awesome fix to be setting module override
>> in /etc/make.conf to only build the 4-5 specific modules one needs.
>>
>> To be honest I thin
On Sun, Dec 09, 2012 at 09:52:18PM -0800, Tim Kientzle wrote:
>
> On Dec 3, 2012, at 12:46 AM, Garrett Cooper wrote:
>
> > On Sun, Dec 2, 2012 at 11:06 PM, Garrett Cooper wrote:
> >> On Sun, Dec 2, 2012 at 9:20 PM, Garrett Cooper wrote:
> >>> On Sun, Dec 2, 2012 at 9:08 PM, Adrian Chadd wrote:
.. what was the previous kernel version?
adrian
On 9 December 2012 22:08, Tim Kientzle wrote:
> I haven't found any useful clues yet, but thought I'd ask if anyone else
> was seeing hangs in a recent kernel.
>
> I just upgraded to r244036 using a straight GENERIC i386 kernel.
> (Straight buil
37 matches
Mail list logo
