___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Wed, Mar 21, 2018 at 7:59 AM, Warner Losh wrote:
> On Wed, Mar 21, 2018 at 7:32 AM, George Mitchell
> wrote:
>
> > On 03/21/18 04:51, Eitan Adler wrote:
> > > On 19 March 2018 at 22:59, Dewayne Geraghty
> > > wrote:
> > >> [...]
> > >> PS Normally I would bisect, but we're converting 2 large
On Wed, Mar 21, 2018 at 7:32 AM, George Mitchell
wrote:
> On 03/21/18 04:51, Eitan Adler wrote:
> > On 19 March 2018 at 22:59, Dewayne Geraghty
> > wrote:
> >> [...]
> >> PS Normally I would bisect, but we're converting 2 large PROLOG
> applications
> >> to erlang... (prayers welcome)
> > [...]
On 03/21/18 04:51, Eitan Adler wrote:
> On 19 March 2018 at 22:59, Dewayne Geraghty
> wrote:
>> [...]
>> PS Normally I would bisect, but we're converting 2 large PROLOG applications
>> to erlang... (prayers welcome)
> [...]
What next, converting a FORTH application to LISP? (Sorry, couldn't
resi
On 19 March 2018 at 22:59, Dewayne Geraghty
wrote:
> Hi Eitan,
> Agreed. Unfortunately all I have is that it abruptly shuts down. Both
> under load (10,8,?) - during a full package rebuild (~1200 ports); and
> during periods of idleness between 1am-2am. From our console.log there are
> approxi
On Tue, Mar 20, 2018 at 11:10:47AM -0700, Jeremy Chadwick wrote:
> (Please keep me CC'd as I am not subscribed to -stable)
>
> I haven't seen any issues, but that means very little. Details:
>
> Two boxes -- one bare metal, one VPS (QEMU):
>
> $ uname -a
> FreeBSD XXX 11.1-STABLE Fr
On Tue, 2018-03-20 at 10:50 +, Pete French wrote:
>
> On 20/03/2018 01:05, Dewayne Geraghty wrote:
> >
> > We rebuild 11.1-Stable at least every two weeks. Our build on the 7th
> > Feb is in use on our development boxes, however the rebuild on 22nd
> > resulted in frequent crashes and our re
(Please keep me CC'd as I am not subscribed to -stable)
I haven't seen any issues, but that means very little. Details:
Two boxes -- one bare metal, one VPS (QEMU):
$ uname -a
FreeBSD XXX 11.1-STABLE FreeBSD 11.1-STABLE #0 r330529: Tue Mar 6
11:36:04 PST 2018
root@XXX
On 20/03/2018 01:05, Dewayne Geraghty wrote:
We rebuild 11.1-Stable at least every two weeks. Our build on the 7th
Feb is in use on our development boxes, however the rebuild on 22nd
resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE
r329008. Is anyone actually running a St
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 19 March 2018 at 18:05, Dewayne Geraghty
wrote:
> We rebuild 11.1-Stable at least every two weeks. Our build on the 7th
> Feb is in use on our development boxes, however the rebuild on 22nd
> resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE
> r329008. Is anyone actually r
On Tue, Mar 20, 2018 at 12:05:33PM +1100, Dewayne Geraghty wrote:
> We rebuild 11.1-Stable at least every two weeks. Our build on the 7th
> Feb is in use on our development boxes, however the rebuild on 22nd
> resulted in frequent crashes and our reverting to FreeBSD 11.1-STABLE
> r329008. Is an
Quoting Boris Samorodov (from Thu, 17 Dec 2009 20:55:44 +0300):
Ivan Voras writes:
Alexander Leidinger wrote:
Hi,
please CC me on replies.
Seems you were not CCed...
I'm now subscribed to stable@, thanks for forwarding this.
I have a system which was at 7.1-pX. After the update to 7.2
Alexander Leidinger wrote:
Hi,
please CC me on replies.
I have a system which was at 7.1-pX. After the update to 7.2-p5 it
started to exhibit deadlocks after some minutes of uptime.
With 7.1 (generic kernel) it was running fine, with 7.2 generic the
problems started directly.
The system i
Miroslav Lachman wrote:
I have same problem on ASUS RS120 with Seagate ST3250820AS/3.AAC
drives (disk loses, system reboots, slow read/write speed), but I
think this is drive problem - all drives has high
Reallocated_Sector_Ct value in SMART (above 130 reallocated sectors
after few weeks, some
Mike Jakubik wrote:
Dominic Marks wrote:
Jerome Sobecki wrote:
Hi all,
We have here some Supermicro Superserver 5015P-TR
(http://www.supermicro.com/products/system/1U/5015/SYS-5015P-TR.cfm)
Those servers, with a ICH7 controler, are currently working with FreeBSD
6.1 and everything seems ok
Dominic Marks wrote:
Jerome Sobecki wrote:
Hi all,
We have here some Supermicro Superserver 5015P-TR
(http://www.supermicro.com/products/system/1U/5015/SYS-5015P-TR.cfm)
Those servers, with a ICH7 controler, are currently working with FreeBSD
6.1 and everything seems ok, except that it's the t
Jerome Sobecki wrote:
Hi all,
We have here some Supermicro Superserver 5015P-TR
(http://www.supermicro.com/products/system/1U/5015/SYS-5015P-TR.cfm)
Those servers, with a ICH7 controler, are currently working with FreeBSD
6.1 and everything seems ok, except that it's the third time, on two
diff
On Sun, Oct 02, 2005 at 07:54:25PM +0200, Jurij Kovacic wrote:
> The panic message is ussually somewhere along these lines:
> panic: kmem_malloc(4096) kmem map too small: 48496066400 total allocated
> cpuid =0
> boot() called on cpu#0
> ...
A similar problem is described in
http://lists.freebsd.o
On 10/2/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 02, 2005 at 07:54:25PM +0200, Jurij Kovacic wrote:
> > Hello!
> >
> > We are running FreeBSD 5.2.1-RELEASE-p14 with SMP kernell on one of our
> > servers and are experiencing stability problems; the server has the
> > tendency to re
On Sun, Oct 02, 2005 at 07:54:25PM +0200, Jurij Kovacic wrote:
> Hello!
>
> We are running FreeBSD 5.2.1-RELEASE-p14 with SMP kernell on one of our
> servers and are experiencing stability problems; the server has the
> tendency to reboot itself for no apparent reason at least once per month.
A
On Wed, Dec 04, 2002 at 10:06:11AM +, Tarquin McDowell wrote:
> On Wed, Dec 04, 2002 at 09:47:39AM +0100, Stijn Hoop wrote:
> > Anyone getting any better results? Is there something I can do to fix
> > this? The drivers are of no use to me if they are this unreliable.
> > More info available on
* Marko Cuk <[EMAIL PROTECTED]> [001108 01:52] wrote:
>
>
> Roman Shterenzon wrote:
>
> >
> > I've a perfectly good PR about vinum (panics) open. There's no even single
> > follow up (kern/22103).
> > I couldn't stand it any longer, so I'm not able to recreate it since I'm
> > using raid1 on th
Roman Shterenzon wrote:
>
> I've a perfectly good PR about vinum (panics) open. There's no even single
> follow up (kern/22103).
> I couldn't stand it any longer, so I'm not able to recreate it since I'm
> using raid1 on those disks now. I waited for almost one month but
> aparently nothing was
On Sat, 4 Nov 2000, Marko Cuk wrote:
> Hello !!
>
> Can anyone explain me, why is FreeBSD known as powerful sistem with
> industrial strenghth and rock stability, but I manage to crash it several
> times.
>
> The bridge code in 4.1x is unstable in conjuction with ipfw, I had several
> problems
On Sat, 4 Nov 2000, Bosko Milekic wrote:
> Hi Marko,
>
> On Sat, 4 Nov 2000, Marko Cuk wrote:
>
> > Hello !!
> >
> > Can anyone explain me, why is FreeBSD known as powerful sistem with
> > industrial strenghth and rock stability, but I manage to crash it several
> > times.
> >
> > The bridge
I think one simple solution is to 'hide' the -current distro, or make
it a little less accessible. That seems like a good first step. No
one who can't figure it out needs tobe running it anyway, and it
certainly won't hurt the development effort. Then, of course, keep
whipping 4.x into shape, t
On Fri, 31 Mar 2000, J McKitrick wrote:
> "STABLE" refers to the code base, NOT the stability of systems running
> it.
> Simple concept, deep meaning. Newbies should understand ...
And therein lies the problem. Newbies don't understand much of anything
about this (or any other) project. The app
Well, I had 3.3-RC on my box and now I have 3.3-RELEASE. I had no problems
at all except for one and that I tracked down to what I'll call user error.
I also have similar hardware as you do.
k6/2-300, 64mb ram, fic 503+ w/ VIA MVP4 chipset.
It may help to get a panic and possibly a crash dump t
29 matches
Mail list logo