TB --- 2011-12-17 03:59:49 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-12-17 03:59:49 - starting HEAD tinderbox run for mips/mips
TB --- 2011-12-17 03:59:49 - cleaning the object tree
TB --- 2011-12-17 03:59:58 - cvsupping the source tree
TB --- 2011-12-17 03:59:58 - /usr/bin/c
On 16. Dec 2011, at 16:42 , Dimitry Andric wrote:
> On 2011-12-16 16:46, FreeBSD Tinderbox wrote:
> ...
>> ===> usr.sbin/bsnmpd/modules/snmp_mibII (all)
>> cc -fpic -DPIC -O -pipe -G0
>> -I/src/usr.sbin/bsnmpd/modules/snmp_mibII/../../../../contrib/bsnmp/lib
>> -I/src/usr.sbin/bsnmpd/modules/s
TB --- 2011-12-16 22:26:50 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-12-16 22:26:50 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2011-12-16 22:26:50 - cleaning the object tree
TB --- 2011-12-16 22:27:06 - cvsupping the source tree
TB --- 2011-12-16 22:27:06 - /u
TB --- 2011-12-16 22:22:36 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-12-16 22:22:36 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2011-12-16 22:22:36 - cleaning the object tree
TB --- 2011-12-16 22:22:51 - cvsupping the source tree
TB --- 2011-12-16 22:22:51 - /usr
(This was originally posted to freebsd-hackers, I'm reposting following
email suggestions.)
We've observed a panic in FreeBSD 7 (7.2-PRERELEASE FreeBSD) several
times that we've not been able to track down. Upgrading is not an
option at this time.
Does this look at all familiar to anyone?
TB --- 2011-12-16 21:01:21 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-12-16 21:01:21 - starting HEAD tinderbox run for ia64/ia64
TB --- 2011-12-16 21:01:21 - cleaning the object tree
TB --- 2011-12-16 21:01:36 - cvsupping the source tree
TB --- 2011-12-16 21:01:36 - /usr/bin/c
TB --- 2011-12-16 21:26:12 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-12-16 21:26:12 - starting HEAD tinderbox run for mips/mips
TB --- 2011-12-16 21:26:13 - cleaning the object tree
TB --- 2011-12-16 21:26:21 - cvsupping the source tree
TB --- 2011-12-16 21:26:21 - /usr/bin/c
On Dec 16, 2011, at 4:18 PM, John Baldwin wrote:
> On Friday, December 16, 2011 11:02:20 am Andrew Boyer wrote:
>>
>> On Dec 16, 2011, at 9:52 AM, Luigi Rizzo wrote:
>>
>>> On Thu, Dec 15, 2011 at 04:21:51PM -0500, Andrew Boyer wrote:
These two changes allow you to set PXE as the default M
On Friday, December 16, 2011 11:02:20 am Andrew Boyer wrote:
>
> On Dec 16, 2011, at 9:52 AM, Luigi Rizzo wrote:
>
> > On Thu, Dec 15, 2011 at 04:21:51PM -0500, Andrew Boyer wrote:
> >> These two changes allow you to set PXE as the default MBR boot selection,
which enables you to write a 'reboot
On Friday, December 16, 2011 1:37:41 pm Chase Epoch Cameron wrote:
> Salutations all,
>
>
> I continuously see this error pop up when I boot my system as it loads,
> and it appears as such:
> Code:
>
>
> gptzfsboot error 49 lba 1
> gptzfsboot error 49 lba 32
> gptzfsboot error 49 lba 1
> gptzf
On Thu, 2011-12-15 at 18:39:59 -0800, Doug Barton wrote:
> On 12/14/2011 05:20, Sean Bruno wrote:
> > We're seeing what looks like a syncher/ufs resource starvation on 9.0 on
> > the cvs2svn ports conversion box.
>
> ... sounds like a good reason not to migrate the history to me. :)
Sounds more l
On 2011-12-16 19:37, Chase Epoch Cameron wrote:
> Salutations all,
>
>
> I continuously see this error pop up when I boot my system as it loads,
> and it appears as such:
> Code:
>
>
> gptzfsboot error 49 lba 1
> gptzfsboot error 49 lba 32
> gptzfsboot error 49 lba 1
> gptzfsboot error 49 lba
Salutations all,
I continuously see this error pop up when I boot my system as it loads,
and it appears as such:
Code:
gptzfsboot error 49 lba 1
gptzfsboot error 49 lba 32
gptzfsboot error 49 lba 1
gptzfsboot error 49 lba 32
I have run dd to check for bad sectors both destructively and I am
Can someone please write up a nice, concise blog post somewhere
outlining all of this?
Extra bonus points if it's a blog that is picked up by
blogs.freebsdish.org and/or some of the other BSD sites.
Guys/girls/fuzzy things - this is 2011; people look at shiny blog
sites with graphs rather than ma
On 2011-12-16 16:46, FreeBSD Tinderbox wrote:
...
> ===> usr.sbin/bsnmpd/modules/snmp_mibII (all)
> cc -fpic -DPIC -O -pipe -G0
> -I/src/usr.sbin/bsnmpd/modules/snmp_mibII/../../../../contrib/bsnmp/lib
> -I/src/usr.sbin/bsnmpd/modules/snmp_mibII/../../../../contrib/bsnmp/snmpd
> -DHAVE_ERR_H -
Hi,
[resend on the ml, my bad]
On Fri, Dec 16, 2011 at 5:54 AM, Attilio Rao wrote:
> 2011/12/16 Arnaud Lacombe :
>> Hi,
>>
>> On Thu, Dec 15, 2011 at 2:32 AM, O. Hartmann
>> wrote:
>>> Just saw this shot benchmark on Phoronix dot com today:
>>>
>>> http://www.phoronix.com/scan.php?page=news_ite
On Fri, Dec 16, 2011 at 11:19:22AM +, Anton Shterenlikht wrote:
> On Fri, Dec 16, 2011 at 11:37:20AM +0100, Marius Strobl wrote:
> > On Fri, Dec 16, 2011 at 08:40:48AM +, Anton Shterenlikht wrote:
> > > Updating from r216048 to r228561 on sparc64,
> > > with sys/conf/newvers.sh changed to R
On Dec 16, 2011, at 9:52 AM, Luigi Rizzo wrote:
> On Thu, Dec 15, 2011 at 04:21:51PM -0500, Andrew Boyer wrote:
>> These two changes allow you to set PXE as the default MBR boot selection,
>> which enables you to write a 'reboot to the network' script. We've found it
>> to be very useful. Wha
TB --- 2011-12-16 14:50:02 - tinderbox 2.8 running on freebsd-current.sentex.ca
TB --- 2011-12-16 14:50:02 - starting HEAD tinderbox run for mips/mips
TB --- 2011-12-16 14:50:02 - cleaning the object tree
TB --- 2011-12-16 14:50:12 - cvsupping the source tree
TB --- 2011-12-16 14:50:12 - /usr/bin/c
On Thu, Dec 15, 2011 at 04:21:51PM -0500, Andrew Boyer wrote:
> These two changes allow you to set PXE as the default MBR boot selection,
> which enables you to write a 'reboot to the network' script. We've found it
> to be very useful. What do people think?
seems good to me. John's comments a
On Thursday, December 15, 2011 4:21:51 pm Andrew Boyer wrote:
> These two changes allow you to set PXE as the default MBR boot selection,
which enables you to write a 'reboot to the network' script. We've found it
to be very useful. What do people think?
I think these are good. One suggestion
Am 16.12.2011 08:06, schrieb O. Hartmann:
> For the underlying OS, as far as I know, the compiler hasn't as much
> impact as on userland software since autovectorization and other neat
> things are not used during system build.
>
> From my experience using gcc 4.2 or 4.4/4.5 does not have an impac
Arnaud Lacombe schreef:
Hi,
On Thu, Dec 15, 2011 at 2:32 AM, O. Hartmann
wrote:
Just saw this shot benchmark on Phoronix dot com today:
http://www.phoronix.com/scan.php?page=news_item&px=MTAyNzA
it might be worth highlighting that despite Oracle Linux 6.1 Server is
using a kernel + compile
On Fri, Dec 16, 2011 at 11:37:20AM +0100, Marius Strobl wrote:
> On Fri, Dec 16, 2011 at 08:40:48AM +, Anton Shterenlikht wrote:
> > Updating from r216048 to r228561 on sparc64,
> > with sys/conf/newvers.sh changed to REVISION="9.9".
> >
> > Trinscribed by hand:
> >
> > FreeBSD 9.9-CURRENT #3
2011/12/16 Arnaud Lacombe :
> Hi,
>
> On Thu, Dec 15, 2011 at 2:32 AM, O. Hartmann
> wrote:
>> Just saw this shot benchmark on Phoronix dot com today:
>>
>> http://www.phoronix.com/scan.php?page=news_item&px=MTAyNzA
>>
> it might be worth highlighting that despite Oracle Linux 6.1 Server is
> usin
On Thu, Dec 15, 2011 at 9:58 PM, Mike Tancsa wrote:
> On 12/15/2011 11:56 AM, Attilio Rao wrote:
>> So, as very first thing, can you try the following:
>> - Same codebase, etc. etc.
>> - Make the test 4 times, discard the first and ministat for the other 3
>> - Reboot
>> - Change the steal_thresh
On Fri, Dec 16, 2011 at 08:40:48AM +, Anton Shterenlikht wrote:
> Updating from r216048 to r228561 on sparc64,
> with sys/conf/newvers.sh changed to REVISION="9.9".
>
> Trinscribed by hand:
>
> FreeBSD 9.9-CURRENT #3 r228561M:
>
> panic: kmem_suballoc: bad status return of 3
> KDB: enter: pa
On Fri, Dec 16, 2011 at 10:24:44AM +0100, Monthadar Al Jaberi wrote:
> Hi,
>
> do you get your panic at early in the boot stage?
yes, the panic is straight after
WARNING: WITNESS option enabled, expect reduced performance.
> I get the same message on arm when I set the DEBUG_MEMGUARD flag earl
on 13/12/2011 19:49 Andriy Gapon said the following:
> on 11/12/2011 23:45 Andriy Gapon said the following:
>>
>> There are a few cases when the kernel needs to interact with a user via
>> syscons.
>> This is the cases where the kernel not only spews some output but also
>> expects
>> some input.
Hi,
do you get your panic at early in the boot stage?
I get the same message on arm when I set the DEBUG_MEMGUARD flag early
on bootup:
Nov 24 201018:40:27
poweron_pll
EMI_CTRL 0x1C084040
FRAC 0x92926192
init_clock
init_ddr_mt46v32m16_133Mhz
exit self refresh timeout
power 0x00310710
Frac 0x9292
Updating from r216048 to r228561 on sparc64,
with sys/conf/newvers.sh changed to REVISION="9.9".
Trinscribed by hand:
FreeBSD 9.9-CURRENT #3 r228561M:
panic: kmem_suballoc: bad status return of 3
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at 0x02937e0: ta%xcc,1
db>
The keyboard froz
Am 16.12.2011 07:06, schrieb Alex Kuster:
> On 12/16/2011 02:41, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Thu, Dec 15, 2011 at 2:32 AM, O. Hartmann
>> wrote:
>>> Just saw this shot benchmark on Phoronix dot com today:
>>>
>>> http://www.phoronix.com/scan.php?page=news_item&px=MTAyNzA
>>>
>> it might
Den 15/12/2011 kl. 22.21 skrev Andrew Boyer:
> These two changes allow you to set PXE as the default MBR boot selection,
> which enables you to write a 'reboot to the network' script. We've found it
> to be very useful. What do people think?
I think this is very useful for e.g. re-installing
33 matches
Mail list logo
