Re: clock running fast

On Thu, 2004-Dec-30 15:59:10 -0500, Harlan Stenn wrote: >> Remove /var/db/ntpd.drift before you reboot or restart your ntpd. > >Why would you want to do this? On a number of occasions, I've had the ntpd PLL start oscillating and winding up saturated at +500ppm or -500ppm. Removing ntpd.drift lets

Re: clock running fast

I'd appreciate it if somebody would add this information to: http://ntp.isc.org/Support/KnownOsIssues H ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTEC

Re: clock running fast

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Kinsey wrote: Have you tried all possible values for kern.timecounter.hardware? #sysctl kern.timecounter.choice My most recent encounter with this issue, a K6-2/500 on an Asus P5A mobo, needed "i8254". Thank you vociferously. A value of i8254 for

Re: USB flash not working anymore

Julian Elischer <[EMAIL PROTECTED]> probably said: > do you have access to anything with an EHCI or OHCI controller for > comparison with that device? My (now usually windows only) amd64 desktop box has ohci, but it doesn't have any ethernet devices that 4 has support for (5 does, apparently) so

5.3-RELEASE: SMP: system clock has died

I have an ASUS P2B-DS motherboard with dual P2 400MHz CPU's. I have compiled the SMP kernel and noticed that something is not right. In "top" the CPU values indicate 0% across the board, even idle! last pid: 9462; load averages: 0.00, 0.00, 0.00up 2+18:57:30 13:11:47 14 processes:

RE: iTE IT8212 card/ata problems

Brian, See http://www.xl0.org/FreeBSD/13-12-04.html#ite-it8212f-gigabyte-raid-controlle r-supported -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Szymanski Sent: 31. december 2004 01:52 To: freebsd-stable@freebsd.org Subject: iTE IT8212 card/ata

iTE IT8212 card/ata problems

