Re: Strange sendmail behaviour after upgrade to 9.1-BETA2
On Wed, Jul 31, 2013 at 04:54:08PM +0400, Pavel Timofeev typed: I've just installed new fresh 9.2-BETA2 amd64 on another machine. Same behaviour - Sendmail asks DNS only for record of mx server. We don't use IPv6 in our company. 2013/7/31 Pavel Timofeev tim...@gmail.com: I wanted to say that sendmail asks only (IPv6) record of mx server, but not A (IPv4). Any ideas? 2013/7/31 Pavel Timofeev tim...@gmail.com: Looks like my sendmail uses only IPv6 to resolve mx server dns name to ip address. 14:59:50.793338 IP reticulum.xxx.ru.19032 hercules.xxx.ru.domain: 53417+ ? xxx.ru. (24) [13/98] 14:59:50.793662 IP hercules.xxx.ru.domain reticulum.xxx.ru.19032: 53417* 0/1/0 (75) 14:59:50.793696 IP reticulum.xxx.ru.55299 hercules.xxx.ru.domain: 53418+ A? xxx.ru. (24) Here it is definately asking an A record. 14:59:50.794087 IP hercules.xxx.ru.domain reticulum.xxx.ru.55299: 53418* 7/0/0 A 192.168.2.11, A 192.168.2.12, A 192.168.41.4, A 192.168.14.12, A 192.168.34.100, A 192.168.34.110, A 192.168.44.19 (136) And here is the reply. The quetion is more why is it repeating the same query (below) over and over. Ruben 14:59:50.973445 IP reticulum.xxx.ru.29244 hercules.xxx.ru.domain: 53419+ MX? xxx.ru. (24) 14:59:50.973754 IP hercules.xxx.ru.domain reticulum.xxx.ru.29244: 53419* 1/0/1 MX kalmar.xxx.ru. 10 (63) 14:59:50.974061 IP reticulum.xxx.ru.56461 hercules.xxx.ru.domain: 53420+ ? kalmar.xxx.ru. (31) 14:59:50.974340 IP hercules.xxx.ru.domain reticulum.xxx.ru.56461: 53420* 0/1/0 (82) 14:59:50.974570 IP reticulum.xxx.ru.28332 hercules.xxx.ru.domain: 53421+ ? kalmar.xxx.ru. (31) 14:59:50.974887 IP hercules.xxx.ru.domain reticulum.xxx.ru.28332: 53421* 0/1/0 (82) 14:59:50.974919 IP reticulum.xxx.ru.21453 hercules.xxx.ru.domain: 53422+ ? kalmar. (24) 14:59:50.975290 IP hercules.xxx.ru.domain reticulum.xxx.ru.21453: 53422 ServFail 0/0/0 (24) 14:59:50.975314 IP reticulum.xxx.ru.63038 hercules.xxx.ru.domain: 53422+ ? kalmar. (24) 14:59:50.975674 IP hercules.xxx.ru.domain reticulum.xxx.ru.63038: 53422 ServFail 0/0/0 (24) 14:59:50.975749 IP reticulum.xxx.ru.38393 hercules.xxx.ru.domain: 53423+ ? kalmar.xxx.ru. (31) 14:59:50.976105 IP hercules.xxx.ru.domain reticulum.xxx.ru.38393: 53423* 0/1/0 (82) 14:59:50.976176 IP reticulum.xxx.ru.45558 hercules.xxx.ru.domain: 53424+ ? kalmar. (24) 14:59:50.976483 IP hercules.xxx.ru.domain reticulum.xxx.ru.45558: 53424 ServFail 0/0/0 (24) 14:59:50.976512 IP reticulum.xxx.ru.45297 hercules.xxx.ru.domain: 53424+ ? kalmar. (24) 14:59:50.976864 IP hercules.xxx.ru.domain reticulum.xxx.ru.45297: 53424 ServFail 0/0/0 (24) How to force it to use IPv4? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
MFC openssh fix versionaddendum?
http://www.freebsd.org/cgi/query-pr.cgi?pr=163843 The fix was committed to -current, but in 9.1 it's still not working. cheersRuben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
On 21 jun 2012, at 09:54, Andrey V. Elsukov wrote: On 20.06.2012 22:23, Ruben de Groot wrote: ata2: reset tp2 stat0=50 stat1=00 devices=0x1 (ada0:ata2:0:0:0): Command timed out (ada0:ata2:0:0:0): Retrying command ata2: reset tp1 mask=03 ostat0=58 ostat1=00 ata2: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 (ada0:ata2:0:0:0): Command timed out (ada0:ata2:0:0:0): Retrying command It seems it is not related to the problem with integrity checks. I think so too. However, this still does not make a stable-9 kernel bootable on my stystem. Do you know of any loader variable that would stop this ada0:ata2 probing? Should not this be the default behaviour, to just quit after a number of tries? If I have the time I'll try to find the code myself later today. But I'm not a kernel programmer, so I might get lost. -- Ruben de Groot -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
I'm resending this email as I got no response the first time. After over 3 years of uptime, I decided to upgrade one of my SUN boxes to 9-stable. However the new kernel didn't boot because of geom integrity check issues. This I understand as I remember I had to use some weird tricks in the past to get the entire disks used in the first place. Anyway, I felt lucky this was a known and documented problem, with a workaround: http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#AEN1277 However, the workaround doesn't seem to work :-( Type '?' for a list of commands, 'help' for more detailed help. OK set kern.geom.part.check_integrity=0 OK boot jumping to kernel entry at 0xc007. Copyright (c) 1992-2012 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 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012 SNIP Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: MAXTOR STM3160215A 3.AAD ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: MAXTOR STM3160215A 3.AAD ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? -- cheers, Ruben de Groot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
On 20 jun 2012, at 18:34, Andrey V. Elsukov wrote: On 20.06.2012 19:14, Ruben de Groot wrote: Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: MAXTOR STM3160215A 3.AAD ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: MAXTOR STM3160215A 3.AAD ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? Can you enable verbose boot mode and show what you will get? It looks like it gets stuck in some loop and I can only break to lom and reset. Type '?' for a list of commands, 'help' for more detailed help. OK unload OK set kern.geom.part.check_integrity=0 OK boot kernel.9 -v /boot/kernel.9/kernel data=0x5af3d8+0xc2fd8 syms=[0x8+0x77fe8+0x8+0x7119d] /boot/kernel.9/geom_mirror.ko text=0x37a10 data=0x5a0+0x18 syms=[0x8+0x1650+0x8+0x1159] jumping to kernel entry at 0xc007. Copyright (c) 1992-2012 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 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012 r...@morninglightmountain.hacktor.net:/usr/obj/usr/src/sys/MORNINGLIGHTMOUNTAIN sparc64 Preloaded elf kernel /boot/kernel.9/kernel at 0xc089a000. Preloaded elf module /boot/kernel.9/geom_mirror.ko at 0xc089a1a0. real memory = 536870912 (512 MB) avail memory = 503963648 (480 MB) machine: SUNW,UltraAX-i2 cpu0: Sun Microsystems UltraSparc-IIe Processor (400.00 MHz CPU) mask=0x14 maxtl=5 maxwin=7 INTR: Adding CPU 0 as a target ULE: setup cpu 0 nfslock: pseudo-device mem: memory null: null device, zero device openfirm: Open Firmware control device random: entropy source, Software, Yarrow ctl: CAM Target Layer loaded nexus0: Open Firmware Nexus device pcib0: U2P UPA-PCI bridge mem 0x1fe-0x1fe,0x1fe0100-0x1fe01ff irq 2032,2030,2031,2021 on nexus0 pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 66MHz pcib0: DVMA map: 0x6000 to 0x63ff 8192 entries pcib0: PROM IOTSB size: 1 (2048 entries) pcib0: bus range 0 to 0; PCI bus 0 initalizing intr_countp pcib0: [GIANT-LOCKED] pci0: OFW PCI bus on pcib0 pci0: domain=0, physical bus=0 found- vendor=0x108e, dev=0xa001, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0146, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x10b9, dev=0x1533, revid=0x00 domain=0, bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x000f, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D3 current D0 found- vendor=0x10b9, dev=0x7101, revid=0x00 domain=0, bus=0, slot=3, func=0 class=00-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x1282, dev=0x9102, revid=0x31 domain=0, bus=0, slot=12, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0147, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x50 (2400 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (1 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x1, size 8, enabled map[14]: type Memory, range 32, base 0, size 8, enabled found- vendor=0x1282, dev=0x9102, revid=0x31 domain=0, bus=0, slot=5, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0147, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x50 (2400 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (1 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x10100, size 8, enabled map[14]: type Memory, range 32, base 0x2000, size 8, enabled found- vendor=0x10b9, dev=0x5237, revid=0x03 domain=0, bus=0, slot=10, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x50 (2 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0x100, size 12, memory disabled found- vendor=0x10b9, dev=0x5229, revid=0xc3 domain=0, bus=0, slot=13, func=0 class=01-01
kern.geom.part.check_integrity=0 not working. not able to boot 9-STABLE
Hi, After over 3 years of uptime, I decided to upgrade one of my SUN boxes to 9-stable. However the new kernel didn't boot because of geom integrity check issues. This I understand as I remember I had to use some weird tricks in the past to get the entire disks used in the first place. Anyway, I felt lucky this was a known and documented problem, with a workaround: http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#AEN1277 However, the workaround doesn't seem to work :-( Type '?' for a list of commands, 'help' for more detailed help. OK set kern.geom.part.check_integrity=0 OK boot jumping to kernel entry at 0xc007. Copyright (c) 1992-2012 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 9.0-STABLE #5: Thu Jun 14 19:24:33 UTC 2012 r...@morninglightmountain.hacktor.net:/usr/obj/usr/src/sys/MORNINGLIGHTMOUNTAIN sparc64 real memory = 536870912 (512 MB) avail memory = 503963648 (480 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (400.00 MHz CPU) ctl: CAM Target Layer loaded nexus0: Open Firmware Nexus device pcib0: U2P UPA-PCI bridge mem 0x1fe-0x1fe,0x1fe0100-0x1fe01ff irq 2032,2030,2031,2021 on nexus0 pcib0: Sabre, impl 0, version 0, IGN 0x1f, bus A, 66MHz pcib0: DVMA map: 0x6000 to 0x63ff 8192 entries pcib0: [GIANT-LOCKED] pci0: OFW PCI bus on pcib0 pci0: bridge, PCI-ISA at device 7.0 (no driver attached) pci0: old, non-VGA display device at device 3.0 (no driver attached) dc0: Davicom DM9102A 10/100BaseTX port 0x1-0x100ff mem 0-0xff at device 12.0 on pci0 miibus0: MII bus on dc0 amphy0: DM9102 10/100 media interface PHY 1 on miibus0 amphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:ba:05:fa:5c dc1: Davicom DM9102A 10/100BaseTX port 0x10100-0x101ff mem 0x2000-0x20ff at device 5.0 on pci0 miibus1: MII bus on dc1 amphy1: DM9102 10/100 media interface PHY 1 on miibus1 amphy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: Ethernet address: 00:03:ba:05:fa:5c pci0: serial bus, USB at device 10.0 (no driver attached) atapci0: AcerLabs M5229 UDMA66 controller port 0x10200-0x10207,0x10218-0x1021b,0x10210-0x10217,0x10208-0x1020b,0x10220-0x1022f at device 13.0 on pci0 atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata2: ATA channel at channel 0 on atapci0 ata3: ATA channel at channel 1 on atapci0 nexus0: syscons type unknown (no driver attached) Timecounter tick frequency 4 Hz quality 1000 Event timer tick frequency 4 Hz quality 1000 Timecounters tick every 1.000 msec ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: MAXTOR STM3160215A 3.AAD ATA-7 device ada0: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata3 bus 0 scbus1 target 0 lun 0 ada1: MAXTOR STM3160215A 3.AAD ATA-7 device ada1: 66.700MB/s transfers (UDMA4, PIO 8192bytes) ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad1 GEOM: ada0: adding VTOC8 information. GEOM_PART: integrity check failed (ada0, VTOC8) this is where it hangs, just like without setting kern.geom.part.check_integrity. Is this a regression? -- cheers, Ruben de Groot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How to bind a route to a network adapter and not IP
On Fri, Jun 15, 2012 at 07:54:52PM +0200, sth...@nethelp.no typed: Perhaps you can ask the very same question in another way so its easier to understand why you losing packets? All in all I always thought TCP/IP was the basic unit in Internet based networking but feel free to correct me if you have any news I might have missed... :) This is an old and well known problem, with no solution as of today (unless you want to run quagga/zebra or similar). With Cisco and Juniper (and probably lots of other big name) routers, if I create a static route pointing to a next hop on one interface, and the interface goes down (e.g. Ethernet cable is unplugged), 1. the static route is removed from the routing table. But then, when the interface later comes back up 2. the static route is reinstalled in the routing table. With FreeBSD point 1 above happens, but not point 2. I would love to have the functionality where FreeBSD would reinstall the route as in point 2 above. I think this is definitely the least surprising behavior (POLA), and should happen even without running an explicit routing system like quagga. This can be quite easily programmed with kqueue, use EVFILT_NETDEV for notices of interface up/down events and adjust the routing table accordingly. Big chance Cisco and Juniper are doing something similar. -- Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 'zfs send -i': destination has been modified
On Wed, Oct 20, 2010 at 08:32:33AM -0400, Dan Langille typed: I am trying to do a 'zfs send -i' and failing. This is my simple proof of concept test: Create the data # zfs create storage/a # touch /storage/a/1 # touch /storage/a/2 # touch /storage/a/3 Snapshot # zfs snapshot storage/a...@2010.10.19 send # zfs send storage/a...@2010.10.19 | zfs receive -v storage/compressed/a receiving full stream of storage/a...@2010.10.19 into storage/compressed/a...@2010.10.19 received 252KB stream in 2 seconds (126KB/sec) # Create one more file and snapshot that # touch /storage/a/4 # zfs snapshot storage/a...@2010.10.20 send it # zfs send -i storage/a...@2010.10.19 storage/a...@2010.10.20 | zfs receive -v storage/compressed/a receiving incremental stream of storage/a...@2010.10.20 into storage/compressed/a...@2010.10.20 received 250KB stream in 3 seconds (83.4KB/sec) What do we have? # find /storage/compressed/a /storage/compressed/a /storage/compressed/a/1 /storage/compressed/a/2 /storage/compressed/a/3 /storage/compressed/a/4 Of note: * FreeBSD 8.1-STABLE * ZFS filesystem version 4. * ZFS pool version 15. * zfs send is on compression off * zfs receive has compression on What I actually want to do and what fails: # zfs snapshot storage/bac...@2010.10.19 # zfs send storage/bac...@2010.10.19 | zfs receive -v storage/compressed/bacula receiving full stream of storage/bac...@2010.10.19 into storage/compressed/bac...@2010.10.19 received 4.38TB stream in 42490 seconds (108MB/sec) # zfs snapshot storage/bac...@2010.10.20 # zfs send -i storage/bac...@2010.10.19 storage/bac...@2010.10.20 | zfs receive -v storage/compressed/bacula receiving incremental stream of storage/bac...@2010.10.20 into storage/compressed/bac...@2010.10.20 cannot receive incremental stream: destination storage/compressed/bacula has been modified since most recent snapshot warning: cannot send 'storage/bac...@2010.10.20': Broken pipe I have no idea why this fails. Clues please? To my knowledge, the destination has not been written to. Has any read operation been done on the destination (ie: updated atime) ? Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Results of BIND RFC
On Fri, Apr 02, 2010 at 02:08:27PM -0400, Charles Sprickman typed: Can we do sendmail next April 1? Better yet, defer all questions about moving X out of the base system by referring to the Grand Discussion that'll take place *next year* on the first of april. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: stable-8 regression: time stands still
On Tue, Mar 02, 2010 at 09:36:32AM -0800, Jeremy Chadwick typed: On Tue, Mar 02, 2010 at 06:12:27PM +0100, Ruben de Groot wrote: On Tue, Mar 02, 2010 at 12:09:21PM +0100, C. P. Ghost typed: On Tue, Mar 2, 2010 at 9:43 AM, Ruben de Groot mai...@bzerk.org wrote: malenfant# sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-100) kern.timecounter.hardware: HPET Just a wild guess... but is HPET really enabled in the BIOS? Well, there's no such option in the BIOS. Just checked. It's btw an AMI BIOS. I'm totally unfamiliar with timecounter hardware, but after resetting the BIOS to factory settings (which I think it allready was, since I only change anything there when there is a real reason) the problem persists. The BIOS option could be labelled something like Multimedia Timer or High Prevision Event Timer. Each mainboard or BIOS manufacturer seems to have their own naming convention for it, though Wikipedia does shed some light on the confusion. I've looked through all options, without succes :( I'm going to get this kern.timecounter sysctl from the system booted with a 7.x livecd this evening. But really, I think this is a regression. Even if this system is the only one known to be affected (which I sincerely doubt). You can force a timecounter choice by setting it in /boot/loader.conf. I would recommend choosing ACPI-safe on your system to see if that improves things: kern.timecounter.hardware=ACPI-safe Thanks, that solved my issue. Allthough for correctness I must add that this line must be put in /etc/sysctl.conf; it does nothing in loader.conf. Also the sysctl can be run in multiuser and immediately fixed the problem. One question remains: why did this suddenly become a problem in FreeBSD 8 and not in FreeBSD 7. cheers, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: stable-8 regression: time stands still
Hi Ronald, On Mon, Mar 01, 2010 at 10:30:16PM +0100, Ronald Klop typed: Hi Ruben, Some shots in the dark. - Do you run powerd? Try to disable it. Not running powerd, it's a server - What is your output of 'sysctl kern.timecounter'? Maybe try setting another timecounter. malenfant# sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-100) kern.timecounter.hardware: HPET kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 16475 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 4294967295 kern.timecounter.tc.ACPI-safe.counter: 2418769071 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.HPET.mask: 4294967295 kern.timecounter.tc.HPET.counter: 4294967295 kern.timecounter.tc.HPET.frequency: 14318180 kern.timecounter.tc.HPET.quality: 900 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 36728411 kern.timecounter.tc.TSC.frequency: 2700107136 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1 Not sure what knobs to turn to set another timecounter or which one. Doesn't look like this is a documented course of action. What do you suggest? - Maybe you shouldn't name your computer 'ill child' in french. :-) Heheh! Didn't know the karma of a computer was influenced by its name ;) Malenfant btw is the main character in the manifold SF trilogy by Stephen Baxter. cheers, Ruben Ronald. On Mon, 01 Mar 2010 22:14:41 +0100, Ruben de Groot mai...@bzerk.org wrote: Forgot to mention. The kernel is GENERIC + IPFIREWALL* and IPDIVERT options; nothing else. I also build a RELEASE_8_0 kernel and it shows the same problems, so it's not just a recent -stable issue. On Mon, Mar 01, 2010 at 09:34:50PM +0100, Ruben de Groot typed: Hi, After upgrading my 7.2-PRERELEASE system to 8-stable I encountered some very strange problems, most obvious: - startup would hang on starting devd, only continuing after a ^C - reboot would hang, but reboot -q would work. - nfs clients would report strange locking problems. Now I've found that probably the real problem here is that NO TIME IS PASSING (!!). Successively calling 'date' will allways give me the exact same time to the second. A 'sleep 1' will hang indefinetely. The BIOS is OK. After (and only after) a reboot, time will be updated to the time of reboot, but stay there forever after. Before I go back to 7.2 (tested there are still no problems there with a livecd) maybe someone want to shed some light on this. I've attached dmesg.boot. cheers, Ruben Copyright (c) 1992-2009 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 8.0-RELEASE-p2 #6: Sun Feb 21 15:45:07 CET 2010 r...@malenfant.lan:/usr/obj/usr/src/sys/MALENFANT module_register: module g_label already exists! Module g_label failed to register: 17 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2700.11-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1958805504 (1868 MB) ACPI APIC Table: 090908 APIC1020 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: 090908 RSDT1020 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fff0, 10 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 77f0 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xc000-0xc0ff mem 0xf000-0xf7ff,0xfe9f-0xfe9f,0xfe80-0xfe8f irq 18 at device 5.0 on pci1
Re: stable-8 regression: time stands still
On Tue, Mar 02, 2010 at 12:09:21PM +0100, C. P. Ghost typed: On Tue, Mar 2, 2010 at 9:43 AM, Ruben de Groot mai...@bzerk.org wrote: malenfant# sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-100) kern.timecounter.hardware: HPET Just a wild guess... but is HPET really enabled in the BIOS? Well, there's no such option in the BIOS. Just checked. It's btw an AMI BIOS. I'm totally unfamiliar with timecounter hardware, but after resetting the BIOS to factory settings (which I think it allready was, since I only change anything there when there is a real reason) the problem persists. I'm going to get this kern.timecounter sysctl from the system booted with a 7.x livecd this evening. But really, I think this is a regression. Even if this system is the only one known to be affected (which I sincerely doubt). Ruben -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
stable-8 regression: time stands still
Hi, After upgrading my 7.2-PRERELEASE system to 8-stable I encountered some very strange problems, most obvious: - startup would hang on starting devd, only continuing after a ^C - reboot would hang, but reboot -q would work. - nfs clients would report strange locking problems. Now I've found that probably the real problem here is that NO TIME IS PASSING (!!). Successively calling 'date' will allways give me the exact same time to the second. A 'sleep 1' will hang indefinetely. The BIOS is OK. After (and only after) a reboot, time will be updated to the time of reboot, but stay there forever after. Before I go back to 7.2 (tested there are still no problems there with a livecd) maybe someone want to shed some light on this. I've attached dmesg.boot. cheers, Ruben Copyright (c) 1992-2009 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 8.0-RELEASE-p2 #6: Sun Feb 21 15:45:07 CET 2010 r...@malenfant.lan:/usr/obj/usr/src/sys/MALENFANT module_register: module g_label already exists! Module g_label failed to register: 17 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2700.11-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1958805504 (1868 MB) ACPI APIC Table: 090908 APIC1020 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: 090908 RSDT1020 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fff0, 10 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 77f0 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xc000-0xc0ff mem 0xf000-0xf7ff,0xfe9f-0xfe9f,0xfe80-0xfe8f irq 18 at device 5.0 on pci1 pcib2: ACPI PCI-PCI bridge at device 5.0 on pci0 pci2: ACPI PCI bus on pcib2 re0: RealTek 8101E/8102E/8102EL PCIe 10/100baseTX port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3400 re0: MAC rev. 0x miibus0: MII bus on re0 rlphy0: RTL8201L 10/100 media interface PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:1f:e2:6a:ac:35 re0: [FILTER] atapci0: ATI IXP600 SATA300 controller port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI v1.10 controller with 4 3Gbps ports, PM supported ata2: ATA channel 0 on atapci0 ata2: port is not ready (timeout 0ms) tfd = 01d0 ata2: software reset clear timeout ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: port is not ready (timeout 0ms) tfd = 01d0 ata3: software reset clear timeout ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] ohci0: OHCI (generic) USB controller mem 0xfe7fe000-0xfe7fefff irq 16 at device 19.0 on pci0 ohci0: [ITHREAD] usbus0: OHCI (generic) USB controller on ohci0 ohci1: OHCI (generic) USB controller mem 0xfe7fd000-0xfe7fdfff irq 17 at device 19.1 on pci0 ohci1: [ITHREAD] usbus1: OHCI (generic) USB controller on ohci1 ohci2: OHCI (generic) USB controller mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.2 on pci0 ohci2: [ITHREAD] usbus2: OHCI (generic) USB controller on ohci2 ohci3: OHCI (generic) USB controller mem 0xfe7fb000-0xfe7fbfff irq 17 at device 19.3 on pci0 ohci3: [ITHREAD] usbus3: OHCI (generic) USB controller on ohci3 ohci4: OHCI (generic) USB controller mem 0xfe7fa000-0xfe7fafff irq 18 at device 19.4 on pci0 ohci4: [ITHREAD] usbus4: OHCI (generic) USB controller on ohci4 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe7ff000-0xfe7ff0ff irq 19 at device 19.5 on pci0 ehci0: [ITHREAD] usbus5: EHCI version 1.0 usbus5: EHCI (generic) USB 2.0 controller on ehci0 pci0: serial
Re: stable-8 regression: time stands still
Forgot to mention. The kernel is GENERIC + IPFIREWALL* and IPDIVERT options; nothing else. I also build a RELEASE_8_0 kernel and it shows the same problems, so it's not just a recent -stable issue. On Mon, Mar 01, 2010 at 09:34:50PM +0100, Ruben de Groot typed: Hi, After upgrading my 7.2-PRERELEASE system to 8-stable I encountered some very strange problems, most obvious: - startup would hang on starting devd, only continuing after a ^C - reboot would hang, but reboot -q would work. - nfs clients would report strange locking problems. Now I've found that probably the real problem here is that NO TIME IS PASSING (!!). Successively calling 'date' will allways give me the exact same time to the second. A 'sleep 1' will hang indefinetely. The BIOS is OK. After (and only after) a reboot, time will be updated to the time of reboot, but stay there forever after. Before I go back to 7.2 (tested there are still no problems there with a livecd) maybe someone want to shed some light on this. I've attached dmesg.boot. cheers, Ruben Copyright (c) 1992-2009 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 8.0-RELEASE-p2 #6: Sun Feb 21 15:45:07 CET 2010 r...@malenfant.lan:/usr/obj/usr/src/sys/MALENFANT module_register: module g_label already exists! Module g_label failed to register: 17 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ (2700.11-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x60fb2 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 1958805504 (1868 MB) ACPI APIC Table: 090908 APIC1020 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: 090908 RSDT1020 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fff0, 10 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 77f0 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xc000-0xc0ff mem 0xf000-0xf7ff,0xfe9f-0xfe9f,0xfe80-0xfe8f irq 18 at device 5.0 on pci1 pcib2: ACPI PCI-PCI bridge at device 5.0 on pci0 pci2: ACPI PCI bus on pcib2 re0: RealTek 8101E/8102E/8102EL PCIe 10/100baseTX port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x3400 re0: MAC rev. 0x miibus0: MII bus on re0 rlphy0: RTL8201L 10/100 media interface PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:1f:e2:6a:ac:35 re0: [FILTER] atapci0: ATI IXP600 SATA300 controller port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI v1.10 controller with 4 3Gbps ports, PM supported ata2: ATA channel 0 on atapci0 ata2: port is not ready (timeout 0ms) tfd = 01d0 ata2: software reset clear timeout ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: port is not ready (timeout 0ms) tfd = 01d0 ata3: software reset clear timeout ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] ohci0: OHCI (generic) USB controller mem 0xfe7fe000-0xfe7fefff irq 16 at device 19.0 on pci0 ohci0: [ITHREAD] usbus0: OHCI (generic) USB controller on ohci0 ohci1: OHCI (generic) USB controller mem 0xfe7fd000-0xfe7fdfff irq 17 at device 19.1 on pci0 ohci1: [ITHREAD] usbus1: OHCI (generic) USB controller on ohci1 ohci2: OHCI (generic) USB controller mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.2 on pci0 ohci2: [ITHREAD] usbus2: OHCI (generic) USB controller on ohci2 ohci3: OHCI (generic) USB controller mem 0xfe7fb000-0xfe7fbfff irq 17 at device 19.3 on pci0 ohci3: [ITHREAD] usbus3: OHCI (generic) USB
devd hang after upgrade to 8.0-STABLE
Just wondering if others have seen this too. Yesterday, after upgrading from 7.2-stable to 8.0-stable, my server would hang on startup on the Starting devd line. bootverbose did not get me any more information, and I had to manually hit ^C or ^\ to continue booting. Also, the reboot command will hang after killing syslogd. Only a reboot -q will actually reboot the system. Now, I've disabled devd in rc.conf, but this is not an ideal configuration for me. Any hints on how to further debug this? cheers, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, Jan 23, 2010 at 10:43:49PM +1030, Daniel O'Connor typed: On Sat, 23 Jan 2010, Ruben de Groot wrote: On Sat, Jan 23, 2010 at 01:23:28AM +, Adrian Wontroba typed: I concur that the 235 MB size of an amd64 8.0 kernel is a bit of a surprise. An i386 kernel is a mere 135 MB. IMO increasing the sysinstall default root slice size for at least amd64 would be a good thing. To be a little more precise: it's not the kernel that is so big. It's all the (mostly not needed) modules and symbol files that fill up / Maybe they could be put somewhere else.. I don't think you need them unless remote debugging and in that case you are multiuser (I would have thought anyway). If they went into /usr then /boot could remain slim. But what if you have /usr on a gmirror, glabel, zfs filesystem or any other device that is not compiled in your kernel? Sure you can build a custom kernel, but I would expect a lot of questions, frustrations and footshooting from such a change. I think increasing / (again) would be the least painfull. Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-RELEASE - -STABLE and size of /
On Sat, Jan 23, 2010 at 01:23:28AM +, Adrian Wontroba typed: I concur that the 235 MB size of an amd64 8.0 kernel is a bit of a surprise. An i386 kernel is a mere 135 MB. IMO increasing the sysinstall default root slice size for at least amd64 would be a good thing. To be a little more precise: it's not the kernel that is so big. It's all the (mostly not needed) modules and symbol files that fill up / ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make buildkernel failing on zfs
On Fri, Jan 22, 2010 at 10:40:17AM +0100, Christer Solskogen typed: On Fri, Jan 22, 2010 at 9:56 AM, Colin free...@southportcomputers.co.uk wrote: Anyone got any pointers? Could you post your /etc/make.conf? That said, I recon you build your kernel in a rather wierd way. Delete /usr/obj/* and run make cleandir make cleandir in /usr/src. Then Bit redundant ;) cleandir only effects /usr/obj, which you just blew away. Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-questions mailing list
On Wed, Dec 16, 2009 at 08:53:43AM -0500, Glen Barber typed: On Wed, Dec 16, 2009 at 7:41 AM, Jamie Griffin j...@koderize.com wrote: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ Sign me up for a me too. The last message from that list in my mailbox is the (overly drawn out) Root Exploit thread. Yup, I noticed this too. Last message in the archives is from Sun Dec 13 17:10:40 UTC 2009 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-questions mailing list
On Wed, Dec 16, 2009 at 10:46:13AM -0500, Lowell Gilbert typed: Jamie Griffin j...@koderize.com writes: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ I asked the postmaster, and got a reply that the reply isn't really well understood yet. I don't know mailman that well, or I'd've volunteered to help out. Mailman's not rocket science. And the list is offline now for 3 days! I volunteer! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-BETA2 on soekris discarding packets?
Hi, I'm trying 8.0-BETA2 on a 4511 soekris board, but found a problem. Outgoing networking is fine, but it looks like incoming connections are silently discarded. No firewall is configured. Here's a tcpdump of normal outgoing DNS traffic (IP address of the soekris is 192.168.179.15): listening on sis0, link-type EN10MB (Ethernet), capture size 96 bytes 10:33:50.053875 IP 192.168.179.15.23093 ei.lan.domain: 45893+ PTR? 255.179.168.192.in-addr.arpa. (46) 10:33:50.055038 IP ei.lan.domain 192.168.179.15.23093: 45893 NXDomain* 0/1/0 (109) 10:33:50.066917 IP 192.168.179.15.13890 ei.lan.domain: 45894+ PTR? 9.179.168.192.in-addr.arpa. (44) 10:33:50.067834 IP ei.lan.domain 192.168.179.15.13890: 45894* 1/1/1 (113) And here's a dump of an incoming ssh connection: listening on sis0, link-type EN10MB (Ethernet), capture size 96 bytes 10:26:40.176756 IP ei.lan.55742 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 1961056657 ecr 0,sackOK,eol], length 0 10:26:43.175176 IP ei.lan.55742 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 1961059657 ecr 0,sackOK,eol], length 0 10:26:46.374688 IP ei.lan.55742 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 1961062857 ecr 0,sackOK,eol], length 0 10:26:49.574197 IP ei.lan.55742 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,sackOK,eol], length 0 10:26:52.773759 IP ei.lan.55742 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,sackOK,eol], length 0 Et cetera. No replies. This goes for all tcp ports, but ping works. nmap from another host says: # nmap soekris Starting Nmap 4.85BETA7 ( http://nmap.org ) at 2009-09-08 13:31 CEST All 1000 scanned ports on 192.168.179.15 are filtered MAC Address: 00:00:24:CB:93:28 (Connect AS) Nmap done: 1 IP address (1 host up) scanned in 21.67 seconds Anyone else seeing this? Ruben kernel config is below. include GENERIC cpu I486_CPU cpu I586_CPU ident SOEKRIS machine i386 options CPU_ELAN options CPU_SOEKRIS options HZ=150 #options CPU_ELAN_XTAL options CPU_GEODE ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Going to BSD 8 from RELENG_7
On Mon, Aug 17, 2009 at 09:18:11AM +0200, Bartosz Stec typed: And as usual MAKE A GOOD BACKUP Regards, Johan As I remember when I did upgrade from FreBSD 6.4 to 7.0, I ran 'portupgrade -afi' after thar, BUT as I remember all my ports in fact works before they were upgraded. If I understand correctly, the reason of this was not making delete-old and delete-old-libs? So should following upgrade procedure be painless? 0. Backup! 1. cvsup 8.0-stable 2. make buildworld make buildkernel 3. make installkernel 4. reboot and jump to single user mode 5. make installworld mergemastger 6. take a deep breath reboot 7. portupgrade -afi 8. make delete-old make delete-old-libs 9. reboot 10. Hooray! My concern is - will my ports works after point 6. ? Quite important thing when machine can't be offline by hours during portupgrade -afi What do you want to hear? Yes, all will be fine ? There's never such guarantee. If it means that much to you, MAKE A GOOD BACKUP. And be prepared to restore it. And if the machine really can't be offline for some hours, you should have a fallback machine anyway which you could use to test it on. cheers, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is /boot/kernel/*.symbols?
On Tue, Jul 07, 2009 at 07:29:24PM +0300, Dan Naumov typed: On Tue, Jul 7, 2009 at 7:09 PM, Rick C. Pettyrick-freebsd2...@kiwi-computer.com wrote: On Tue, Jul 07, 2009 at 11:24:51AM +0200, Ruben de Groot wrote: On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed: On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote: On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed: Right, so it's a lot bigger on amd64. ?I guess those 64-bit pointers aren't entirely free. :) I'm not sure where the size difference comes from. I have some sparc64 systems running -current with symbols and the size of /boot/kernel is more comparable to i386, even with the 8-byte pointer size: Um, probably there are a lot of devices on amd64 that aren't available for sparc64? Yes, That's probably it. It was just a theory; I don't have sparc64. ?What's your output of ls -1 /boot/kernel | wc? -- Rick C. Petty atom# uname -a FreeBSD atom.localdomain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 atom# ls -1 /boot/kernel | wc 10111011 15243 On sparc: morninglightmountain# uname -pr 8.0-CURRENT sparc64 morninglightmountain# ls /boot/kernel | wc 853 853 13045 morninglightmountain# wc -l /usr/src/sys/sparc64/conf/GENERIC /usr/src/sys/amd64/conf/GENERIC 247 /usr/src/sys/sparc64/conf/GENERIC 322 /usr/src/sys/amd64/conf/GENERIC 569 total So, fewer drivers and also less devices in GENERIC, as might be expected. regards, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is /boot/kernel/*.symbols?
On Mon, Jul 06, 2009 at 04:20:45PM -0500, Rick C. Petty typed: On Mon, Jul 06, 2009 at 11:39:04AM +0200, Ruben de Groot wrote: On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed: Right, so it's a lot bigger on amd64. I guess those 64-bit pointers aren't entirely free. :) I'm not sure where the size difference comes from. I have some sparc64 systems running -current with symbols and the size of /boot/kernel is more comparable to i386, even with the 8-byte pointer size: Um, probably there are a lot of devices on amd64 that aren't available for sparc64? Yes, That's probably it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is /boot/kernel/*.symbols?
On Sun, Jul 05, 2009 at 12:38:34AM +0100, Ian J Hart typed: I just had an installworld fail due to this (/rescue). Given that many people will have chosen the default root size offered by sysinstall a different build default would seem prudent. In any case sysinstall needs to be updated (1GB?). Let's not put off new users anymore than we have to. The default root partition created by sysinstall (provided the disk is large enough) is 512 MB, which is more than enough. #define ROOT_DEFAULT_SIZE 512 Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: What is /boot/kernel/*.symbols?
On Mon, Jul 06, 2009 at 10:46:50AM +0200, Dimitry Andric typed: On 2009-07-06 10:41, Dan Naumov wrote: atom# uname -a FreeBSD atom.localdomain 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 9 18:02:21 UTC 2009 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 atom# du -hs /boot/kernel* 205M/boot/kernel Right, so it's a lot bigger on amd64. I guess those 64-bit pointers aren't entirely free. :) I'm not sure where the size difference comes from. I have some sparc64 systems running -current with symbols and the size of /boot/kernel is more comparable to i386, even with the 8-byte pointer size: uname -p sparc64 du -sk /boot/kernel 137918 /boot/kernel So indeed, on amd64 and possibly some other 'big' architectures (ia64?), cranking the default root filesystem size to e.g. 1024M would be nice. Indeed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Upgrade from 7.1-RELEASE to 7.2-RELEASE through freebsd update
On Thu, Jun 18, 2009 at 10:34:54AM +0200, Erwan David typed: I tried to upgrade my 7.1-RELEASE into 7.2-RELEASE. However freebsd-update kept asking me to merge every file in /etc whose $Id$ line changed (that makes about all files). Is there a way, as with mergemaster, to make it not consider the $Id$ line for the manual merge ? You could let freebsd-update ignore /etc (but not /usr/src) and use mergemaster for your configuration files. Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem when compiling stable FreeBSD kernel
On Tue, May 19, 2009 at 12:59:46PM +0200, Laurent Grangeau typed: Hi ! I'm new on FreeBSD and I have some troubles with an option in the kernel config. I was reading http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/consoles.html#CONSOLES-VIDCONTROLto increase the resolution of my console. So I put this two options in my kernel config file : options VESA options SC_PIXEL_MODE And when I try to compile it, it says that option VESA is not recognise. Is it normal ? I'm using the stable kernel on an AMD64 cpu. (I'm not on my computer now, so I can't send you my conf file, and the error, but I will do it tonight.) Last time I checked, VESA was i386 (32 bit) only. Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sysinstall automatic partition labelling/sizing problem
/boot/kernel is ~118 MB on my system (including debugging symbols). Default size of the root partition created by sysinstall is 512 MB, in your case downsized to 360 to accomodate other partitions on your 8GB disk. Should still be enough though. Do you have any other big files hanging around in your root partition? Ruben On Wed, Dec 03, 2008 at 03:42:04PM +0900, Nathan Butcher typed: Automatic labelling on 7.0 created about 360MB for my root partition on a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition was exhausted during the installkernel. Maybe automatic labelling in sysinstall needs to allocate more than 360MB in the root (/) partition if it's going to stay big enough to accomodate a buildkernel and installkernel from source. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [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: du and df don't agree
On Mon, Nov 10, 2008 at 11:21:11PM +0700, Eugene Grosbein typed: On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: Why would du show 630k used by /tmp while df show 161M used by /tmp? I have run fstat /tmp and can't find any files that are using the space that df is claiming as being used. You need lsof +aL1 /tmp to see an answer. Please don't advise people to install third party apps (lsof) where base system tools (fstat) can do the job. Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: du and df don't agree
On Tue, Nov 11, 2008 at 10:22:42AM +0100, Willem Jan Withagen typed: Ruben de Groot wrote: On Mon, Nov 10, 2008 at 11:21:11PM +0700, Eugene Grosbein typed: On Mon, Nov 10, 2008 at 11:01:00AM -0500, Stephen Clark wrote: Why would du show 630k used by /tmp while df show 161M used by /tmp? I have run fstat /tmp and can't find any files that are using the space that df is claiming as being used. You need lsof +aL1 /tmp to see an answer. Please don't advise people to install third party apps (lsof) where base system tools (fstat) can do the job. Why not? Because it gives the impression the base system is incomplete, which it is not, at least not in this situation. The wording you need lsof is plain wrong. This is one of the ways I pick up on all kinds of nice tools I've not heard of before. And it is not like this is swamping the list with of topic questions. Difference of opinion; I prefer to use FreeBSD tools before falling back to 3rd party tools, no matter how nice. You might have redirected the question to questions@ I don't see the point. Why didn't you redirect it? OTOH The initial question indicated that fstat did not give the info wanted. Your info does not help, because you told him to use fstat, but forgot to mention HOW. So he is in no way any wiser after your answer. Yes, my bad. But he allready found the answer himself (using fstat -f I guess). Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Fri, Sep 05, 2008 at 01:24:49PM +0200, Kai Otto typed: I think someone mentioned it earlier, but I'm not shure. IMHO it would _be_ nice if there's a HTML-browser in the standard installation (with option to not install it in sysinstall). I say HTML and not web because I think about the /usr/share/doc .html-documentation. If someone really has no Internet-connection as mentioned before he/she isn't able to read the handbook, which IMHO is a very important part of FreeBSD. There are great manpages and exaple files, but the best explanations are in the handbook. Isn't that why we have: /usr/share/doc/handbook/book.txt ?? Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Panics in kern_timeout.c (7-STABLE)
Hi,
I've experienced 2 panics in the last couple of days after upgrading to
7-stable sources of about 2 weeks ago:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x9608
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc05f095f
stack pointer = 0x28:0xd4ceec80
frame pointer = 0x28:0xd4ceecbc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 13 (swi4: clock sio)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 3d6h24m45s
Physical memory: 503 MB
Dumping 96 MB: 81 65 49 33 17 1
#0 doadump () at pcpu.h:195
195 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) list *0xc05f095f
0xc05f095f is in softclock (/usr/src/sys/kern/kern_timeout.c:203).
198 curticks = softticks;
199 bucket = callwheel[curticks callwheelmask];
200 c = TAILQ_FIRST(bucket);
201 while (c) {
202 depth++;
203 if (c-c_time != curticks) {
204 c = TAILQ_NEXT(c, c_links.tqe);
205 ++steps;
206 if (steps =
MAX_SOFTCLOCK_STEPS) {
207 nextsoftcheck = c;
The backtrace doesn't look very informative to me, but I'll include it
here for completeness:
(kgdb) bt
#0 doadump () at pcpu.h:195
#1 0xc05de987 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc05dec49 in panic (fmt=Variable fmt is not available.) at
/usr/src/sys/kern/kern_shutdown.c:572
#3 0xc08961cc in trap_fatal (frame=0xd4ceec40, eva=38408) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0896b4f in trap (frame=0xd4ceec40) at /usr/src/sys/i386/i386/trap.c:280
#5 0xc087cb8b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc05f095f in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:202
#7 0xc05bf55b in ithread_loop (arg=0xc2997280) at
/usr/src/sys/kern/kern_intr.c:1036
#8 0xc05bc339 in fork_exit (callout=0xc05bf3b0 ithread_loop, arg=0xc2997280,
frame=0xd4ceed38) at /usr/src/sys/kern/kern_fork.c:783
#9 0xc087cc00 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205
Can anyone offer a hand in how to debug this further?
cheers,
Ruben
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
sunlabel trouble
Hi, This is on 6.2-STABLE, updated last week. I've added a new ~250 GB disc to my netra X1. It's working OK but somehow sunlabel is unwilling to install the bootstrap code on the disc because of some sizing issue with the c partition (whole disk). Even though sysinstall let me partition the disc just fine for some reason it has made the c partition way too small, causing the sunlabel -B command to error out. Any tips? ad1: 238475MB WDC WD2500JB-00REA0 20.00K20 at ata3-master UDMA66 # sunlabel -nB ad1 sunlabel: partition f extends past end of disk sunlabel: invalid label # # sunlabel ad1 # /dev/ad1: text: FreeBSD233G cyl 25767 alt 2 hd 16 sec 63 bytes/sector: 512 sectors/cylinder: 1008 sectors/unit: 25973136 8 partitions: # # Size is in sectors. # Offset is in cylinders. #size offset #-- -- a:1049328 0 b:4195296 1041 c: 25973136 0 d:4195296 5203 e:1049328 9365 f: 16778160 10406 g: 461127744 27051 cheers, Ruben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0-BETA1: Fatal trap 18 in ata_raid_promise_read_meta
This is an nForce4 chipset (Gigabyte GA-K8NF-9). Installation from the iso disc1 is fine, but at the first boot I get dropped in the debugger: ad0: 28620MB ExcelStor Technology ES3230 ES7CA24G at ata0-master UDMA66 Fatal trap 18: integer divide fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0x8022fb5a stack pointer = 0x10:0x809d8940 frame pointer = 0x10:0x809d89a0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0 ] Stopped at ata_raid_promise_read_meta+0x9a:divq%rsi,%eax db tr Tracing pid 0 tid 0 td 0x80811e40 ata_raid_promise_read_meta() at ata_raid_promise_read_meta+0x9a ata_raid_read_metadata() at ata_raid_read_metadata+0x29b ata_raid_subdisk_attach() at ata_raid_subdisk_attach+0x27 device_attach() at device_attach+0x292 bus_generic_attach() at bus_generic_attach+0x18 ad_attach() at ad_attach+0x37e device_attach() at device_attach+0x292 bus_generic_attach() at bus_generic_attach+0x18 ata_identify() at ata_identify+0xe6 ata_boot_attach() at ata_boot_attach+0x42 run_interrupt_driven_config_hooks() at run_interrupt_driven_config_hooks+0x2a mi_startup() at mi_startup+0xd3 btext() at btext+0x2c db Full console messages: /boot.config: -hConsoles: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 638kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Tue Jul 12 07:18:27 UTC 2005) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x546b40 data=0xac448+0xdd2e8 syms=[0x8+0x8d4e0+0x8+0x75380] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... \GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2005 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 6.0-BETA1 #0: Tue Jul 12 09:02:51 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1809.28-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20ff0 Stepping = 0 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,b25,LM,3DNow+,3DNow real memory = 536805376 (511 MB) avail memory = 506187776 (482 MB) ACPI APIC Table: Nvidia AWRDACPI ioapic0 Version 1.1 irqs 0-23 on motherboard acpi0: Nvidia AWRDACPI on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR pci_link0: ACPI PCI Link LNK1 irq 11 on acpi0 pci_link1: ACPI PCI Link LNK2 on acpi0 pci_link2: ACPI PCI Link LNK3 irq 10 on acpi0 pci_link3: ACPI PCI Link LNK4 on acpi0 pci_link4: ACPI PCI Link LNK5 on acpi0 pci_link5: ACPI PCI Link LUBA irq 11 on acpi0 pci_link6: ACPI PCI Link LUBB on acpi0 pci_link7: ACPI PCI Link LMAC on acpi0 pci_link8: ACPI PCI Link LACI irq 12 on acpi0 pci_link9: ACPI PCI Link LMCI on acpi0 pci_link10: ACPI PCI Link LSMB irq 10 on acpi0 pci_link11: ACPI PCI Link LUB2 irq 5 on acpi0 pci_link12: ACPI PCI Link LIDE on acpi0 pci_link13: ACPI PCI Link LSID on acpi0 pci_link14: ACPI PCI Link LFID on acpi0 pci_link15: ACPI PCI Link LPCA on acpi0 pci_link16: ACPI PCI Link APC1 irq 0 on acpi0 pci_link17: ACPI PCI Link APC2 irq 0 on acpi0 pci_link18: ACPI PCI Link APC3 irq 0 on acpi0 pci_link19: ACPI PCI Link APC4 irq 0 on acpi0 pci_link20: ACPI PCI Link APC5 irq 16 on acpi0 pci_link21: ACPI PCI Link APCF irq 0 on acpi0 pci_link22: ACPI PCI Link APCG irq 0 on acpi0 pci_link23: ACPI PCI Link APCH irq 0 on acpi0 pci_link24: ACPI PCI Link APCJ irq 0 on acpi0 pci_link25: ACPI PCI Link APCK irq 0 on acpi0 pci_link26: ACPI PCI Link APCS irq 0 on acpi0 pci_link27: ACPI PCI Link APCL irq 0 on acpi0 pci_link28: ACPI PCI Link APCZ irq 0 on acpi0 pci_link29: ACPI PCI Link APSI irq 0 on acpi0 pci_link30: ACPI PCI Link APSJ irq 0 on acpi0 pci_link31: ACPI PCI Link APCP irq 0 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci_link26: Unable to choose an IRQ pci_link21: Unable to choose an IRQ pci_link27: Unable to choose an IRQ pci_link24: Unable to choose an IRQ pci0: memory at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus
Re: Mounting a filesystem-in-a-file via fstab? (md/mfs)
On Mon, Mar 21, 2005 at 11:42:05AM +0100, Raphael H. Becker typed:
Hi *,
I recently tried to move my newsspool into a seperate filesystem in a
flatfile and mounted it as a md device. Works perfectly with hands-on,
but there doesn't seem to exist a proper way to do this during startup
(/etc/fstab).
Actually I have this line in /etc/fstab, but everytime that filesystem
is mounted via fstab, it will be formatted using newfs:
md /var/spool/news mfs rw,-F/data/spool_news.ufs,-U 0 0
How do I disable the newfs from mount_mfs?
Is there any proper way in the bootscripts, to set up md-devices and
mount them automatically? It should even destroy /dev/md${n} on umount.
Any solutions? TIA.
There's a PR (and patch) on this issue. It was about to be committed
somewhere in November, but unfortunately not yet.
http://www.freebsd.org/cgi/query-pr.cgi?pr=57641
Ruben
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Change IP address
On Tue, Oct 26, 2004 at 11:18:22AM -0400, Willie Winslow typed: I need to change the IP address of my FreeBSD box, it is also our Name Server. I am aware that I need to change the following; /etc/rc.conf /etc/resolv.conf /etc/namedb/mydomain.com Is there anything else that needs to be changed? The nameserver configuration on all your clients :-) I hope you have DHCP ;) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newbie question - users deleted after playing with sysinstall
On Tue, Jun 08, 2004 at 11:38:13AM +0300, Haim Ashkenazi typed: Hi I've just finished install FreeBSD 4.10 for the first time. I'm an experienced linux user, but have no experience with FreeBSD. after a very basic installation (only the first step, to get ssh) I've put the computer at my ISP (of-course everything is blocked by a firewall) and continued from home. I then installed some packages from the Distribution menu, and played with the menus to see what I can configure. today, I couldn't login to the computer (ssh), and when I checked (I had someone there who logged in locally) I found out root has no password and the regular user I created was gone. my question is: could something I've done in sysinstall delete the user and root password? it's not likely that someone broke into the system because it's completely blocked (only open from my IP). Yes, that very likely. For instance, if you install the bin distribution more than once, it'll overwrite all files in /etc, including master.passwd each time you do that. Ruben thanx -- Haim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PR 37395 - even with NO_SENDMAIL=true, /usr/sbin/sendmail overwritten
On Wed, Dec 04, 2002 at 07:28:24AM -0800, Michael Sierchio typed: What's the deal with this? This puppy broke a couple of my machines by overwriting /var/qmail/bin/sendmail via the symlink in /usr/sbin. Ack. Pppt. /usr/sbin/sendmail should be a symlink to /usr/sbin/mailwrapper. You can use mailer.conf(5) to point to your MTA. Example /etc/mail/mailer.conf: sendmail/var/qmail/bin/sendmail send-mail /var/qmail/bin/sendmail mailq /var/qmail/bin/sendmail newaliases /var/qmail/bin/sendmail There should be a single switch to disable sendwhale. I'll reiterate that the make.conf switches are no substitute for packagizing the ever-more-bloated base system. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
burncd - resetting devices
Hi, Last time I used burncd on this machine was before the ata mfc. Now when I try burning a .iso image I get: Jul 28 18:44:38 ei /kernel: acd0: READ_TRACK_INFO command timeout - resetting Jul 28 18:44:38 ei /kernel: ata1: resetting devices .. ata1-slave: ATAPI identif y retries exceeded Jul 28 18:44:38 ei /kernel: done Jul 28 18:45:54 ei /kernel: acd0: WRITE_BIG command timeout - resetting Jul 28 18:45:54 ei /kernel: ata1: resetting devices .. done And the command hangs forever. I cannot even kill -9 it. This box was build with sources of juli 4 2002. Now I wonder about the ata1-slave: ATAPI identify retries exceeded; there's nothing on ata1-slave. Here's the relevant parts of dmesg: ruben@ei$ dmesg|egrep 'ata|ATA' atapci0: VIA 82C686 ATA100 controller port 0x9000-0x900f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: Promise ATA100 controller port 0xbc00-0xbc3f,0xb800-0xb803,0xb400-0xb407,0xb000-0xb003,0xac00-0xac07 mem 0xdf00-0xdf01 irq 5 at device 12.0 on pci0 ata2: at 0xac00 on atapci1 ata3: at 0xb400 on atapci1 ata1-slave: ATAPI identify retries exceeded ad0: 39083MB Maxtor 5T040H4 [79408/16/63] at ata0-master UDMA100 ar0: 38172MB ATA RAID1 array [4866/255/63] status: READY subdisks: 0 READY ad4: 38172MB MAXTOR 6L040J2 [77557/16/63] at ata2-master UDMA33 1 READY ad6: 38172MB MAXTOR 6L040J2 [77557/16/63] at ata3-master UDMA33 acd0: CD-R CR-2801TE at ata1-master PIO3 ata1: resetting devices .. ata1-slave: ATAPI identify retries exceeded ata1: resetting devices .. done Any suggestions? thanks, Ruben To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make world considered harmful
On Mon, Jul 22, 2002 at 08:38:50AM -0400, Brian T. Schellenberger typed: On Monday 22 July 2002 07:41 am, Jamie Bowden wrote: | On Sun, 21 Jul 2002, Barney Wolff wrote: | :When is make world the right thing to do? If the answer is never | :then why don't we remove it from /usr/src/Makefile? Its availability | :just leads people into trouble. | | Since when? I use it regularly after CVSupdating /usr/src, works fine. It's definately not recommended even if it will sometimes work. It causes you to try to start running with the new world while still running the older kernel. (Or, I guess, you could follow the sequence make kernel, reboot, make world, mergemaster. That sequence would seem relatively safe, I guess.) Save, but not supported. You must buildworld before you can buildkernel. | | Jamie Bowden -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) http://www.babbleon.org http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.6 Release?
On Sun, Jun 09, 2002 at 10:47:47AM -0600, Korey Pelton typed: Carl, Yesterday evening, I exchanged the line *default tag=RELENG_4_5 with *default tag=RELENG_4_6 and cvsup looked like it added a bunch of stuff, so I assume 4.6 is good to go. I am a newbie, so if anything I say sounds rediculous, please say so. When I tried to buildworld, however, I got an error saying that pam_ssh.c cannot find the file log.h, so I don't know what is up with that. Is anyone else getting this error? I got the same error after trying to do a make cleandir twice and re-cvsuping. RELENG_4_5 are security related patches against the sources of 4.5-RELEASE. You must first update to 4.6-RELEASE (which has not yet been released) before you can start following RELENG_4_6. I think you might have messed up your source tree. Beter re-install the 4.5 sources and cvsup RELENG_4_5 again, or wait a few days and install 4.6 when it comes out. hope this helps. Korey Pelton From: Carl Petersen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: 4.6 Release? Date: Sun, 9 Jun 2002 10:11:18 -0400 MIME-Version: 1.0 Received: from [216.136.204.119] by hotmail.com (3.2) with ESMTP id MHotMailBECCAD1A001B40043161D888CC775B900; Sun, 09 Jun 2002 07:11:40 -0700 Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18])by mx2.freebsd.org (Postfix) with ESMTPid E96E155464; Sun, 9 Jun 2002 07:11:28 -0700 (PDT)(envelope-from [EMAIL PROTECTED]) Received: by hub.freebsd.org (Postfix, from userid 538)id 7B52237B407; Sun, 9 Jun 2002 07:11:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org (Postfix) with SMTPid 3151B2E800D; Sun, 9 Jun 2002 07:11:24 -0700 (PDT) Received: by hub.freebsd.org (bulk_mailer v1.12); Sun, 9 Jun 2002 07:11:24 -0700 Received: from mail.san.yahoo.com (mail.san.yahoo.com [209.132.1.30])by hub.freebsd.org (Postfix) with ESMTP id 7420837B403for [EMAIL PROTECTED]; Sun, 9 Jun 2002 07:11:22 -0700 (PDT) Received: from ender (24.61.89.45) by mail.san.yahoo.com (6.5.017.1) id 3D030B647F4F for [EMAIL PROTECTED]; Sun, 9 Jun 2002 07:10:52 -0700 From [EMAIL PROTECTED] Sun, 09 Jun 2002 07:11:52 -0700 Delivered-To: [EMAIL PROTECTED] Message-ID: 006f01c20fbf$86ab0400$0800a8c0@ender X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600. X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600. Sender: [EMAIL PROTECTED] List-ID: freebsd-stable.FreeBSD.ORG List-Archive: http://docs.freebsd.org/mail/ (Web Archive) List-Help: mailto:[EMAIL PROTECTED]?subject=help (List Instructions) List-Subscribe: mailto:[EMAIL PROTECTED]?subject=subscribe%20freebsd-stable List-Unsubscribe: mailto:[EMAIL PROTECTED]?subject=unsubscribe%20freebsd-stable X-Loop: FreeBSD.ORG Precedence: bulk Anybody have up to date info on the 4.6 release. Web site says yesterday. img SRC=http://life.VisualRevolutions.com/bio.php height=1 width 1 border=0brHello, a href=http://www.VisualRevolutions.com/vr.htm?BioPChave a nice day!!/a _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: For Review: sendmail 8.12.2 import into -STABLE
I just followed your instructions and now I have sendmail 8.12.2 running. I encountered no problems whatsoever. Excellent work ! cheers, Ruben Gregory Neil Shapiro [EMAIL PROTECTED] wrote: I am seeking volunteers to review and test the infrastructure changes needed to import sendmail 8.12.2 into FreeBSD (-STABLE). If you are interested in helping, please visit: http://people.freebsd.org/~gshapiro/STABLE-8.12.2 and following the instructions there. Please report any successes or failures to me directly. My goal is to commit these patches this weekend or the beginning of next week depending on the feedback I receive. Positive testing feedback will push it earlier, negative testing feedback may delay it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
