Re: statd/lockd startup failure
On Wed, Feb 9, 2011 at 9:20 AM, wrote: > Under 8.2-PRERELEASE (GENERIC kernel), about 15% of the times I boot up > (with rpc.statd and rpc.lockd enabled in rc.conf), I get: > > Feb 4 07:31:11 wonderland rpc.statd: bindresvport_sa: Address already in use > Feb 4 07:31:11 wonderland root: /etc/rc: WARNING: failed to start statd > > and slightly later: > > Feb 4 07:31:36 wonderland kernel: NLM: unexpected error contacting NSM, > stat=5, errno=35 > > I can start rpc.statd and rpc.lockd manually at this point (and I have to > start them to run firefox and mail with my NFS-mounted home directory and > mail spool). But what might cause the above errors? -- George Mitchell > > ___ > 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" > Don't rpc.statd and lockd try to choose a random port upon startup? I seem to remember a similar problem I had a long time ago. I opted to use a consistent, not-used port and haven't seen the problem since (this was years ago, so I can't remember if the error you're seeing was identical to mine). /etc/rc.conf: rpc_statd_flags="-p 898" rpc_lockd_flags="-p 4045" -Proto ___ 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"
correct way to setup gmirror on 7.4?
I'm migrating away from my old pseudo-RAID partitions to GEOM gmirror and I have some questions on the right way to accomplish this. I've got two new 1TB disks that I'm setting up for the new mirror, and unfortunately they're Western Digital drives with 4k sectors that report themselves as 512b. Here's what I'm currently doing to setup this array. The disks are detected as ad4 and ad6 on my FreeBSD 7.4 server. # initialize/wipe MBR dd if=/dev/zero of=/dev/ad4 bs=512 count=79 dd if=/dev/zero of=/dev/ad6 bs=512 count=79 # gpart gpart create -s gpt ad4 gpart create -s gpt ad6 gpart bootcode -b /boot/pmbr ad4 gpart bootcode -b /boot/pmbr ad6 # add partitions gpart add -t freebsd-ufs -l raidhome1-2 -b 2048 -s 195330048 ad4 gpart add -t freebsd-ufs -l raidhome2-2 -b 2048 -s 195330048 ad6 gpart add -t freebsd-ufs -l raidvault1-2 -b 195338240 -s 1758167040 ad4 gpart add -t freebsd-ufs -l raidvault2-2 -b 195338240 -s 1758167040 ad6 (I'm using these partition start values because they divide evenly into 4k blocks. I don't mind wasting a few MB on each disk to have correctly-aligned partitions) gpart show ad4 =>34 1953525101 ad4 GPT (932G) 342014 - free - (1.0M) 2048 1953300481 freebsd-ufs (93G) 1953320966144 - free - (3.0M) 195338240 17581670402 freebsd-ufs (838G) 1953505280 19855 - free - (9.7M) gpart show ad6 =>34 1953525101 ad6 GPT (932G) 342014 - free - (1.0M) 2048 1953300481 freebsd-ufs (93G) 1953320966144 - free - (3.0M) 195338240 17581670402 freebsd-ufs (838G) 1953505280 19855 - free - (9.7M) gmirror label -v -n -b round-robin gm0p1 /dev/ad4p1 newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p1 gmirror label -v -n -b round-robin gm0p2 /dev/ad4p2 newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0p2 (then I mount /dev/mirror/gm0p1 and /dev/mirror/gm0p2 and copy data from my original array to this new array) Finally I insert the ad6 disk and wait for the array to sync: gmirror configure -a gm0p1 gmirror insert gm0p1 /dev/ad6p1 gmirror configure -a gm0p2 gmirror insert gm0p2 /dev/ad6p2 Once the array is synchronized things generally look good, although after a reboot I did see the following that had me concerned (from dmesg output): GEOM: ad4: the primary GPT table is corrupt or invalid. GEOM: ad4: using the secondary instead -- recovery strongly advised. Am I using the correct process to create this array? Since I still have my old array in the system I can rebuild it again if needed, and would prefer to do it correctly if I'm not already. Thanks all! -Proto ___ 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: correct way to setup gmirror on 7.4?
On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider wrote: > Michael Proto wrote: >> Am I using the correct process to create this array? > > No. While this works with MBR it fails with GPT as GPT and GEOM both > want to use the last sector of the disk. > > First create the mirror and after that gpart it. It will create a > message like > > GEOM: da0: the secondary GPT header is not in the last LBA. > GEOM: da1: the secondary GPT header is not in the last LBA. > > which afaik is ignorable. At least it works fine here and I didn't find > any caveats in the net. > > Another workaround is not to mirror the disk but only slices or > partitions. > > HTH, Helmut > Thank you for the advice and direction, but I'm still a bit confused. In my setup I am mirroring only partitions, creating partitions ad4p1, ad6p1, ad4p2 and ad6p2 with gpart first, and then mirrors gm0p1 and gm0p2 on top of those. I'd prefer not to mirror the whole disk. The "primary GPT table is corrupt or invalid" error I'm seeing is with this configuration. Or perhaps I'm misunderstanding what you're saying. -Proto ___ 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: correct way to setup gmirror on 7.4?
On Wed, Apr 27, 2011 at 4:43 PM, Helmut Schneider wrote: > Michael Proto wrote: > >> On Wed, Apr 27, 2011 at 3:35 PM, Helmut Schneider >> wrote: >> > Michael Proto wrote: >> >> Am I using the correct process to create this array? >> > >> > No. While this works with MBR it fails with GPT as GPT and GEOM both >> > want to use the last sector of the disk. >> > >> > First create the mirror and after that gpart it. >> >> In my setup I am mirroring only partitions, creating partitions ad4p1, >> ad6p1, ad4p2 and ad6p2 with gpart first, and then mirrors gm0p1 and >> gm0p2 on top of those. > [...] >> Or perhaps I'm misunderstanding what you're saying. > > 1. Create the mirror > 2. Create the partition(s) > > Or do the steps described in section 19.4.2 at > http://eis.bris.ac.uk/~mexas/geom-mirror.html > Ah, thanks for that link, 19.4.2 does seem to describe what I'm trying to do (couldn't find it via google search). I'll give this a thorough reading and try it out. Thanks again! -Proto ___ 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: correct way to setup gmirror on 7.4?
On Wed, Apr 27, 2011 at 6:30 PM, Freddie Cash wrote: > On Wed, Apr 27, 2011 at 3:15 PM, Clifton Royston wrote: >> I don't know; it looks correct to me, but I may be missing something >> as I don't currently use gpart. > > gmirror (well, really, any GEOM) doesn't play well with GPT due to the > way they store their metadata. > > gmirror doesn't touch the start of the disk, but saves it's metadata > in the last sector of the disk, and creates a new GEOM provider that's > one sector shorter. > > GPT stores it's partition table in the first sector of the disk, and > saves a backup copy of it in the last sector of the disk. > > Depending on the order you do things, gmirror can overwrite the > secondary GPT table. Or, if you mirror the disk and then gpart the > mirror, gpt will complain that the secondary table is not in the last > sector of the disk (due to the order that GEOM tastes things as gpt > goes first). > > I've tried to document it here. Let me know if there's anything incorrect. > https://forums.freebsd.org/showthread.php?t=22125 > What I ultimately decided to do was use fdisk in interactive mode to manually align 2 4k-boundary MBR partitions, /dev/ad4s1 and /dev/ad4s2, created 2 gmirrors out of them, then bsdlabel-ed and newfs-ed the mirror devices. socrates:mike/ $ fdisk /dev/ad4 *** Working on device /dev/ad4 *** parameters extracted from in-core disklabel are: cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1938021 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 2048, size 195330048 (95376 Meg), flag 80 (active) beg: cyl 2/ head 0/ sector 33; end: cyl 245/ head 13/ sector 29 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 195338240, size 1758167040 (858480 Meg), flag 0 beg: cyl 251/ head 14/ sector 63; end: cyl 593/ head 4/ sector 20 The data for partition 3 is: The data for partition 4 is: (note the "start 2048" and "start 195338240" for the partitions above, which are 4k-aligned) gmirror label -v -n -b round-robin gm0s1 /dev/ad4s1 gmirror configure -a gm0s1 gmirror label -v -n -b round-robin gm0s2 /dev/ad4s2 gmirror configure -a gm0s2 bsdlabel -w /dev/mirror/gm0s1 bsdlabel -w /dev/mirror/gm0s2 newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0s1a newfs -U -b 32768 -f 4096 -S 4096 /dev/mirror/gm0s2a I believe this will work since there's no last-block used for MBR partitions, only GPT. gmirror should happily have its metadata in the last block and partitions shouldn't complain. I'm copying data to the arrays now and will insert my /dev/ad6 partitions after that. I'll reboot once more to confirm no strangeness (apart from GEOM complaining about my sector boundaries due to these 4k-reporting-as-512b disks). Thanks everyone for the suggestions and support, it is very much appreciated here!! -Proto ___ 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: correct way to setup gmirror on 7.4?
On Thu, Apr 28, 2011 at 11:43 AM, Pete French wrote: >> Correct. The layering is not, in itself, the issue. The issue is >> that the loader or kernel or whatever reads the first sector of the >> disk, finds a GPT so it then looks for the backup GPT in the last >> physical sector of the disk and doesn't find it. At this point, >> gmirror is not loaded (or not noticed, since there's nothing in the >> first sector of the disk to show it's a mirror). Once gmirror is >> loaded, then the GPT stops complaining as the first and last sectors >> of the gmirrror provider have the GPT tables. > > Is not the problem here that you are trying to GPT label a gmirrored disc ? > If you instead gmirror two GPT partitions then the problem goes away > doesnt it ? Thats how I set things up - use parititoning on the ohysical > drives, and then put the mirroring into the partitions thus created. > Works fine, and doesnt suffer from any of the afforementioned problems. > > -pete. > ___ > 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" > Actually I was first creating 2 GPT partitions on each disk and then creating a mirror on each of those partitions (2 partitions per disk, 2 mirrors). When doing that I ran into the secondary GPT block displaying as "not found" during boot. As I mentioned, I didn't know if that was a problem per-se, which is why I posted to the list to see if there was a better way of mirroring partitions. From what I'm gathering, I think I did things correctly actually. -Proto ___ 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: possible regression - rum ap problem under 8.1R
On Tue, Jul 27, 2010 at 6:06 PM, Nenhum_de_Nos wrote: > hail, > > I have a small mini itx, crusoe based, and it was running pfSense 1.2.3R > (FreeBSD 7.2). there was an ap using tp-link tl-wn321 usb adapter. no > problems. I then installed 8.1R and tried the same config, and got kernel > panic. Installed 7.2R (no patches applied) and it is working. > > the only info is that 7.2R does not load acpi, but I tried this on 8.1R to > no avail. with acpi 7.2R would not use my integrated nic. > > it complaints about no dump device and I imagine there is no dump. > > is this known ? > what info can I get to help ? > ... > on 8.1R: > > wlans_rum0="wlan0" > ifconfig_wlan0="inet 192.168.12.254" > create_args_wlan0="wlanmode ap ssid rush" > hostapd_enable="YES" > > the hostapd.conf is the same, just change wlan0 to rum0. both load > wlan_ccmp and wlan_xauth on boot. > > thanks, You might want to add the following to rc.conf: ifconfig_rum0="up" -Proto ___ 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 with Bridging ... and bge devices under FreeBSD 7.x?
On Tue, Oct 28, 2008 at 7:56 PM, Marc G. Fournier <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > I'm trying to run a QEMU VM on top of a FreeBSD 7.x server ... I've tried > the > exact same setup on my desktop, using 192.168.1.x and an fxp device, and it > all > works perfectly, but as soon as I do this on another machine on a public > IP, > I'm not getting any routing, I can't even ping it from the same machine ... > > My first thought was that there was an issue with IP aliases already on > the > bge device, but tried doing the following: > > ifconfig bridge0 destroy > ifconfig tap0 destroy > ifconfig fxp0 -alias 192.168.1.101 > ifconfig fxp0 alias 192.168.1.101 netmask 255.255.255.255 > ifconfig bridge0 create > ifconfig tap0 create > ifconfig bridge0 addm fxp0 addm tap0 up > > on my desktop here and then starting up the qemu image, and all worked as > expected, so having an alias on the interface, before or after, doesn't > make a > difference ... at least with the fxp device ... > > Using VNC to connect to the VM, I can look at the interface, and it says it > is > connected ... and the IP/Gateway are all set right for the network I'm on, > netmask is set to 255.255.255.0, same as on the 'private network' ... > > Please note that when I say "it works" on my private network / desktop, I'm > using it to connect to my work computer, across the Internet, via Windows > RDP, > and it works flawlessly ... > > Looking at /var/log/messages, you can see the bridge being setup: > > > Oct 27 18:53:21 io kernel: bridge0: Ethernet address: ce:44:c7:1b:47:40 > > as well as the tap device: > > Oct 27 18:53:25 io kernel: tap0: Ethernet address: 00:bd:96:ae:67:00 > Oct 27 18:53:41 io kernel: tap0: promiscuous mode enabled > > and the ethernet going promiscuous: > > Oct 26 20:53:56 ganymede kernel: fxp0: promiscuous mode enabled > > So, all I have left is that everything is being setup okay, but there is > something I'm missing here ... something with bridge<->bge, maybe? I've > even > tries to compare the output of 'ifconfig -a' as far as the bridge0 and tap0 > devices are concerned, and other then the mac address, they look identical > also > ... > > So, pointers to what I may be missing here? a sysctl value that I need to > set > for this interface? > > I'm having a little trouble understanding the setup you have. In your test case, is the IP of your VM 192.168.1.101? If so, then I don't think you want that IP aliased on the physical interface of your bridge. The VM NIC will answer for packets destined on your local segment, which the bridge would forward to the physical interface. If you assign the VM's IP to that physical interface, then your host would think that traffic is destined for itself and not pass it to the bridge. If I'm misunderstanding and the 192.168.1.101 alias (or whatever the equiv in your production setup) isn't being used by your VM then I would start looking at the ARP traffic crossing both the tap0, lo0, and physical interfaces. What does an 'ifconfig -a' look like on both systems? netstat -rn? Any packet filtering? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LORs in RELENG_7
On Thu, Nov 20, 2008 at 4:11 PM, Ulrich Spoerlein <[EMAIL PROTECTED]>wrote: > Hi, > > I'm running my RELENG_7 kernel with WITNESS and there's always a LOR > when pf(4) is enabled: > > lock order reversal: > 1st 0xc09ca828 ifnet (ifnet) @ /usr/src/sys/net/if.c:849 > 2nd 0xc45d604c pf task mtx (pf task mtx) @ > /usr/src/sys/modules/pf/../../contrib/pf/net/pf_if.c:916 > KDB: stack backtrace: > db_trace_self_wrapper(c08df797,fb671764,c0630e8e,c08e1c96,c45d604c,...) at > db_trace_self_wrapper+0x26 > kdb_backtrace(c08e1c96,c45d604c,c45d3b1c,c45d3b1c,c45d379e,...) at > kdb_backtrace+0x29 > witness_checkorder(c45d604c,9,c45d379e,394,c08e9058,...) at > witness_checkorder+0x6de > _mtx_lock_flags(c45d604c,0,c45d379e,394,fb6717dc,...) at > _mtx_lock_flags+0xbc > pfi_attach_group_event(0,c445,c08e9058,374,c44a920c,...) at > pfi_attach_group_event+0x4e > if_addgroup(c441c000,c08f70d6,4,0,0,...) at if_addgroup+0x2c7 > if_clone_createif(0,0,c08e9563,87,0,...) at if_clone_createif+0x81 > if_clone_create(fb671943,4,0,44,180,...) at if_clone_create+0x8c > tunclone(0,c461e400,fb671943,4,fb67195c,...) at tunclone+0x17a > devfs_lookup(fb6719d0,fb6719d0,fb671b7c,c418de04,2,...) at > devfs_lookup+0x50e > VOP_LOOKUP_APV(c0928f40,fb6719d0,c412f230,c08e77ef,2a9,...) at > VOP_LOOKUP_APV+0xa5 > lookup(fb671b7c,c08e77ef,c6,bf,c461e92c,...) at lookup+0x58e > namei(fb671b7c,c412f230,fb671a74,246,c0983774,...) at namei+0x34b > vn_open_cred(fb671b7c,fb671c78,ce8,c461e400,c4460558,...) at > vn_open_cred+0x2c9 > vn_open(fb671b7c,fb671c78,ce8,c4460558,c05e807d,...) at vn_open+0x33 > kern_open(c412f230,80a0f18,0,3,808ecfa,...) at kern_open+0xe7 > open(c412f230,fb671cfc,c,c08e28c3,c092c0b8,...) at open+0x30 > syscall(fb671d38) at syscall+0x2b3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (5, FreeBSD ELF32, open), eip = 0x2835a65b, esp = 0xbfbfeafc, > ebp = 0xbfbfeb38 --- > > > Are you using user or group rules in your pf.conf? IIRC there is still a known LOR in the socket layer with rules using the user or group filters. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7, runaway clock as guest OS on Microsoft Virtual Server
On Wed, Jan 21, 2009 at 2:41 PM, Jeffrey Williams wrote:
> Hi Folks,
>
> I am trying to run FreeBSD 7 on Microsoft Virtual Server 2005 R2, Windows
> Server 2003, on a Dell 2950.
>
> I am having a problem with the system clock running excessively fast, I
> initially tried installing 7.1 release but received a nearly continuous
> stream of the "calcru: runtime went backward errors", I tried rolling back
> to 7.0, and it improved somewhat, but I still received regular "calcru"
> errors, and it the system clock was running to fast for ntpd to keep up with
> it, I set sysctl kern.timecounter.hardware to i8254 (it tries to default to
> ACPI-safe), which helped more, ntpd is now able to keep pace with it, but
> only barely, and I haven't seen any "calcru" errors yet.
>
> From the boot time dmesg, on the CPU line, the frequency reported with in
> the parenthesizes varies on almost every reboot.
>
> Are there any other adjustments I can make to get this under control?
>
> Following are samples of sysctl values, dmesg, and a short log sample to
> show the time and time reset rates.
>
> sysctl grep clockrate:
>
> kern.clockrate: { hz = 1000, tick = 1000, profhz = 1024, stathz = 128 }
> hw.clockrate: 1061
>
> sysctl grep timecounter:
>
> kern.timecounter.tick: 1
> kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-100)
> kern.timecounter.hardware: i8254
> kern.timecounter.nsetclock: 12
> kern.timecounter.ngetmicrotime: 8071302
> kern.timecounter.ngetnanotime: 9
> kern.timecounter.ngetbintime: 0
> kern.timecounter.ngetmicrouptime: 2310540
> kern.timecounter.ngetnanouptime: 3870
> kern.timecounter.ngetbinuptime: 237939
> kern.timecounter.nmicrotime: 48722
> kern.timecounter.nnanotime: 2143
> kern.timecounter.nbintime: 50865
> kern.timecounter.nmicrouptime: 4498
> kern.timecounter.nnanouptime: 1
> kern.timecounter.nbinuptime: 477504
> kern.timecounter.stepwarnings: 0
> kern.timecounter.tc.i8254.mask: 4294967295
> kern.timecounter.tc.i8254.counter: 3077011530
> kern.timecounter.tc.i8254.frequency: 1193182
> kern.timecounter.tc.i8254.quality: 0
> kern.timecounter.tc.ACPI-safe.mask: 16777215
> kern.timecounter.tc.ACPI-safe.counter: 14993826
> kern.timecounter.tc.ACPI-safe.frequency: 3579545
> kern.timecounter.tc.ACPI-safe.quality: 850
> kern.timecounter.tc.TSC.mask: 4294967295
> kern.timecounter.tc.TSC.counter: 3664196446
> kern.timecounter.tc.TSC.frequency: 1061252458
> kern.timecounter.tc.TSC.quality: 800
> kern.timecounter.smp_tsc: 0
>
> ** sample log:
>
> Jan 20 19:25:08 host ntpd[1829]: time reset -12.179675 s
> Jan 20 19:25:08 host ntpd[1829]: kernel time sync disabled 6041
> Jan 20 21:25:34 host ntpd[1829]: time reset -17.665523 s
> Jan 20 21:25:34 host ntpd[1829]: kernel time sync enabled 2001
> Jan 20 23:43:24 host ntpd[1829]: kernel time sync enabled 6001
> Jan 20 23:59:15 host ntpd[1829]: time reset -67.677336 s
> Jan 20 23:59:15 host ntpd[1829]: kernel time sync enabled 2001
> Jan 21 00:51:31 host ntpd[1829]: kernel time sync enabled 6001
> Jan 21 00:51:27 host ntpd[1829]: time reset -11.695334 s
> Jan 21 00:51:27 host ntpd[1829]: kernel time sync enabled 2001
>
> ** dmesg.boot:
>
> 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-RELEASE-p9 #0: Tue Jan 13 19:45:51 PST 2009
> r...@host:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(R) CPU E5320 @ 1.86GHz (1364.45-MHz 686-class
> CPU)
> Origin = "GenuineIntel" Id = 0x6fb Stepping = 11
>
> Features=0x7c0a97b
> AMD Features2=0x1
> Cores per package: 4
> real memory = 536805376 (511 MB)
> avail memory = 511385600 (487 MB)
> kbd1 at kbdmux0
> ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
> hptrr: HPT RocketRAID controller driver v1.1 (Jan 13 2009 19:45:26)
> acpi0: on motherboard
> acpi0: [ITHREAD]
> acpi0: Power Button (fixed)
> acpi0: reservation of 0, a (3) failed
> acpi0: reservation of 10, 1ff0 (3) failed
> Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
> pcib0: port 0xcf8-0xcff on acpi0
> pci0: on pcib0
> isab0: at device 7.0 on pci0
> isa0: on isab0
> atapci0: port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0
> ata0: on atapci0
> ata0: [ITHREAD]
> ata1: on atapci0
> ata1: [ITHREAD]
> pci0: at device 7.3 (no driver attached)
> vgapci0: mem 0xf800-0xfbff at device 8.0 on
> pci0
> de0: port 0xec00-0xec7f mem
> 0xfebff000-0xfebf irq 11 at device 10.0 on pci0
> de0: 21140A [10-100Mb/s] pass 2.0
> de0: using obsoleted if_watchdog interface
> de0: Ethernet address: 00:03:ff:48:a7:20
> de0: [ITHREAD]
> atkbdc0: port 0x60,0x64 irq 1 on acpi0
> atkbd0: irq
Re: zfs drive keeps failing between export and import
On Thu, Jan 22, 2009 at 4:24 PM, David Ehrmann wrote: > On Fri, Jan 16, 2009 at 3:21 PM, David Ehrmann wrote: >> On Fri, Jan 16, 2009 at 3:33 AM, Pete French >> wrote: a software problem before hardware. Both drives are encrypted geli devices. I tried to reproduce the error with 1GB disk images (vs >>> >>> This is probably a silly question, but are you sure that the drives >>> are not auto detaching ? I had big problems with a zfs mirror on top >>> of geli which turned out to be that drives mounted using "geli_devices" >>> in rc.conf will auto detach unless you set "geli_autodetach" to NO. >> >> Not silly at all. I didn't know that could be an issue, but they >> weren't mounted with "geli_devices," they were mounted by hand with >> "geli attach /dev/ad." I did not set the -d flag on attach, and >> I don't think I used the -l flag on detach, either. Listing the >> device says this: >> >> Geom name: ad10.eli >> EncryptionAlgorithm: AES-CBC >> KeyLength: 128 >> Crypto: hardware >> UsedKey: 0 >> Flags: NONE >> >> (and more stuff) >> >> One more interesting thing: I accidentally rebooted the system without >> any detaching/exporting (it involved a different, bad drive). When it >> came up, I was able to re-import tank without any problems. >> > > Ok, here's where it gets interesting: > > The next time I saw the import error, I ran zdb -l on the actual dev. > It couldn't find the labels. So I used dd to grab the first 4k of the > .eli device and the actual device. Once I got it working, I repeated. > The data in the first 4k of /dev/ad8 were all 0x00 both times. I'm > guessing this is reserved, or something. The data in the first 4k of > /dev/ad8.eli differed between runs (so zdb -l is probably right about > not finding the label). > > In the /dev/ad8.eli that zfs doesn't recognize, I found a 16 byte > string that was repeated a lot, but it was also repeated in another > place: the good /dev/ad10.eli (though the offsets were different). > The other weird thing: the good and bad /dev/ad8.eli look a lot alike: > one 16 byte string, then another that gets repeated, then another 16 > byte string randomly shows up at 0x200. > > Why the same data appear in the bad ad8.eli as the good ad10.eli, I'm > not sure (I do have the same password and no keyfile with geli), but > the patterns of data looking the same make me think something's wrong > with the encryption. It's using 128 bit AES-CBC, and these patterns > would not be hidden by it (128 bits == 16 bytes). > > I'm using a Via C7 CPU's padlock cryptographic accelerator, and geli > reports this. I'm guessing this is either a padlock or a geli bug. > > I can't reliably reproduce this problem, but doing it with padlock off > might be a good test. > ___ > 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" > I saw something similar (minus zfs) when I was playing with padlock and geli on my C7-Esther fileserver. When trying to mount a geli partition I'd intermittently get a bad decryption key error. Run the same command again to mount the partition and it'd work fine. This was using both password and key-file operations. IIRC when I disabled padlock acceleration it worked fine in my limited testing. That was 6.4, now that I'm on 7.1 it might be worth looking at again. -Proto ___ 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: SSH problem
On Tue, Jan 27, 2009 at 1:44 PM, Jasvinder S. Bahra wrote: But, when I try to use WinSCP under windows, it always failed. WinSCP errors: "Network error: Connection refused". Both scp & sftp fail if using WinSCP. > > Is there an entry /etc/hosts.allow allowing connections to the applicable > port? > > Jazz > If tcpwrappers were at fault I'd expect to see the connection open and then immediately close, not a connection-refused error. I'd lean more towards a network/port problem as some of the previous posters have mentioned. tcpdump would be a good tool here. -Proto ___ 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: ntpd fails to synchronize on FreeBSD 6.3-STABLE
Pongthep Kulkrisada wrote:
> (2)
> My next problem after buildworld is ``man pages are not updated''.
> They are still FreeBSD 6.2. What happen? How to fix it?
>
You need to delete your old catman pages.
find /usr/share/man/cat* -type f -exec rm -f {} \;
>
> Please someone point me out.
>
> Thanks in advance.
> Pongthep
-Proto
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with promise SATA300 TX2Plus
Jisakiel wrote: > Greetings. I was trying to install FreeBSD 7 on an old machine to make it a > fileserver. Machine is an AMD K7 1200 on an Abit AN-7 mobo (nforce2 400), > which has booted Freebsd 7.0 RC1 beforehand (for testing ZFS; only ACPI > didn't work as it hung it). > > I recently bought a PCI SATA card on the cheap variety, Promise SATA300 > TX2Plus, and a couple of 500GB Maxtors. Unfortunately, when any hard drive > (both of the 500's and an older 250 Maxtor which I use) is plugged to the > SATA ports of the pci card I get an instantaneous reboot when trying to boot > the bootonly cd (it doesn't reach the bootloader). If no disks are plugged it > works but hangs while booting (with ACPI disabled). > > Things I tried: > > - Booting another OS. Card works perfectly both in linux (2.6.24) and > windows, with the two hard drives visible. > - Leaving just one SATA drive connected to the whole system through the PCI > card. It doesn't matter which drive I let, both the 250G and the 500G make it > reboot. > - Swapping the power cable. > - Unplugging my former 2 drives to ease the load on the Enermax 365W power > supply. It works in Windows though, with everything on... > - Disabling both integrated SATA of the motherboard (SI3112 which works both > in linux and freebsd), and integrated firewire (just in case). > - Moving the PCI card to another slot. I only have another pci device, a > soundcard, and moving it changed the bios boot order (first the pci, then the > integrated sata or viceversa) with no change at all afterwards. > - Trying 6.3 livecd. Same insta-reboot. > - Updating the card's bios. There is no newer one, 1.0.0.34 is what came and > what's on the promise web. > > Is there any way to make this card work on FreeBSD 7, or anything else that I > could try? I bought it specifically for that; I might be in time to return > it, though I'd have to buy another one on the same price range then (perhaps > Promise FastTrak TX2300, HightPoint RocketRaid 1520 or Adaptec 1210SA which I > seem to recall that doesn't work too well on linux). Otherwise I'd be more > than willing to help debugging it ^^. > > Thanks everybody... > > > [EMAIL PROTECTED] > For what its worth, I have a RocketRaid 1520 in my fileserver at home that I've been using for over a year without any problems: atapci0: port 0xff00-0xff07,0xfe00-0xfe03 ,0xfd00-0xfd07,0xfc00-0xfc03,0xec00-0xecff irq 17 at device 8.0 on pci0 ata2: on atapci0 ata3: on atapci0 ... ad4: 286168MB at ata2-master UDMA133 ad6: 286168MB at ata3-master UDMA133 ar0: 286168MB status: READY -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.9-stable: weird messages in /var/log/messages?
Torfinn Ingolfsen wrote: > On Tue, 04 Mar 2008 20:52:23 +0100 > Kris Kennaway <[EMAIL PROTECTED]> wrote: > >> It is reporting large variations in the rate of your time clock (see >> kern_tc.c). > > Aha, I see. Thanks for explaining that. > >> Also, you appear to be emailing from the distant future. Please >> reply with stock tips :) > > distant future, even? :-) > The two things share a common symptom; the nic on that particular > machine is a ral(4) one, and I am having connectivity problems > (connections from other machines to this particular machine drops). > That's why I booted the machine with verbose messages, and got those > messages in the first place. > It looks like network connectivity going away without the network > interface going down / up has confused ntpd, I had to restart it just > now. I've noticed this with ntpd myself in various scenarios, mainly when using MPD (via a ng_pppoe tunnel) and the tunnel drops-out from underneath ntpd. Normally when this happens I see two instances of ntpd running instead of one, and it doesn't respond to a normal kill signal. I've written the following quick-hack script to restart it (running every 5 minutes from cron): #!/bin/sh -e for conf in /etc/defaults/rc.conf /etc/rc.conf /etc/rc.conf.local; do [ -f "$conf" ] && . "$conf" done if [ $ntpd_enable = "YES" ]; then PROGNUM=`ps xww | grep "$ntpd_program .* $ntpd_flags" | grep -v grep | wc -l` if [ "$PROGNUM" -gt 1 ]; then /etc/rc.d/ntpd stop sleep 10; killall -9 ntpd /etc/rc.d/ntpd start fi fi -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Approaching the limit on PV entries
Stephen Clark wrote: > Alfred Perlstein wrote: >> * Ivan Voras <[EMAIL PROTECTED]> [080311 08:46] wrote: >> >>> During heavy postgresql load (pgbench), /var/log/messages registers >>> (multiple times) the following message: >>> >>> "Approaching the limit on PV entries, consider increasing either the >>> vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl" >>> >>> I'm increasing both, but no matter what I increase them to, after a >>> short time they again get increased by the system (???). >>> >>> The values are currently: >>> >>> vm.pmap.shpgperproc: 1134 >>> vm.pmap.pv_entry_max: 800 >>> >>> But the last sysctl setting, verified by retrieving it from my shell >>> command line history, is that I set vm.pmap.shpgperproc to 800. >>> >>> Is this normal, and what are the common settings for these values? The >>> machine is 2x4-core, currently 4 GB RAM (which will increase to at least >>> 6 GB), amd64, running postgresql, php and apache. >>> >>> >> >> try setting: >> >> sysctl kern.ipc.shm_use_phys=1 >> >> >> >> > Could you please explain what that does and why? > > Also could someone point me to where all these sysctls are documented > other than in the source code - which lots > of time has no explanation. It would really help the average sys admin/ > user if these were documented. > > Thanks, > Steve > tuning(7) is a good place to start. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panics on 6.3-RELEASE in IP stack
Robert Watson wrote: > > On Fri, 18 Apr 2008, Bruce M. Simpson wrote: > >>> I concur, this fix should really be MFCed. The problem went away in >>> 7.x due to a total rewrite. I am distracted by other stuff at the >>> moment, so, starter's orders... >> >> This just bit me. The fix is in RELENG_6, but it is not present after >> the -p1 tag. So updating to STABLE should fix the problem for Petr. >> >> Whilst 6 is no longer the STABLE branch, I think this really should go >> onto 6 in case any other releases happen from that branch. > > There are (tentative) plans to release a 6.4-RELEASE, but I don't think > there's a schedule yet. Developers should plan on continuing to merge > changes, especially bug fixes, to RELENG_6. > > Robert N M Watson > Computer Laboratory > University of Cambridge > ___ Just a note that I'd really like it for a 6.4-RELEASE to be made available if possible. I still have some hosts on 6-STABLE for a variety of reasons (including one very nasty problem with 7-STABLE, pf, and IPSec with NAT traversal that I'm trying to troubleshoot in preparation for a possible PR, once I find out exactly where the problem is). Thanks, Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: samba build failure on 6-STABLE
Greg Byshenk wrote: > I'm posting this to freebsd-stable even though it is a problem with a port, > because the port itself has not changed, but a rebuild fails (on a system > and with a configuration that worked before my most recent system updates). > > Basically my problem is that the current Samba3 (samba-3.0.28,1) won't build > on a recent 6-STABLE system (I noticed it with sources csup'd 24 April, and > it continues with sources csup'd today, 1 May). The strange thing is that > this is a version of samba that has previously built successfully, on the > machine and with the configuration that is now failing. (I was attempting > to rebuild because I saw some strange library errors.) This at least > suggests to me that the problem is _not_ due to something changing with Samba, > but to some other change that is being reflected in the Samba build. > > > The system in question is built from sources csup'd today (1 May 2008), with > all installed ports current as of today. The same Samba did build > successfully > with a source and ports tree csup'd on 7 March 2008. > > As a test to see if there is some problem with the ports dependencies, I've > tried a 'portupgrade -fR samba'; all of the dependencies built fine, but then > I got the same error when attempting to build Samba itself. It is not > definitive, but this suggests to me that this is not a ports problem (per se), > but a kernel/world problem. > > This latter is highlighted by the fact that Samba builds without error on a > system with sources csup'd on 17 April. That is, if I take the exact same > system on which the build fails, revert my world/kernel to a build from > 17 April (leaving everything else exactly the same), then the error > disappears and Samba builds successfully. > > > The actual error is below. Any ideas are welcome. I have a machine that I can > play with if someone would like me to try anything. > > -greg > > > Compiling smbd/oplock_linux.c > smbd/oplock_linux.c: In function `signal_handler': > smbd/oplock_linux.c:73: error: structure has no member named `si_fd' > The following command failed: > cc -I. -I/usr/ports/net/samba3/work/samba-3.0.28/source -O2 > -fno-strict-aliasing -pipe -D_SAMBA_BUILD_=3 -I/usr/local/include > -I/usr/ports/net/samba3/work/samba-3.0.28/source/iniparser/src -Iinclude > -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include > -I./libaddns -I./librpc -DHAVE_CONFIG_H -I/usr/local/include > -DLDAP_DEPRECATED-I/usr/ports/net/samba3/work/samba-3.0.28/source/lib > -D_SAMBA_BUILD_=3 -fPIC -DPIC -c smbd/oplock_linux.c -o smbd/oplock_linux.o > *** Error code 1 > > Stop in /usr/ports/net/samba3/work/samba-3.0.28/source. > *** Error code 1 > > Stop in /usr/ports/net/samba3. > *** Error code 1 > > Stop in /usr/ports/net/samba3. > I can confirm this on a 6-STABLE system last SUPed (kernel and world rebuilt) to 20080428 11:23 EDT. samba-3.0.28,1 built fine on this box when it was 6.3-RELEASE, and now fails in exactly the same place when trying to rebuild on 6-STABLE. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: broken re(4)
Gerrit Kühn wrote: > On Tue, 27 May 2008 11:45:19 -0400 Michael Proto <[EMAIL PROTECTED]> > wrote about Re: broken re(4): > > MP> > Any hints what I should do next to find the culprit? > > MP> I'm running 6.3 on the exact same Jetway board at home, and while I > MP> haven't been bitten by the DOWN/UP issue I have seen the occasional > MP> "corrupted MAC on input" error when doing an ssh/scp. Seems to have > MP> simmered-down since moving from 6.3-RELEASE to 6.3-STABLE (last > MP> supped/rebuilt on 5/6/08). > > MP> Note this is using only one of the 2 on-board NICs. I disabled the 2nd > MP> one in the BIOS as I don't need it at the moment. > > After my experiences with the patch Pyun provided is seems to me that > running one or two nics makes somehow a difference. > I am still wondering why I have two boards with the same hardware that > work flawlessly. > However, when comparing all things, I found some minor differences: > The working boards are some months older and their CPU shows up like this: > > CPU: VIA C7 Esther+RNG+AES+AES-CTR+SHA1+SHA256+RSA (1500.01-MHz 686-class > CPU) Origin = "CentaurHauls" Id = 0x6a9 Stepping = 9 > > Features=0xa7c9baff > Features2=0x181 > > > The one that doesn't work is newer and dmesg identifies: > > CPU: VIA C7 Processor 1500MHz (1500.01-MHz 686-class CPU) > Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0 > > Features=0xa7c9baff > Features2=0x4181 > VIA Padlock Features=0xffcc > > > This is the only difference I can make out so far. Which board do you > exactly have? > > > cu > Gerrit > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" I've got the newer revision: CPU: VIA Eden Processor 1200MHz (1200.01-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0 Features=0xa7c9baff Features2=0x4181 VIA Padlock Features=0xffcc That's actually why I had to move to 6-STABLE. The CPUID detection routines for the 0x6d0 revision aren't in 6.3-RELEASE. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AMD Geode LX crypto accelerator (glxsb)
Patrick Lamaizière wrote: > Le Fri, 6 Jun 2008 23:41:35 +0200, > Patrick Lamaizière <[EMAIL PROTECTED]> a écrit : > > Hello, > >> I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE >> (via the NetBSD port). >> " The glxsb driver supports the security block of the Geode LX >> series processors. The Geode LX is a member of the AMD Geode family >> of integrated x86 system chips. >> >> Driven by periodic checks for available data from the generator, >> glxsb supplies entropy to the random(4) driver for common usage. >> >> glxsb also supports acceleration of AES-128-CBC operations for >> crypto(4)." > > Well, I hope this is the final version. > > http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz > > I added a patch for FreeBSD 6 but i'am not able to test it. > > On 7-STABLE, I've tested with hundred openssl encryptions and some flood > pings under ipsec in the background. Looks good for me. > > If someone can test and review it, it would be cool. I don't know if you built it for this or not, but I just tested your module on 8-CURRENT (last supped May 19) and its working beautifully on an ALIX.3c1 (GeodeLX 700): 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 8.0-CURRENT #0: Thu Jun 5 22:44:20 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MINIBSD8 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Geode(TM) Integrated Processor by AMD PCS (431.65-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x5a2 Stepping = 2 Features=0x88a93d AMD Features=0xc040 real memory = 134217728 (128 MB) avail memory = 126152704 (120 MB) pnpbios: Bad PnP BIOS data checksum wlan: mac acl policy registered K6-family MTRR support enabled (2 registers) ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cryptosoft0: on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 Geode LX: PC Engines ALIX.2 v0.98 tinyBIOS V1.4a (C)1997-2007 glxsb0: mem 0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0 Output from "openssl speed -engine cryptodev -elapsed -evp aes-128-cbc aes-128-cbc" engine "cryptodev" set. You have chosen to measure elapsed time instead of user CPU time. To get the most accurate results, try to run this program when this computer is idle. Doing aes-128 cbc for 3s on 16 size blocks: 668161 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 64 size blocks: 178842 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 256 size blocks: 45510 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 1024 size blocks: 11435 aes-128 cbc's in 3.00s Doing aes-128 cbc for 3s on 8192 size blocks: 1429 aes-128 cbc's in 3.00s Doing aes-128-cbc for 3s on 16 size blocks: 61055 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 64 size blocks: 59430 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 256 size blocks: 53475 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 1024 size blocks: 37812 aes-128-cbc's in 3.00s Doing aes-128-cbc for 3s on 8192 size blocks: 9323 aes-128-cbc's in 3.00s OpenSSL 0.9.8e 23 Feb 2007 built on: Thu Jun 5 21:15:55 EDT 2008 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes(partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: gettimeofday The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 3563.35k 3815.11k 3883.37k 3901.80k 3900.02k aes-128-cbc325.65k 1267.73k 4562.72k12904.84k 25453.89k Thanks for that, hopefully it can/will be committed soon! -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is read-write nullfs safe?
Rong-en Fan wrote: > I'm running 6.2-RELEASE, and I am wondering > if using nullfs w/ rw is safe in a production environment? > My impression is that ro nullfs is ok, but not rw. > Is this still the case? I've been using a r/w nullfs for the last several months with no issues. Granted, I don't do a heavy amount of writing to the mount point but I haven't seen any issues with it whatsoever. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: miniBSD vs 6.2-STABLE
Morgan Reed wrote: > I now have my target PXE booting from my FreeBSD host (chalk one up to > not writing config files at ungodly hours of the night, thanks to > Danny for spotting the error.) > > The boot is proceeding to the boot menu but after this the kernel freezes; > With acpi.ko in the image the acpi module loads, the next spinner > appears and the system freezes. > Without acpi.ko I get the message "ACPI autoload failed - no such file > or directory", the next spinner appears and the system freezes. > > My kernel is a stripped GENERIC, essentially minus a bunch of network > drivers (the driver for the adapter in the machine is still there ;o) > ), and all the SCSI controllers. > Is this embedded system booting with a standard monitor and keyboard attached, or via serial console? What you are seeing seems to remind me of a system that is configured to display boot output via video when there is no monitor connection (from my own MiniBSD work with the Soekris NET4501 and PCEngines WRAP platforms). -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rc.local equivalent
Morgan Reed wrote: > I'm working on a small footprint semi-embedded system, I need a means > to load and save parts of /var (which is a memory-backed filesystem) > at boot and shutdown. > > Given that rc.local is now deprecated, what is the "correct" way to > perform extra startup/shutdown processes, should I write an rc.d > script for it and insert it into the rcorder appropriately, or is > there another mechanism? > > Thanks in advance > > Morgan I'm also doing embedded system work on a PC Engines WRAP platform with a CF-based disk, and I'm using custom rc.d scripts for this purpose. Mainly little scripts to enable specific LEDs at the end of the boot process and to copy misc. read-only files from the CF into a memory filesystem during boot. Works rather well, and the documentation in /usr/share/doc/en/articles/rc-scripting was a big help in this regard. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growing partition
RYAN M. vAN GINNEKEN wrote: > Hello i am trying to grow an existing partition which has become full. The > system was originally install in a 80gig drive but has since been moved to a > 300g drive. However Freebsd is still only showing 80g of space please help. > Check the man pages for and growfs(8) and (as a prerequsite) bsdlabel(8), they should supply the info needed to grow a partition on disk. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
update from RELEASE to STABLE changed /dev/ad or geom behavior?
Hello all, To fix a bug in PF I recently updated my home firewall platform (a shrunk-down install of FreeBSD 6 on a CompactFlash card mounted read-only as /dev/ad0a) from the RELENG_6_2 to the RELENG_6 branch. All went very well there and the PF problem is resolved, but now I've run across a new issue. Previously, when updating my CompactFlash image "in the field", I would boot the system into single-user mode via serial console, setup a small memory filesystem big enough to hold gzip, dd, and reboot (and their required libraries, with LD_LIBRARY_FLAGS set appropriately), copy the new flash image to the mfs, and run (from the MFS) "gzip -dc 16 # gzip -dc http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: update from RELEASE to STABLE changed /dev/ad or geom behavior?
Michael Proto wrote: > Hello all, > > To fix a bug in PF I recently updated my home firewall platform (a > shrunk-down install of FreeBSD 6 on a CompactFlash card mounted > read-only as /dev/ad0a) from the RELENG_6_2 to the RELENG_6 branch. All > went very well there and the PF problem is resolved, but now I've run > across a new issue. > > Previously, when updating my CompactFlash image "in the field", I would > boot the system into single-user mode via serial console, setup a small > memory filesystem big enough to hold gzip, dd, and reboot (and their > required libraries, with LD_LIBRARY_FLAGS set appropriately), copy the > new flash image to the mfs, and run (from the MFS) "gzip -dc | dd of=/dev/ad0 bs=8k" and then run "reboot -lnq" to reboot into the > new image. > > This all worked well and good until the update to RELENG_6, and now I > see the following when I try to dd the new image: > > # sysctl kern.geom.debugflags=16 > kern.geom.debugflags: 0 -> 16 > > # gzip -dc dd: /dev/ad0: Invalid argument > 298+1 records in > 298+0 records out > 1220608 bytes transferred in 1.330433 secs (917452 bytes/sec) > > > With the above kern.geom.debugflags sysctl, I thought I would have the > ability to directly write to /dev/ad0 via dd, and this was the case with > RELENG_6_2. Is this no longer the case? Didn't see anything in > /usr/src/UPDATING to indicate any sort of change, and I'm not sure where > in the RELENG_6 code this would exist (GEOM perhaps)? > > Anyone have any ideas or suggestions as to why this doesn't work anymore? > I found a solution to this problem that I'd like to share with the list. Here's my problem: # gzip -dc http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: device polling and weird timer interrupt count from vmstat
Artem Kuchin wrote: > Oliver Fromme wrote: >> Artem Kuchin wrote: >>> Oliver Fromme wrote: Artem Kuchin wrote: > 3) Is timer int really generated on each cpu? Am i really wasting > cpu time on ~4000 ints per second? 4000 ints per second is rather nothing on any modern CPU. Have a look at the top(1) display of an otherwise idle system. The "%interrupt" column should be zero, even if it's processing 4000 timer interrupts per second. As far as I know, the cpu timer interrupt handler is very light- weight. >>> >>> Thank you for the answer. My convern is that with 4 CPUs i get 8000 >>> ints/second. While em generates only about 200 ints/second. As i >>> undertand not all int handlers are the same. Some are heavy and some >>> are light on CPU. So, the question is what is better (better=less CPU >>> time): 8000 ints/sec from timer or 200 ints/sec from NIC? >> >> There's no simple answer to the question. The best way is >> to just try it. As I wrote, run top(1) while the system is >> idle, so only the cpu timer interrupts are active. If the >> "%interrupt" column is zero most of the time, then there >> is nothing to worry about at all. >> >> However, if you have a constant non-zero %interrupt value, >> you might consider lowering HZ, and you might reconsider >> whether polling really has advantages in your situation. >> Do you have reasons to believe so? Remember that the main >> purpose of polling is to improve interactivity under very >> high network load. If you're not in such a situation, then >> polling probably doesn't buy you much. > > Well, problem with top is that on dual 3GHZ box it alsway s > shows 0% load when not loaded with real traffic (web traffic) no matter > if it is polling of int handling. And when loaded with real traffic > web server eat a lot more cpu power then traffic handling, so, no > separate measurement of traffic cpu load is possible. > But i think it is possible to simulate this kind of load, need to think > about > it. > > Also, when it comes to public web server i can never be secure enough and > crazy load of traffic can come any time from DDOS attack which can bring > down any box. So, for public web server it is a matter of security and > managebility to have server interactive even on high traffic load. So, > even from > this poing of view polling can be usefull. > Would it not be advisable then to simply limit the maximum number of allowed connections, ala sysctl kern.ipc.somaxconn, rather then to enable polling? I can see using polling on a router or some device that funnels traffic through multiple interfaces, but rarely have I seen it useful on a single-homed box where sysctls might be better used to limit connections. May be old news, but I've read that polling on a SMP machine is questionable anyway (http://info.iet.unipi.it/~luigi/polling/). -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-RELEASE always hang
Unga wrote: > Hi all > > I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz, > 512MB Ram computer. > > Its very irritatingly hangs very frequently, more than > 10 times a day. Do others find FreeBSD 6.2-RELEASE > always hangs? I simply cannot use it for any serious > use, not even to send a mail, other than browsing web. > > I find it mostly when I try to move the mouse it > hangs. Upward and downward cursor keys press and hold > also hangs, but not always. These may be just > coincidental. How do I find why it hangs? How is the > stability of the upcoming 7.0? > > Best Regards > Unga > I'm sure I'm not alone in this, but I'm running several 6.2-RELEASE-p8 boxes (servers and laptop workstations) for several months now without a single lock-up. I'd first look into hardware, testing memory, testing the power supply, and checking CPU/chipset temperatures as they have often contributed to problems similar to what you are describing. 6.2 has been working extremely well for me with no stability issues that weren't related to hardware problems. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2-RELEASE always hang
Unga wrote: > > Mine is also an ATI Radeon card: > ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1 > Chipset ATI Radeon 9200PRO 5960 (AGP) > > I cannot ssh to the machine while its freezes. It says > 'no route to host'. That is, the machine is completely > dead. > > The other thing is, FreeBSD installer has not > installed an xorg.conf. > > I have created an xorg.conf using Xorg -configure and > moved to /etc/X11/. Adjusted the HorizSync and > VertRefresh to match the monitor, driver I used "ati", > added Modes and an DRI section with Mode 0666. > > If it crashes again I'll let the list know. > Just a thought, but you might also want to try using the VESA X driver for a while and see if the same symptoms persist. Its slower than a native driver but can also be used to identify if the X driver is in fact causing problems. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPSEC + Via Padlock + racoon + Windows
Dewayne Geraghty wrote: > We're looking to deploy FreeBSD on our main firewall. The firewall config > is a VIA C7 (padlock), racoon(ipsec-tools-0.7), IPSec. We're testing racoon > with a windows box, however the firewall doesn't function correctly when > net.inet.ipsec.crypto_support=1 is set. With a > net.inet.ipsec.crypto_support=0 it does. > > The firewall was configured with FreeBSD 6.2R and replaced with 6.3RC1 on a > separate HDD (as at 2007-12-02). > > "Doesn't function correctly" means that after phase 1 & 2 negotiation the > Windows box is able to send a ping (from WXP-SP2+) to the server. The > server doesn't respond to the pings, but generates pfkey Update failed > messages during racoon debugging. (wireshark was running on the PC-WXP, > tcpdump on FreeBSD) > > The testing was performed with both ends configured for esp transport mode, > 3des and md5 for encryption and hashing, and pfs (diffe-helman 2 (1024)). > These two machines were connected on a stand-alone network (via crossover > cables). > > Server kernel uses > options FAST_IPSEC > device cryptodev > device padlock > options IPFIREWALL > > /etc/sysctl.conf contains the following which may be relevant: > net.inet.ip.fastforwarding=1 > kern.cryptodevallowsoft=1 > net.inet.ipsec.crypto_support=1# this was toggled 1/0 during testing > net.inet.icmp.icmplim=10 # These may be off-track? > net.inet.tcp.slowstart_flightsize=4 > > I hope that someone can provide some guidance, as I'm looking forward to > getting the performance out of these energy efficient little processors. I > should note that IPSec works fine between FreeBSD boxes with > net.inet.ipsec.crypto_support=1 however we have to reconfigure for > high-value PC communications. I'd like to have my cake > (freebsd-ipsec-padlock) and eat it too (WXP) ;) > > Reference: > net.inet.ipsec.crypto_support values from > (http://groups.google.ca/group/mailing.freebsd.stable/browse_frm/thread/f3f1 > 40e615d9ca62/31935038340cc323?lnk=st&q=fast_ipsec+net.inet.ipsec.crypto_supp > ort&rnum=5&hl=en#31935038340cc323 ) > Not that this solves your problem, but doesn't the padlock crypto engine only provide acceleration for AES symmetric encryption? From the man page: The C3 and Eden processor series from VIA include hardware acceleration for AES. The C7 series includes hardware acceleration for AES, SHA1, SHA256 and RSA. All of the above processor series include a hardware random number generator. Does using AES instead of 3DES change your situation at all? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.3-PRERELEASE unable to change file permission
Anjang Aki wrote: > hi!.. i'm not able to change file permission to disable rlogin and > login on my box even as root > > # ls -lo /usr/bin/login /usr/bin/rlogin > -r-sr-xr-x 1 root wheel schg 19996 Dec 1 13:04 /usr/bin/login > -r-sr-xr-x 1 root wheel schg 10140 Dec 1 13:04 /usr/bin/rlogin > > # chflags -R nouchg login rlogin > chflags: /usr/bin/login: Operation not permitted > chflags: /usr/bin/rlogin: Operation not permitted > > # chmod a=rx /usr/bin/login /usr/bin/rlogin > chmod: /usr/bin/login: Operation not permitted > chmod: /usr/bin/rlogin: Operation not permitted > > it makes me uneasy as my users can still use login and rlogin to gain > access to the box > > my system: > # uname -a > FreeBSD k3.college.edu 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #1: Sun > Dec 2 18:51:02 MYT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EDU > i386 > > thanks for advice > It looks like these files have the system-immutable flags set (schg), not the user-immutable (uchg). What happens if you do "chflags noschg /usr/bin/login /usr/bin/rlogin"? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPSEC + Via Padlock + racoon + Windows
Dewayne Geraghty wrote: > My apologies for the confusion, yes, the C7 only helps with AES. > > The configuration detail is: between branch offices I use FreeBSD ipsec > (AES), and within the branches Windows boxes access the firewall boxes. The > "firewalls" run samba inside a jail. Due to sensitive information (see your > local Privacy legislation), we also need to encrypt the information between > samba jail and the PC-WXP devices. Hence the need to use ipsec-AES on the > WAN and ipsec-3des on the LAN (as 3des is the best option selectable for > WXP). > > Regards, Dewayne. > Just out of curiosity, what happens if you set net.inet.ipsec.crypto_support = -1 when using 3DES in your testing? Does the firewall work then? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IRQ sharing check command
Balgansuren Batsukh wrote: > Hello, > > Which command I need to use IRQ sharing check or allocated IRQ information? > > Balgaa Try vmstat -i -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Working mini PCIe wireless?
Michael Proto wrote: > > I don't have access to my laptop at the moment (and hence can't pull the > exact kernel output regarding the adapter), but I have a ThinkPad R60 > with the ThinkPad a/b/g miniPCI-e wireless card that worked fine under > FreeBSD 6.2. I believe you can find the actual part here: > > http://shop.lenovo.com/SEUILibrary/controller/e/web/LenovoPortal/en_US/catalog.workflow:item.detail?GroupID=38&Code=40Y7026¤t-category-id=DD119CA6FA0E4518A4086EB8FF1FDD2B&model-number=9456 > > Part number: 40Y7026 > I neglected to mention this is an Atheros adapter that appears as ath0 on my system. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Working mini PCIe wireless?
Geoff Buckingham wrote: > I recently purchased the Dell I6400 Ubuntu laptop, with the express intent of > running FreeBSD on it. > > My intention was to use this a working machine using PC-BSD, I.E. RELENG_6, > limiting tinkering, experimentation to other systems. > > It comes with an Intel 3945[1] mini PCIe card, which I knew would not work. > So > I ordered myself a Azurewave Atheros based mini PCIe card to replace it. > Unfortunatly the ath_hal[2] doesn't recognise the hardware revision, so that > doesn't work either. > > Does anybody know of a mini PCIe wireless card that works under RELENG_6? > Failing that an ExpressCard? (The 6400 has no Card Bus) > > Notes: > > [1]I know there is a 3945 driver for 7 and an older rev fo 6, I tried it > it locks up the machine. > [2] Sam has a more recent HAL on his "people" page, but the headers have > changed making it non-trivial, for me at least, to compile into a > RELENG_6 kernel/module. > I don't have access to my laptop at the moment (and hence can't pull the exact kernel output regarding the adapter), but I have a ThinkPad R60 with the ThinkPad a/b/g miniPCI-e wireless card that worked fine under FreeBSD 6.2. I believe you can find the actual part here: http://shop.lenovo.com/SEUILibrary/controller/e/web/LenovoPortal/en_US/catalog.workflow:item.detail?GroupID=38&Code=40Y7026¤t-category-id=DD119CA6FA0E4518A4086EB8FF1FDD2B&model-number=9456 Part number: 40Y7026 -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Trying to initialize padlock support on Via C7 Eden CPU
Hello, I purchased a Jetway J7F4K1G2E w/VIA Eden 1.2GHz cpu/motherboard combo (http://e-itx.com/jetway-j7f4k1g2e-mini-itx-motherboard.html) that I'm trying to get working with the FreeBSD padlock driver. Based on what I see from the manufacturer's CPU support list , http://www.jetwaycomputer.com/VIA3.html, I have a C7 Esther processer. It looks like the CPUID for this processor isn't recognized by FreeBSD 6.3-RC1 or 7.0-BETA3. GENERIC on 7.0-BETA3 detects the CPU as follows: CPU: VIA/IDT Unknown (1200.01-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0 Features=0xa7c9baff Features2=0x4181 ... padlock0: No ACE support. The other list posts I've seen for the C7 reference a 0x6a9 Id with a stepping of 9. I added a small patch to /sys/i386/i386/identcpu.c to detect this Id: --- sys/i386/i386/identcpu.c.old2007-05-29 19:39:18.0 + +++ sys/i386/i386/identcpu.c2007-12-21 13:54:57.0 + @@ -585,6 +585,8 @@ goto via_common; case 0x6a0: strcpy(cpu_model, "VIA C7 Esther"); + case 0x6d0: + strcpy(cpu_model, "VIA C7 Esther"); via_common: do_cpuid(0xc000, regs); i = regs[0]; And now GENERIC sees the Esther along with the supported crypto functions, but padlock doesn't initialize: CPU: VIA C7 Esther+RNG+AES+AES-CTR+SHA1+SHA256+RSA (1200.01-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0 Features=0xa7c9baff Features2=0x4181 ... padlock0: No ACE support. Unfortunately I'm at a loss on where to go next. I looked through initcpu.c and everything in /sys/crypto/via/ but I don't grok C so I don't really know what I'm looking at. Any ideas on how to get this CPU supported with padlock would be much appreciated. Thanks and happy holidays, -Michael Proto Below is a verbose 7.0-BETA3 dmesg.boot (with my above identcpu.c patch applied) Copyright (c) 1992-2007 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-BETA3 #0: Sat Dec 22 07:39:36 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0d6e000. Preloaded elf module "/boot/kernel/padlock.ko" at 0xc0d6e19c. Preloaded elf module "/boot/kernel/crypto.ko" at 0xc0d6e248. Preloaded elf module "/boot/kernel/zlib.ko" at 0xc0d6e2f4. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0d6e3a0. Calibrating clock(s) ... i8254 clock: 1193579 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1200010302 Hz CPU: VIA C7 Esther+RNG+AES+AES-CTR+SHA1+SHA256+RSA (1200.01-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0 Features=0xa7c9baff Features2=0x4181 real memory = 1055784960 (1006 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x01028000 - 0x3dce4fff, 1019990016 bytes (249021 pages) avail memory = 1019531264 (972 MB) Table 'FACP' at 0x3eee3080 Table 'APIC' at 0x3eee83c0 MADT: Found table at 0x3eee83c0 MP Configuration Table version 1.4 found at 0xc00f22f0 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) ACPI APIC Table: bios32: Found BIOS32 Service Directory header at 0xc00f9d30 bios32: Entry = 0xfa1b0 (c00fa1b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xa200 pnpbios: Found PnP BIOS data at 0xc00fac30 pnpbios: Entry = f:ac60 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 ACPI: RSDP @ 0x0xf7c40/0x0014 (v 0 CN700 ) ACPI: RSDT @ 0x0x3eee3000/0x002C (v 1 CN700 AWRDACPI 0x42302E31 AWRD 0x) ACPI: FACP @ 0x0x3eee3080/0x0074 (v 1 CN700 AWRDACPI 0x42302E31 AWRD 0x) ACPI: DSDT @ 0x0x3eee3100/0x5281 (v 1 CN700 AWRDACPI 0x1000 MSFT 0x0300) ACPI: FACS @ 0x0x3eee/0x0040 ACPI: APIC @ 0x0x3eee83c0/0x005A (v 1 CN700 AWRDACPI 0x42302E31 AWRD 0x) MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec0 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x VER: 0x00050014 LDR: 0x DFR: 0x lint0: 0x0001070
Re: RELENG7 using lpt causes panic
Adrian Wontroba wrote: > I've recently switched some of my home systems to RELENG7. > > All seemed fairly well until I tried printing a CUPS test page on my > backup and print server to an elderly Laserjet IIIp, where I seem to > have a reproducible panic. It has happened twice. This is painful, as > I have a big home fileystem (striped over two mirrors over most of two > 500 GB disks). The gmirror syncronisation and background fsck leave the > system close to unusable for hours while they fight over the disks. > > I was somewhat startled that something so basic as printing causes a > panic. There have been no hardware changes since I last printed under > RELENG6, but I don't print often, so hardware decay is a possibility. > > Is this a known problem? If not, I'll take the time to try various tests > (with /home unmounted) and raise a PR. > > I envisage tests such as: > * Does switching to a kernel without SMP and apic make a difference? > * Does direct output cause a crash? > * Does polling make a difference? > * Does the parallel port mode (I think extended at present) make a > difference? > > Some detail below. > > Throwaway comment: On my workstation I find that a GENERIC - SMP - apic > + SCHED_ULE kernel is MUCH more responsive during buildworld than a > GENERIC kernel. > > console / dmesg > === > > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > lpt0: [GIANT-LOCKED] > lpt0: [ITHREAD] > Fatal trap 30: reserved (unknown) fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xc0a5747b > stack pointer = 0x28:0xe67ea968 > frame pointer = 0x28:0xe67ea96c > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, IOPL = 0 > current process = 1421 (parallel) > trap number = 30 > panic: reserved (unknown) fault > cpuid = 0 > Uptime: 23m3s > Physical memory: 1011 MB > Dumping 168 MB: 153 137 121 105 89 73 57 41 25 9 > Dump complete > > Which? > == > > RELENG7 cvsupped and built in the late evening of Sunday 06/01/07 > > [EMAIL PROTECTED] ~]# uname -a > FreeBSD rottcodd.hanley.stade.co.uk 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: > Sun Jan 6 23:33:45 GMT 2008 [EMAIL > PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > kgdb > > > [EMAIL PROTECTED] ~]# kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.1 > [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: > Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > > > Fatal trap 30: reserved (unknown) fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xc0a5747b > stack pointer = 0x28:0xe67ea968 > frame pointer = 0x28:0xe67ea96c > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, IOPL = 0 > current process = 1421 (parallel) > trap number = 30 > panic: reserved (unknown) fault > cpuid = 0 > Uptime: 23m3s > Physical memory: 1011 MB > Dumping 168 MB: 153 137 121 105 89 73 57 41 25 9 > > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) where > #0 doadump () at pcpu.h:195 > #1 0xc0753f07 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc07541c9 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc0a6737c in trap_fatal (frame=0xe67ea928, eva=0) at > /usr/src/sys/i386/i386/trap.c:899 > #4 0xc0a6813d in trap (frame=0xe67ea928) at /usr/src/sys/i386/i386/trap.c:686 > #5 0xc0a4df4b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #6 0xc0a5747b in spinlock_exit () at cpufunc.h:365 > #7 0xc0a53e20 in ioapic_program_intpin (intpin=0xc3f05d3c) at > /usr/src/sys/i386/i386/io_apic.c:273 > #8 0xc0a541b1 in ioapic_disable_intr (isrc=0xc3f05d3c) at > /usr/src/sys/i386/i386/io_apic.c:375 > #9 0xc0a530bc in intr_remove_handler (cookie=0xc47019c0) at > /usr/src/sys/i386/i386/intr_machdep.c:208 > #10 0xc0a5f1b1 in nexus_teardown_intr (dev=0xc3fc4a80, child=0xc4199980, > r=0xc419d6c0, ih=0xc47019c0) > at /usr/src/sys/i386/i386/nexus.c:498 > #11 0xc0774942 in bus_generic_teardown_intr (dev=0xc3fc4180, > child=0xc4199980, irq=0xc419d6c0, cookie=0xc47019c0) at bus_if.h:416 > #12 0xc0774942 in bus_generic_teardown_intr (dev=0xc3f52d00, > child=0xc4199980, irq=0xc419d6c0, cookie=
Re: cd ripping to flac
On Sat, Mar 7, 2009 at 2:12 AM, Zoran Kolic wrote:
> Howdy!
> I'd like to rip my cd-s to flac files using some
> command line app, like cdda2wav or cdparanoia.
> Using pipe to flac utility would be nice and the
> way I'd take. What program acts in that matter?
> Since cdda2wav is in the base, I suppose people
> use it regurarly. Something like:
> program {options} - | flac - flac_file.flac
> One more thing bothers me. I cannot see songs on
> the cd in the way of "/dev/acd0t1". I tried to
> stress it using cdcontrol, but no way. The kernel
> is customized, no sound in it, and a lot of others
> has gone. The box is speakers-free, so cannot
> check if it plays in deed.
Take a look at ports/audio/abcde, great command-line util with
configurable options for ripper and encoder.
-Proto
___
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: upgrading ports without recompiling
On Mon, Jul 6, 2009 at 12:04 PM, Ishmael F.E. wrote: > Hi there > . > ¿How can I upgrade my ports without having to recompile everything? > . > I allready did > # freebsd-update -r 7.2-RELEASE upgrade install > # reboot > # freebsd-update install > . > But it didn'nt upgrade the ports, so I tryed > # portupgrade -af > but it tried to compile everything > . > I also tried > # portsnap fetch > # portsnap extract > # portsnap fetch update > # portupgrade -a --batch -u -P > . > but it also tried to compile everything > . > so, ¿how can I upgrade the ports? > unfortunatley I don't have time to compile my 64bit system You could use packages provided by the FreeBSD package repositories... portupgrade -aP Although those packages will contain the standard port options, which may differ from your installed ports if you compiled them originally and changed any of the options screens. If you're looking to upgrade ports with custom options applied, then rebuilding your ports from source is your only real option. -Proto ___ 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: upgrading ports without recompiling
On Mon, Jul 6, 2009 at 12:47 PM, Michael Proto wrote: > You could use packages provided by the FreeBSD package repositories... > > portupgrade -aP > > Although those packages will contain the standard port options, which > may differ from your installed ports if you compiled them originally > and changed any of the options screens. If you're looking to upgrade > ports with custom options applied, then rebuilding your ports from > source is your only real option. > > > -Proto > Sorry, try "portupgrade -aPP" to use ONLY precompiled packages. -Proto ___ 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: pw groupadd/useradd fail when the nscd cache is used for name/group resolution
On Mon, Jul 13, 2009 at 12:57 PM, Ulrich Spörlein wrote: > On Thu, 09.07.2009 at 16:13:25 +0300, Vlad Galu wrote: >> I've stumbled upon this while installing postgres. In >> /etc/nsswitch.conf I had "group: cache files compat" and "passwd: >> cache files compat". Once I commented them out things started working >> again. Before the change, this is how it looked like: >> >> -- cut here -- >> [r...@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g >> 70 >> pw: group disappeared during update >> [r...@vgalu /usr/ports/databases/postgresql84-server]# pw group add pgsql -g >> 70 >> pw: group 'pgsql' already exists >> [r...@vgalu /usr/ports/databases/postgresql84-server]# >> -- and here -- >> >> Shouldn't 'files' be used upon a cache miss? If this is a PEBKAC, >> sorry for the noise. > > Just a me too. This is most likely because nscd is also caching negative > lookups. The usual workaround would be to restart it using > /etc/rc.d/nscd restart > A slightly lower-impact alternative would be to use "nscd -i passwd" to invalidate the password cache. -Proto ___ 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 v13 on FreeBSD 7 release/fixit iso's?
On Fri, Oct 16, 2009 at 11:58 AM, Ben Stuyts wrote: > Hi, > > I've recently upgraded a few FreeBSD-7-stable servers, and I see ZFS v13 has > made it into the tree. From what I can tell, the existing 7.2 release & > fixit cd's do not support v13 yet. > > I'd rather not upgrade the pools without a rescue cd available... Are there > any 7-stable iso's available which support zfs v13? > > Ben > > ___ > 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" > How about ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200906/ ? -Proto ___ 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: fetch hangs on AMD64 RELENG_6
Justin T. Gibbs wrote: > Hi, > > I'm seeing fetch hang under AMD64/RELENG_6 when fetching data > from several different sites. An i386 machinem sitting next to it > running current from a few weeks back is not showing this problem > when fetching the same files. The failing machine is a Dell 2850 > with an em0 device. We have a T-1 here, so transfer speeds are > usually well over 100KBps. fetch is stuck in sbwait. Restarting > fetch a few times will eventually allow the transfer to complete. > Anyone else seen this? Any hints on how I might help debug the > problem? > Are these fetches for ports installs, and if so are they from the gnu.org site(s)? I noticed a similar issue myself last night when doing some installs from ports, and they were all related to gnu.org FTP sites. Otherwise fetch was working just as expected. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Writing application
Mihir Sanghavi wrote: > Hi, > I have installed freeBSD 5.5 and am connected to the net now. I would like > to install apache and devlop some application from there. How should i > start > writing my application, execute it. I even make to figure out what > folder to > write application and how to deal with it. Thank you > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Provides a good start -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please confirm: top(1) cpu time broken on FreeBSD 6.1 (RELEASE/STABLE) SMP ?
Martin Blapp wrote: > > Hi, > >> Disable hyperthreading in your BIOS. > > Off course this is a solution, but I don't like > it. On a untuned, unmodified, unpatched system top(1) > should display the correct values IMHO. On some systems (like my Dell) it does work as expected on an untuned system, as hyperthreading defaults to off in the BIOS. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic with PF
Michal Mertl wrote: > Hello, > > I am deploying FreeBSD based application proxies' based firewall > (www.kernun.com, but not much English there) and am having frequent > panics of RELENG_6_1 under load. The server has IP forwarding disabled. > > I've got two machines in a carp cluster and the transparent proxies use > PF to get the data. > > I don't know much about kernel internals and PF but from the following > backtrace I understand that the crash happens because rpool->cur on line > 2158 in src/sys/contrib/pf/net/pf.c is NULL and is dereferenced. It > probably shouldn't happen yet it does. > > The machines are SMP and were running SMP kernel. The only places where > pool.cur (or pool->cur) is assigned to are in pf_ioctl.c. It seems there > are some lock operations though so it is probably believed that the > coder is properly locked. > > I have been running with kern.smp.disabled=1 for a moment before I put > the old firewall in place and haven't seen the panic but the time was > deffinitely too short to make me believe it fixes the issue. Can setting > debug.mpsafenet to 0 possibly also help? > ... Are you using user and/or group rules in your PF ruleset? If so, then you will want to set debug.mpsafenet to 0 as its a known issue with pf(4) currently. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iwi(4) in RELENG_6
Don Wilde wrote: >> Okay, I've gotten it working with all encryption off (raw DHCP). All the >> nasty messages went away, so I'll see what's changed in the ifconfig >> options. >> >> ifconfig_iwi0="DHCP ssid rewired channel 11 authmode shared weptxkey 1 >> wepmode on wepkey 0x1234567890" >> >> Can anybody spot it off the top? >> > > By removing the hardwired 'channel 11 authmode shared' from both sides, I > have been able to connect successfully with WEP authentication. > Just a note (and someone please correct me if I'm wrong), but setting the channel in the client's ifconfig statement is invalid in BSS mode-- it will pull the appropriate channel from the AP during the association. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.5 (VMware) on Fedora core 5
Jon Holstrom wrote: > Hello, > I am running Fedroa core 5 Dual PIII 800, with VMware server. > > I am not sure if or should i install FreeBSD 5.5 stable +SMP kernel! > I am looking at a basic web server config, > Apache 1.3 > PHP4 > MySQL 4.1 > OSCommerce > ProFTP > some sort of mail server also, POP, SMTP. > Its all for the sake of learning it and doing it as of now. > > FreeBSD is intalled as a Virutal Machine now. > but after thinking a bit, got stuck with the SMP kernel! > Unless one of the applications to be installed in your guest needs SMP its better to just use a uniprocessor kernel in VMware-Server. This is what I've gathered from the VMware discussion boards anyway. I've got 3 FreeBSD 6.1 virtual machines running happily on a P4-3.0Ghz with hyperthreading enabled, all of them uniprocessor. None are running the applications you provided but they are running DNS, mail (via postfix, spamassassin, and amavisd), and HTTP (via lighttpd) services very nicely. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.1-STABLE: Unexplained power off
Android Andrew [:] wrote: > > > Peter Jeremy wrote: >> On Tue, 2006-Aug-15 21:17:21 +0300, Apatewna wrote: >>> O/H Android Andrew [:] ??: I've checked supply voltages by digital multimeter, >> >> This won't show a noisy supply rail (eg due to high ESR capacitors). >> If you suspect power, check the rails under load (eg lots of disk >> seeks and I/O) using an oscilloscope. > I've checked voltages on MB contacts exactly under load (during port > compilation). I have no oscilloscope, so I can't control voltage > impulse, especially on multiple channels. > In this case I could only replace PSU for testing. I would recommend this based on my own personal experience. PSUs are the single most-replaced component in both my desktops and servers (white-box servers anyway), and I've spent countless hours trying to track down similar issues only to have the problem disappear when the power supply was replaced. I keep a collection of various spare PSUs at my site just for this purpose, as its often not a case of IF a power supply will start going out, but WHEN. Your mileage may vary of course, but if it were me I'd try replacing the PSU first and see if the situation improves. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPFW rules
SigmaX asdf wrote: > I'm trying to setup IPFW to block all ports except those I specify. > For starters I'm just opening SSH. > > # ipfw list > 00050 divert 8668 ip4 from any to any via rl0 > 00100 allow ip from any to any via lo0 > 00200 deny ip from any to 127.0.0.0/8 > 00300 deny ip from 127.0.0.0/8 to any > 00301 allow log tcp from any to any dst-port 22 > 00399 deny ip from any to any > 65000 allow ip from any to any > 65535 deny ip from any to any > > Traffic is still blocked on port 22 -- I can't login via SSH. What am > I doing wrong, and what rule should I be using to allow SSH in and > through? > You need to allow the return traffic. Either something like: ipfw add 1 allow tcp from any to any established or: ipfw add 1 check-state and change your port 22 rule to read ipfw allow log tcp from any to any port 22 keep-state (check the ipfw(8) man page to be sure, I haven't touched ipfw rules in a long time and my above syntax may be a bit buggy) -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: probs on 6.2-prerelease
Michael Vince wrote: > Hey all, > > I don't know if this is pre 6.2 specific but I changed my /etc/tty for > device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't > login via regular KVM console, just don't get a login. > The more alarming thing was that while it appeared everything was > booting up from the boot up messages on the screen, I couldn't remotely > log into the server in fact it appears the machine didn't bring up the > Ethernet device as I couldn't even ping it. > As soon as I switched the ttyd0 back to 'off' and rebooted it I could > ssh back into the server etc. > I have a regular kernel and 1 jail and samba on this machine. > I know this isn't a "yes I'm having problems" response but thought it might be useful anyway. I'm running 6.2-pre on a Soekris Engineering Net4501 with ttyd0 enabled in /etc/ttys and I'm not having any problems with the system booting or logging in via serial console. SSH logins work fine and the network is brought-up as normal during boot. I've had this system in the same config (in regards to /etc/ttys) since the 6 was still the HEAD branch and I have yet to see problems with it. One difference here is that I don't have any virtual consoles enabled BUT ttyd0 (and pseudo-terminals), as this box doesn't have a video card, just a serial port. FreeBSD marconi.localnet 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Tue Sep 12 03:06:13 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MINIBSD6 i386 /etc/ttys: # # $FreeBSD: src/etc/etc.i386/ttys,v 1.10 2003/10/24 15:44:08 simokawa Exp $ # @(#)ttys5.1 (Berkeley) 4/17/89 ... console noneunknown off secure # ttyv0 "/usr/libexec/getty Pc" cons25 off insecure # Virtual terminals ttyv1 "/usr/libexec/getty Pc" cons25 off insecure ttyv2 "/usr/libexec/getty Pc" cons25 off insecure ttyv3 "/usr/libexec/getty Pc" cons25 off insecure ttyv4 "/usr/libexec/getty Pc" cons25 off insecure ttyv5 "/usr/libexec/getty Pc" cons25 off insecure ttyv6 "/usr/libexec/getty Pc" cons25 off insecure ttyv7 "/usr/libexec/getty Pc" cons25 off insecure ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off insecure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 "/usr/libexec/getty std.9600" dialup on secure ttyd1 "/usr/libexec/getty std.9600" dialup off secure ttyd2 "/usr/libexec/getty std.9600" dialup off secure ttyd3 "/usr/libexec/getty std.9600" dialup off secure # Dumb console dcons "/usr/libexec/getty std.9600" vt100 off secure -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ensuring inetd is started before any RPC services
Brooks Davis wrote: > On Tue, Oct 17, 2006 at 08:46:49AM +0200, Trond Endrest?l wrote: >> I have on many occasions run into the situation where the RPC based >> services have occupied the well-known ports for other non-RPC based >> services. Last week rpc.lockd on one of my systems got hold of TCP >> port 995, leaving inetd unable to start any pop3s services. >> >> The easy cure is to add this line >> >> # BEFORE: rpcbind >> >> to /etc/rc.d/inetd. >> >> You might want to consider fixing /etc/rc.d/inetd prior to the release >> of 6.2. > > I'm pretty sure this change would break inetd's rpc service support and > would change the startup order more significantly than I think is > appropriate this late in the release cycle. > > -- Brooks What about adding a default port flag to /etc/defaults/rc.conf that doesn't conflict with /etc/services? mountd_flags="-r -p 924" (or similar) -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ensuring inetd is started before any RPC services
Michael Proto wrote: > Brooks Davis wrote: >> On Tue, Oct 17, 2006 at 08:46:49AM +0200, Trond Endrest?l wrote: >>> I have on many occasions run into the situation where the RPC based >>> services have occupied the well-known ports for other non-RPC based >>> services. Last week rpc.lockd on one of my systems got hold of TCP >>> port 995, leaving inetd unable to start any pop3s services. >>> >>> The easy cure is to add this line >>> >>> # BEFORE: rpcbind >>> >>> to /etc/rc.d/inetd. >>> >>> You might want to consider fixing /etc/rc.d/inetd prior to the release >>> of 6.2. >> I'm pretty sure this change would break inetd's rpc service support and >> would change the startup order more significantly than I think is >> appropriate this late in the release cycle. >> >> -- Brooks > > What about adding a default port flag to /etc/defaults/rc.conf that > doesn't conflict with /etc/services? > > mountd_flags="-r -p 924" (or similar) > Doh! I just read the parent and see its regarding rpc.lockd and not mountd, my mistake. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compiler Options
>From /usr/src/sys/conf/kern.mk:
# On the i386, do not align the stack to 16-byte boundaries. Otherwise GCC
# 2.95 adds code to the entry and exit point of every function to align the
# stack to 16-byte boundaries -- thus wasting approximately 12 bytes of
stack
# per function call. While the 16-byte alignment may benefit micro
benchmarks,
# it is probably an overall loss as it makes the code bigger (less efficient
# use of code cache tag lines) and uses more stack (less efficient use
of data
# cache tag lines). Explicitly prohibit the use of SSE and other SIMD
# operations inside the kernel itself. These operations are exclusively
# reserved for user applications.
#
.if ${MACHINE_ARCH} == "i386" && ${CC} != "icc"
CFLAGS+=-mno-align-long-strings -mpreferred-stack-boundary=2 \
-mno-mmx -mno-3dnow -mno-sse -mno-sse2
INLINE_LIMIT?= 8000
.endif
-Proto
Jason C. Wells wrote:
> I have set CPUTYPE=p3 in make.conf. When I compile my kernel I see
> -march=pentium3 as I expect. I also see -mno-mmx and -mno-sse are set
> which I do not expect given that -march=pentium3 is used. I presume
> that I want MMX and SSE since my processor supports it. What options do
> I set and where do I set them to get a kernel properly tuned for pentium3?
>
> Thanks,
> Jason C. Wells
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Michael Proto| SecureWorks
Unix Administrator |
PGP ID: 5D575BBE | [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: FreeBSD 6.x, NIS, local root password, and nsswitch.conf
Mark Hennessy wrote: > The machine in question having the problem with its root password being > clobbered by NIS is an NIS Slave Server running FreeBSD 6.1, the other > machines that aren't having this problem are clients running FreeBSD > 4.11, and the NIS Master Server is running FreeBSD 6.1. > > The pam config for login and su don't appear to be pointing specifically > to NIS for anything, just system. > What does /etc/passwd look like? I've seen this happen in our environment when a +entry in /etc/password is above the equivalent user account. Like if "+root..." or "[EMAIL PROTECTED]" were above the default root account. Incidentally, my /etc/nsswitch.conf looks like this and does work appropriately with NIS: group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rc doesn't see my script on boot
Gregory Edigarov wrote:
> Hello, Everybody
>
> Well, here is what I am doing:
> ls -l /usr/local/etc/rc.d
> total 30
> -r-xr-xr-x 1 root wheel 4744 Nov 13 11:38 apache22
> -r-xr-xr-x 1 root wheel 673 Nov 13 14:27 clamav-clamd
> -r-xr-xr-x 1 root wheel 722 Nov 13 14:27 clamav-freshclam
> -r-xr-xr-x 1 root wheel 1057 Nov 13 14:27 clamav-milter
> -r-xr-xr-x 1 root wheel 1254 Nov 13 13:01 gnugk
> -r-xr-xr-x 1 root wheel 198 Nov 15 01:17 l2tpd
> -r-xr-xr-x 1 root wheel 196 Nov 14 12:35 popa3d
> -r-xr-xr-x 1 root wheel 1642 Nov 13 11:19 quagga
> -r-xr-xr-x 1 root wheel 4371 Nov 13 14:00 samba
> -r-xr-xr-x 1 root wheel 1324 Nov 14 15:20 squid
> -r-xr-xr-x 1 root wheel 564 Nov 13 11:19 watchquagga
>
> cat /usr/local/etc/rc.d/l2tpd
> #!/bin/sh
>
> #PROVIDE l2tpd
> #REQUIRE NETWORKING
>
> . /etc/rc.subr
>
> name="l2tpd"
> rcvar=`set_rcvar`
> command="/usr/local/sbin/${name}"
> flags=""
> echo "l2tp debug"
>
> load_rc_config $name
> run_rc_command "$1"
>
> in rc.conf:
> l2tpd_enable="YES"
>
> Then after reboot:
> ps ax | grep l2tpd
> 667 v1 RL+0:00.00 grep l2tpd
>
> i.e no l2tpd has been started.
> no messages on console, either. My script just got silently skipped.
>
> What's wrong?
It looks like the formatting of the PROVIDE and REQUIRE statements may
be incorrect. Try:
# PROVIDE: l2tpd
# REQUIRE: NETWORKING
(note a single space between the hash mark and PROVIDE/REQUIRE, and the
colon and a single space after PROVIDE/REQUIRE)
-Proto
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpd flipping between PLL and FLL mode
Roland Smith wrote: > On Tue, Dec 19, 2006 at 04:41:51AM -0800, Jeremy Chadwick wrote: > >> Dec 19 00:22:26 icarus ntpd[624]: kernel time sync enabled 2001 >> Dec 19 01:47:48 icarus ntpd[624]: kernel time sync enabled 6001 >> Dec 19 02:04:52 icarus ntpd[624]: kernel time sync enabled 2001 > > Looks very familiar, unfortunately. > > >> I looked at the ntpd code for this, and there does not appear to >> be a way to disable logging of this message without impacting other >> important ntpd messages. :-( > > Since this is about the only message I ever see from ntpd, I put the > following line in /etc/ntpd.conf: > > logconfig -syncall > > At least this got rid of those annoying messages. Maybe syncinfo or > syncevents would be sufficient to kill these messages. I haven't checked > if LOG_NOTICE in the source code is equivalent to the message type > "info" in the manpage. > > IMHO, it violates the tradition that programs shouldn't blather. An alternate workaround I've discovered is to use a maxpoll of 9 in /etc/ntp.conf: server rolex.peachnet.edu maxpoll 9 Since implementing this I haven't seen any of the FLL/PLL flips in my logs. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpd flipping between PLL and FLL mode
Jeremy Chadwick wrote: > On Tue, Dec 19, 2006 at 10:56:22AM -0500, Michael Proto wrote: >> An alternate workaround I've discovered is to use a maxpoll of 9 in >> /etc/ntp.conf: >> >> server rolex.peachnet.edu maxpoll 9 >> >> Since implementing this I haven't seen any of the FLL/PLL flips in my logs. > > How would decreasing the polling time fix this? I do not understand > the semantics/behaviour of NTP very well. > > Taken from the manpage: > > maxpoll maxpoll > These options specify the minimum and maximum poll intervals for > NTP messages, in seconds to the power of two. The maximum poll > interval defaults to 10 (1,024 s), but can be increased by the > maxpoll option to an upper limit of 17 (36.4 h). The minimum > poll interval defaults to 6 (64 s), but can be decreased by the > minpoll option to a lower limit of 4 (16 s). > I made the change some time ago after combing newsgroups for this issue, so my memory is a little hazy, but I seem to remember something about the FLL/PLL switch being right at about 1024s. Check the Tuning section here: http://www.eecis.udel.edu/~ntp/ntpfaq/NTP-s-algo.htm -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Interrupt (SCSI?) hang on 4.x
Jeremy Chadwick wrote: > Once the machine is hung like described, since running shell > commands (date/vmstat/even spawning sh itself) involves disk I/O, > this won't work. If date and vmstat could be cached in memory > somewhere, this might work, but I don't know how one would do that. > (A memory filesystem could work, but pretty much all of / would > have to be there for this to work...) > > The best I could do would be to have a cronjob or a process running > in a screen session which does date && vmstat -i over and over to a > log file, and examine that log once the machine hung like described. > This wouldn't tell us if the numbers were increasing/fluxuating > *after* the hang, though. :-( > You *could* create a small ramdisk, copy /lib into it (along with /usr/bin/vmstat, /bin/sh, and any other needed utils), then set the LD_LIBRARAY_PATH to /mnt/lib or wherever the ramdisk is mounted and run vmstat. If you are already logged-in prior to the hang then utils on the mfs should run provided all their libraries are also on the mfs. I use a very similar process on a small Soekris box when I do an in-place flash upgrade which runs dd over the entire disk (a 32 MB compact flash card) while the box is still running from the same disk. My pre-upgrade script copies /sbin/reboot, /bin/dd, /lib/libc.so.6, and /lib/libutil.so.5 to a small mfs mounted at /mnt and sets LD_LIBRARY_PATH to /mnt prior to running dd (after which "reboot -lnq" is run, also from the mfs). -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: running mksnap_ffs
Willem Jan Withagen wrote: > Hi, > > I got the following Filesystem: > FilesystemSizeUsed Avail Capacity iused ifree %iused > /dev/da0a 1.3T422G823G34% 565952 1828334700% > > Running of a 3ware 9550, on a dual core Opteron 242 with 1Gb. > The system is used as SMB/NFS server for my other systems here. > > I would like to make weekly snapshots, but manually running mksnap_ffs > freezes access to the disk (I sort of expected that) but the process > never terminates. So I let is sit overnight, but looking a gstat did not > reveil any activity what so ever... > The disk was not released, mksnap_ffs could not be terminated. > And things resulted in me rebooting the system. > > So: > - How long should I expect making a snapshot to take: > 5, 15, 30min, 1, 2 hour or even more??? > - How do I diagnose the reason why it is not terminating? > > --WjW For a point of reference, I have 2 300GB SerialATA disks in a RAID1 config that I take daily snapshots of. df info: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ar0s1d 283810134 160945668 11718826458%/r1 As of last night, this snapshot took 18m59.77s to complete. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vBulletin
Matthew Herzog wrote: > Hi all. > > I seem to have screwed up my ports nicely. I have two versions of the > same php modules > installed. GAH! > > php5-session-5.1.6_3 The session shared extension for php > php5-session-5.2.0 The session shared extension for php > php5-shmop-5.1.6_3 The shmop shared extension for php > php5-shmop-5.2.0The shmop shared extension for php > > How do I remove the older versions? If you have /usr/ports/sysutils/portupgrade installed, try "pkgdb -F", it should prompt you to remove the old packages from your repository without actually deleting the files from the new packages. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: does -STABLE support VIA VT6103 NIC?
Brian Reichert wrote: > I'm looking at the release notes for 6.2-RELEASE: > > http://www.freebsd.org/releases/6.2R/hardware-i386.html#ETHERNET > > I'm considering the botherboard on this 1U system: > > > http://www.ironsystems.com/Customkititems.asp?kc=SYS%2DS%2DA113%2D01&Cc=ACLASS > > Which describes a VIA 'VT6103 10/100 Base-T Ethernet PHY' interface. > > This is not specifically mentioned as supported; does anyone know for sure? > According to http://developer.novell.com/yes/66541.htm, the VT6105 is a Via Rhine III adapter, which is supported by the vr driver. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Update on buildworld failing with NO_SHARED
Bill Vermillion wrote: > OK. > > So I tried using the variable documented in > /usr/share/examples/etc/make.conf of NO_DYNAMIC_ROOT. > > I rebuilt the world and kernel [I did not remove the /usr/obj/src > directory this time - maybe that's it] - but all the files > in /bin and /sbin are still "dynamically linked (users shared libs, > stripped) when I run 'file' on them. > > Is this strange, or is it just me. > > Bill According to the make.conf(5) manpage and the examples/etc/make.conf file (at least on my 6.2 box), the knob is NO_DYNAMICROOT, not NO_DYNAMIC_ROOT. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ng_deflate prob?
Brian wrote: > I cvsupped a couple days ago and a buildworld kept getting me > > make: don't know how to make ng_deflate.4. Stop > *** Error code 2 > > I see now there is an update in a cvsup this morning, just wanted to > post incase anyone else saw this. > > Brian See http://lists.freebsd.org/pipermail/freebsd-stable/2007-January/032667.html, should be fixed. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsupgrade problem on 6.2-RELEASE
Georg Bege wrote: > Hi > > Sry I dont get it, I searched now again and didnt find much. > There is nothing about this on freebsd.org. > If so then tell me where? > Please be more clearer and give me an URL or so where its pointed out >> how to manual upgrade<. > Check /usr/ports/UPDATING -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: java 1.5 diablo binaries from freebsd foundation
Jeffrey Williams wrote: > Has anyone tried loading the java 1.5 diablo binaries from the freebsd > foundation on 6.2 yet? > > Thanks > Jeff Just reinstalled my workstation at the office at the beginning of the year with 6.2 and installed the diablo-jdk-1.5.0.07.01 binary package. Been running fine for a month with no problems, browser java plugin works very nicely with Firefox 2.0. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0: ath_reset: unable to reset hardware; hal status 3
Henrik Brix Andersen wrote: > I have been searching for a replacement for my current 5212-based > atheros miniPCI card and came across these two products: > > http://www.netgate.com/product_info.php?cPath=26_34&products_id=279 > http://www.netgate.com/product_info.php?cPath=26_34&products_id=393 > > Both are based on the Atheros AR5006xs 6th generation chipset (AR5414) > but only one of them supports Super AG. > > Does anybody know if these cards will work the the ath(4)/ath_hal(4) > found in FreeBSD? > > According to the ath_hal(4) man page, the only supported cards are > those based on the Atheros AR5210, AR5211 and AR5212 chipsets? This week I ordered a ThinkPad R60 with an AR5006 PCI Express card. If you can wait a week or two, I'll have some information on FreeBSD's success with it. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SVG-based traffic grapher
Vivek Khera wrote: > > On Feb 21, 2007, at 4:17 AM, Dominik Zalewski wrote: > >> I was wondering howto do a SVG-based traffic grapher like they did in >> pfSense >> project. > > pfSense is open source, so download the source and read it... there are > no state secrets in there :-) > You can also look at the Monowall sources, http://m0n0.ch/wall, as the SVG-based grapher is there too (and I believe pfSense's version comes from Monowall). -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: kmem_malloc(16384): kmem_map too small: md-mounted /tmp filled up
Kris Kennaway wrote: > On Tue, Feb 27, 2007 at 04:24:21PM -0500, Mikhail Teterin wrote: >> The strings "panic" and "-o reserve" are mentioned in neither mdmfs(8) nor >> in >> rc.conf(5)... Is one supposed to look elsewhere? > > Yes, mdconfig, which is what creates the device (mdmfs is a legacy > wrapper for 4.x compatibility). > Isn't this backwards? mdconfig is the legacy-compatibility wrapper for mdmfs, not the other way around. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: kmem_malloc(16384): kmem_map too small: md-mounted /tmp filled up
Kris Kennaway wrote: > On Tue, Feb 27, 2007 at 04:24:21PM -0500, Mikhail Teterin wrote: >> The strings "panic" and "-o reserve" are mentioned in neither mdmfs(8) nor >> in >> rc.conf(5)... Is one supposed to look elsewhere? > > Yes, mdconfig, which is what creates the device (mdmfs is a legacy > wrapper for 4.x compatibility). Please disregard my last post I was thinking of mount_mfs, which is a compatibility interface into mdmfs, not mdconfig. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with portupgrade
Phillip Ledger wrote: > i have been trying to get portupgrade working, however everything i try > to run it im getting an error with the portsdb. now i have tryed to > rebuild it as requested initaly by portupgrade but im still getting an > error > > portupgrade -aRr > [missing key: categories] [Updating the portsdb in > /var/tmp ... - 16413 port entries found > .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000 > . done] > missing key: categories: Cannot read the portsdb! > /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database > file error (PortsDB::DBError) >from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:702:in `port' >from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:890:in > `all_depends_list' >from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:809:in `tsort_build' >from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `each' >from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:801:in `tsort_build' >from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:823:in `sort_build' >from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:827:in `sort_build!' >from /usr/local/sbin/portupgrade:721:in `main' >from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' >from /usr/local/sbin/portupgrade:220:in `new' >from /usr/local/sbin/portupgrade:220:in `main' >from /usr/local/sbin/portupgrade:2084 > > > any idea whats causeing the issue or how to fix it? Try removing /usr/ports/INDEX-6.db and running "portsdb -u", which should rebuild it from your existing /usr/ports/INDEX-6 file. (if you're using FreeBSD 5 it would be INDEX-5 above). -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: time goes slow in VmWare
Frank Behrens wrote: > Mark Dotson <[EMAIL PROTECTED]> wrote on 19 Mar 2007 9:50: >> (Add the following to /boot/loader.conf and reboot: kern.hz="100") >> >> Worked well for me. I still have minor drift (about 5 minutes after a >> week) but it can easily be handled by ntp at that point. >> >> I'd give that a try. :-) > > As I wrote in my previous post it does not work for me. :-( > After setting kern.hz to 100, have you tried the following in the .VMX file for this virtual machine: tools.syncTime="TRUE" Of course, VMWare-tools also needs to be installed in the guest. With hz=100 and this setting I haven't seen much of this problem anymore. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present)
Kris Kennaway wrote: > On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote: >> Hi, >> >> Recently I have noticed that one of our Dell PE1950's has been crashing >> a lot with the following reason "supervisor read, page not present". >> >> The system runs 6.2 Release under i386. >> >> I have attached 2 back traces, and I still have both cores if any more >> information is required. Any light that can be shed on this problem >> would be greatly appreciated. >> >> Tom >> >> === >> >> uname -a >> FreeBSD narthex.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon >> Apr 2 20:13:11 BST 2007 >> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE1950 i386 >> >> >> ## Core 1 >> >> [EMAIL PROTECTED] '13:14:47' '/home/london/tj' >>> $ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.1 >> [GDB will not be able to debug user-mode threads: >> /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you are >> welcome to change it and/or distribute copies of it under certain >> conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for details. >> This GDB was configured as "i386-marcel-freebsd". >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0x15c >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc05df61f >> stack pointer = 0x28:0xe4f63c30 >> frame pointer = 0x28:0xe4f63c90 >> code segment= base 0x0, limit 0xf, type 0x1b >>= DPL 0, pres 1, def32 1, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 12 (swi1: net) >> trap number = 12 >> panic: page fault >> cpuid = 0 >> Uptime: 1h25m33s >> Dumping 2047 MB (2 chunks) >> chunk 0: 1MB (159 pages) ... ok >> chunk 1: 2047MB (523944 pages) 2031 2015 1999 1983 1967 1951 1935 1919 >> 1903 1887 >> <7>arp_rtrequest: bad gateway 172.31.1.1 (!AF_LINK) >> <7>arp_rtrequest: bad gateway 172.31.0.1 (!AF_LINK) > > You might be hitting a bug in an obscure code path because of the > above errors. I'm CC'ing someone who might be able to help. > > Kris > Bear in mind that a recent "urgent" firmware update was released by Dell last week for 1950, 1955, and 2950 systems that is supposed to fix some data-corruption issues related to dual-core processors. I don't know if this problem is a symptom of that, but it strongly suggested to apply the firmware update regardless. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Limiting the number of probed interfaces?
Patrick M. Hausen wrote: > Hello, all! > > In former times configuring a kernel was a bit more cumbersome, > yet more straightforward than is today: > > deviceisa > devicesio0at isa? port IO_COM1 flags 0x10 irq 4 > devicesio1at isa? port IO_COM2 flags 0x0 irq 3 > > to keep the kernel from messing with the second device > completely, you simply removed the second line. > > > Today I have: > > devicepci > devicemiibus > devicebge > > I have a particular system that uses what FreeBSD 6.2 detected > as bge1 for remote console access over IP. As soon as the > interface is probed and activated by the kernel, the connection > to the remote management controller breaks. > > Is there a way to limit the number of probed entities for > a certain pci device class to, say, 1 in my case? > I'd like to use bge0 for FreeBSD but the kernel should leave > everything else that might be a bge interface alone. > > Thanks, > Patrick > Would the following in /boot/device.hints achieve what you are after? hint.bge.1.disabled="1" hint.bge.2.disabled="1" ... -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (no subject)
David Kalliecharan wrote: > Hello Everyone! > I seem to have run into a snag as I am trying to install FreeBSD Stable or > Current (preferrable stable) on a HP Pavilion dv6308ca AMD Turion X2, No > avail not even with current (installer lags?) due to the ACPI? Cannot > upgrade bios because it is at the highest version. > Anyway I was wondering about installing FreeBSD Stable on a >Compaq Presario AMD Sempron Processor 3500+ 1.8GHz Laptop (V6317CA) - > Future Shop Exclusive > > Will this go through the same problems as a dv6308ca pavilion? The reason I > ask for the compaq presario is that it has a sempron and will hopefully not > go through the same problem as a AMD turion X2. Any information will be > appreciated! I've got a AMD Sempron 3100+ in a desktop at home with a MSI mainboard and FreeBSD 6.2 installed fine on it with no problems. Haven't done much with it since the install (yet), but the install went smooth as silk. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network performance 6.1 stable vs 4.9
Stephen Clark wrote: > Dominic Marks wrote: > >> Stephen Clark wrote: >> >> >>> Hello List, >>> >>> We have a network appliance that is currently based on 4.9. We are in >>> the process of releasing >>> a new version based on 6.1 stable. >>> >> >> You are going to get asked this, so I'll ask first. >> >> Whats the reason behind not running a more recent STABLE? I understand >> developing a product on a moving platform is not ideal, but its going to >> be mentioned! >> >> >> >>> In our testing using nttcp thru the appliance we see insignifant >>> difference in thruput between the 2 >>> versions in a controlled environment - aproximately 94mbs on a 100mb >>> lan. >>> >>> We have a person that is testing the both system inhouse surfing out >>> over the internet on our T1 >>> link and he complains that he is consistently seeing the 6.1 version >>> being much slower than the >>> 4.9 version (on the same hardware). >>> He has been comparing the 6.1 system to 4.9 system for a couple of weeks >>> and continues to insist the 6.1 version is much slower. >>> >> >> You don't mention what the appliance actually does beyond just moving >> packets about? Surfing implies some sort of proxy or gateway device? >> >> >> >>> Are there any sysctl tunables that may affect performance going over the >>> internet >>> with a slower link, dropped packets, etc that could cause this? >>> >>> Any ideas would be appreciated. >>> >>> >> >> Dominic >> >> >> > Hi Dominic, > > The appliance is basically a firewall/nat/vpn device. We started on 6.1 > last year and it has > taken us a while to get things tested, plus I don't like to use a brand > new release. If we go to > a later release it means we have to do complete regression testing, etc. > > We are basically using a GENERIC config for our kernel. We, meaning the > R&D team don't see any > performance issues in a controlled environment - 6.1 performs just as > well as 4.9. > > In subjective tests R&D has done using the following setup we see "no" > problem: > > freebsd+firefox <--100mbs lan---> 6.1 network appliancelink> internet > freebsd+firefox <--100mbs lan---> 4.9 network appliance link> internet > > One of our testers has the same setup but is using winblows/ie in place of > freebsd+firefox and subjectively says the 6.1 system is slower than the > 4.9 system. > > I was just wandering if there were any tunables that might cause this. > > Thanks, > Steve > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html The section on TCP Bandwidth Delay Product might be of a little assistance. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: can I change probe order of mpt controllers?
Vivek Khera wrote: > I have a shiny new Sun X4100 here and it works pretty well (except that > there is a bug in the ILOM bios that refuses to let the serial port > console run at 115200!!!) > > I attached an external RAID array using an LSI fibre channel card, and > now the boot disk is not found after the kernel boots. Ie, it can't > find the root volume. This is because the fibre channel card is probed > as mpt0 and the on-board disks are connected to mpt2. (Where's mpt1? > no idea.) Once the RAID volume was initialized, the ordering of the > disk device names changed. > > Is there some way to force the boot drive controller to be probed first > and be mpt0? Or is there some way to force the boot drive to be a fixed > device name? > > I'm planning to play with the RAID configuraitons and change partitions > and add logical drives, etc., so this will be painful to reconfigure the > OS every time I reconfigure the RAID. Any advice will be appreciated. > Thanks! > > I'm running 6.2/amd64 from a fresh CD install. > > > > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Vivek Khera, Ph.D.Khera Communications, Inc. > Internet: [EMAIL PROTECTED] Rockville, MD +1-301-869-4449 x806 > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" I believe you can use the following in your kernel config: options ROOTDEVNAME=\"ufs:da2s1" Or whatever the appropriate device/slice for your mpt2 controller. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Installing FreeBSD 6.0 on IBM BladeCenter HS20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Damian Gerow wrote: > > Do isp/ispfw do any funkiness with the keyboard? Even when booting with > hint.atkbd.0.disabled="1", my keyboard still doesn't work. > > - Damian Try this at the loader prompt: hint.atkbd.0.flags="0x1" - -Proto -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEBEtgOLq/wl1XW74RAny1AKCJTIwIKEnVGtC6ris75rOLcc6aHQCfSSdc mOi4EES06+KuJzdGtAhWGUg= =xBWQ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broadcom BCM5714 ethernet not recognized by 6.0-RELEASE
Do you have ACPI disabled by any chance? I ran into a similar situation with a BCM5751 (I think) and 5.4 with ACPI disabled. I was able to resolve it by enabling ACPI, at which point the card was successfully recognized by the bge driver. -Proto Vivek Khera wrote: > I have an IBM e326m Opteron system for evaluation. Everything seems > to be working ok except the ethernet is not recognized. > > According to the system specs and product literature, it has two > Broadcom BCM5714 controllers in it, which the 6.0-RELEASE kernel is > not attaching. > > They identify via pciconf -l -v as follows: (had to hand-transcribe > since I can't cut/paste) > > [EMAIL PROTECTED]:4:0: class=0x02 card=0x03291014 chip=0x166a14e4 > rev=0x03 hdr=0x00 >vendor=Broadcom Corp >class=network >subclass=ethernet > > Can anyone help with appropriate defines to get the bge(4) driver to > detect this chipset? > > Thanks. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Michael Proto| [EMAIL PROTECTED] Unix Administrator | 404-417-3726 x226 SecureWorks, Inc.| Rock-solid Internet security *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_4 on flash disk and swap
In this case I'd just ignore swap. Since /dev/md0 is only a memory disk anyway, you don't really buy anything by having it as swap as opposed to unallocated RAM. Just make sure that all your running programs are able to fit in the 256Mb of RAM you have, otherwise processes will fail to start or others will die when they need to allocate additional RAM. I'm running FreeBSD in 64Mb with no swap and it works fine. A few sysctls that I've found helpful for running without swap: vm.swap_enabled=0 vm.disable_swapspace_pageouts=1 kern.ipc.shm_use_phys=1 -Proto Dmitry Pryanishnikov wrote: > Hello! > > Suppose I have machine with 256Mb of RAM and 256Mb flash ATA disk-on-module. > What configuration (using RELENG_4) should I select: > > 1. No swap at all. > 2. /dev/md0 (default 10Mb) added as a swap device. > > In other words, does RELENG_4 kernel work stable and robust w/o swap or > should I provide a minimum-size swap device? Which configuration (1 or 2) > will give more robustness in case of physical memory shortage? > > Sincerely, Dmitry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_4 on flash disk and swap
Dmitry Pryanishnikov wrote: > On Sat, 4 Mar 2006, Peter Jeremy wrote: >> Once you've received this message, the OS is free to kill your >> processes until it frees up some swap (which it can't do if you don't >> have any). I suggest you have a quick look through vm/swap_pager.c >> and vm/vm_pageout.c, looking at swap_pager_full and swap_pager_almost_full. > > This is still a concern for me. IMHO it would be useful to have the ability > to disable process killing due to the lack of swap, because having this > enabled on e.g. transit router can lead to very unpleasant scenario. Imagine > someone DoS-attacks it's sshd, and kernel kills the process with the largest > RSS - it could e.g. be a vital part of the routing software (zebra/ripd/bgpd), > and killing this process will render our router unreachable and unusable! > > Sincerely, Dmitry My suggestion would then be to utilize resource limits in /etc/login.conf for the sshd user (in your example) or other user accounts for applications that you don't want running out of control. See login.conf(5) and login_cap(3) for more details on this. In particular, the datasize, stacksize, memoryuse, and vmemoryuse options may be of benefit. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_4 on flash disk and swap
>On Fri, 10 Mar 2006, Michael Proto wrote: >> My suggestion would then be to utilize resource limits in >> /etc/login.conf for the sshd user (in your example) or other user >> accounts for applications that you don't want running out of control. >> See login.conf(5) and login_cap(3) for more details on this. In >> particular, the datasize, stacksize, memoryuse, and vmemoryuse options >> may be of benefit. > > OK, I'm aware about this measure. But have your tried it yourself against, >e.g., OpenSSH? I doubt it. Look at the following: > >[EMAIL PROTECTED] ps axu |grep ssh >root 20213 0.0 1.3 54724 3356 ?? Is4:00PM 0:00.10 sshd: dmitry > [priv] >dmitry 20216 0.0 1.3 54724 3356 ?? I 4:00PM 0:00.03 sshd: > [EMAIL > PROTECTED] >root 20229 0.0 1.3 54724 3356 ?? Ss4:00PM 0:00.10 sshd: dmitry > [priv] >dmitry 20232 0.0 1.3 54724 3356 ?? S 4:00PM 0:00.03 sshd: > [EMAIL > PROTECTED] > >It's the result of 2 incoming OpenSSH sessions: 2 processes per session, >one of them root's and another user's. SSH.COM's sshd always works as a root. >Also, during the DoS attack (simultaneous setup of many incoming TCP >connections to 22th port) there will be many root's processes like this: > >root 20278 0.0 1.1 52016 2884 ?? Is4:07PM 0:00.04 sshd: > [accepted] > >Do you really advise to lower root's limits? I'm sure you don't ;) > > >Sincerely, Dmitry >-- >Atlantis ISP, System Administrator >e-mail: [EMAIL PROTECTED] >nic-hdl: LYNX-RIPE You're correct, I could have sworn that sshd ran as the sshd user with the (somewhat) new privsep settings but it appears that I'm mistaken. My only other (albeit limited) suggestion would be to do something like inbound connection limiting that is available in pf to prevent the DOS-like scenarios you are mentioning. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpdate
cd /usr/src/usr.sbin/ntp make depend make make install gareth wrote: > On Thu 2006-03-30 (08:54), Scot Hetzel wrote: >> 2. change to sub directory where FreeBSD builds ntpdate: >> cd /usr/src/usr.sbin/ntp/ntpdate >> make clean >> make >> make install >> make clean > > cool, thanx, i found that earlier with a 'locate ntpdate | grep Makefile' > and tried to run make but it gives: > > [EMAIL PROTECTED]:/usr/src/usr.sbin/ntp/ntpdate# make > Warning: Object directory not changed from original /usr/src/usr.sbin/ntp/ntpdate > cc -O -pipe -I/usr/src/usr.sbin/ntp/ntpdate/../../../contrib/ntp/include -I/usr/src/usr.sbin/ntp/ntpdate/../ -DSYS_FREEBSD -DPARSE -DHAVE_CONFIG_H -DOPENSSL -c /usr/src/usr.sbin/ntp/ntpdate/../../../contrib/ntp/ntpdate/ntpdate.c > sh -e /usr/src/usr.sbin/ntp/ntpdate/../scripts/mkver ntpdate > Version > cc -O -pipe -I/usr/src/usr.sbin/ntp/ntpdate/../../../contrib/ntp/include -I/usr/src/usr.sbin/ntp/ntpdate/../ -DSYS_FREEBSD -DPARSE -DHAVE_CONFIG_H -DOPENSSL -c version.c > cc -O -pipe -I/usr/src/usr.sbin/ntp/ntpdate/../../../contrib/ntp/include -I/usr/src/usr.sbin/ntp/ntpdate/../ -DSYS_FREEBSD -DPARSE -DHAVE_CONFIG_H -DOPENSSL -o ntpdate ntpdate.o version.o /usr/src/usr.sbin/ntp/ntpdate/../libntp/libntp.a -lmd > cc: /usr/src/usr.sbin/ntp/ntpdate/../libntp/libntp.a: No such file or directory > *** Error code 1 > > Stop in /usr/src/usr.sbin/ntp/ntpdate. > > > and the same thing if i run 'make clean' first. there's a > directory called /usr/src/contrib/ntp/libntp/ , but there's > no libntp.a on the system. > ___ > 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: ntpdate
Just curious, do you have ipv6 enabled in your kernel and working on your Ethernet interface? It looks like you're only getting an ipv6 address returned by the resolver for nom.uct.ac.za. I did a lookup myself and I got both an ipv4 and ipv6 address: descartes:mproto/ $ host nom.uct.ac.za nom.uct.ac.za has address 137.158.128.11 nom.uct.ac.za has IPv6 address 2001:4200:300:100:20e:cff:fe5c:f5c4 Perhaps someone with a better knowledge of the resovler can answer to why no ipv4 address is returned. -Proto gareth wrote: > On Thu 2006-03-30 (10:35), Michael Proto wrote: >> cd /usr/src/usr.sbin/ntp >> make depend >> make >> make install > > yay, ok that works ta (going into /usr/src/usr.sbin/ntp > as opposed to /usr/src/usr.sbin/ntp/ntpdate) and the > binary gets rebuilt. but, same problem :/ > > # ntpdate nom.uct.ac.za > Looking for host nom.uct.ac.za and service ntp > host found : 2001:4200:300:100:20e:cff:fe5c:f5c4 > 30 Mar 17:58:16 ntpdate[35787]: cannot find family compatible socket to send ntp packet > # > ___ > 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: bind() fd 6, family 28, port 123 at boot time
Miguel wrote: > Hi, looking at the messages i see errors with ntp everytime i reboot my > server: > > shiva2# tail /var/log/messages > Apr 5 15:32:46 shiva2 kernel: Trying to mount root from ufs:/dev/da0s1a > Apr 5 15:32:46 shiva2 ntpd[385]: ntpd 4.2.0-a Tue Mar 14 04:43:54 UTC > 2006 (1) > Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 6, family 28, port 123, addr > fe80:1::20b:cdff:fe42:3d63, in6_is_addr_multicast=0 flags=0 fails: Can't > assign requested address > Apr 5 15:32:46 shiva2 ntpd[385]: bind() fd 7, family 28, port 123, addr > fe80:2::20b:cdff:fe42:3d62, in6_is_addr_multicast=0 flags=0 fails: Can't > assign requested address > Apr 5 15:32:47 shiva2 kernel: bge0: link state changed to UP > Apr 5 15:32:48 shiva2 kernel: bge1: link state changed to UP > Apr 5 15:33:51 shiva2 ntpd[385]: sendto(200.138.151.150): No route to host > Apr 5 15:36:03 shiva2 ntpd[385]: kernel time sync disabled 2041 > Apr 5 15:37:08 shiva2 ntpd[385]: kernel time sync enabled 2001 > > > someone suggested in the archives that disabling ipv6 could resolv the > problem, i already commented out options inet6 and recompiled the > kernel, i think the time is syncronized thoug. > what can i check? > --- > Miguel > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > I've seen the "sendto... no route to host" error myself, although I'm not sure if you are seeing the same behavior I was. In my case, my external interface was a Netgraph tunnel interface (ng0) ports/net/mpd which would sometimes die at the hands of my Internet provider. When the tunnel would die and then get rebuilt, ntpd would give this error because it was still bound to the old tunnel. My fix was to create an mpd startup script that would restart ntpd whenever ng0 was recreated. In any case, perhaps it is due to your Internet connection not being available when ntpd starts? You could verify that your time is still being synced by running ntpdc at the command line, then running "peers" at the prompt. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Odd "phantom MFS mountpoint" issue
H. Wade Minter wrote: > I've got a 5.4-RELEASE-p9 system that I was doing some memory filesystem > testing on. I'm seeing something odd, though - a small MFS partition > mounted over top of /tmp that I can't get rid of. > > Here's the system now: > > [EMAIL PROTECTED] mrvoice]$ mount > /dev/ad0s1a on / (ufs, local, soft-updates) > devfs on /dev (devfs, local) > /dev/ad0s1d on /tmp (ufs, local, soft-updates) > /dev/ad0s1f on /usr/www (ufs, local, soft-updates) > /dev/ad0s1e on /var (ufs, local, soft-updates) > /dev/md0 on /tmp (ufs, local) > > There's no md0 line in /etc/fstab: > > [EMAIL PROTECTED] mrvoice]$ cat /etc/fstab > # DeviceMountpoint FStype Options Dump > Pass# > /dev/ad0s1b noneswapsw 0 0 > /dev/ad0s1a / ufs rw 1 1 > /dev/ad0s1d /tmpufs rw 2 2 > /dev/ad0s1f /usr/wwwufs rw 2 > 2 > /dev/ad0s1e /varufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > > I can see the md0 device with mdconfig: > > [EMAIL PROTECTED] ~]# mdconfig -l > md0 > > I can stop all activity on /tmp, unmount it, and do mdconfig -d -u 0 to > delete the resources. However, when I reboot the system, the mountpoint > is back. I can't tell where the system is getting that from. > > How should I remove this mfs mountpoint permanently to get the disk-based > /tmp back? > > --Wade Do you have tmpmfs defined in /etc/rc.conf? If tmpfs is enabled there it will create a /tmp mfs as you are indicating. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Odd "phantom MFS mountpoint" issue
H. Wade Minter wrote: > On Mon, 10 Apr 2006, Michael Proto wrote: > >>> How should I remove this mfs mountpoint permanently to get the disk-based >>> /tmp back? >>> >>> --Wade >> Do you have tmpmfs defined in /etc/rc.conf? If tmpfs is enabled there it >> will create a /tmp mfs as you are indicating. > > Not that I see: > > [EMAIL PROTECTED] ~]$ grep -i tmp /etc/rc.conf > [EMAIL PROTECTED] ~]$ > > Thanks, > Wade Does /tmp exist and is writable when the system is started? Looking at the test in /etc/rc.d/tmp, it looks like /tmp will be mounted as a mfs if "/bin/mkdir -p /tmp/.diskless" fails. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Brian Szymanski wrote: > Hi... > > I saw this in the 6.1 release notes and eagerly upgraded: > "The amr(4) driver now supports ioctl(2) requests necessary for Linux > LSI MegaRaid tools on FreeBSD's Linux emulation environment." > > However, when I pulled over a megamgr.bin binary from a linux machine, and > try to execute it on my freebsd machine, I get: > [EMAIL PROTECTED] ~/src/megaraid]# ./megamgr.bin > ELF binary type "0" not known. > bash: ./megamgr.bin: cannot execute binary file > > Has anyone got this working? What did they need? Any help would be > appreciated, as I'm seriously sick of megarc :) > > Thanks in advance! > Since it appears to require Linux emulation, have you tried branding the binary is a Linux ELF with brandelf(1)? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Brian Szymanski wrote: > Oh, duh, it's been so long since I used linux binary emulation that I > forgot all about brandelf... Thanks Michael! > > ... But now that the binary is properly branded, I get a different error: > Error opening terminal: xterm. > I get the same error for xterm-color, cons25, vt220, and everything else > I've tried... (and I know for a fact that TERM=xterm works on my linux > machines)... Any ideas? I suspect its looking for xterm in your /compat/linux emulation environment. I don't know if there's a linux-xterm port available (I didn't see one), but you *might* be able to get away with hardlinking or copying /usr/X11R6/bin/xterm to /compat/linux/usr/X11R6/bin/xterm (assuming you have linux-XFree86-libs or linux-xorg-libs installed). Perhaps someone better versed in X11 and Linux emulation can answer to this. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 6.1-RELEASE problems with make buildkernel
Don't you want a release tag of RELENG_6_1 and not RELENG_6_1_0_RELEASE? -Proto Yousef Raffah wrote: > Hi, > > I'm trying to upgrade from 6.1-RC to 6.1-RELEASE > > my cvssup file is: > *default host=cvsup3.de.FreeBSD.org > *default base=/var/db > *default prefix=/usr/ > *default tag=RELENG_6_1_0_RELEASE > *default release=cvs delete use-rel-suffix compress > src-all > > my /etc/make.conf is: > # added by use.perl 2006-03-31 21:01:28 > PERL_VER=5.8.8 > PERL_VERSION=5.8.8 > CPUTYPE=pentium3 > NO_I4B=true > NO_INET6=true > NO_RCMDS=true > NO_SHAREDOCS=true > ENABLE_WPA_SUPPLICANT_EAPOL=true > > After cvsupping using the above cvs-supfile, I managed to buildworld > with problems (I get a lot of segmentation fault 11) but it completed > the build after several tries. > Now the problem comes when building the kernel. To insure I have a > working "world", I thought of building a new GENERIC kernel, therefore, > I used the following, assuming this would build a new GENERIC Kernel; > > # cd /usr/src > # make buildkernel > > Unfortunately, it keeps on failing with the following: > > MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh > GENERIC > cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/contrib/altq > -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf > -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd > -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -ffreestanding -Werror vers.c > linking kernel.debug >textdata bss dec hex filename > 5951318 622880 323724 6897922 694102 kernel.debug > objcopy --strip-debug kernel.debug kernel > cd /usr/src/sys/modules; > MAKEOBJDIRPREFIX=/usr/obj/usr/src/sys/GENERIC/modules > KMODDIR=/boot/kernel DEBUG_FLAGS="-g" MACHINE=i386 > KERNBUILDDIR="/usr/obj/usr/src/sys/GENERIC" /usr/obj/usr/src/make.i386/make > all > ===> 3dfx (all) > cc -O2 -fno-strict-aliasing -pipe -march=pentium3 -Werror -D_KERNEL > -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS > -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ > -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g > -I/usr/obj/usr/src/sys/GENERIC -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -ffreestanding -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 > -c /usr/src/sys/modules/3dfx/../../dev/tdfx/tdfx_pci.c > ld -d -warn-common -r -d -o 3dfx.kld tdfx_pci.o > touch export_syms > awk -f /usr/src/sys/modules/3dfx/../../conf/kmod_syms.awk 3dfx.kld > export_syms | xargs -J% objcopy % 3dfx.kld > *** Error code 1 > > Stop in /usr/src/sys/modules/3dfx. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/GENERIC. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > Any suggestions? :'( > > > -- > Sincerely, > Yousef Raffah > Senior Systems Administrator > -- > > Aren't you using Firefox? Get it at http://www.getfirefox.com > > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel can't find root filesystem
Robert Ames wrote: >> From: "M.Hirsch" <[EMAIL PROTECTED]> >> >> I had the same problem with 6.1. But only on some occasions, not >> always (iirc). >> The installations I made over the last weeks had all very different >> environments and deployment methods. >> I can't tell anymore when it happens and when not because I simply >> added the below loader.conf setting to my postinstall-script. >> >> Add "vfs.root.mountfrom=ufs:da0s1" to /boot/loader.conf to fix it. > > Thank you. That solves my problem even though it seems more like > a workaround than an actual solution. But I'll take it. :-) > > Also, someone responded asking if I had a valid entry in /etc/fstab > for the root filesystem. > > foo# cat /etc/fstab > # DeviceMountpoint FStype Options Dump > Pass# > /dev/da0s1a / ufs rw > 1 1 > /dev/da0s1b none swapsw > 0 0 > /dev/da1s1d /local ufs rw > 2 2 > /dev/cd0/cdrom cd9660 ro,noauto > 0 0 > If I'm not mistaken, you could also try to (re)install the boot0 loader: boot0cfg /dev/da0 -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wi0 down when print a lot of data to screen over ssh
Ren Zhen wrote: > wi0 goes down when I run a program print a lot of data to > stdout, or when I use zmrx-zmtx it also goes down. > > kernel says: > kernel: wi0: timeout in wi_seek to 152/0 > last message repeated 7 times > kernel: wi0: device timeout > kernel: wi0: timeout in wi_seek to 152/0 > kernel: wi0: link state changed to DOWN > > another time kernel says: > kernel: wi0: timeout in wi_cmd 0x010b; event status 0x8000 > kernel: wi0: xmit failed > kernel: wi0: timeout in wi_seek to 128/0 > last message repeated 3 times > I used to see similar behavior with wi0 on my ThinkPad A30p (IBM High Rate Wireless, PRISM 2.5) when powersave was enabled via ifconfig (I believe it may be on by default, not sure about that). If you disable powersave via 'ifconfig wi0 -powersave' do you still see the problem? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with fetch
Christopher Hobbs wrote: > I'm a first time poster, so forgive me if this is the wrong list or if I break > etiquette. > > Fetch frequently fails for me when installing ports via "pkg_add" or directly > from the ports tree. Regardless of the port I'm trying to add, it almost > always > returns the following... > > Using 'pkg_add': > > --BEGIN SNIP-- > > [EMAIL PROTECTED]:~ 160:0# pkg_add -r xpdf > Error: FTP Unable to get > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz: > Syntax error in parameters or arguments > pkg_add: unable to fetch > 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz' > by URL > > --END SNIP-- ... This is probably better-suited to the freebsd-questions@ list, but I'll take a quick stab at it. Could it be that you're behind a firewall or FTP proxy that doesn't support active FTP transfers? You mentioned you tried several of the knobs for fetch, but did you try the same fetch with the -p flag? fetch -p ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.1-release/Latest/xpdf.tbz -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