Hello... FreeBSD 5.3 on x86 I've installed an addon ATA card, an IT8212(F), and it comes in at bios time, detects drives and such, but freebsd doesn't see it on booting. I thought maybe this was because no drives were attached, but no dice with a drive attached (even though the card sees this dri

Re: clock running fast

On Dec 30, 2004, at 15:58, Federico Galvez-Durand Besnard wrote: Your NTPD will never be stable with a wrong localtime setting. NTP does not care about local time. All values that NTP uses are in UTC: local time is a function of the operating system and is not used when calculating time values.

Re: USB flash not working anymore

Peter Radcliffe wrote: Julian Elischer <[EMAIL PROTECTED]> probably said: this means exactly what it sounds like... something in the usb system tried to allocate memory while in an interrupt context. do you have access to anything with an EHCI or OHCI controller for comparison with that

Re: clock running fast

> [ rc.conf and ntp.conf snipped ] > > Thank you for the suggestions. Unfortunately, I've been through all > that, including the rude values of minpoll and maxpoll, using multiple > servers, and starting with a fresh drift file. I'm pretty sure ntpd > isn't the problem. In addition, the hard

Re: USB flash not working anymore

Julian Elischer <[EMAIL PROTECTED]> probably said: > this means exactly what it sounds like... something in the usb system > tried to allocate memory while in an interrupt context. I don't know anything about the USB subsystem, nor what can or cannot be done while handling an interrupt. > I don'

Re: USB flash not working anymore

Peter Radcliffe wrote: I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop. I'm having increasingly worse USB problems as time goes on. Nothing that I try new works and various older devices that I bought specificly because they were supported and worked fine for years now do not work.

Re: problem burning iso images

Warren Liddell wrote this message on Fri, Dec 31, 2004 at 07:14 +1000: > next writeable LBA 0 > writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB > written this track 274400 KB (100%) total 274400 KB > next writeable LBA 137352 > writing from stdin > > Every time i goto burn a iso fil

Re: clock running fast

Oops, I meant: cp /usr/share/zoneinfo/Etc/GMT+8/etc/localtime if you want Pacific Time in GMT format (don't use GMT-8). Harlan Stenn wrote: No way. ntpd operates in gmt/utc only; localtime is completely out of the question. H -- Hmmm, are you using the same localtime in all machines? I

problem burning iso images

next writeable LBA 0 writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB written this track 274400 KB (100%) total 274400 KB next writeable LBA 137352 writing from stdin Every time i goto burn a iso filoe of onto CD it ends up getting stuck at the above part. any reasons why this may

Re: clock running fast

No way. ntpd operates in gmt/utc only; localtime is completely out of the question. H -- > Hmmm, are you using the same localtime in all machines? > I remember having the same problem several years ago, in 3.x, with a > server. The clock kept walking. Hardware was OK. It came back to normal > a

Re: clock running fast

Harlan Stenn wrote: Remove /var/db/ntpd.drift before you reboot or restart your ntpd. Why would you want to do this? And in config files, iburst is your friend. See http://ntp.isc.org/Support/ for more informaion. H True only when NTPD is running in stable steady state. In this case, NTPD i

Re: clock running fast

> Remove /var/db/ntpd.drift before you reboot or restart your ntpd. Why would you want to do this? And in config files, iburst is your friend. See http://ntp.isc.org/Support/ for more informaion. H ___ freebsd-stable@freebsd.org mailing list http://li

Re: clock running fast

Hmmm, are you using the same localtime in all machines? I remember having the same problem several years ago, in 3.x, with a server. The clock kept walking. Hardware was OK. It came back to normal after setting localtime correctly. Remember, if you are in Pacific Time you are GMT+8 (some people w

Re: clock running fast

> But isn't that what the drift file is for, to improve the accuracy of > the local clock during those times when the configured NTP servers aren't > available? Yes. H ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

Re: dump/restore with ufs2

On Thu, Dec 30, 2004 at 05:54:25PM +, Ceri Davies wrote: > On Tue, Dec 28, 2004 at 01:23:50PM -0500, Brian Szymanski wrote: > > When I run the following script, I get a warning message, and I'm > > wondering if it's ignorable or indicates there is a little more work to be > > done in getting du

New Ad-aware software!

Ad-Aware is designed to provide advanced protection from known Data-mining, aggressive advertising, Parasites, Scumware, selected traditional Trojans, Dialers, Malware, Browser hijackers, and tracking components. With the release of Ad-Aware SE Personal edition, Lavasoft takes the f

Re: clock running fast

Brooks Davis wrote: On Thu, Dec 30, 2004 at 11:37:04AM -0800, Javier Henderson wrote: /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ - -f /var/db/ntpd.drift It's generally recommended that you never trust your own clock since it's completely crap as time sources go. It's also r

Re: clock running fast

On Thu, Dec 30, 2004 at 11:37:04AM -0800, Javier Henderson wrote: > > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ > > > - -f /var/db/ntpd.drift > > > > It's generally recommended that you never trust your own clock since > > it's completely crap as time sources go. It's also recommen

Re: how to remote update 4.10 -> 5.3?

Igor Pokrovsky wrote: Are there any other advantages of UFS2 over UFS except maximum disk size? There's FFS snapshots capability in UFS2, for starters... Cheers, Paul. -- e-mail: [EMAIL PROTECTED] "Without music to decorate it, time is just a bunch of boring production deadlines or dates by whic

Re: clock running fast

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Federico Galvez-Durand Besnard wrote: Set /etc/localtime to your correct timezone before doing anything in your machine. Remove /var/db/ntpd.drift before you reboot or restart your ntpd. [ rc.conf and ntp.conf snipped ] Thank you for the suggestions.

Re: clock running fast

Set /etc/localtime to your correct timezone before doing anything in your machine. Remove /var/db/ntpd.drift before you reboot or restart your ntpd. This is what I use in /etc/rc.conf: +++ ntpd_enable="YES" # Run ntpd Network Time Protocol (or NO). ntpd_program="/usr/sbin/ntpd" #

Re: clock running fast

> > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ > > - -f /var/db/ntpd.drift > > It's generally recommended that you never trust your own clock since > it's completely crap as time sources go. It's also recommended that you > use at least 5 time sources to avoid problems with bad clocks

Re: how to remote update 4.10 -> 5.3?

On Thu, Dec 30, 2004 at 07:32:20PM +0100, Palle Girgensohn wrote: > > > --On torsdag, december 30, 2004 20.36.56 +0300 Igor Pokrovsky > <[EMAIL PROTECTED]> wrote: > > > > > >Are there any other advantages of UFS2 over UFS except maximum disk size? > > acl -- access control lists > mac -- Mandato

Re: clock running fast

[Please don't top post]. On Thu, Dec 30, 2004 at 11:13:55AM -0800, David Talkington wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Federico Galvez-Durand Besnard wrote: > > >what do you have in : > >/etc/ntp.conf > > Only: > > servertime.u.washington.edu > server

USB flash not working anymore

I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop. I'm having increasingly worse USB problems as time goes on. Nothing that I try new works and various older devices that I bought specificly because they were supported and worked fine for years now do not work. My SanDisk CF reader (S

Re: clock running fast

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Federico Galvez-Durand Besnard wrote: what do you have in : /etc/ntp.conf Only: server time.u.washington.edu server 127.127.1.0 fudge 127.127.1.0 stratum 10 Command line: /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ - -f

Re: how to remote update 4.10 -> 5.3?

Igor Pokrovsky wrote this message on Thu, Dec 30, 2004 at 20:36 +0300: > > That's not so bad. A reinstall means you can newfs your partitions as > > UFS2 filesystems, which wouldn't be the case if you upgraded 4.10 in-place. > > Are there any other advantages of UFS2 over UFS except maximum disk

Re: Memory handling problem with FreeBSD 5.3?

Bosko Milekic wrote: On Thu, Dec 30, 2004 at 10:41:27AM -0700, Scott Long wrote: Christian R. wrote: On Thu, 30 Dec 2004 12:02:16 +0100, you wrote: Would the AMD64 version of FreeBSD 5.3 be a better choice? I have now installed the AMD64 version on the server. It has been running stable now for s

Re: how to remote update 4.10 -> 5.3?

--On torsdag, december 30, 2004 20.36.56 +0300 Igor Pokrovsky <[EMAIL PROTECTED]> wrote: On Wed, Dec 29, 2004 at 04:38:23PM -0500, Paul Mather wrote: Palle Girgensohn wrote: > I've tried the UPDATING instructions, both locally and remotely (the > latter failed ;-). But really, everything has to

Re: Strange networking problems after update 5.2.1->5.3

On Thu, 30 Dec 2004, Gerrit Kühn wrote: > I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2.1 > worked fine, the update went without any noticable problem according to the > docs. 5.3 behaves well apart from a strange networking problem. > The notebook lives in a /16 subnet

Re: Memory handling problem with FreeBSD 5.3?

On Thu, Dec 30, 2004 at 10:41:27AM -0700, Scott Long wrote: > Christian R. wrote: > >On Thu, 30 Dec 2004 12:02:16 +0100, you wrote: > > > > > >>Would the AMD64 version of FreeBSD 5.3 be a better choice? > > > > > >I have now installed the AMD64 version on the server. It has been > >running stable

Re: icc8 failed on 4.10: Illegal instruction

On Wed, 29 Dec 2004, Igor Sysoev wrote: > On Tue, 28 Dec 2004, Kris Kennaway wrote: > > > On Wed, Dec 29, 2004 at 10:21:05AM +0300, Igor Sysoev wrote: > > > > > > > > > Then I installed the port and I ran > > > > > > > /usr/local/intel_cc_80/bin/icc, > > > > > > > but it always failed with messag

Re: dump/restore with ufs2

On Tue, Dec 28, 2004 at 01:23:50PM -0500, Brian Szymanski wrote: > When I run the following script, I get a warning message, and I'm > wondering if it's ignorable or indicates there is a little more work to be > done in getting dump/restore happy with ufs2... > > $ cd /altroot > $ dump -L -0 -a -f

Re: Memory handling problem with FreeBSD 5.3?

Christian R. wrote: On Thu, 30 Dec 2004 12:02:16 +0100, you wrote: Would the AMD64 version of FreeBSD 5.3 be a better choice? I have now installed the AMD64 version on the server. It has been running stable now for some hours with alot of load and all the 6 GB activated. It seems to be a problem

Re: how to remote update 4.10 -> 5.3?

On Wed, Dec 29, 2004 at 04:38:23PM -0500, Paul Mather wrote: > Palle Girgensohn wrote: > > >I've tried the UPDATING instructions, both locally and remotely (the > >latter failed ;-). But really, everything has to be reinstalled, ports > >and the lot, so a new install is probably the best way...

clock running fast

what do you have in : /etc/ntp.conf *alk-ml at prairienet.org* dtalk-ml at prairienet.org /Wed Dec 29 19:13:42 PST 2004/ * Previous message: Multiple Vinum Problems Since Upgrade From 4.9 To 4.10

Re: Memory handling problem with FreeBSD 5.3?

On Thu, 30 Dec 2004 12:02:16 +0100, you wrote: >Would the AMD64 version of FreeBSD 5.3 be a better choice? I have now installed the AMD64 version on the server. It has been running stable now for some hours with alot of load and all the 6 GB activated. It seems to be a problem with the i386 versi

backward compat in /etc/fstab?

Hi, In 5.2 when you wished to make mdmfs in an /etc/fstab entry, you were actually using the compatibility mode for the old mount_mfs. It was not possible to set permissions and ownerships in an /etc/fstab entry. So a workaround should be made then in /etc/rc.local It this still the same in 5.3

Strange networking problems after update 5.2.1->5.3

Hi folks, I recently updated my old Compaq Armada 1500c from 5.2.1 to 5-stable. 5.2.1 worked fine, the update went without any noticable problem according to the docs. 5.3 behaves well apart from a strange networking problem. The notebook lives in a /16 subnet with a /16 netmask and has a 16bit NE

Re: Dummynet related panic in 5.3-RELEASE-p1

Gleb Smirnoff <[EMAIL PROTECTED]> writes: > is it easy to reproduce it? Can you set debug.mpsafenet=0 and > try to reproduce it? It looks like debug.mpsafenet=0 make the crashes happen more frequently. I now managed to get a crashdump. kernel.debug and vmcore.1 are in the tarball available here

Problem mounting root from CD9660 on 4.x

I have a 4.10 system that I'm trying to build a bootable DVD for (for disaster recovery purposes). Whilst it boots OK, it won't mount root from the native ATAPI device but only off the SCSI emulation. Has anyone else seen this? The ISO image is built with mkisofs -b boot/cdboot -no-emul-boot -r

Re: Memory handling problem with FreeBSD 5.3?

On Thu, 30 Dec 2004 10:02:31 +0100, you wrote: >>Upgrade to 5-STABLE. I fixed these problems a few weeks ago. > >I already have done that. I'm using RELENG_5 "5.3-STABLE FreeBSD >5.3-STABLE #0: Tue Dec 28 17:56:04 CET 2004" > >Setting hw.physmem=3D3G at boot time has also made the system stable,

Re: Memory handling problem with FreeBSD 5.3?

On Wed, 29 Dec 2004 19:32:04 -0700, you wrote: >Christian R. wrote: >> I have installed FreeBSD 5.3-STABLE i386 on a new Dell PowerEdge 2850, >> but it crashes under load like "make buildworld" with a "panic: page >> fault". >> >> The server has following configuration: 2x Intel Xeon 3.4 GHz (800

Re: -stable, uhci and the iRiver H320.

Alexey Zakirov wrote: On Thu, 30 Dec 2004, [ISO-8859-1] Jean-S?bastien P?dron wrote: I am now looking into purchasing an iRiver H320 player. There was not a lot of information turning up on Google in regard to people being successful, or not, with this device under either Linux or FreeBSD, so I am

Re: USB scanner not attached when connected after system startup]

On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote: > > My scanner (EPSON PERFECTION 1650) is working alright if it is connected > before system startup. > But when connected to the running system it doesn't get attached by usbd. I > can't find out from Handbook, manpages or mailing lis