Re: 6to4 suddenly stopped working to 2001: addresses
> I've got three installations of FreeBSD using 6to4 in three different > physical locations, attached to three different ISPs. Sometime in the last > few days all of them have stopped talking to IPv6 addesse which are > not also 6to4. I can still talk to 2002: addresses, but not to 2001: > addresses. > > This all worked fine a few days ago, and nothing has changed in the config of > any of these machines. I can ping 192.88.99.1 under IPv4, so I should > have a route to 2002:c390:806::, but traceroute6 to anything not in > 2002: doesnt show any hops, and I cannot connect to any of these sites. You need to talk to the operators of the last hop before 192.88.99.1 in the traceroute. > Can anyone shed any light on this ? It hardly seems likely that theres > been some massive failure of 6to4 in the London area, but I can't > see any reason why all of this would have suddenly stopped working. > > -pete. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6to4 suddenly stopped working to 2001: addresses
I've got three installations of FreeBSD using 6to4 in three different physical locations, attached to three different ISPs. Sometime in the last few days all of them have stopped talking to IPv6 addesse which are not also 6to4. I can still talk to 2002: addresses, but not to 2001: addresses. This all worked fine a few days ago, and nothing has changed in the config of any of these machines. I can ping 192.88.99.1 under IPv4, so I should have a route to 2002:c390:806::, but traceroute6 to anything not in 2002: doesnt show any hops, and I cannot connect to any of these sites. Can anyone shed any light on this ? It hardly seems likely that theres been some massive failure of 6to4 in the London area, but I can't see any reason why all of this would have suddenly stopped working. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no more src/compat and install.sh
On Tue, Jun 24, 2008 at 05:56:37PM +0800, Mars G Miro wrote: > Greetz, > > src/compat was repocopied to src/cddl/compat about > 2months ago. I > think we need to remove for good 'compat' in > src/release/scripts/src-install.sh. > Fixed, thanks. -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: READ_DMA timeouts, etc. on FreeBSD 7-STABLE SATA
On Wed, Jun 25, 2008 at 01:27:52PM -0500, Reid Linnemann wrote: > Does anyone have any ideas? I've googled but can't find any solutions. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues And I've begun to make a separate page solely for ATA/SATA issues, which is still *very* much under development. The DMA and timeout issues you see are listed on that page. http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting If the LBA changes, then chances are it's not your disks. SMART stats might help validate/refute that. Otherwise, sorry that there's no solution, but rest assured, you're not alone. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tracking -stable in the enterprise
On Jun 25, 2008, at 3:46 AM, Peter Wemm wrote: Correct. We roll our own build snapshots periodically, but we also keep a pretty careful eye on what's going on in the -stable branches. Okay, that makes sense to me ;-) I mean, I guess Yahoo has enough resources to literally run every commit to -stable through a full test cycle and push it out to every machine, but my No. Why on earth would we do that? if we wanted to cause ourselves that much pain for no good reason, we'd go get a pencil and stab ourselves in the eye. Yes, we are definitely on the same page. Thanks for the clarification ;-) We don't upgrade machines that have been deployed unless there is a good reason to. Do you deploy machines for longer than 1 year? How do you deal with security patches in the longer term? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
READ_DMA timeouts, etc. on FreeBSD 7-STABLE SATA
Hi guys, I'm running 7-STABLE, last synced early June (June 7 I think). I have two SATA disks, identical 160G Western Digital WD1600AAJS on a SiS 180 SATA controller that are gmirrored, and the mirror provides all of my individual filesystems. After I built the mirror in single user mode and rebooted, I started getting DMA errors such as: Jun 21 11:56:28 hautlos kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=2830976 Jun 21 11:56:28 hautlos kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=2901888 Jun 21 11:56:28 hautlos kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=2995328 The LBA is apparently random. Most of the time this just makes the machine crawl and is annoying, but if, say, a filesystem were removed uncleanly from a power failure, the combined activity of the mirror rebuilding and the fsck cause much more disconcerting errors, eg: Jun 21 11:48:46 hautlos kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly Jun 21 11:49:02 hautlos kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=196200751 Jun 21 11:49:02 hautlos kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=196442127 But, now for the weird part... I tried booting in single user mode, disabling DMA, and disabling ACPI, to no avail. Soft boot, hard boot, doesn't matter. But - if I power the machine down, cut power to the power supply, and cycle the remaining juice through the system by hitting the ATX power on, and then boot up, the DMA errors completely or nearly completely vanish. Since I did this on Jun 21 I have logged only 2 READ_DMA timeouts: messages:Jun 22 03:02:15 hautlos kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=56884207 messages:Jun 24 10:52:41 hautlos kernel: ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=243514511 Does anyone have any ideas? I've googled but can't find any solutions. I'm not currently subscribed to stable@, so please cc: me in responses. My uname -a and dmesg follows. FreeBSD hautlos 7.0-STABLE FreeBSD 7.0-STABLE #7: Sat Jun 7 10:46:48 CDT 2008 root@:/usr/obj/usr/src/sys/HAUTLOS i386 Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #7: Sat Jun 7 10:46:48 CDT 2008 root@:/usr/obj/usr/src/sys/HAUTLOS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1999.44-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20fc2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 real memory = 1073676288 (1023 MB) avail memory = 1037291520 (989 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3fef (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x480-0x48f,0x1000-0x10df,0x10e0-0x10ff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xd000-0xd0ff mem 0xd000-0xd7ff,0xe802-0xe802 irq 16 at device 0.0 on pci1 vgapci1: mem 0xd800-0xdfff,0xe803-0xe803 at device 0.1 on pci1 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x4000-0x400f at device 2.5 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcm0: port 0xe000-0xe0ff,0xe100-0xe17f irq 18 at device 2.7 on pci0 pcm0: [ITHREAD] pcm0: ohci0: mem 0xe8124000-0xe8124fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xe812-0xe8120fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] hci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xe8121000-0xe8121fff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] ohci2:
Re: Problem with /boot/loader
On Wed, Jun 25, 2008 at 7:38 AM, Kelly Black <[EMAIL PROTECTED]> wrote: > I have a problem with loader. I recently upgraded from 6_rel to 7_rel. > Now when I install world there is a problem booting. > > Here is what I do: [snip] > Now when I reboot there is a problem. I get an error that the system > cannot boot. Part of it looks like this: > Can't work out which disk we are booting from. > Guessed BIOS device 0x not found by probes, defaulting to disk0: > > If I boot from a live disk and replace /boot/loader with > /boot/loader.old it boots up fine and everything looks good. A new > world and a new kernel. I would be grateful for any help or any > pointers. What do you have in /etc/make.conf? I recall there being a point in time where incorrect CFLAGS options could build a broken loader. Try renaming /etc/make.conf (or just commenting out all CFLAGS/CXXFLAGS options) and rebuilding either just the loader or the whole world, and see if that makes a difference. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tracking -stable in the enterprise
On Wed, Jun 25, 2008 at 4:07 AM, Claus Guttesen <[EMAIL PROTECTED]> wrote: >>> FWIW, Yahoo! tracks -stable branches, not point releases. >> >> I'm curious about this (and stealing the dead thread). >> >> How does one track -stable in an enterprise environment? I assume that what >> you mean is "we pick points in -stable that we believe are stable enough and >> create a snapshot from this point that we test and roll out to production" >> ...? Am I wrong? >> [snip] > > I only have a handfull of web-servers so I do a 'make buildworld' and > -kernel on one server and then nfs-mount it from the other servers > (remember mount-root-option if doing this). I don't have any problems > running stable if it works. So I usually just upgrade one server to > whatever stable is at that moment and if it runs without problems for > a while I upgrade the remaining servers a few days apart. That's pretty much what we do as well, here in the local school district. We track the -stable and -current mailing lists, read all the Head's Up messages, and read through cvsweb logs for the devices/apps we're interested in. When there's a commit that interests us, we update the source tree to after that commit, run through the buildworld cycle on a test box, make sure everything works over a few days/weeks, and then export /usr/obj and /usr/src to the systems we want to upgrade. It's not all that time consuming, even though it's just me doing the work. > When it comes to our db-server I usually track release, but since my > web-servers and db-server is the same hardware I'm somewhat confident > that an upgrade to stable will work if the need to do so arises. We keep all our server hardware as identical as possible, which greatly simplifies things. We have four hardware profiles that run FreeBSD, and only two of those track -STABLE. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata on alix/geode stopped being detcted.
> hi, > latest changes in dev/ata broke this, on older -stable> ... > ata0-master: pio=PIO4 wdma=UNSUPPORTED udma=UNSUPPORTED cable=40 =wire > ad0: success setting PIO4 on National chip > ad0: 977MB at ata0-master PIO4 > > on latest -stable: > ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire > > and no disk. > > cheers, > danny problem solved: somehow 'device atadisk' was lost from the kernel configuration file ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire ad0: setting PIO4 on CS5536 chip ad0: setting WDMA2 on CS5536 chip ad0: 1953MB at ata0-master WDMA2 ad0: 4001760 sectors [3970C/16H/63S] 4 sectors/interrupt 1 depth queue danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with /boot/loader
Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make installworld mergemaster Now when I reboot there is a problem. I get an error that the system cannot boot. Part of it looks like this: Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: If I boot from a live disk and replace /boot/loader with /boot/loader.old it boots up fine and everything looks good. A new world and a new kernel. I would be grateful for any help or any pointers. Sincerely, Kel PS I do not do anything special with my loader config files: $ cat loader.conf snd_ich_load="YES" $ cat loader.rc \ Loader.rc \ $FreeBSD: src/sys/boot/i386/loader/loader.rc,v 1.4 2005/10/30 05:41:42 scottl Exp $ \ \ Includes additional commands include /boot/loader.4th \ Reads and processes loader.conf variables start \ Tests for password -- executes autoboot first if a password was defined check-password \ Load in the boot menu include /boot/beastie.4th \ Start the boot menu beastie-start -- ___ Kelly Black Phone: (518) 388-8727 Department of Mathematics FAX: (603) 388-6005 Union College e-mail: [EMAIL PROTECTED] Schenectady NY 12308 (USA) WWW: http://blackk.union.edu/~black ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AGP bridge detected as pcib
On Tuesday 24 June 2008 07:39:20 pm Daniel O'Connor wrote: > On Wed, 25 Jun 2008, John Baldwin wrote: > > > Nothing in /dev though.. > > > [midget 22:56] ~ >ls -la /dev/agp* > > > zsh: no match > > > > And does kldstat -vv | grep agp show anything? > > Yes. > [midget 9:01] ~ >kldstat -vv| grep agp > 438 hostb/agp_ali > 439 hostb/agp_amd > 440 hostb/agp_amd64 > 441 hostb/agp_ati > 442 vgapci/agp_i810 > 443 hostb/agp_intel > 444 hostb/agp_nvidia > 445 hostb/agp_sis > 446 hostb/agp_via I would add start adding printfs to the amd64 probe adn attach routines. Note that in 7.0 because of the hostb changes you can now kldload agp after boot which may aid in testing. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tracking -stable in the enterprise
>> FWIW, Yahoo! tracks -stable branches, not point releases. > > I'm curious about this (and stealing the dead thread). > > How does one track -stable in an enterprise environment? I assume that what > you mean is "we pick points in -stable that we believe are stable enough and > create a snapshot from this point that we test and roll out to production" > ...? Am I wrong? > > I mean, I guess Yahoo has enough resources to literally run every commit to > -stable through a full test cycle and push it out to every machine, but my > mind boggles to imagine the manpower cost of doing so. (and to justify the > manpower cost versus the gain from doing so...) I only have a handfull of web-servers so I do a 'make buildworld' and -kernel on one server and then nfs-mount it from the other servers (remember mount-root-option if doing this). I don't have any problems running stable if it works. So I usually just upgrade one server to whatever stable is at that moment and if it runs without problems for a while I upgrade the remaining servers a few days apart. When it comes to our db-server I usually track release, but since my web-servers and db-server is the same hardware I'm somewhat confident that an upgrade to stable will work if the need to do so arises. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tracking -stable in the enterprise
On Wed, Jun 25, 2008 at 2:23 AM, Jo Rhett <[EMAIL PROTECTED]> wrote: > On Jun 23, 2008, at 7:51 AM, John Baldwin wrote: >> >> FWIW, Yahoo! tracks -stable branches, not point releases. > > > I'm curious about this (and stealing the dead thread). > > How does one track -stable in an enterprise environment? I assume that what > you mean is "we pick points in -stable that we believe are stable enough and > create a snapshot from this point that we test and roll out to production" > ...? Am I wrong? Correct. We roll our own build snapshots periodically, but we also keep a pretty careful eye on what's going on in the -stable branches. When I say "we", I mostly mean John does it. :) Quite often the biggest factor that tells us when to roll a new internal release is when there's something that has gone into -stable that we want. We have many local modifications, so freebsd.org's concept of a "release" is pretty much meaningless to us. However, we do quietly help in freebsd.org's release process. We make a point of trying to run some recent snapshots in production in the leadup to a freebsd.org release. This helps shake out silly problems that might not get noticed in time. > I mean, I guess Yahoo has enough resources to literally run every commit to > -stable through a full test cycle and push it out to every machine, but my > mind boggles to imagine the manpower cost of doing so. (and to justify the > manpower cost versus the gain from doing so...) No. Why on earth would we do that? if we wanted to cause ourselves that much pain for no good reason, we'd go get a pencil and stab ourselves in the eye. We don't upgrade machines that have been deployed unless there is a good reason to. -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tracking -stable in the enterprise
On Jun 23, 2008, at 7:51 AM, John Baldwin wrote: FWIW, Yahoo! tracks -stable branches, not point releases. I'm curious about this (and stealing the dead thread). How does one track -stable in an enterprise environment? I assume that what you mean is "we pick points in -stable that we believe are stable enough and create a snapshot from this point that we test and roll out to production" ...? Am I wrong? I mean, I guess Yahoo has enough resources to literally run every commit to -stable through a full test cycle and push it out to every machine, but my mind boggles to imagine the manpower cost of doing so. (and to justify the manpower cost versus the gain from doing so...) -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
