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
different machines, that the
At 08:09 PM 5/21/2006, Kris Kennaway wrote:
We did ourselves a big disservice by not pointing out clearly in the
todo list that most of the listed problems are VERY RARE and are
unlikely to affect most/all users. In future we're going to have to
be clearer about that, because you're not the onl
On Mon, May 22, 2006 at 10:03:33AM +1200, Andrew Thompson wrote:
> On Sun, May 21, 2006 at 01:20:24PM -0600, Brett Glass wrote:
> > Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last
> > month), it
> > shouldn't be a problem to do a 4.12 release as a "last gasp" to tide us
> >
On Thu, 2006-04-06 at 16:53 +0200, Stefan Ehmann wrote:
> I recently acquired a CanoScan LiDE 60.
>
> It basically works but it is very unstable: It often stops during the
> scan and sane returns an error, or it just hangs during the scan (making
> ugly noises). The only remedy is to re-plug the u
I recently acquired a CanoScan LiDE 60.
It basically works but it is very unstable: It often stops during the
scan and sane returns an error, or it just hangs during the scan (making
ugly noises). The only remedy is to re-plug the usb cable. (which
sometimes causes a panic)
I tried on my notebook
Jeff Roberson merged a large number of VFS stability improvements to the
RELENG_6 tree this morning. These are intended to appear in the next beta,
and in stability tests run by Kris and others, they appear to help a lot.
However, change comes with risk, and as such, this message is to let
On Fri, 28 Oct 2005, Carl Makin wrote:
I've been having a heap of trouble with the primary network interface on
a box that was running 5.4 and recently upgraded to 6.0-Beta5 where the
interface would just go dead. Nothing in ifconfig or syslog or dmesg
would indicate a problem, but nothing wo
Carl Makin wrote:
> John Pettitt wrote:
>
>> Carl Makin wrote:
>>
>>
>>
>>> Morning All,
>>>
>>> the interface would just go dead. Nothing in ifconfig or syslog or
>>> dmesg would indicate a problem, but nothing would go in or out. The
>>> only way to fix it was reboot.
>>>
>>
>> What sort
John Pettitt wrote:
Carl Makin wrote:
Morning All,
the interface would just go dead. Nothing in ifconfig or syslog or
dmesg would indicate a problem, but nothing would go in or out. The
only way to fix it was reboot.
What sort of network card? I've been having the same syptoms with
Carl Makin wrote:
> Morning All,
>
> I've been having a heap of trouble with the primary network interface
> on a box that was running 5.4 and recently upgraded to 6.0-Beta5 where
> the interface would just go dead. Nothing in ifconfig or syslog or
> dmesg would indicate a problem, but nothing
On Fri, Oct 28, 2005 at 09:55:21AM +1000, Carl Makin wrote:
> Morning All,
>
> I've been having a heap of trouble with the primary network interface on
> a box that was running 5.4 and recently upgraded to 6.0-Beta5 where the
> interface would just go dead. Nothing in ifconfig or syslog or dmes
Morning All,
I've been having a heap of trouble with the primary network interface on
a box that was running 5.4 and recently upgraded to 6.0-Beta5 where the
interface would just go dead. Nothing in ifconfig or syslog or dmesg
would indicate a problem, but nothing would go in or out. The only
On Sat, Oct 22, 2005 at 07:24:35PM -0700, Brandon Fosdick wrote:
> Dick Hoogendijk wrote:
> >>Oops, it seems this feature is in 7-CURRENT only. If the appropiate
> >>person is reading this, why isnt something like that available in 6? I
> >>think it would be a very useful feature.
> >
> >
> > Wh
Dick Hoogendijk wrote:
>>Oops, it seems this feature is in 7-CURRENT only. If the appropiate
>>person is reading this, why isnt something like that available in 6? I
>>think it would be a very useful feature.
>
>
> What a shame. You made me glad for a very short time. This seemed to be
> the opt
On Sat, Oct 22, 2005 at 03:41:33PM +0200, dick hoogendijk wrote:
> On Fri, 21 Oct 2005 15:30:52 -0400
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> > > But he old libraries are still on the system than, aren't they?
> > > Or will they not be used and if not, why?
> >
> > Use libchk and pkg_which
On 22 Oct Mike Jakubik wrote:
> On Sat, October 22, 2005 12:25 pm, Mike Jakubik wrote:
>
> > You can run make check-old in /usr/src.
> >
> Oops, it seems this feature is in 7-CURRENT only. If the appropiate
> person is reading this, why isnt something like that available in 6? I
> think it would
On Sat, October 22, 2005 12:25 pm, Mike Jakubik wrote:
> You can run make check-old in /usr/src.
>
>
> # check-old - Print a list of old files/directories in the
> system. # delete-old - Delete obsolete files and directories
> interactively. # delete-old-libs - Delete obsole
On Sat, October 22, 2005 9:41 am, dick hoogendijk wrote:
> On Fri, 21 Oct 2005 15:30:52 -0400
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
>
>>> But he old libraries are still on the system than, aren't they?
>>> Or will they not be used and if not, why?
>>>
>>
>> Use libchk and pkg_which..see thei
On Fri, 21 Oct 2005 15:30:52 -0400
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > But he old libraries are still on the system than, aren't they?
> > Or will they not be used and if not, why?
>
> Use libchk and pkg_which..see their manpages.
After looking into the manual(s) this seems to be a "dan
On Fri, Oct 21, 2005 at 08:21:27PM +0200, dick hoogendijk wrote:
> On Wed, 19 Oct 2005 18:53:51 -0400
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote:
> > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications.
> > > If you
On Wed, 19 Oct 2005 18:53:51 -0400
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote:
> > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications.
> > If you have them it's ok. If you recompile everything you don't
> > need the COMPAT
On Oct 20, 2005, at 4:16 PM, Michael Nottebrock wrote:
On Thursday, 20. October 2005 21:20, Vivek Khera wrote:
personally, I don't see the point of doing that. just let your ports
naturally get replaced as they are upgraded due to version bumps and
such.
That is dangerous, see other repli
On Thu, Oct 20, 2005 at 03:20:52PM -0400, Vivek Khera wrote:
>
> On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote:
>
> >Wat is the best way to get the cleanest FreeBSD-6.x system without
> >installing from scratch? Recompile each port? Or use the
> >COMPAT_FREEBSD5 layer?
> >
> >
>
> this is a
On Thursday, 20. October 2005 21:20, Vivek Khera wrote:
> personally, I don't see the point of doing that. just let your ports
> naturally get replaced as they are upgraded due to version bumps and
> such.
That is dangerous, see other replies in this thread for the reasons why.
--
,_, | Mi
On Oct 19, 2005, at 5:10 PM, dick hoogendijk wrote:
Wat is the best way to get the cleanest FreeBSD-6.x system without
installing from scratch? Recompile each port? Or use the
COMPAT_FREEBSD5 layer?
this is a different question than you asked before... the
COMPAT_FREEBSD5 will allow your
On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote:
> On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote:
>
> >On Mon, 17 Oct 2005 15:52:00 -0400
> >Vivek Khera <[EMAIL PROTECTED]> wrote:
> >
> >>On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
> >
> >>> The
On Wed, 19 Oct 2005 23:10:46 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote:
On Mon, 17 Oct 2005 15:52:00 -0400
Vivek Khera <[EMAIL PROTECTED]> wrote:
On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
> The *ONLY* question is: will I need to *recompile* all installed
> ports if I go fro
On Mon, 17 Oct 2005 15:52:00 -0400
Vivek Khera <[EMAIL PROTECTED]> wrote:
> On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
> > The *ONLY* question is: will I need to *recompile* all installed
> > ports if I go from 5.4 to 6.0 release?
>
> No, the kernel has COMPAT_FREEBSD5 and COMPAT_FREEB
On Tue, October 18, 2005 10:30 pm, Joel Rees wrote:
>
>>> How come the kernel is reporting that an AMD chip has HTT? Is this
>>> a bug?
>>>
>>
>> No, this is how dual core is reported.
>>
>
> Huh?
>
>
> Don't scare me like that, Mike.
I guess i got a little confused here. Before multicore detectio
On 平成 17/10/18, at 13:05, Mike Jakubik wrote:
On Mon, October 17, 2005 11:56 pm, Brett Glass wrote:
Features=0x178bfbff,PG
E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x1
AMD Features=0xe2500800
AMD Features2=0x3
Multicore: 2 physical cores
How come the kernel is reporti
On 平成 17/10/18, at 17:21, Pertti Kosunen wrote:
Brett Glass wrote:
How come the kernel is reporting that an AMD chip has HTT? Is this
a bug?
It is the AMD HyperTransport™ Technology, not Hyper Threading as
Intels have.
http://www.amd.com/us-en/Processors/DevelopWithAMD/
0,,30_2252_2
On Mon, Oct 17, 2005 at 07:56:34PM -0600, Brett Glass wrote:
> At 06:38 PM 10/17/2005, Mike Tancsa wrote:
>
> >Two of our scanners in the cluster are SMP boxes-- dual core AMD running in
> >386 mode and an Intel D830.
> >Both work really well, and take quite a load against them network / cpu
>
At 11:56 PM 17/10/2005, Brett Glass wrote:
At 08:13 PM 10/17/2005, Mike Tancsa wrote:
One thing we're looking at doing is deploying some single-core AMD64s.
Some of the motherboards use the NVidia NForce chipsets, so we
need to know if the nve driver works
I have seen lots of problem reports
Brett Glass wrote:
How come the kernel is reporting that an AMD chip has HTT? Is this a bug?
It is the AMD HyperTransport™ Technology, not Hyper Threading as Intels
have.
http://www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_2252_2353,00.html
__
On Mon, October 17, 2005 11:56 pm, Brett Glass wrote:
>> Features=0x178bfbff> E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
>> Features2=0x1
>> AMD Features=0xe2500800
>> AMD Features2=0x3
>> Multicore: 2 physical cores
>>
>
> How come the kernel is reporting that an AMD chip has HTT? Is this
At 08:13 PM 10/17/2005, Mike Tancsa wrote:
One thing we're looking at doing is deploying some single-core AMD64s.
Some of the motherboards use the NVidia NForce chipsets, so we
need to know if the nve driver works
I have seen lots of problem reports with the nve. A board that
works well for
At 09:56 PM 17/10/2005, Brett Glass wrote:
At 06:38 PM 10/17/2005, Mike Tancsa wrote:
>Two of our scanners in the cluster are SMP boxes-- dual core AMD
running in 386 mode and an Intel D830.
>Both work really well, and take quite a load against them network
/ cpu wise. Lots of threads running
ia) or if it pays to install PCI NICs for
speed and stability.
--Brett Glass
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
At 07:46 PM 15/10/2005, Brett Glass wrote:
The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a
projected date for the finished product. How close is it?
My guess, very soon. But for me, RELENG_6 has been small 's' stable
for some time. Got with 6.0R when it comes
On Oct 16, 2005, at 7:57 AM, dick hoogendijk wrote:
The news I read about fFreeBSD-6.0 is quit good lately. I might even
upgrade my 5.4 box. I'm told it will be a rather smooth proces.
so far, I've upgraded from 5.4-RELEASE: a Dell PE1300 (pentium 3
750MHz) SCSI disks, a generic AMD Duron
s, and
> putting some workload and various testing on them. So far
> I have not encountered any serious problems that were not
> resolved. So, stability seems to be very good; my feeling
> is that 6.0 will be a _lot_ better than 5.0. A _lot_.
Don't let the .0 confuse you. 6.0 is nothing *AT ALL* like 5.0 in
terms of development history and quality.
Kris
pgpdURrvqgkqj.pgp
Description: PGP signature
FWIW, I'm running RELENG_6 on two machines (a notebook and
a server) for several weeks, updating every few days, and
putting some workload and various testing on them. So far
I have not encountered any serious problems that were not
resolved. So, stability seems to be very good; my fee
On Sunday, 16. October 2005 18:34, Ronald Klop wrote:
> There are a couple of options:
> 1. Do not remove old (5.4) libraries. All 5.4 libs wil still be found.
> 2. Remove old libraries and install ports/misc/compat5x. All 5.4 lib wil
> still be found.
> 3. Remove old libraries and use /etc/libmap
On Sun, 16 Oct 2005 13:57:52 +0200, dick hoogendijk <[EMAIL PROTECTED]> wrote:
On Sat, 15 Oct 2005 23:03:53 -0400
"Joshua Coombs" <[EMAIL PROTECTED]> wrote:
For what it's worth, on UP, my 386 (stop laughing) is showing twice
the inbound and outbound tcp throughput across multiple apps compared
On Sun, 16 Oct 2005, dick hoogendijk wrote:
On Sat, 15 Oct 2005 23:03:53 -0400
"Joshua Coombs" <[EMAIL PROTECTED]> wrote:
For what it's worth, on UP, my 386 (stop laughing) is showing twice
the inbound and outbound tcp throughput across multiple apps compared
to 4.11. Disk throughput is sligh
On Sat, 15 Oct 2005 23:03:53 -0400
"Joshua Coombs" <[EMAIL PROTECTED]> wrote:
> For what it's worth, on UP, my 386 (stop laughing) is showing twice
> the inbound and outbound tcp throughput across multiple apps compared
> to 4.11. Disk throughput is slightly higher, but nothing super
> impres
Brett Glass wrote:
At 06:34 PM 10/15/2005, David Syphers wrote:
http://www.freebsd.org/releases/6.0R/todo.html
Linked to from the schedule page...
Been there. Want to get folks' opinions, and also more detail
than is likely to appear on th epage.
Good to see alot of it just need
"Brett Glass" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
The release schedule for FreeBSD 6.0, on the FreeBSD Web site,
doesn't show a
projected date for the finished product. How close is it? We are
(believe it
or not) still running and building production servers with 4.11,
At 06:34 PM 10/15/2005, David Syphers wrote:
>http://www.freebsd.org/releases/6.0R/todo.html
>
>Linked to from the schedule page...
Been there. Want to get folks' opinions, and also more detail
than is likely to appear on th epage.
--Brett
___
freebsd
On Saturday 15 October 2005 04:46 pm, Brett Glass wrote:
> With what known problems
> is 6.0 likely to ship, and of these which are likely to impact uniprocessor
> systems? Are any "showstopper" bugs merely being worked around for release?
http://www.freebsd.org/releases/6.0R/todo.html
Linked to
The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a
projected date for the finished product. How close is it? We are (believe it
or not) still running and building production servers with 4.11, and would
love to move to 6.0 (at least for uniprocessor systems; we may wait
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; t
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
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.
Dmesg:
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979
ven underclock it to keep it cooler
- build your own system. Either go the low power route (mini-ITX) so
you don't need noisy fans or use an over-rated PSU and CPU heatsink
to keep fan speed (and noise) down. In either case, you'll need to
look around to find a quiet HDD.
So, what&
rnels. The stack trace was
very similar; the fault address (0x24) and the top three stack frames
were the same as without Giant:
propagate_priority
turnstile_wait
_mtx_lock_sleep
At this point I no longer have access to the hardware, the customer
wanted his servers bac
was
very similar; the fault address (0x24) and the top three stack frames were
the same as without Giant:
propagate_priority
turnstile_wait
_mtx_lock_sleep
At this point I no longer have access to the hardware, the customer wanted
his servers back. They're going int
David Sze wrote:
At 11:31 PM 10/04/2005 -0600, Scott Long wrote this to All:
Making a driver PAE-ified means either teaching it to do 64-bit
scatter-gather (assuming that the peripheral hardware can do this
and that it's documented), or teaching the driver to correctly handle
EINPROGRESS from bus_d
: David Sze [mailto:[EMAIL PROTECTED]
Sent: 11 April 2005 06:12
To: Scott Long
Cc: Anthony Downer; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [PATCH] Stability fixes for IPS driver for 4.x
At 09:17 AM 09/04/2005 -0600, Scott Long wrote this to All:
>All,
>
>Thanks to the keen eye of
At 11:31 PM 10/04/2005 -0600, Scott Long wrote this to All:
Making a driver PAE-ified means either teaching it to do 64-bit
scatter-gather (assuming that the peripheral hardware can do this
and that it's documented), or teaching the driver to correctly handle
EINPROGRESS from bus_dmamap_load() alon
e iobuf must be put back on the bufq.
Yes, I forgot that synchronization is a bit different here than in
5.x/6.0. Your second patch with the MfC is exactly what I had in
mind for the ips_start_io_request() function.
Two patches are attached to this message:
1. ips.RELENG_4.stability.patch is jus
ack on the bufq.
Two patches are attached to this message:
1. ips.RELENG_4.stability.patch is just the stability patch as described.
2. ips.RELENG_4.mfc-and-stability.patch is an MFC of your IPS cleanup and
optimization that you committed to HEAD on 01/28/05, plus the stability
patch as d
All,
Thanks to the keen eye of David Sze, the cause of the instability in the
ips driver in FreeBSD 4.x might have been found. If it's affecting you,
please try the attached patch and let me know the results. I'll commit
it when everyone is happy with it.
Thanks,
Scott
Index: ips_commands.c
==
# [EMAIL PROTECTED] / 2004-04-14 20:29:45 -0700:
> Finally! No serial console but it is crashing right now (with the
> updated BIOS installed) and I see it is dumping to the dumpdev and the
> screen is filling up with stuff :)
cool! (if FreeBSD crashing can be cool :)
--
FreeBSD 4.9-RELEA
On Wed, Apr 14, 2004 at 08:29:45PM -0700, Rick Updegrove wrote:
> Sorry to post all over the place here without waiting for replies on the
> others first but as soon as I get the "boot -v" mystery solved and
> figure out what else I should send.
/boot/loader.conf:
#
boot_verbose="YES" # Ca
On Wed, Apr 14, 2004 at 07:45:09PM -0700, Rick Updegrove wrote:
> Ok BIOS is updated.
> Sorry for the attachments, but the lines would wrap badly.
>
>
> Kris Kennaway wrote:
> >Run mptable.
>
> See mptable.txt
>
> >Look in /modules for stale files, and check kldstat to see what you're
> >runnin
Kris Kennaway wrote:
Are you sure that nothing is displayed on the system console before it
reboots? Hooking up a serial console can be a good way to catch this.
Finally! No serial console but it is crashing right now (with the
updated BIOS installed) and I see it is dumping to the dumpdev and
Rick Updegrove wrote:
See modules.txt
Oops that one was unreadable.. please see this one.
Also, here are the relevant portions of dmesg for my next question.
amr0: mem 0xf000-0xf7ff irq 16 at device 7.1
on pci0
amr0: Firmware D.02.05, BIOS B.01.04, 16MB RAM
amrd0: on amr0
amrd0: 3470
Ok BIOS is updated.
Sorry for the attachments, but the lines would wrap badly.
Kris Kennaway wrote:
Run mptable.
See mptable.txt
Look in /modules for stale files, and check kldstat to see what you're
running.
See modules.txt
How do I know if they are stale?
[EMAIL PROTECTED] /modules # kldstat
I
On Wed, Apr 14, 2004 at 06:19:39PM -0700, Rick Updegrove wrote:
> I will do this just as soon as I sent this reply, which has more
> questions I need answered. Besides, I need to run the new BIOS with the
> 4.10-BETA kernel until it crashes to eliminate the BIOS as a suspect right?
Yes.
>
> >*
On Fri, 2003-01-03 at 15:43, Thomas Seck wrote:
> * Nimrod Mesika ([EMAIL PROTECTED]):
>
> [Uptime]
>
> > Think about compute servers. Our CAD servers can run simulations and
> > other types of processes for ~40 hours. You definitely don't want to
> > interrupt a running system and it finding som
On Fri, 3 Jan 2003, Dimitry Andric wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2003-01-03 at 02:29:49 Chris Doherty wrote:
>
> >> Additionally HP-UX, Linux, Solaris and recent releases of FreeBSD cycle
> >> back to zero after 497 days
>
> > wacky. how/why is this the case?
>
>
> I haven't seen FBSD 4.7 system with uptime > 1000 days, for quite
> obvious reasons.. Should I recommend everyone to install FBSD 2.2.8
> since it has good uptime records? :)
Sorry to step into the middle of a thread here, but to me it says that
FreeBSD has had, and likely continues to have, a
On Fri, 2003-01-03 at 02:17, Mark wrote:
>
> What is it that makes people rave about the longest uptime? To me, this is
> just a list of sites whose admins have neglected to perform the necessary
> upgrade-maintenances, seemingly for almost three years even. To me, this is
> just a list of potenti
- Original Message -
From: "Marcus Reid" <[EMAIL PROTECTED]>
To: "Mike Hogsett" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 1:02 AM
Subject: Re: FreeBSD Stability
> I lik
On Fri, 3 Jan 2003 10:05:05 -0800 (PST) Philip Hallstrom <[EMAIL PROTECTED]>
wrote:
> 26 www.cravath.com 102 ok892 939 940 Solaris 8
> Apache/1.3.27 (Unix) PHP/4.2.3
>
> That's certainly more than 492 days... so even if they do reboot,
> netcraft is ignoring it or accomodating it s
> On Thu, Jan 02, 2003 at 06:09:11PM -0600, Dave Uhring said:
> > You do realize, I hope, that Linux and Solaris roll over their uptimes
> > at something like 492 days.
>
> from http://uptime.netcraft.com/up/accuracy.html#whichos
> --
> Additionally HP-UX, Linux, Solaris and recent releases of Free
> That is impressive. I'm curious if they stayed at a particular version or
> if they update as new versions are available? I thought I read somewhere
> that FreeBSD could load a new kernel without rebooting?
I am interested in this, and I must admit that I dont really know that
much about the k
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 h
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 s
Sorry, forgot the dmesg-output in my previous posting.
Here it is.
--
Morten A. Middelthon
Freenix Norge
http://www.freenix.no/
Jun 26 12:32:06 atreides /kernel: Copyright (c) 1992-2000 The FreeBSD Project.
Jun 26 12:32:06 atreides /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jun 26 1
Recently I've experienced stability problems with one of my 4.0-STABLE
boxes. When it freezes/locks up I can still ping it, and I can change
between virtual consoles, but everything else is dead. Ctrl-alt-del
doesn't work, or any other input on the console, except for print-screen.
A
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
Hi,
On Tue, 28 Sep 1999, Jordan K. Hubbard wrote:
> I'd suggest trying a 3.3-stable snapshot, just as soon as I can
> get those rolling off of releng3.freebsd.org again. If it still
> occurs, we're now at least debugging the latest and greatest.
Isn't -STABLE tracking OK ?
Unfortunately I do
And - to add to this - I still can freeze up my pentium
laptop rather quickly (3.2-RELEASE, 40meg memory, P90) running
setiathome.
And - I've got DDB in the kernel, and ensured it's not overheating
(it will freeze up in less than a minute from a _very_ cold start.)
I don't get a panic, ddb promp
om: Donald Burr [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, September 24, 1999 7:06 AM
> To: FreeBSD Questions
> Cc: [EMAIL PROTECTED]
> Subject: Stability problems in 3.3-R?
>
> I just installed FreeBSD 3.3 on my machine (AMD K6-2/350, EPoX
> EP-MVP4A motherboard [VIA MV
Hi,
On Sat, 25 Sep 1999, Chris Costello wrote:
> On Sat, Sep 25, 1999, Adrian Penisoara wrote:
> > PS: I could have filed a PR but I can't figure any way of reproducing
> > this -- just a double panic caught by my co-worker, details posted on
> > -stable on 19th Sep with "3.2-STABLE hang
Hi,
On Sat, 25 Sep 1999, The Hermit Hacker wrote:
>
> Just to confirm...I've had similar problems, but *only* after moving to
> INN-CURRENT, which makes *very* heavy use of MMAP() :(
>
> What version of INN are you running?
I'm not running any kind of INN -- but lately I have been playing w
his machine had NO problems before upgrading to
> 3.2/3.3 and had respectable uptimes (now I can't get over 3 days of
> uptime).
>
> This is not intended to subminate FreeBSD's image but rather to launch a
> "HEADS UP" warning in respect of -stable branch stabil
On Sat, Sep 25, 1999, Adrian Penisoara wrote:
> PS: I could have filed a PR but I can't figure any way of reproducing
> this -- just a double panic caught by my co-worker, details posted on
> -stable on 19th Sep with "3.2-STABLE hangs after several hours" in
> the subject...
When i
d NO problems before upgrading to
3.2/3.3 and had respectable uptimes (now I can't get over 3 days of
uptime).
This is not intended to subminate FreeBSD's image but rather to launch a
"HEADS UP" warning in respect of -stable branch stability in this period
of time. I'm wil
ve been
reading some messages in freebsd-stable and there seem to be other people
having stability problems with their boxen under 3.3, whereas the same
hardware works perfectly under 3.2. So I'm wondering if there any
known stability issues with 3.3-RC, and will a cvsup and upgrade
to 3.3-STAB
101 - 197 of 197 matches
Mail list logo
