Re: natd in a jail
> I've not used it myself, but this sound like something VIMAGE may be good > for, basically it's a virtual tcp stack per jail, there's some docs at > http://wiki.freebsd.org/Image but I seem to remember a more up to date one > elsewhere but can't find it at the moment! AFAIK, VIMAGE is still experimental feature. ___ 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: console in graphic mode
2012/8/6 Eugene M. Zheganin : > I'm trying to play with a console in graphic mode and with UTF-8 in it. > Nowadays device sc and options SC_PIXEL_MODE are in GENERIC, so I added only > the > > options TEKEN_UTF8 > > and built/installed the new kernel. > > Now I'm stuck in a pretty stupid situation: my monitor refuses to work in > any of the graphical mode available. Only text modes are working. > My monitor is a Dell E177FP, it's manufactured in 2006. I understand that > this isn't the last model, but still it's not a museum showpiece. > > Can something be done in this situation ? > You need VESA and X86BIOS support in your kernel (for i386/amd64 archs). options VESA is already included in GENERIC, you need to add options X86BIOS to kernel config file or load modules during boot process (man loader.conf) wbr ___ 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: LibreOffice crashes after buildworld
> I've rebuilt world (9-stable amd64) from fresh sources and found out that the > LibreOffice Calc application crashes with core dump during start. LibreOffice > worked fine with my previous system (dated June 27). Any tips? Sometimes you should rebuild all your ports after rebuilding world. Try to debug core dump and get backtrace. --- wbr, Nickolas ___ 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: Why Are You NOT Using FreeBSD ?
>> Hmm, in my local testing we've been able to use the 40G mlxen(4) >> adapters fine with the OFED stack. I believe we have also done a bit >> more involved testing on the IB side than just ping as well (at least >> RX and TX of UDP packets). >> > Well, it didn't work for us. We have the connext3 cards. And our goal > was making iscsi-over-RDMA and NFS-over-RDMA work. Though at the end > we've settled with linux and not using RDMA, because that's kinda messy. > > When we've tried to do some testin with netcat, no packets were > transmitted really. They've got somewhere lost, there had been some > error message in the syslog, which i can't recall now. We felt like the > packets are getting lost somewhere between the OFED and the IP stack. > Have you run subnet manager (e.g. opensm)? Infinband networks doesn't work without it. --- wbr, Николай ___ 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: (bsd)tar and multi-volume
Hello, Harald. To create multivolume archive, you may use tar + split. --- wbr, Nickolas 2012/6/16 Harald Schmalzbauer : > Hello, > > according to tar(1), the base system tape archiver is bsdtar since 8.x , > which lacks support for multi-volumes. > I guess I can easily omit that restriction by installing gtar from > archivers/ in the ports collection. > Is there any plan to implement split volume support again for the base > system? Any better app to feed tapes these days in FreeBSD? > > Regards, > > -Harry > > ___ 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 couldn't resolve host name on system boot
Matthew, netwait script is already implemented: http://lists.freebsd.org/pipermail/svn-src-head/2011-June/028593.html So, you shuld just add netwit_* entries in your rc.conf file. 2012/5/17 Matthew Doughty : > Dear Jerermy, > > Whilst searching for a solution to a problem, I found your post: > http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064350.html > > Please could you explain how I can implement the netwait script to solve > the problem? I'm new to freenas/BSD but am willing to try working from the > Cmd line. > > Best regards, > > Matthew > > > PS: Here are the messages > > May 14 13:32:59 freenas kernel: SMP: AP CPU #1 Launched! > > May 14 13:32:59 freenas kernel: GEOM: da0s1: geometry does not match label > (16h,63s != 255h,63s). > > May 14 13:32:59 freenas kernel: GEOM: da0s2: geometry does not match label > (16h,63s != 255h,63s). > > May 14 13:32:59 freenas kernel: Trying to mount root from > ufs:/dev/ufs/FreeNASs2a > > May 14 13:32:59 freenas kernel: WARNING: /data was not properly dismounted > > May 14 13:32:59 freenas kernel: ZFS filesystem version 4 > > May 14 13:32:59 freenas kernel: ZFS storage pool version 15 > > May 14 13:33:00 freenas ntpd[1512]: ntpd 4.2.4p5-a (1) > > May 14 13:33:00 freenas root: /etc/rc: WARNING: failed precmd routine for > vmware_guestd > > May 14 13:33:02 freenas ntpd_initres[1526]: host name not found: > 0.freebsd.pool.ntp.org > > May 14 13:33:02 freenas ntpd_initres[1526]: couldn't resolve ` > 0.freebsd.pool.ntp.org', giving up on it > > May 14 13:33:02 freenas ntpd_initres[1526]: host name not found: > 1.freebsd.pool.ntp.org > > May 14 13:33:02 freenas ntpd_initres[1526]: couldn't resolve ` > 1.freebsd.pool.ntp.org', giving up on it > > May 14 13:33:02 freenas ntpd_initres[1526]: host name not found: > 2.freebsd.pool.ntp.org > > May 14 13:33:02 freenas ntpd_initres[1526]: couldn't resolve ` > 2.freebsd.pool.ntp.org', giving up on it > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [stable-9] Touchpad mouse stopped working
2012/5/17 Tom Evans : > /usr/local/etc/rc.d/gdm onestart ; sleep 20 ; /usr/local/etc/rc.d/gdm > onerestart > > Normally after it has restarted once, X can finally talk to hald and > find the mice and keyboards. I have the same problem. ___ 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: booting 8.2 on Gigabyte GA-790XTA-UD4
>> I am having problems booting the FreeBSD 8.2 CD image on >> GA-790XTA-UD4(rev. 1.0). The last thing that I can see is "BIOS drive A: >> is disk0". Is this completely not supported? Can I do anything to >> install FreeBSD on such box? > > Have you done the usual stuff? > - if not running the latest BIOS, try to update > - try to fiddle with relevant settings in BIOS > - Try another release of FreeBSD (older or newer), or a new snapshot > - Google "name of board + FreeBSD" You've fogot about BIOS SATA/IDE setting. Try to play with it. --- wbr, Nickolas ___ 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 on geli vs. geli on zfs (via zvol)
2011/7/1 Todd Wasson : > Thanks to both C. P. and Pete for your responses. Comments inline: > >> Case 1.) is probably harmless, because geli would return a >> corrupted sectors' content to zfs... which zfs will likely detect >> because it wouldn't checksum correctly. So zfs will correct it >> out of redundant storage, and write it back through a new >> encryption. BE CAREFUL: don't enable hmac integrity checks >> in geli, as that would prevent geli from returning corrupted >> data and would result in hangs! > > Perhaps the hmac integrity checks were related to the lack of reporting of > problems back to zfs that Pete referred to? Maybe we need someone with more > technical experience with the filesystem / disk access infrastructure to > weigh in, but it still doesn't seem clear to me what the best option is. > >> Case 2.) is a bigger problem. If a sector containing vital >> geli metadata (perhaps portions of keys?) gets corrupted, >> and geli had no way to detect and/or correct this (e.g. by >> using redundant sectors on the same .eli volume!), the whole >> .eli, or maybe some stripes out of it, could become useless. >> ZFS couldn't repair this at all... at least not automatically. >> You'll have to MANUALLY reformat the failed .eli device, and >> resilver it from zfs redundant storage later. > > This is precisely the kind of thing that made me think about putting zfs > directly on the disks instead of geli... This, and other unknown issues that > could crop up and are out of geli's ability to guard against. > Agree. If you wanna have encrypted ZFS it's better to wait until zpool version 30 (which supports encryption) will be ported to FreeBSD. --- wbr, Nickolas ___ 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"
GPT labels and gjournal
Hello stable. I've tried to make two journaled partitions on new GPT disk. Partitions have GPT labels storage and backup: gpart show -l ada1 =>34 2930277101 ada1 GPT (1.4T) 34 8388608 1 (null) (4.0G) 8388642 2415919104 2 storage (1.1T) 2424307746 8388608 3 (null) (4.0G) 2432696354 497580781 4 backup (237G) gjournal label /dev/gpt/storage /dev/gptid/3570dff6-9a73-11e0-ad0e-001e8c0ecc19 gjournal label /dev/gpt/backup /dev/gptid/58db2577-9a73-11e0-ad0e-001e8c0ecc19 newfs -J /dev/gpt/storage.journal newfs -J /dev/gpt/backup.journal Where 3570dff6-9a73-11e0-ad0e-001e8c0ecc19 is GPT UUID of ada1p1 and 58db2577-9a73-11e0-ad0e-001e8c0ecc19 is GPT UUID of ada1p3 partition. This partitions have been added to fstab: /dev/gpt/storage.journal /mnt/storage ufs async,rw 0 0 /dev/gpt/backup.journal /mnt/backup ufs async,rw 0 0 After reboot system doesn't wanna see gpt-labeled partitions /dev/gpt/storage.journal and /dev/gpt/backup.journal (so, mount fails) but has /dev/ada1p2.journal and /dev/ada1p4.journal instead. How can I mount this partitions using GPT labels? uname -a FreeBSD cloud 8.2-STABLE FreeBSD 8.2-STABLE #37 r223311: Mon Jun 20 04:16:22 EEST 2011 root@cloud:/usr/obj/usr/src/sys/CLOUD amd64 Options GEOM_PART_GPT, GEOM_LABEL and GEOM_JOURNAL present in kernel configuration file. --- wbr, Nickolas ___ 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"
UFS SU+J
Hi all! I' like to know, if there plans to MFC journaled softupdates to 8-stable? If yes, when it would be done? Thanks. wbr, Nickolas ___ 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: doscmd under 8-stable, anyone?
2011/6/15 Jeremy Chadwick :
> On Wed, Jun 15, 2011 at 03:57:05PM +0200, Joerg Wunsch wrote:
>> When trying to use doscmd on 8-stable, all I get is:
>>
>> Error mapping HMA, HMA disabled: : Invalid argument
>> Segmentation fault (core dumped)
>>
>> The segfault happens at the end of mem_init(), when the allocated DOS
>> memory (which is located at virtual address 0) is attempted to be
>> written to. Apparently, the mmap() failure that causes the "HMA
>> disabled" message is actually a fatal error rather than a benign one
>> the could be ignored, as it results in no valid DOS memory allocation
>> at all.
>>
>> Right now, the only older system I could test it against uses FreeBSD
>> 5.x, where the mmap() works as expected. So does anyone have an idea
>> why this mmap() call:
>>
>> if (mmap((caddr_t)0x00, 0x10,
>> PROT_EXEC | PROT_READ | PROT_WRITE,
>> MAP_ANON | MAP_FIXED | MAP_SHARED,
>> -1, 0) == MAP_FAILED) {
>> perror("Error mapping HMA, HMA disabled: ");
>> HMA_a20 = -1;
>> close(HMA_fd_off);
>> close(HMA_fd_on);
>> return;
>> }
>>
>> yields an EINVAL now under 8-stable?
As I remember, mapping of "zero" page forbidden by default.
> I imagine that the page size ordeal is probably what's biting you. Now,
> I'm not sure if page size in that above context refers to "kernel page
> size" (e.g. hw.pagesizes or hw.pagesize) or if it refers to "a page of
> memory" as in what libc/malloc uses.
It refers. mmap(2) is system call.
On i386/amd64 "big" page size is 2MB, and code above is trying to
allocate 1MB, so memory will be allocated with 4KB-sized pages.
>
> I'm not sure why a person would need or want MAP_FIXED in this
> situation; why can't they just take the result of mmap() (a void *) and
> use that as a base address offset instead of assuming zero in their
> software?
AFAIK, doscmd is trying to emulate real mode on real hardware while
being in protected mode, thus it want first pages of memory.
Another way to do the same thing - open /dev/mem and call mmap() at zero offset.
___
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: [SOLVED] Re: labelling root file system (RELENG_8)
2011/6/8 Josh Carroll : >>> That would mean the only time a >>> person can use tunefs on a root filesystem is when they either do it >>> manually during the FreeBSD installation (adding "-t" to the list of >>> newfs flags in the filesystem creation UI), or if they boot off of some >>> other medium (USB flash drive, CD, PXE, etc.). >> >> Or when your root fs is mounted r/o, which is not as bad as what you listed >> above. Or when you've booted form device (not label), e.g. /dev/ada0s1a and have set sysctl kern.geom.debugflags=16 > > Perhaps I'm doing something wrong, but in my experience, at least with > glabel, the label will not stick even if you have the root fs mounted > ro. I have had to boot from an alternative media (boot cd, alternate > root fs, etc) in order to create a label for the root fs with glabel. > To be specific, I'm talking about the "automatic" labels created with > glabel label . > > I just tested this again in a VM, and sure enough if I boot single > user mode but use ad0s1a as the ro root file system during single user > mode, it still doesn't stick and upon reboot I don't have a /dev/label > entry. Here is the exact sequence I used: > > 1. boot single user with the default root fs (ad0s1a). > 2. leave / mounted read only > 3. glabel label -v root ad0s1a # reports successful addition of metadata > 4. /dev/label/root exists as expected > 5. reboot > 6. /dev/label/root does not exist You should mount fs from label device - /dev/label/root in your case, which must be in /etc/fstab, e.g.: /dev/label/root/ufs rw1 1 Otherwise if you mount fs from device directly (not from label) label entry (/dev/label/root) would be removed from /dev file system as unused device. This action will be reported in dmesg (you may check it) So, afrer labeling device you should add fstab record. After that you can reboot. ___ 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: [SOLVED] Re: labelling root file system (RELENG_8)
2011/6/8 Matthias Andree : > Am 08.06.2011 15:11, schrieb nickolas...@gmail.com: >> 1. Change your root fstab record to /dev/ada0s4a (not label!), reboot >> to single mode and try to re-label partition. > > Indeed not mounting from the label was (apparently) the key to solve > this. Thank you. > > In fact the successful procedure was: > > - from boot menu, escape to loader prompt > - set vfs.root.mountfrom=ufs:/dev/ada0s4a > - boot -s > - tunefs -L mylabel /dev/ada0s4a > - mount -a > - edit /etc/fstab to use /dev/ufs/mylabel as device for / > - shutdown -r now > Right, you cannot re-label partition because you've mount filesystem through label device. So this device is already in use and re-labeling would destroy label device. - wbr, Nickolas ___ 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: labelling root file system (RELENG_8)
1. Change your root fstab record to /dev/ada0s4a (not label!), reboot to single mode and try to re-label partition. 2. Try boot from live CD or installation CD (fixup console) and label file system without mounting 2011/6/8 Matthias Andree : > Greetings, > > I've tried to re-label an existing (and up to date) 8-STABLE > installation's root partition. This failed, tunefs reports it cannot > write the super block. > > I have attempted this sequence: > > 1. reboot (through BIOS and loader) directly into single-user mode > (boot -s) > 2. sysctl kern.geom.debugflags=16 > 3. tunefs -L root /dev/ada0s4a # that's the dev I mount the root > # partition from > > Still no joy => tunefs cannot update the super block. > > Remounting / as rw doesn't help, as expected. > > The root fs uses softupdates but no journalling -- what other hoops do I > need to jump through to create labels for my root ufs file system? > > Thanks. > > Best regards, > Matthias > ___ > 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" > --- wbr, Nickolas ___ 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: mountlate not late enough for nfe0 with dhcp
2011/5/27 Jeremy Chadwick : > This has been discussed at length in the past, causing me to write an > rc.d script to work around the problem. You can drop this script into > /usr/local/etc/rc.d, chmod 755 it, and make use of it appropriately. > The comments in the script should help you understand it. > > http://jdc.parodius.com/freebsd/netwait > > Example entries in rc.conf: > > netwait_enable="yes" > netwait_ip="4.2.2.1 4.2.2.2" > netwait_if="em0" Maybe it's time to add this script to -STABLE? Problem touch many people, who need it (IMHO) ___ 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: Enabling DDB prevent kernel from panicing
Hello, Mark 2011/1/11 Mark Saad : > All > This was originally posted to hackers@ > > I have a good question that I cant find an answer for. I believe > found a kernel bug in 7.3-RELEASE that prevents me from booting 64-bit > kernels on HP's DL360 G4p . The kernel dies with "Fatal trap 12: page > fault while in kernel mode " . The hardware works fine in 7.2-RELEASE > amd64, 7.1-RELEASE amd64, and 6.4-RELEASE amd64 . > > In 7.3-RELEASE amd64 I can not boot from cd or pxe correctly using the > stock 7.3-RELEASE amd64 kernel however i386 works fine. To see if this > issue was some how fixed in 7.3-RELEASE-p4 amd64 I rebuilt a GENERIC > kernel using patches sources and tried to boot and I got the same > crash. > > Next I rebuilt the kernel with KDB and DDB to see if I could get a > core-dump of the system. I also set loader.conf to > > kernel="kernel.DEBUG" > kern.dumpdev="/dev/da0s1b" > > Next I pxebooted the box and the system does not crash on boot up, it > will easily load a nfs root and work fine. So I copied my debug > kernel, and loader.conf to the local disk and rebooted and it boots > fine from the local disk . Looks like a race condition. Well, you don't need to compile KDB and DDB, just add makeoptions DEBUG=-g into your kernel config file and rebuild kernel. Then after you got a crash dump you can easy debug it (see FreeBSD Developers Handbok): http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html wbr, Nickolas ___ 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 running 8.1R on KVM with AMD hosts
> http://lukemarsden.net/8.1R-KVM-AMD-failure.png This picture is useless. No debug symbols == no useful information. 1. Please, build your kernel with debug symbols. Your kernel configuration file should contain string makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols 2. Show kgdb output, as described here: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html ___ 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: SuperMicro i7 (UP) - very slow performance
> md5 -t is quite a small benchmark, even with his misfunctioning CPU it > took <6 seconds to complete. > > If his problem is a misapplied heatsink/fan, then his CPU could be > throttling when it gets hot, the hotter it gets the more it throttles, > which could explain his massive buildworld walltime. Perhaps running > something like: > > apply -0 "md5 -t" `jot 10` > > would display a notable difference. You may also run openssl speed or "linpack" test (/usr/ports/math/linpack) or hpl (/usr/ports/benchmarks/hpl) to load your CPU ___ 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: Policy for removing nonworking code
2010/9/9 Andriy Gapon : > on 09/09/2010 12:33 Andriy Gapon said the following: >> People, who care, are expected to read current@ and stable@ even if they use >> only releases and security branches. At the very least, to see what's >> cooking >> up for them and what to expect. > > Not to mention isdn@ for this particular case. > BTW, I changed the subject line, because the code in question became > non-working > when Giant support in network stack was dropped. Please, stop this useless thread ___ 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: csup: Invalid greeting from server
2010/7/6 Alexander Petrovsky : > Wrong! > http://www.freebsd.org/doc/en/books/handbook/cvsup.html What's wrong? This config file hasn't changed since 8.0 release date and everything was fine. So, it's either server or client problem. But it's not config file problem! > 2010/7/6 >> >> Hi all! >> >> Is everything OK with cvsup.freebsd.org? >> I got message "Invalid greeting from server" during last two days: >> >> csup -L 2 /etc/supfile >> Parsing supfile "/etc/supfile" >> Connecting to cvsup.freebsd.org >> Connected to 72.233.193.64 >> Invalid greeting from server >> >> My supfile looks like this: >> >> *default host=cvsup.freebsd.org >> *default base=/var/db >> *default prefix=/usr >> *default release=cvs >> *default compress delete use-rel-suffix >> >> src-all tag=RELENG_8 >> ports-all tag=. >> doc-all tag=. >> ___ >> 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" > > > > -- > Петровский Александр / Alexander Petrovsky, > > ICQ: 350342118 > Jabber: ju...@jabber.ru > Phone: +7 914 8 820 815 > ___ 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"
csup: Invalid greeting from server
Hi all! Is everything OK with cvsup.freebsd.org? I got message "Invalid greeting from server" during last two days: csup -L 2 /etc/supfile Parsing supfile "/etc/supfile" Connecting to cvsup.freebsd.org Connected to 72.233.193.64 Invalid greeting from server My supfile looks like this: *default host=cvsup.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs *default compress delete use-rel-suffix src-all tag=RELENG_8 ports-all tag=. doc-all tag=. ___ 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"
Kernel panic in pppoe_findsession (ng_pppoe.c)
Hello!
Yestarday I've got 4 kernel panics with the same problem - page fault
while in kernel mode, in netgraph pppoe module.
I've defined, that fault produce pppoe_findsession() function - see below.
Here is the contents of /var/crash/info.5 file:
Dump header from device /dev/gpt/swap
Architecture: amd64
Architecture Version: 2
Dump Length: 1490821120B (1421 MB)
Blocksize: 512
Dumptime: Tue Jun 29 14:35:53 2010
Hostname: cloud
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.1-PRERELEASE #18: Sun Jun 6 00:32:09 EEST 2010
r...@cloud:/usr/obj/usr/src/sys/CLOUD
Panic String: page fault
Dump Parity: 4273635620
Bounds: 5
Dump Status: good
I can give more information, if you need (core.txt.5 file, kernel
config file, etc).
And here is kgdb log:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x8064ed050
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x803c2869
stack pointer = 0x28:0xff803bee7880
frame pointer = 0x28:0xff803bee78c0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (nfe0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 19d12h24m25s
Physical memory: 2024 MB
Dumping 1421 MB: 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262
1246 1230 1214 1198 1182 1166 1150 1134 1118 1102 1086 1070 1054 1038
1022 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766
750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494
478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222
206 190 174 158 142 126 110 94 78 62 46 30 14
Reading symbols from /boot/kernel/vesa.ko...Reading symbols from
/boot/kernel/vesa.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/vesa.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/sound.ko...Reading symbols from
/boot/kernel/sound.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from
/boot/kernel/snd_hda.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/snd_hda.ko
Reading symbols from /boot/kernel/acpi_asus.ko...Reading symbols from
/boot/kernel/acpi_asus.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_asus.ko
Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols
from /boot/kernel/acpi_aiboost.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_aiboost.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/procfs.ko...Reading symbols from
/boot/kernel/procfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/procfs.ko
Reading symbols from /boot/kernel/pseudofs.ko...Reading symbols from
/boot/kernel/pseudofs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/pseudofs.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from
/boot/kernel/linprocfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/linsysfs.ko...Reading symbols from
/boot/kernel/linsysfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linsysfs.ko
Reading symbols from /boot/kernel/blank_saver.ko...Reading symbols
from /boot/kernel/blank_saver.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/blank_saver.ko
Reading symbols from /usr/local/modules/rtc.ko...done.
Loaded symbols for /usr/local/modules/rtc.ko
Reading symbols from /boot/kernel/if_gif.ko...Reading symbols from
/boot/kernel/if_gif.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/if_gif.ko
#0 doadump () at pcpu.h:223
223 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
(kgdb) list *0x803c2869
0x803c2869 is in pppoe_findsession
(/usr/src/sys/netgraph/ng_pppoe.c:567).
562 uint16_thash = SESSHASH(session);
563 sessp sp = NULL;
564
565 mtx_lock(&privp->sesshash[hash].mtx);
566 LIST_FOREACH(sp, &privp->sesshash[hash].head, sessions) {
567 if (sp->Session_ID == session &&
568 bcmp(sp->pkt_hdr.eh.ether_dhost,
569 wh->eh.ether_shost, ETHER_ADDR_LEN) == 0) {
570 break;
571 }
(kgdb) backtrace
#0 doadump () at pcpu.h:223
#1 0x802e7cd9 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:416
#2 0x802e810c in panic (fmt=0x80581c64 "%s") at
/usr/src/sys/kern/kern_shutdown.c:590
#3 0x8051dfd8 in trap_fatal (frame=0xff0002415ba0,
eva=Variable "eva" is not available.
) at /usr/src/sys/amd64/amd64/tra
Re: openbgpd / openospf / carp / vlan (on 7.2) trouble
Hi Bjørn! I also have had troubles with openbdpd few years ago. All troubles vanished after installing quagga instead of openbgpd. Well, maybe it's not great solution, but it's workaround. wbr. 2010/5/25 Ask Bjørn Hansen : > Hi, > > Since upgrading from openbgpd 4.5 to 4.7 (tried 4.6, too with bad results) > openbgpd doesn't work on my vlan interface. I have two routers (10.0.100.2 > and .3). That network is on vlan2; with carp2 running .1. > > Running .3 on 4.6 or 4.7 makes it immediately lose it's route to the 100.0/24 > network when bgpd starts. bgpd is announcing 10.0.100.0/24 (and understands > that it's a locally routed network, according to bgpctl show ip bgp, see > below). > > ... but somehow the routing able gets changed to have that network routed to > 10.0.100.2 (the other router, running 4.5) instead of 0.0.0.0/vlan2. I can't > even ping 10.0.100.3 (the vlan2 IP) from the box itself. If I ping that IP > from a box on a different network it works. > > Also, I can restore the route with > > route del -net 10.0.100.0/24 10.0.100.2 > route add -net 10.0.100.0/24 -interface vlan2 > > ... but as soon as bgpd reconnects it will mess it up again. > > Any ideas? Am I doing it wrong? I understand that bgpd is exchanging the > routes; but until v4.5 it'd keep the local interface as a preference. What's > the proper forum to for the FreeBSD openbgpd port? I can't even find a > changelog for the different versions... > > For what it's worth - on a non-vlan, non-carp interface in another otherwise > similar setup it's working ok with 4.6 and 4.7. > > > - ask > > gw-b.dev# bgpctl show ip bgp > flags: * = Valid, > = Selected, I = via IBGP, A = Announced > origin: i = IGP, e = EGP, ? = Incomplete > > flags destination gateway lpref med aspath origin > AI*> 10.0.100.0/24 0.0.0.0 100 0 i > *> 10.0.201.0/24 10.77.80.6 100 30 64701 i > > > gw-b.dev# netstat -rn | grep 10.0.100 > 10.0.100.0/24 10.0.100.2 UGC 5 186 vlan2 > 10.0.100.1 10.0.100.2 UGHW3 0 3 vlan2 3053 > 10.0.100.3 10.0.100.2 UGHW3 0 1 vlan2 3522 > 10.0.100.13 10.0.100.2 UGHW3 0 34 vlan2 3599 > 10.0.100.103 10.0.100.2 UGHW3 0 32 vlan2 3583 > 10.0.100.104 10.0.100.2 UGHW3 0 4 vlan2 3565 > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Hello and a small problem with 8.0-RELEASE (amd64)
2010/2/12 Sean McCullough : > Hello, nicholasbug! > > On 2/11/2010 4:34 PM, nickolas...@gmail.com wrote: >> 2010/2/11 Sean McCullough : >> >>> Any ideas as to how to get the 8.0-RELEASE running on my amd64 machine >>> would be appreciated greatly. If I need to ask elsewhere, please >>> recommend accordingly. >>> >>> >> Try binary update (use freebsd-update). >> >> > Thank you for the suggestion. Unfortunately, the machine in question has > no access to highspeed internet service and has dialup only. I need to > be able to install the new OS from CD/DVD successfully. > > No disrespect intended, but I'd like to be able to live to see the > solution implemented. :-) I've had the same problem, I've reinstall OS from CD. ___ 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: Looking for testers: atacontrol SMART support
2010/1/26 Jeremy Chadwick : > As mentioned a while back on the list[1], I worked on getting atacontrol > to spit out SMART statistics for ATA disks. Specifically, this would be > those using the standard ata(4) layer (including ataahci.ko and > similar), but not ahci(4) (ahci.ko), which uses ATA/CAM. > > Output resembles the following: > > ID# Attribute Name Curr Worst Thrsh Bytes > --- - - - - - > 1 Raw Read Error Rate 200 200 51 00 00 00 00 00 00 > 3 Spin Up Time 234 229 21 53 20 00 00 00 00 > 4 Start/Stop Count 100 100 0 11 00 00 00 00 00 > 5 Reallocated Sector Count 200 200 140 00 00 00 00 00 00 > 7 Seek Error Rate 200 200 0 00 00 00 00 00 00 > 9 Power On Hours Count 95 95 0 9b 0f 00 00 00 00 > 10 Spin Retry Count 100 253 0 00 00 00 00 00 00 > 11 Calibration Retry Count 100 253 0 00 00 00 00 00 00 > 12 Power Cycle Count 100 100 0 0c 00 00 00 00 00 > 192 Power Off Retract Count 200 200 0 0b 00 00 00 00 00 > 193 Load Cycle Count 200 200 0 11 00 00 00 00 00 > 194 Temperature 116 113 0 22 00 00 00 00 00 > 196 Reallocated Event Count 200 200 0 00 00 00 00 00 00 > 197 Current Pending Sectors 200 200 0 00 00 00 00 00 00 > 198 * Uncorrected Sector Count 200 200 0 00 00 00 00 00 00 > 199 UltraDMA CRC Error Count 200 200 0 00 00 00 00 00 00 > 200 * Write Error Rate 200 200 0 00 00 00 00 00 00 > --- - - - - - > * = values only updated after a short/long/offline test > > Things to note: > > - I've only been testing on RELENG_8 amd64. The code should work on > i386, but if something explodes, let me know. I don't recommend > patching RELENG_7 or even a RELEASE tag with this. > > - I did my best to document the SMART "stuff" throughout the source. > Much to my disappointment SMART attributes are not part of the ATA > or ACS specification; they're mentioned, but attributes and their > interpretation are 100% vendor specific. Decoding them will involve > examining the smartmontools source, which takes time. > > This is why there is no smartmontools "RAW_VALUE" equivalent -- the > code for that piece simply hasn't been written. Instead, I display > the raw bytes associated with each attribute. This should help with > debugging (for the time being). I'll work things out... :-) As I know, there is no decode for raw value (even in smartmontools). So, you can just store this six bytes in 64-bit variable and print it out. > > - All operations done are read-only (in fact the device is opened in > read-only mode). There may be plans down the road to implement things > like inducing SMART short/long/offline tests, but for now I want to > get attribute support in there. Implementation of tests is quite easy. I've wrote nearly the same project for linux some time ago, so I can htlp you with this project. Please, mail me if you're get interested in my help. wbr, Nickolas ___ 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"
some options in src.conf has no effect (RELENG_8)
Hi all. I've found out that some options in src.conf has no effect. Here is my src.conf file: --CUT-- WITHOUT_ASSERT_DEBUG="YES" WITHOUT_ATM="YES" WITHOUT_CTM="YES" WITHOUT_CVS="YES" WITHOUT_FREEBSD_UPDATE="YES" WITHOUT_GPIB="YES" WITH_IDEA="YES" WITHOUT_IPFILTER="YES" WITHOUT_IPFW="YES" WITHOUT_IPX="YES" WITHOUT_LPR="YES" WITHOUT_PORTSNAP="YES" WITHOUT_RCS="YES" WITHOUT_ROUTED="YES" --CUT-- And there are options that have no effect: WITHOUT_CTM WITHOUT_CVS WITHOUT_FREEBSD_UPDATE WITHOUT_IPFW WITHOUT_PORTSNAP WITHOUT_RCS WITHOUT_ROUTED I've done "make delete-old" and "make delete-old-libs" during upgrade. Can somebody comment this? wbr, Nickolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8 GPT install, how?
2009/12/8 Steven Hartland : > Thanks to all those who responded the missing piece of data was indeed > you MUST use the DVD, the CD which mentioned in several places simply > doesn't work as it doesn't have the required files. > > It also still shocks me that the emergency holographic shell still > doesn't have mount_ufs which pretty much makes it useless :( Use "mount" (not mount_ufs). It mounts UFS by default. If you wanna use another FS, you should load kernel module - use kldload with full path to kernel module. For example, if you wanna load ext2fs module, type kldload /dist/boot/kernel/ext2fs.ko mount -t ext2fs ___ 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: root partition too small
2009/12/7 : > Label from freebsd sysinstall in auto mode, make root partition 500mb > For update OS (kernel + kernel.old) need about 700mb > > Howto rebild kernel with litsted in kldstat modules? > > -- > alexs > You may say "make reinstallkernel" instead of "make installkernel" ___ 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"
