Hi I read the pdf detailing new changes in 5.3 networking and noticed
a new sysctl variable is added 'net.inet.ip.process_options'
Here is the description.
IP Options do not have any practical use today. The only useful
application is RR
(Record Route) where it remembers the last 8 hops the
Hi
I Installed a fresh apache-moddssl port
(using portinstall www/apache13-modssl)
When i start apache using apachectl start everything works just fine,
but when i try apachectl startssl i have some errors i have no idea
what to do with
httpd-error log gives me :
[Fri Apr 1 11:40:24 2005]
As per subject, I need to do this urgently, but with minimum downtime.
Will it be ok just to cvsup, rebuild kernel and world, mergemaster,
(etc) like any normal update? Or do I have to do a reinstall? Any help
appreciated.
Regards,
Philip Brennan
___
My 5.x machines are regularly reporting that the kernel is flipping
between FLL and PLL mode (as shown by STA_MODE in syslog messages).
This isn't occuring on my 4.x machines (they typically report 2040
then 2041 and stay indefinitely in that mode).
Any suggestions as to why this is happening?
Hello
When I try to use rfcomm_sppd -a Mts-freeze -t /dev/ttyp6, I receive
an error: Could not connect socket. Connection refused.
What that mean?
FreeBSD Release 5.3
___
freebsd-stable@freebsd.org mailing list
* Phil Brennan [EMAIL PROTECTED] [20050401 12:19]:
Will it be ok just to cvsup, rebuild kernel and world, mergemaster,
(etc) like any normal update? Or do I have to do a reinstall?
Read UPDATING (all of it).
Read UPDATING (all of it).
Did you notice the 20041001 entry? You should be able
On Fri, Apr 01, 2005 at 11:20:09AM +0100, Phil Brennan wrote:
As per subject, I need to do this urgently, but with minimum downtime.
Will it be ok just to cvsup, rebuild kernel and world, mergemaster,
(etc) like any normal update? Or do I have to do a reinstall? Any help
appreciated.
There
Hi folks,
I have a XS-Drive Pro VP300 (Vosonic) here which runs fine as USB1
device, but completely screws up my system when pluggeg into a USB2 port.
I'm running
(%:~)- uname -a
FreeBSD arc.pmp.uni-hannover.de 5.3-STABLE FreeBSD 5.3-STABLE #2: Thu Dec
9 12:00:08 CET 2004
[EMAIL
On Apr 1, 2005, at 05:45, Peter Jeremy wrote:
Any suggestions as to why this is happening? (And how I can stop
it regularly flipping)
I don't think this is really an issue. It may be annoying to see it in
the logs, but NTPv4 uses each algorithm when it's appropriate to get
the most accurate
At 07:39 AM 01/04/2005, Gerrit Kühn wrote:
Hi folks,
I have a XS-Drive Pro VP300 (Vosonic) here which runs fine as USB1
device, but completely screws up my system when pluggeg into a USB2 port.
I'm running
(%:~)- uname -a
FreeBSD arc.pmp.uni-hannover.de 5.3-STABLE FreeBSD 5.3-STABLE #2: Thu Dec
9
On Fri, 01 Apr 2005 08:05:47 -0500 Mike Tancsa [EMAIL PROTECTED] wrote
about Re: USB device causes kernel panic:
MT (%:~)- uname -a
MT FreeBSD arc.pmp.uni-hannover.de 5.3-STABLE FreeBSD 5.3-STABLE #2: Thu
MT Dec 9 12:00:08 CET 2004
MT Try updating to the latest RELENG_5. There have been a lot
Hi,
At 14:04 01/04/2005, David Magda wrote:
On Apr 1, 2005, at 05:45, Peter Jeremy wrote:
Any suggestions as to why this is happening? (And how I can stop
it regularly flipping)
I don't think this is really an issue. [etc]
I think this is an issue:
- As stated, machines running 4.x don't seem to
On Apr 1, 2005 12:49 PM, Joan Picanyol i Puig
[EMAIL PROTECTED] wrote:
* Phil Brennan [EMAIL PROTECTED] [20050401 12:19]:
Will it be ok just to cvsup, rebuild kernel and world, mergemaster,
(etc) like any normal update? Or do I have to do a reinstall?
Read UPDATING (all of it).
Read
On Thu, Mar 31, 2005 at 06:32:27PM -0800, Dave Knight wrote:
That document also says:
As is detailed in the operational information below, snapshots are
definitely alpha-test code and are NOT yet ready for production use.
Is this the current opinion of snapshots ?
Not really, you just have
Hello everybody,
I had 5.3 STABLE. Did cvsup as I always do with
*default tag=RELENG_5
That should leave the server in STABLE, should not it? Here is the problem.
#cvsup -g /etc/cvsupfile
#make buildworld
#make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=INET
#make -DALWAYS_CHECK_MAKE
Hello everybody,
I had 5.3 STABLE. Did cvsup as I always do with
*default tag=RELENG_5
That should leave the server in STABLE, should not it? Here is the problem.
#cvsup -g /etc/cvsupfile
#make buildworld
#make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=INET
#make
On Fr, 1.04.2005, 16:59, Irina sagte:
Hello everybody,
Hi there,
I had 5.3 STABLE. Did cvsup as I always do with
*default tag=RELENG_5
After rebooting and telneting to the server I saw
FreeBSD 5.4-PRERELEASE (INET) #4: Thu Mar 31 20:41:59 EST 2005
Where is it coming from? Does
From: Uwe Doering [mailto:[EMAIL PROTECTED]
...
As far as I understand this family of controllers the OS
drivers aren't involved at all in case of a disk drive
failure. It's strictly the controller's business to deal
with it internally. The OS just sits there and waits until
the
on 01.04.2005 16:24 Bob Bishop said the following:
I think this is an issue:
- As stated, machines running 4.x don't seem to do it
- In addition to the mode schizophrenia, undex 5.3 I'm also seeing
resets of several seconds which don't happen on identical hardware
running 4.11 in the same
On Thu, Mar 31, 2005 at 12:02:20PM -0500, Matthew N. Dodd wrote:
On Wed, 30 Mar 2005, Karl Denninger wrote:
Removing the FIRST delta, which is:
218a219,221
if (!dumping)
callout_reset(request-callout, request-timeout * hz,
Hi,
At 17:38 01/04/2005, Andriy Gapon wrote:
[...]
I suppose that it might be possible that the root cause is in my local
network conditions, [etc]
Unlikely I think. As I said, I've got several machines on the same LAN: the
5.3's misbehave; the others don't.
--
Bob Bishop +44
On Fri, Apr 01, 2005 at 02:24:50PM +0100, Bob Bishop wrote:
Any suggestions as to why this is happening? (And how I can stop
it regularly flipping)
I don't think this is really an issue. [etc]
I think this is an issue:
- As stated, machines running 4.x don't seem to do it
- In
Hi,
At 18:42 01/04/2005, Roland Smith wrote:
On my amd64 box I also get the mode flipping, but I don't get resets.
Hmm. I am getting resets on my amd64.
--
Bob Bishop +44 (0)118 940 1243
[EMAIL PROTECTED] fax +44 (0)118 940 1295
We are trying out an Intel 855 that is not able to boot RELENG_5. It locks
up hard (NUM LOCK doesnt work) on bootup at the same spot. However,
RELENG_4 is able to boot just fine.
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
Can you try setting hw.pci.enable_io_modes=0 at the loader prompt then booting?
I've seen this same problem on a reasonable amount of machines now (mainly
toshiba/acer laptops, but not only)
Regards,
Graham Lilley
Ibex Systems (Maidstone) Ltd
-Original Message-
From: [EMAIL PROTECTED]
At 01:29 PM 01/04/2005, Gray Lilley wrote:
Can you try setting hw.pci.enable_io_modes=0 at the loader prompt then
booting?
Thanks! That did the trick!!
OK set hw.pci.enable_io_modes=0
OK boot
/boot/kernel/acpi.ko text=0x41520 data=0x1da4+0x112c
syms=[0x4+0x7630+0x4+0x9c97]
KDB: debugger
Don Bowman wrote:
From: Uwe Doering [mailto:[EMAIL PROTECTED]
...
As far as I understand this family of controllers the OS
drivers aren't involved at all in case of a disk drive
failure. It's strictly the controller's business to deal
with it internally. The OS just sits there and waits
On Fri, 2005-Apr-01 19:38:41 +0300, Andriy Gapon wrote:
I can second that. I have never seen anything like this with 5.2.1 as
soon as I upgraded to 5.3 I started seeing messages like these:
...
Mar 29 22:15:40 oddity ntpd[400]: time reset -0.288522 s
Mar 29 22:15:40 oddity ntpd[400]: kernel time
No Problems.
Unfortunately, this will disable (at least one) other items of hardware.
Sound Cards seem to be the devices which get killed when using this, but if
your not needing sound, it doesn't seem to be much of a problem.
I'm yet to find anyone who can actually explain what the problem is
Hi guys,
I'm resending this mail again with the hopes of finding someone who is also
seeing this problem. I know that mail isn't the best method perhaps, but
before I open a PR, I thought I'd try again...
My last recent update revealed a bug perhaps. I'm now running:
FreeBSD dakota
On Apr 1, 2005, at 12:56 PM, Bob Bishop wrote:
At 18:42 01/04/2005, Roland Smith wrote:
On my amd64 box I also get the mode flipping, but I don't get resets.
Hmm. I am getting resets on my amd64.
On my dual opteron, I get flipping perhaps a handful of times per day
(5.4-PRE/amd64 from march 22).
Hello,
Last time, the burncd/cdrecord were work when I had FreeBSD
5.4-PRERELEASE #0: Fri Mar 18 14:28:40 CST 2005.. Later when I updated
RELENG_5 to FreeBSD 5.4-PRERELEASE #0: Sun Mar 27 20:11:40 CST 2005 and
the burncd/cdrecord don't work anymore. I tried to update RELENG_5 to
yesterday
On a 5.4-pre system as of the last few days, If I mount a spun down hard
disk (one I am using only for backup):
# mount /backup/usr
I get
ad1: TIMEOUT _ READ DMA retrying (2 retries left) LBA=7340273
ad0: WARNING - removed from configuration
ad1: WARNING - removed from configuration
at0-slave:
IPF in 4.11, 4-Stable breaks the semantics of icmp
keep-state rules. This problem was mentioned in
http://msgs.securepoint.com/cgi-bin/get/ipfilter-0503/31/1/2/1/1.html
I wouldn't make a fuss over this simple matter
except that this constitutes a POLA violation.
To that end, the following pr
On Fri, 1 Apr 2005, Uzi Klein wrote:
I Installed a fresh apache-moddssl port
(using portinstall www/apache13-modssl)
When i start apache using apachectl start everything works just fine,
but when i try apachectl startssl i have some errors i have no idea
what to do with
httpd-error log
On Fri, 1 Apr 2005, Phil Brennan wrote:
On Apr 1, 2005 12:49 PM, Joan Picanyol i Puig
[EMAIL PROTECTED] wrote:
* Phil Brennan [EMAIL PROTECTED] [20050401 12:19]:
Will it be ok just to cvsup, rebuild kernel and world, mergemaster,
(etc) like any normal update? Or do I have to do
On Fri, 1 Apr 2005, Shaun Jurrens wrote:
Hi guys,
I'm resending this mail again with the hopes of finding someone who is also
seeing this problem. I know that mail isn't the best method perhaps, but
before I open a PR, I thought I'd try again...
My last recent update revealed a bug
On Fri, Apr 01, 2005 at 06:59:11PM -0800, Doug White wrote:
pid 62364 (httpd), uid 0: exited on signal 4 (core dumped)
Apr 1 11:48:45 www kernel: pid 62364 (httpd), uid 0: exited on signal 4
(core dumped)
Signal 4 is SIGABRT, which is a software-initiated abort.
Well, no, it's ILL,
38 matches
Mail list logo
