Oliver
I try to use FreeBSD for day-to-day numerical
work, as far as possible. I have to complement
it with linux cluster systems, largely due to
a range of compilers available there.
Anyway, keep me posted if you get anywhere with this.
Anton
___
free
Hi,
On Feb 19, 2013, at 17:58, Adrian Chadd wrote:
> Try top -HS .. to try and break down the kernel threads.
ACPI is eating the cycles, according to top:
0 root 80 0K 496K - 2 1:13 27.88%
kernel{acpi_task_2}
0 root 80 0K 496K - 0 1:1
Davide Italiano writes:
> Unfortunately tinderbox didn't catch this bug because it's triggered
> only when gcc is used to build kernel.
In this particular case, the broken code is only built on platforms
which default to clang. Otherwise, it would have been caught when
building one of the platfo
I forwarded this thread to Christopher Bergstöm and got this reply:
>
> FreeBSD simply isn't a scientific computing platform - There isn't any market
> demand, it's not designed for it, many of the tools commonly used aren't
> available and the amount of work to change that is s
Well, I'm brave and switched several "beta switches" on my FreeBSD
10.0-CUR systems on and I realize, that I receive a lot of
make: "/usr/ports/Mk/bsd.port.mk" line 5137: warning: using previous
script for "-depends" defined here
make: "/usr/ports/Mk/bsd.port.mk" line 5140: warning: duplicate scri
From mexas Thu Feb 14 09:51:50 2013
To: freebsd-questi...@freebsd.org
Subject: daily otput: rejected mail hosts?
Reply-To: me...@bristol.ac.uk
I see in the daily output:
Checking for rejected mail hosts:
172 553 check_mail system.mail exist
Am 02/20/13 10:09, schrieb Anton Shterenlikht:
> Oliver
>
> I try to use FreeBSD for day-to-day numerical
> work, as far as possible. I have to complement
> it with linux cluster systems, largely due to
> a range of compilers available there.
>
> Anyway, keep me posted if you get anywhere with th
On Tue, Feb 19, 2013 at 08:52:49PM -0500, Rick Macklem wrote:
> >
> > I cannot find how to get information about maximum buffer size for
> > the getpwnam_r() function. This information should be returned by
> > sysconf(_SC_GETPW_R_SIZE_MAX), but since it does not work on FreeBSD
> > it is necessar
On Tue, Feb 19, 2013 at 7:51 PM, Konstantin Belousov
wrote:
> On Mon, Feb 18, 2013 at 11:18:16PM +0100, Svatopluk Kraus wrote:
>> On Mon, Feb 18, 2013 at 9:36 PM, Konstantin Belousov
>> wrote:
>> Well, I'm taking a part on porting FreeBSD to ARM11mpcore. UP case was
>> simple. SMP case is more co
On 20/02/2013 11:09, Anton Shterenlikht wrote:
> From mexas Thu Feb 14 09:51:50 2013
> To: freebsd-questi...@freebsd.org
> Subject: daily otput: rejected mail hosts?
> Reply-To: me...@bristol.ac.uk
>
> I see in the daily output:
>
> Checking for rejected mail hos
Compiling most recent sources of CURRENT with Revision: 247040 results
in a kernel crash with funny blinking characters on the screen. This
happens on all systems with different amd64 Intel CPU generations at
this very moment.
Last working sources (reverting and booting kernel.old) is in my case
On Tue, Feb 19, 2013 at 12:27:01AM -0800, Constantine A. Murenin wrote:
> Dear freebsd-{chat,current,doc}@,
>
> I would like to announce and introduce http://mdoc.su/>,
> a deterministic URL shortener for BSD manual pages,
> written entirely in nginx.conf.
>
> It supports several address scheme
At the moment, the most recent kernel of FreeBSD 10.0-CURRENT crashes on
all of the boxes I compiled the most recent kernel sources (build a
world ncluding kernel, not only the kernel, so the system is "consistent").
At the loader prompt, I need to unload the buggy kernel and load the old
working
On Wed, Feb 20, 2013 at 10:54 AM, Dag-Erling Smørgrav wrote:
> Davide Italiano writes:
>> Unfortunately tinderbox didn't catch this bug because it's triggered
>> only when gcc is used to build kernel.
>
> In this particular case, the broken code is only built on platforms
> which default to clang
On 16.02.2013 12:07, Joel Dahl wrote:
> On 14-02-2013 20:37, Joel Dahl wrote:
>> On 12-02-2013 8:51, Hans Petter Selasky wrote:
>>> On Monday 11 February 2013 23:21:05 Joel Dahl wrote:
On 10-02-2013 0:09, Joel Dahl wrote:
> On 09-02-2013 20:28, Alexander Motin wrote:
>> How long ago
On Wednesday, February 20, 2013 7:31:08 am Svatopluk Kraus wrote:
> On Tue, Feb 19, 2013 at 7:51 PM, Konstantin Belousov
> wrote:
> > On Mon, Feb 18, 2013 at 11:18:16PM +0100, Svatopluk Kraus wrote:
> >> On Mon, Feb 18, 2013 at 9:36 PM, Konstantin Belousov
> >> wrote:
> >> Well, I'm taking a part
Sounds like a perfect use case for Boot Environments. Create a new BE,
install the new kernel into it, set it as the default, reboot. If it
fails, you manually set the previous BE as the default, and reboot. That
way, your "known-good", working environment is never affected.
beadm should be par
O. Hartmann wrote on 20.02.2013 18:36:
Compiling most recent sources of CURRENT with Revision: 247040 results
in a kernel crash with funny blinking characters on the screen. This
happens on all systems with different amd64 Intel CPU generations at
this very moment.
Last working sources (revertin
Hi.
These checks are useless after the address length argument is converted
to socklen_t (up to SUSv2). Any objections?
Index: lib/libc/sys/accept.2
===
--- lib/libc/sys/accept.2 (revision 245745)
+++ lib/libc/sys/accept.2
On 02/20/13 18:17, Ruslan Makhmatkhanov wrote:
> O. Hartmann wrote on 20.02.2013 18:36:
>> Compiling most recent sources of CURRENT with Revision: 247040 results
>> in a kernel crash with funny blinking characters on the screen. This
>> happens on all systems with different amd64 Intel CPU generati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/20/13 09:19, Sergey Kandaurov wrote:
> Hi.
>
> These checks are useless after the address length argument is
> converted to socklen_t (up to SUSv2). Any objections?
No objection in general but there is a minor style issue, see below.
[...]
>
On Wed, Feb 20, 2013 at 10:22:29AM -0500, John Baldwin wrote:
> On Wednesday, February 20, 2013 7:31:08 am Svatopluk Kraus wrote:
> > On Tue, Feb 19, 2013 at 7:51 PM, Konstantin Belousov
> > wrote:
> > > On Mon, Feb 18, 2013 at 11:18:16PM +0100, Svatopluk Kraus wrote:
> > >> On Mon, Feb 18, 2013 a
On 20 February 2013 22:42, Xin Li wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 02/20/13 09:19, Sergey Kandaurov wrote:
>> Hi.
>>
>> These checks are useless after the address length argument is
>> converted to socklen_t (up to SUSv2). Any objections?
>
> No objection in genera
On Wednesday, February 20, 2013 2:27:39 pm Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 10:22:29AM -0500, John Baldwin wrote:
> > On Wednesday, February 20, 2013 7:31:08 am Svatopluk Kraus wrote:
> > > On Tue, Feb 19, 2013 at 7:51 PM, Konstantin Belousov
> > > wrote:
> > > > On Mon, Feb 18
On 20/02/2013 13:00, freebsd-current-requ...@freebsd.org wrote:
Gathering informations from many places - as it is with "WHICH
PROFESSIONAL COMPILER WORKS ON FREEBSD WITH PROFESSIONAL HIGH
PERFORMANCE MATH LIBS" is horrible and time consuming. try it on Google
with the tag "Linux" makes you happ
On Wed, 2013-02-20 at 14:32 -0500, John Baldwin wrote:
> On Wednesday, February 20, 2013 2:27:39 pm Konstantin Belousov wrote:
> > On Wed, Feb 20, 2013 at 10:22:29AM -0500, John Baldwin wrote:
> > > On Wednesday, February 20, 2013 7:31:08 am Svatopluk Kraus wrote:
> > > > On Tue, Feb 19, 2013 at 7:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
It seems that fresh -HEAD would give an unusable kernel that
overwrites screen buffer in a way making it impossible to debug.
Using an old world source to do 'make buildworld buildkernel' results
in a (mostly: I have some strange USB issue right
On Wed, Feb 20, 2013 at 02:14:38PM -0800, Xin Li wrote:
> It seems that fresh -HEAD would give an unusable kernel that
> overwrites screen buffer in a way making it impossible to debug.
> Using an old world source to do 'make buildworld buildkernel' results
> in a (mostly: I have some strange USB i
On 02/20/13 14:14, Xin Li wrote:
> Hi,
>
> It seems that fresh -HEAD would give an unusable kernel that
> overwrites screen buffer in a way making it impossible to debug.
> Using an old world source to do 'make buildworld buildkernel' results
> in a (mostly: I have some strange USB issue right now
On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
> On 02/20/13 14:14, Xin Li wrote:
> > Hi,
> >
> > It seems that fresh -HEAD would give an unusable kernel that
> > overwrites screen buffer in a way making it impossible to debug.
> > Using an old world source to do 'make buildworld
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/20/13 14:25, Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
>> On 02/20/13 14:14, Xin Li wrote:
>>> Hi,
>>>
>>> It seems that fresh -HEAD would give an unusable kernel that
>>> overwrites screen b
On 02/20/13 14:25, Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
>> On 02/20/13 14:14, Xin Li wrote:
>>> Hi,
>>>
>>> It seems that fresh -HEAD would give an unusable kernel that
>>> overwrites screen buffer in a way making it impossible to debug.
>>> U
On Wed, Feb 20, 2013 at 02:29:37PM -0800, Xin Li wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 02/20/13 14:25, Konstantin Belousov wrote:
> > On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
> >> On 02/20/13 14:14, Xin Li wrote:
> >>> Hi,
> >>>
> >>> It seems th
On Wed, Feb 20, 2013 at 02:33:23PM -0800, Navdeep Parhar wrote:
> On 02/20/13 14:25, Konstantin Belousov wrote:
> > On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
> >> On 02/20/13 14:14, Xin Li wrote:
> >>> Hi,
> >>>
> >>> It seems that fresh -HEAD would give an unusable kernel tha
On Wed, Feb 20, 2013 at 02:33:23PM -0800, Navdeep Parhar wrote:
> On 02/20/13 14:25, Konstantin Belousov wrote:
> > On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
> >> On 02/20/13 14:14, Xin Li wrote:
> >>> Hi,
> >>>
> >>> It seems that fresh -HEAD would give an unusable kernel tha
On Wed, Feb 20, 2013 at 02:29:37PM -0800, Xin Li wrote:
>
> It would take some time to bi-sect as one needs to do full
> world/kernel build. The only thing I can say definitely is that
> something from userland was broken within the (246858,247057] range.
> I'm compiling 246957 right now.
>
I ha
On Wed, Feb 20, 2013 at 02:48:53PM -0800, Steve Kargl wrote:
> On Wed, Feb 20, 2013 at 02:29:37PM -0800, Xin Li wrote:
> >
> > It would take some time to bi-sect as one needs to do full
> > world/kernel build. The only thing I can say definitely is that
> > something from userland was broken withi
On 02/20/13 14:47, Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 02:33:23PM -0800, Navdeep Parhar wrote:
>> On 02/20/13 14:25, Konstantin Belousov wrote:
>>> On Wed, Feb 20, 2013 at 02:21:50PM -0800, Navdeep Parhar wrote:
On 02/20/13 14:14, Xin Li wrote:
> Hi,
>
> It seems t
On Thu, Feb 21, 2013 at 12:51:54AM +0200, Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 02:48:53PM -0800, Steve Kargl wrote:
> > On Wed, Feb 20, 2013 at 02:29:37PM -0800, Xin Li wrote:
> > >
> > > It would take some time to bi-sect as one needs to do full
> > > world/kernel build. The only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/20/13 14:37, Konstantin Belousov wrote:
> On Wed, Feb 20, 2013 at 02:29:37PM -0800, Xin Li wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>
>> On 02/20/13 14:25, Konstantin Belousov wrote:
>>> On Wed, Feb 20, 2013 at 02:21:50PM -08
Andrey Simonnenko wrote:
> On Tue, Feb 19, 2013 at 08:52:49PM -0500, Rick Macklem wrote:
> > >
> > > I cannot find how to get information about maximum buffer size for
> > > the getpwnam_r() function. This information should be returned by
> > > sysconf(_SC_GETPW_R_SIZE_MAX), but since it does not
I've been talking to others and it seems that several of us are convinced
that BSD is back on the uptake, so I wouldn't be so quick to mark its
demise. :-)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
Hi,
I have the same issues with FreeBSD 10.0-CURRENT #0 r247035. I completed the
buildworld process and was able to install kernel. When I rebooted and
attmpted to installworld, I got the same surprise that everyone got. I was
able to get in the system using SAFE MODE.
FreeBSD 10.0-CURRE
TB --- 2013-02-21 04:10:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-02-21 04:10: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 --- 2013
I was testing a patch on r246300 or so, and wanted to see if it would apply
cleanly to a newer copy of HEAD.
Well it did, except I had a hang at boot, shortly after ZFS version and the
last scsi devices appear.
This easily could have been related to the patch I was testing, so I wiped
/usr/src/ an
TB --- 2013-02-21 04:10:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-02-21 04:10: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 --- 2013
TB --- 2013-02-21 04:10:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-02-21 04:10: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 --- 2013
47 matches
Mail list logo
