Re: buggy ATA controller: I can install 4.11, but not 5.3 !?!
Doug White wrote: On Thu, 31 Mar 2005, Rob wrote: --- Doug White [EMAIL PROTECTED] wrote: AFAIK the RZ1000 bug was that it would corrupt data to the slave channel if the primary channel was also active. If you only have one device then you may not be able to reproduce it. I have two harddisks on ata0: ad0: 520MB ST3660A [1057/16/63] at ata0-master BIOSPIO ad1: 2423MB SAMSUNG WINNER-3 WN32543A(2.5GB) [4924/16/63] at ata0-slave BIOSPIO ad0 has the base OS, and ad1 has /usr/src and /usr/obj for recompiling world and kernel. So far no problems. However, if I remember well, the other IDE connector on the motherboard does not seem to work, which now I realize could be caused by the buggy RZ 1000 chip. Entirely possible. With FreeBSD 4-Stable running still fine, I get this: # grep ata /var/run/dmesg.boot atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible at device 1.0 on pci0 atapci0: ATA channel disabled by BIOS ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ad0: 520MB ST3660A [1057/16/63] at ata0-master BIOSPIO ad1: 2423MB SAMSUNG WINNER-3 WN32543A(2.5GB) [4924/16/63] at ata0-slave BIOSPIO # vmstat -i | grep -i ata interrupt total rate rl0 irq11 3187504 1 fdc0 irq6 2 0 ata0 irq14 33429902 17 sio0 irq4 3 0 sio1 irq3 1 0 clk irq0187773091100 rtc irq8240341556127 Total 464732059247 So ata1 (irq 15) is not in the interrupt table !?! What does that mean? As a reminder: I have following in dmesg output: atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible at device 1.0 on pci0 atapci0: ATA channel disabled by BIOS For the harddisk to be recognized by the kernel, I need exactly this in the kernel config: device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 Without these lines in the kernel config, I get a fatal 'no root device found' error at bootup. Apart from these peculiar findings, 4-Stable is running flawlessly on this old Pentium-1 PC. - Another reminder: when I try to install 5.3 on this PC, I get a no disk found error at a very early stage of the installation procedure. I hope to investigate this further in a not-so-near future Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nss_ldap / top startup
Hi, Any ideas, why this is happening? Will I need 10 seconds, when there are 6 accounts in LDAP? :-) Have you set your indexes correctly? This may result in a huge speedup. I use (this is only for about 180 accounts, but NSS works instantly): # Indices to maintain index objectClass eq index cn sub,pres,eq index uid,uidNumber,gidNumber,homeDirectory pres,eq Also, have you tried truss(1) or ktrace(1) on the process? It might help you try to see if the LDAP server is just being slow, or the LDAP client is. -- Rink P.W. Springer- http://rink.nu God, root, what is difference? - Pitr, Userfriendly pgpILhXpgyjhU.pgp Description: PGP signature
Re: buggy ATA controller: I can install 4.11, but not 5.3 !?!
Rob wrote: Another reminder: when I try to install 5.3 on this PC, I get a no disk found error at a very early stage of the installation procedure. I hope to investigate this further in a not-so-near future Rob, I have a similar problem with 5.3 although I'm not doing a new install - I'm upgrading from an earlier 5.X. Can you please try installing a 5.X from December last year or earlier. Actually, you don't need to install anything - I'd just like to know whether it can see the disk. I've faised PR kern/79332 about it which contains two possible fixes. Thanks, Graham Menhennitt ___ 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.3p6-5.4RC3, Supermicro X6DHR-8G, Dual 3.6GHzXeons,Adaptec aic7902 SCSI interface doesn't work in UPkernel
On Mon, Apr 25, 2005 at 08:06:19PM -0700, Ade Lovett wrote: SuperMicro [...] Seagate [...] on-board aic7902 and, from your dmesg output: da0: SEAGATE ST373207LC 0003 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers [...] At an absolute minimum, have the existing drive swapped out for an ST373453LC model, making VERY certain that the firmware is rev 0006 -- prior revisions WILL corrupt your data, set fire to your cat, and otherwise ruin your entire life -- and that's before they've actually spun up. I've got about 25 similar configurations running. Apart from the initial bootup card state dump, they work ok. I've flashed all Seagate drives to bios version 0007 to get it stable. Marc pgpMXM8gNZGFW.pgp Description: PGP signature
Re: background_fsck=no does not work?
On Mon, 2005-Apr-25 14:19:00 -0400, Bill Moran wrote: Actually, I have seen a similar problem on 5.x WRT OpenOffice ... 0. OpenOffice hangs and cant' be killed 1. Reboot system 2. System claims all buffers flushed, then just hangs 3. After hardbooting, filesystems need fscked This sounds like the fault might be related to the deadlock I reported in http://lists.FreeBSD.org/pipermail/freebsd-stable/2005-April/013839.html In my case, OO.org was definitely involved, and it appears to have become unkillable before /usr locked up. Two of the locks were: - A shared lock on /usr/local/OpenOffice.org1.1.4/program/libpsp645fi.so - /usr/local/OpenOffice.org1.1.4/program/pagein holding an exclusive lock on /usr/local/OpenOffice.org1.1.4/program and wanting an exclusive lock on /usr/local/OpenOffice.org1.1.4/program/libpsp645fi.so I have no idea what pagein is supposed to do but I can't see any good reason for it wanting to lock an OO.org shared library. I have the crashdump lying around in case anyone can suggest somewhere to look for the cause. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buggy ATA controller: I can install 4.11, but not 5.3 !?!
--- Graham Menhennitt wrote: Rob wrote: Another reminder: when I try to install 5.3 on this PC, I get a no disk found error at a very early stage of the installation procedure. I hope to investigate this further in a not-so-near future Rob, I have a similar problem with 5.3 although I'm not doing a new install - I'm upgrading from an earlier 5.X. Can you please try installing a 5.X from December last year or earlier. Actually, you don't need to install anything - I'd just like to know whether it can see the disk. I've faised PR kern/79332 about it which contains two possible fixes. Thank you. The computer is my brother's old Pentium-1 (60 MHz); he and the computer are at the other end of the world. Only when my brother has spare time, we open a live chat connection and I assist him with certain console tasks (he is not at all a Unix/FreeBSD person). However, most of the time I manage this PC remotely (it's now running 4-Stable flawlessly). At some point, we may try once again to install a 5.X version; it should be a straightforward install procedure, because too much freaky stuff might be too complex to explain to a non-Unix, non-FreeBSD person My plan for next time, is to use a serial console during install, so that I can receive the kernel output to get a clue why 5.X cannot find the disk, which 4-Stable does find easily. I may travel to my brother's home some time this year; then I will do whatever freaky tricks are needed to find out why 5.X is not installing properly. Regards, Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nss_ldap / top startup
Hi. On Tue, Apr 26, 2005 at 07:55:37AM +0200, Rink Springer wrote: Any ideas, why this is happening? Will I need 10 seconds, when there are 6 accounts in LDAP? :-) Have you set your indexes correctly? This may result in a huge speedup. I use (this is only for about 180 accounts, but NSS works instantly): Yes, indices and caching are set well and I don't have any problems with the speed of the LDAP server in any way (SMTP, POP, IMAP and so on all work very fast and smooth). Also, have you tried truss(1) or ktrace(1) on the process? It might help you try to see if the LDAP server is just being slow, or the LDAP client is. Well, I wonder why LDAP should be queried (by nss_ldap) at all (with -u used as top option). I did not yet truss/ktrace top, but maybe I should. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpYj51z5RvR1.pgp Description: PGP signature
Re: Re: mysql40-server with linuxthreads and CFLAGS=-DUSE_OLD_FUNCTIONS
On Sun, 17 Apr 2005 [EMAIL PROTECTED] wrote: Does any 1-:) have a compiled mysql4*-server with linuxthreads and CFLAGS=- DUSE_OLD_FUNCTIONS I went by all the deltas from 5500 up to today ( 5734 ) and always get the same error cc -DDBUG_OFF -DUSE_OLD_FUNCTIONS -DUSE_OLD_FUNCTIONS -felide-constructors - fno- rtti -fno-exceptions -fno-implicit-templates -fno-exceptions -fno-rtti - DMYSQLD_NET_RETRY_COUNT=100 -o mysqld sql_lex.o sql_handler.o item.o item_sum.o item_buff.o item_func.o item_cmpfunc.o item_strfunc.o item_timefunc.o thr_malloc.o item_create.o field.o key.o sql_class.o sql_list.o net_serv.o net_pkg.o lock.o my_lock.o sql_string.o sql_manager.o sql_map.o mysqld.o password.o hash_filo.o hostname.o convert.o set_var.o sql_parse.o sql_yacc.o sql_base.o table.o sql_select.o sql_insert.o sql_update.o sql_delete.o uniques.o sql_do.o procedure.o item_uniq.o sql_test.o log.o log_event.o init.o derror.o sql_acl.o unireg.o des_key_file.o time.o opt_range.o opt_sum.o opt_ft.o records.o filesort.o handler.o ha_heap.o ha_myisam.o ha_myisammrg.o ha_berkeley.o ha_innodb.o ha_isam.o ha_isammrg.o sql_db.o sql_table.o sql_rename.o sql_crypt.o sql_load.o mf_iocache.o field_conv.o sql_show.o sql_udf.o sql_analyse.o sql_cache.o slave.o sql_repl.o sql_union.o mini_client.o mini_client_errors.o stacktrace.o repl_failsafe.o - static -DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R -D_THREAD_SAFE - I/usr/local/include/pthread/linuxthreads -DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R - D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads - L/usr/ports/databases/mysql40-server/work/mysql-4.0.24/bdb/build_unix - ldb ../innobase/usr/libusr.a ../innobase/srv/libsrv.a ../innobase/dict/libdict.a ../innobase/que/libque.a ../innobase/srv/libsrv.a ../innobase/ibuf/libibuf.a .. /innobase/row/librow.a ../innobase/pars/libpars.a ../innobase/btr/libbtr.a ../ in nobase/trx/libtrx.a ../innobase/read/libread.a ../innobase/usr/libusr.a ../innob ase/buf/libbuf.a ../innobase/ibuf/libibuf.a ../innobase/eval/libeval.a ../innoba se/log/liblog.a ../innobase/fsp/libfsp.a ../innobase/fut/libfut.a ../innobase/fi l/libfil.a ../innobase/lock/liblock.a ../innobase/mtr/libmtr.a ../innobase/page/ libpage.a ../innobase/rem/librem.a ../innobase/thr/libthr.a ../innobase/sync/lib sync.a ../innobase/data/libdata.a ../innobase/mach/libmach.a ../innobase/ha/libh a.a ../innobase/dyn/libdyn.a ../innobase/mem/libmem.a ../innobase/sync/libsync.a ../innobase/ut/libut.a ../innobase/os/libos.a ../innobase/ut/libut.a ../isam/ li bnisam.a ../merge/libmerge.a ../myisam/libmyisam.a ../myisammrg/libmyisammrg.a . ./heap/libheap.a ../vio/libvio.a ../mysys/libmysys.a ../dbug/libdbug.a ../rege x/ libregex.a ../strings/libmystrings.a -lwrap -L/usr/local/lib -llthread - llgcc_r -lz -lcrypt -lm -llthread -llgcc_r *** Error code 1 I will appreciate a compiled work directory. Hm, odd that it didn't actually print an error message. Are you omitting something? probaly the line below, Stop in /usr/ports/databases/mysql40-server/work/mysql-4.0.24/sql. but I'm not certain somhow I can not find my makefile piped output. but it water under the bridge... Thanks anyhow. I went back to 3.23 however... on my 5.3 traning box 4.1 did compile nicley with WITH_PROC_SCOPE_PTH=yes BUILD_OPTIMIZED=yes BUILD_STATIC=yes Once the 5.4 is released I will retry and test wiht my old tables. Again thanks /r/ wlodek -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getting handbooks via cvsup?
On Sun, Apr 24, 2005 at 02:32:59PM +0300, Ion-Mihai Tetcu wrote: cvsup file: *default host=cvsup.ro.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix doc-all Run cvsup then: cd /usr/doc/ make FORMATS=html html-split ps pdf install textproc/docproj must be installed if one wants to build the docs. Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Using the 6-CURRENT twa driver on 5-STABLE.
Is it better to use the 6-CURRENT driver on 5-STABLE, or the 3ware 9.2 Software Release for 5.x. I see that there have been some changes between the two. Are they improvements, applicable to 5-STABLE as well, or just changes required for 6-CURRENT? It looks like the changes are probably optimisations, but I'm not sure whether that applies for 5-STABLE as well. I've tried both, and am currently using the 6-CURRENT driver on 2 of our 4 5-STABLE boxes without any obvious ill effects. Should I stop? In either case, would it be possible to commit one or the other quite soon after 5.4-RELEASE? (I'm assuming they can't go into 5.4-RELEASE). Thanks, Jason. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
internal modem / pnp0 / FAQ error ?
From: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html 4.5.2. Why is FreeBSD not finding my internal Plug Play modem? You will need to add the modem's PnP ID to the PnP ID list in the serial driver. To enable Plug Play support, compile a new kernel with controller pnp0 in the configuration file, then reboot the system. The kernel will print the PnP IDs of all the devices it finds. Copy the PnP ID from the modem to the table in /sys/i386/isa/sio.c, at about line 2777. Look for the string SUP1310 in the structure siopnp_ids[] to find the table. Build the kernel again, install, reboot, and your modem should be found. You may have to manually configure the PnP devices using the pnp command in the boot-time configuration with a command like pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8 to make the modem show. Compiling with the suggested line controller pnp0 gets: obsolete keyword 'controller' found - use 'device' o.k. Compiling with device pnp0 gets: Warning: device pnp is unknown *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src Trying the pnp enable line at boot doesn't change a thing So - is the FAQ entry an error? uname -a FreeBSD cody.npqr.net 4.11-STABLE FreeBSD 4.11-STABLE #3: Sun Apr 24 18:04:54 PDT 2005 [snip] i386 I have a pci winmodem (yes I know - plan on using ltmdm) inserted into an open pci slot. dmesg shows pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 ATA controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: unknown card (vendor=0x11c1, dev=0x0440) at 9.0 irq 11 pci0: S3 ViRGE graphics accelerator at 10.0 irq 10 dc0: 82c169 PNIC 10/100BaseTX port 0x6300-0x63ff mem 0xe4001000-0xe40010ff irq 9 at device 11.0 on pci0 Anyone know how I can really get the card recognized and maybe go on to install and get working ppp with this modem ? tia Pan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
more troubles with ATA
Good day Soren, i've applied ATA mkIII patch on freshly cvsuped 5.4-STABLE and experienced problems with onboard sata controller.Here is a fragment from dmesg output: atapci1: nVidia nForce3 Pro SATA150 controller port 0xe000-0xe00f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 22 at device 10.0 on pci0 ata2: ATA channel 0 on atapci1 atapci1: failed to enable memory mapping ! device_attach: ata2 attach returned 6 ata3: ATA channel 1 on atapci1 atapci1: failed to enable memory mapping ! device_attach: ata3 attach returned 6 while Fasttrack TX2200 controller recognized as Promise PDC 20571 SATA150 controller works fine. Before ATA mkIII patch the onboard controller recognized as: atapci1: GENERIC ATA CONTROLLER port 0xe000-0xe00f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 11 at device 10.0 on pci0 The motherboard is Gigabyte GA-K8NS nForce3 250 chipset with amd64 Athlon CPU. Any clues about making those two controllers work together ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
vm_page_free: freeing wired page
Hi, all I have problem on high loaded SMP server with FreeBSD 5.3-p10+Apache 1.3.33+Mysql 4.0 reported in kern/75780 ! State still open - not fixed as i understand! If there any possible way to find workaround of this problem !? Maybe cvsup to 5.4 or something else ?! This problem exist only in 5.3 or in 5.x at all !? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: internal modem / pnp0 / FAQ error ?
pan [EMAIL PROTECTED] wrote: From: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html 4.5.2. Why is FreeBSD not finding my internal Plug Play modem? You will need to add the modem's PnP ID to the PnP ID list in the serial driver. [...] That FAQ entry is very outdated. And it does not apply to your case at all. I have a pci winmodem The term PnP from the FAQ entry refers to ISA PnP cards, not to PCI cards. Furthermore, it refers to cards which are controlled by the sio driver (serial I/O), not to win modems. It's a completely different thing. (yes I know - plan on using ltmdm) So your winmodem card uses the Lucent chipset supported by ltmdm? If so, you only need to install ltmdm, and that's all you need to do. If ltmdm doesn't support your winmodem, then it's pretty much a dead horse. I would rather recommend to buy a real modem. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Emacs ist für mich kein Editor. Für mich ist das genau das gleiche, als wenn ich nach einem Fahrrad (für die Sonntagbrötchen) frage und einen pangalaktischen Raumkreuzer mit 10 km Gesamtlänge bekomme. Ich weiß nicht, was ich damit soll. -- Frank Klemm, de.comp.os.unix.discussion ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gvinum causing kernel panic when referencing nonexistent partition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Jason,
Am 25.04.2005 um 16:19 schrieb Jason Andresen:
[...]
Is there maybe a special place on each drive I could dd /dev/zero to
clear out all of the vinum information? I tried clobbering the vinum
slices on every drive and newfsing them as individual filesystems, but
that didn't seem to do the trick.
Well, I ran into this as well... it's a bit weird to solve this issue.
The gvinum-infos are on sector #8 ff. of the drive-slices. In your case
'ad{x}s1'.
If you have a valid backup of your data (which should be no problem to
get as a RAID5-plex should survive *one* faulty disk) I would recommend
to erase all sectors #8-16 of all gvinum-drives as your missing drive
is noted in all of these sectors. Then you have to rebuild the whole
gvinum stuff from scratch.
If that's not possible, do a 'dd if=/dev/ad6s1 of=ad6s1.sec bs=512
count=16' and look at the file 'ad6s1.sec' with your favorite
hex-editor. Or better: make a copy of that file and look at the copy
:-) You have to do this for all your gvinum-drives.
The gvinum meta-data starts with the string 'IN VINO', IIRC at sector
#8, that is 4096 bytes offset in the file. The metadata follows this
'magic' string and is plain ascii.
So, now you can either remove all references to 'media4' or perhaps you
try to rename all occurences of 'mediaa' to 'media4' and see what
happens.
The structure of the metadata is defined in
/sys/geom/vinum/geom_vinum_var.h - look at this file first!
I managed to repair my gvinum installation this way but there's no
guarantee, you do it on your own risk!
Please contact [EMAIL PROTECTED], perhaps he is willing to assist you
during that operation. He is the 'father' of gvinum so his advice is
sure better than mine...
Good luck - matthias
- --
Ciao/BSD - Matthias
Matthias Schuendehuette msch [at] snafu.de, Berlin (Germany)
PGP-Key at pgp.mit.edu and wwwkeys.de.pgp.net ID: 0xDDFB0A5F
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCblWDf1BNcN37Cl8RAkHiAJ9DIuoud82AOsrQ8fouLVh4O0J+UQCeLhEn
Xfbb2/sk4c6vBwzil7CGi3g=
=4NCN
-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]
PostgreSQL in FreeBSD jails
Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. The system is FreeBSD 5.4-PRERELEASE. PostgreSQL-7.4.7. SEM and SHM sysctl setting are: # sysctl -a | grep shm kern.ipc.shmmax: 1 kern.ipc.shmmin: 1 kern.ipc.shmmni: 192 kern.ipc.shmseg: 128 kern.ipc.shmall: 32768 kern.ipc.shm_use_phys: 0 kern.ipc.shm_allow_removed: 0 # sysctl -a | grep sem kern.ipc.semmap: 256 kern.ipc.semmni: 256 kern.ipc.semmns: 512 kern.ipc.semmnu: 256 kern.ipc.semmsl: 60 kern.ipc.semopm: 100 kern.ipc.semume: 10 kern.ipc.semusz: 92 kern.ipc.semvmx: 32767 kern.ipc.semaem: 16384 Trying to solve the problem I've set the following in postgresql.conf files: max_connections = 5 shared_buffers = 100 Please help! What am I doing wrong? -- Alexander Rusinov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
On Tue, Apr 26, 2005 at 05:58:27PM +0300, Alexander Rusinov wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. Is SYSV IPC allowed for jails? It's not enabled by default. -- Spartak Radchenko SVR1-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
Alexander Rusinov [EMAIL PROTECTED] wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. I had this exact same problem. I never found a solution. The cause appears to be that, since shared memory is not segregated between jails, the newly launched Postgres instances corrupt the shared memory of previously running Postgres instances. Supposedly, this shouldn't be possible, but it was happening and I never found a solution. The system is FreeBSD 5.4-PRERELEASE. PostgreSQL-7.4.7. SEM and SHM sysctl setting are: # sysctl -a | grep shm kern.ipc.shmmax: 1 kern.ipc.shmmin: 1 kern.ipc.shmmni: 192 kern.ipc.shmseg: 128 kern.ipc.shmall: 32768 kern.ipc.shm_use_phys: 0 kern.ipc.shm_allow_removed: 0 # sysctl -a | grep sem kern.ipc.semmap: 256 kern.ipc.semmni: 256 kern.ipc.semmns: 512 kern.ipc.semmnu: 256 kern.ipc.semmsl: 60 kern.ipc.semopm: 100 kern.ipc.semume: 10 kern.ipc.semusz: 92 kern.ipc.semvmx: 32767 kern.ipc.semaem: 16384 Trying to solve the problem I've set the following in postgresql.conf files: max_connections = 5 shared_buffers = 100 Please help! What am I doing wrong? -- Alexander Rusinov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
On 26/04/05, Alexander Rusinov [EMAIL PROTECTED] wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. The system is FreeBSD 5.4-PRERELEASE. PostgreSQL-7.4.7. SEM and SHM sysctl setting are: Just add the following line to your /etc/rc.conf jail_sysvipc_allow=YES and ipc configuration will be shared with the jails Regards -- Renato Botelho ICQ: 54596223 AIM: RBGargaBR ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
Spartak Radchenko wrote: On Tue, Apr 26, 2005 at 05:58:27PM +0300, Alexander Rusinov wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. Is SYSV IPC allowed for jails? It's not enabled by default. Yes, it is on: security.jail.sysvipc_allowed: 1 I wouln't be able to run the first instance of PostgreSQL server with IPC disabled. -- Alexander Rusinov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
Renato Botelho wrote: On 26/04/05, Alexander Rusinov [EMAIL PROTECTED] wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. The system is FreeBSD 5.4-PRERELEASE. PostgreSQL-7.4.7. SEM and SHM sysctl setting are: Just add the following line to your /etc/rc.conf jail_sysvipc_allow=YES and ipc configuration will be shared with the jails I have IPC enabled for jails already. So unfortunately this is not a solution. Is anybody here who do run several jailed PostgreSQL servers? -- Alexander Rusinov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: more troubles with ATA
tofik suleymanov wrote: Good day Soren, i've applied ATA mkIII patch on freshly cvsuped 5.4-STABLE and experienced problems with onboard sata controller.Here is a fragment from dmesg output: atapci1: nVidia nForce3 Pro SATA150 controller port 0xe000-0xe00f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 22 at device 10.0 on pci0 ata2: ATA channel 0 on atapci1 atapci1: failed to enable memory mapping ! device_attach: ata2 attach returned 6 ata3: ATA channel 1 on atapci1 atapci1: failed to enable memory mapping ! device_attach: ata3 attach returned 6 while Fasttrack TX2200 controller recognized as Promise PDC 20571 SATA150 controller works fine. Before ATA mkIII patch the onboard controller recognized as: atapci1: GENERIC ATA CONTROLLER port 0xe000-0xe00f,0xb70-0xb73,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 11 at device 10.0 on pci0 The motherboard is Gigabyte GA-K8NS nForce3 250 chipset with amd64 Athlon CPU. Any clues about making those two controllers work together ? It should work on -current, but I have no boards to check this on currently. I have no immediate plans for a new patch for 5.4-STABLE, as it misses the callout updates thats in -current and that ATA needs now. -- -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: internal modem / pnp0 / FAQ error ?
From: Oliver Fromme [EMAIL PROTECTED] Subject: Re: internal modem / pnp0 / FAQ error ? If ltmdm doesn't support your winmodem, then it's pretty much a dead horse. I would rather recommend to buy a real modem. thanks for the reply It is a case of having equipment on hand and wanting to see if it can be made to work. I agree with your advice and will be dropping the win modem and just using an external. Pan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS client/buffer cache deadlock
[changed cc: from standards@ back to stable@ again.] On Tue, Apr 26, 2005 at 12:25:49PM -0400, Brian Fundakowski Feldman wrote: You can assure that this happens in only two ways: 1. Make a complete copy of the data. This is what currently occurs: it gets stuffed into the buffer cache as the write happens. 2. Keep the data around synchronously -- by virtue of the write system call being used synchronously, the thread's VM context is around, and duplication need not occur. It seems as though FreeBSD 4.x either used 2) or does something wrong indeed. Why would 2) be a problem on FreeBSD 5.x ? Can't the pages written from be locked during the write, instead of copied internally ? Btw. running the writev program with 20 * 100 MB on UFS on a 512MB FreeBSD 6-CURRENT system practicly locks the filesystem down _and_ causes all processes to be swapped out in favor of the buffer cache. 'top' however, doesnt' show a rise in BUF usage. On FreeBSD 4.x, the system performance as usual during the writev to UFS. Marc pgple5KkUSnn9.pgp Description: PGP signature
Re: PostgreSQL in FreeBSD jails
On Tue, 26 Apr 2005, Bill Moran wrote: Alexander Rusinov [EMAIL PROTECTED] wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. I had this exact same problem. I never found a solution. The cause appears to be that, since shared memory is not segregated between jails, the newly launched Postgres instances corrupt the shared memory of previously running Postgres instances. I'm running 9 jails on a server right now, each with their own instance: # ps aux | grep postmaster|grep -- -D scrappy 20043 0.0 0.0 18856 504 ?? SsJ Thu08PM 0:58.55 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) pgsql 39126 0.0 0.0 7480 400 ?? SsJ 19Apr05 0:00.99 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 38868 0.0 0.0 8224 552 ?? SsJ 19Apr05 0:02.08 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) pgsql 37375 0.0 0.0 7180 404 ?? SsJ 19Apr05 0:02.47 /usr/local/bin/postmaster -D /usr/local/pgsql/data (postgres) scrappy 36865 0.0 0.0 16556 744 ?? SsJ 19Apr05 0:08.32 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) scrappy 36675 0.0 0.0 258184 1000 ?? SsJ 19Apr05 7:29.85 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) scrappy 36569 0.0 0.0 14552 596 ?? SsJ 19Apr05 0:12.27 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data -S (postgres) scrappy 35961 0.0 0.0 16624 580 ?? SsJ 19Apr05 12:26.68 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) scrappy 54328 0.0 0.0 258248 1596 ?? SJ1:55PM 0:00.00 /usr/local/bin/postmaster -D /usr/local/pgsql/data -S (postgres) and never noticed any issues ... but, this is with 4.11, not 5.x, so maybe something has changed? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
Marc G. Fournier [EMAIL PROTECTED] wrote: On Tue, 26 Apr 2005, Bill Moran wrote: Alexander Rusinov [EMAIL PROTECTED] wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. I had this exact same problem. I never found a solution. The cause appears to be that, since shared memory is not segregated between jails, the newly launched Postgres instances corrupt the shared memory of previously running Postgres instances. I'm running 9 jails on a server right now, each with their own instance: snip and never noticed any issues ... but, this is with 4.11, not 5.x, so maybe something has changed? I was running 5.2 when I had the problems. So it's possible that this guess is correct. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Lock order reversal: em0 and Giant
Hi, FreeBSD 5.3-RELEASE-p5 on a Tyan Tiger LE with two PIII/733s an Intel Pro/1000MT 64-bit NIC in a 66MHz PCI slot nets me these repeatedly on boot immediately after the interface comes up: Apr 26 09:57:56 ram kernel: em0: Link is up 1000 Mbps Full Duplex Apr 26 09:57:56 ram kernel: lock order reversal Apr 26 09:57:56 ram kernel: 1st 0xc162e3b4 em0 (network driver) @ /usr/src/sys/dev/em/if_em.c:980 Apr 26 09:57:56 ram kernel: 2nd 0xc0663d80 Giant (Giant) @ /usr/src/sys/vm/vm_contig.c:538 Apr 26 09:57:56 ram kernel: KDB: stack backtrace: Apr 26 09:57:56 ram kernel: kdb_backtrace(c0619e00,c0663d80,c0615a3e,c0615a3e,c06270aa) at kdb_backtrace+0x2e Apr 26 09:57:56 ram kernel: witness_checkorder(c0663d80,9,c06270aa,21a,d403d964) at witness_checkorder+0x6a6 Apr 26 09:57:56 ram kernel: _mtx_lock_flags(c0663d80,0,c06270aa,21a,c04b9b5f) at _mtx_lock_flags+0x8a Apr 26 09:57:56 ram kernel: contigmalloc(1000,c063d760,1,0,) at contigmalloc+0x42 Apr 26 09:57:56 ram kernel: alloc_bounce_pages(c1737d00,4,101,c18ac100,c162e000) at alloc_bounce_pages+0x83 Apr 26 09:57:56 ram kernel: bus_dmamap_create(c1737d00,1,d403da28,c0672c20,0) at bus_dmamap_create+0x131 Apr 26 09:57:56 ram kernel: em_encap(c162e000,c18ac100,c0609329,267,c162e0e8) at em_encap+0x90 Apr 26 09:57:56 ram kernel: em_start_locked(c162e000,,c044cfc0,c162e000,c162e37c) at em_start_locked+0x254 Apr 26 09:57:56 ram kernel: em_intr(c162e000,0,c0613eaa,269,c0663d40) at em_intr+0x143 Apr 26 09:57:56 ram kernel: ithread_loop(c1566400,d403dd48,c0613cce,323,b20684f9) at ithread_loop+0x172 Apr 26 09:57:56 ram kernel: fork_exit(c04b0410,c1566400,d403dd48) at fork_exit+0xc6 Apr 26 09:57:56 ram kernel: fork_trampoline() at fork_trampoline+0x8 Apr 26 09:57:56 ram kernel: --- trap 0x1, eip = 0, esp = 0xd403dd7c, ebp = 0 --- If there's any other information you need, please let me know. Thanks, Josh -- Josh Tolbert [EMAIL PROTECTED] || http://www.puresimplicity.net/~hemi/ If your sysadmin's not being fascist, you're paying him too much. --Sam Greenfield ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Repeated panics...Suspect USB issues
On Fri, Mar 11, 2005 at 02:03:12AM -0600, Josh Tolbert wrote: A backtrace would be nice. See the developer's handbook on kernel debugging for details. I'm trying to get a backtrace. I've built a kernel with all the right bits, set up dumpdir and dumpdev in /etc/rc.conf, etc...Apparently savecore doesn't like writing to the swap partition (/dev/ar0s1b). I can get to the ddb promp, obtain a trace, panic the machine, etc...But I don't think I can obtain a good core without putting another hard drive in the machine, which isn't going to happen till sometime next week...Is there anything I can provide from the ddb prompt? Thanks, Josh Old problem revival time... Since dumps don't like being written out to a partition on a RAID1 set, this is about the only kind of trace I could obtain: http://www.puresimplicity.net/~hemi/Pics/Misc/trace.jpg For what it's worth, I moved the printer to another machine and removed the USB-to-parallel adapter that was the catalyst of the problem. If anyone cares to work on this problem I'll be more than happy to send the cable on a one-way trip to any interested party in order to help get the problem resolved. If anyone's interested in the cable for testing, etc. just let me know. Thanks, Josh -- Josh Tolbert [EMAIL PROTECTED] || http://www.puresimplicity.net/~hemi/ If your sysadmin's not being fascist, you're paying him too much. --Sam Greenfield ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HAS_CONFIGURE error?
Hello, from the Mk/bsd.port.mk I read:
# CONFIGURE_ARGS
# - Pass these args to configure if ${HAS_CONFIGURE} is set.
# Default: --prefix=${PREFIX} ${CONFIGURE_TARGET} if
# GNU_CONFIGURE is set, CC=${CC} CCFLAGS=${CFLAGS}
# PREFIX=${PREFIX} INSTALLPRIVLIB=${PREFIX}/lib
# INSTALLARCHLIB=${PREFIX}/lib if PERL_CONFIGURE is set,
# empty otherwise.
The first sentence isn't true on 5.4-RC3. If I define HAS_CONFIGURE=yes
without CONFIGURE_ENV=--prefix=${PREFIX} the configure script doesn't get
--prefix set right.
Is the description outdated or is this behaviour not intended?
Thanks,
-Harry
pgpQVlIdVFw1I.pgp
Description: PGP signature
Re: HAS_CONFIGURE error?
Am Dienstag, 26. April 2005 19:31 schrieb Emanuel Strobl:
Hello, from the Mk/bsd.port.mk I read:
# CONFIGURE_ARGS
# - Pass these args to configure if ${HAS_CONFIGURE} is set.
# Default: --prefix=${PREFIX} ${CONFIGURE_TARGET} if
# GNU_CONFIGURE is set, CC=${CC} CCFLAGS=${CFLAGS}
# PREFIX=${PREFIX} INSTALLPRIVLIB=${PREFIX}/lib
# INSTALLARCHLIB=${PREFIX}/lib if PERL_CONFIGURE is set,
# empty otherwise.
The first sentence isn't true on 5.4-RC3. If I define HAS_CONFIGURE=yes
without CONFIGURE_ENV=--prefix=${PREFIX} the configure script doesn't get
--prefix set right.
Of course I meant the second sentence and CONFIGURE_ARGS, not the first and
CONFIGURE_ENV! Sorry!
Is the description outdated or is this behaviour not intended?
Thanks,
-Harry
pgp34ynAVYVQZ.pgp
Description: PGP signature
RE: Using the 6-CURRENT twa driver on 5-STABLE.
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Thomson Sent: Tuesday, April 26, 2005 7:02 AM To: freebsd-stable@freebsd.org Cc: Vinod Kashyap Subject: Using the 6-CURRENT twa driver on 5-STABLE. Is it better to use the 6-CURRENT driver on 5-STABLE, or the 3ware 9.2 Software Release for 5.x. I see that there have been some changes between the two. Are they improvements, applicable to 5-STABLE as well, or just changes required for 6-CURRENT? It looks like the changes are probably optimisations, but I'm not sure whether that applies for 5-STABLE as well. I've tried both, and am currently using the 6-CURRENT driver on 2 of our 4 5-STABLE boxes without any obvious ill effects. Should I stop? In either case, would it be possible to commit one or the other quite soon after 5.4-RELEASE? (I'm assuming they can't go into 5.4-RELEASE). twa on 6 -CURRENT is essentially the same as the 9.2 release, except for the changes needed to be able to build on 6 -CURRENT. You should be able to use it on 5 -STABLE without any problems. I just want it sit in -CURRENT for 2-3 weeks before I commit it to -STABLE. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS non-sleepable lock?
Hi, Found a bunch of these in my logs after looking in to a kernel panic somewhere in NFS. These are from an SMP 5.3-RELEASE-p5 machine. Apr 26 01:40:13 ram kernel: malloc(M_WAITOK) of Mbuf, forcing M_NOWAIT with the following non-sleepable locks held: Apr 26 01:40:13 ram kernel: exclusive sleep mutex nfsd_mtx r = 0 (0xc19c7680) locked @ /usr/src/sys/modules/nfsserver/../../nfsserver/nfs_srvsock.c:712 Apr 26 01:40:13 ram kernel: KDB: stack backtrace: Apr 26 01:40:13 ram kernel: kdb_backtrace(c068f894,d52bfb50,1,1,1) at kdb_backtrace+0x2e Apr 26 01:40:13 ram kernel: witness_warn(5,0,c06279f5,c0614cec,c15de960) at witness_warn+0x1d3 Apr 26 01:40:13 ram kernel: uma_zalloc_arg(c0c1f9a0,d52bfb88,2,c06157a1,18e) at uma_zalloc_arg+0x55 Apr 26 01:40:13 ram kernel: nfsm_disct(d52bfbd8,d52bfbdc,28,24,c17c6500) at nfsm_disct+0xbd Apr 26 01:40:13 ram kernel: nfsm_dissect_xx(28,d52bfbd8,d52bfbdc,126,c19c190f) at nfsm_dissect_xx+0x44 Apr 26 01:40:13 ram kernel: nfs_getreq(c1756600,c1758c00,1,2c8,c3ce3c00) at nfs_getreq+0x5f Apr 26 01:40:13 ram kernel: nfsrv_dorec(c3d7d700,c1758c00,d52bfc64,175,0) at nfsrv_dorec+0x109 Apr 26 01:40:13 ram kernel: nfssvc_nfsd(c15de960,0,c19c1a83,9a,d52bfcfc) at nfssvc_nfsd+0x253 Apr 26 01:40:13 ram kernel: nfssvc(c15de960,d52bfd14,8,7,2) at nfssvc+0x1f2 Apr 26 01:40:13 ram kernel: syscall(2f,2f,2f,0,0) at syscall+0x270 Apr 26 01:40:13 ram kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Apr 26 01:40:13 ram kernel: --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280ccb9f, esp = 0xbfbfeb3c, ebp = 0xbfbfeb58 --- Thanks, Josh -- Josh Tolbert [EMAIL PROTECTED] || http://www.puresimplicity.net/~hemi/ If your sysadmin's not being fascist, you're paying him too much. --Sam Greenfield ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lock order reversal: em0 and Giant
Josh Tolbert wrote: Hi, FreeBSD 5.3-RELEASE-p5 on a Tyan Tiger LE with two PIII/733s an Intel Pro/1000MT 64-bit NIC in a 66MHz PCI slot nets me these repeatedly on boot immediately after the interface comes up: Apr 26 09:57:56 ram kernel: em0: Link is up 1000 Mbps Full Duplex Apr 26 09:57:56 ram kernel: lock order reversal Apr 26 09:57:56 ram kernel: 1st 0xc162e3b4 em0 (network driver) @ /usr/src/sys/dev/em/if_em.c:980 Apr 26 09:57:56 ram kernel: 2nd 0xc0663d80 Giant (Giant) @ /usr/src/sys/vm/vm_contig.c:538 Apr 26 09:57:56 ram kernel: KDB: stack backtrace: Apr 26 09:57:56 ram kernel: kdb_backtrace(c0619e00,c0663d80,c0615a3e,c0615a3e,c06270aa) at kdb_backtrace+0x2e Apr 26 09:57:56 ram kernel: witness_checkorder(c0663d80,9,c06270aa,21a,d403d964) at witness_checkorder+0x6a6 Apr 26 09:57:56 ram kernel: _mtx_lock_flags(c0663d80,0,c06270aa,21a,c04b9b5f) at _mtx_lock_flags+0x8a Apr 26 09:57:56 ram kernel: contigmalloc(1000,c063d760,1,0,) at contigmalloc+0x42 Apr 26 09:57:56 ram kernel: alloc_bounce_pages(c1737d00,4,101,c18ac100,c162e000) at alloc_bounce_pages+0x83 Apr 26 09:57:56 ram kernel: bus_dmamap_create(c1737d00,1,d403da28,c0672c20,0) at bus_dmamap_create+0x131 Apr 26 09:57:56 ram kernel: em_encap(c162e000,c18ac100,c0609329,267,c162e0e8) at em_encap+0x90 Apr 26 09:57:56 ram kernel: em_start_locked(c162e000,,c044cfc0,c162e000,c162e37c) at em_start_locked+0x254 Apr 26 09:57:56 ram kernel: em_intr(c162e000,0,c0613eaa,269,c0663d40) at em_intr+0x143 Apr 26 09:57:56 ram kernel: ithread_loop(c1566400,d403dd48,c0613cce,323,b20684f9) at ithread_loop+0x172 Apr 26 09:57:56 ram kernel: fork_exit(c04b0410,c1566400,d403dd48) at fork_exit+0xc6 Apr 26 09:57:56 ram kernel: fork_trampoline() at fork_trampoline+0x8 Apr 26 09:57:56 ram kernel: --- trap 0x1, eip = 0, esp = 0xd403dd7c, ebp = 0 --- If there's any other information you need, please let me know. Thanks, Josh Crumbs, I'll look at this. Can you provide some details of your system? dmesg? Could you also provide the output of 'sysctl hw.busdma'? Thanks, Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lock order reversal: em0 and Giant
On Tue, Apr 26, 2005 at 12:23:19PM -0600, Scott Long wrote: Crumbs, I'll look at this. Can you provide some details of your system? dmesg? Could you also provide the output of 'sysctl hw.busdma'? Thanks, Scott Hi Scott, The machine is a Tyan Tiger LE with 2x PIII/733s, an Intel Pro/1000 MT 64-bit NIC in a 64-bit/66MHz PCI slot. Storage is 2x WD800JBs in RAID1 on the on-board Promise IDE RAID controller. A CD-RW lives at the on-board primary master IDE location. Video (when I need it) is the on-board ATI. There's not much more to it. The machine is used for NFS, samba, DNS and a few other services for my home network. dmesg: Copyright (c) 1992-2004 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 5.3-RELEASE-p5 #0: Thu Mar 10 23:17:01 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RAM-TEST WARNING: WITNESS option enabled, expect reduced performance. MPTable: AMI CNB30LE Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (731.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 536870912 (512 MB) avail memory = 519897088 (495 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic0 Version 1.1 irqs 0-15 on motherboard ioapic1 Version 1.1 irqs 16-31 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pci0: display, VGA at device 1.0 (no driver attached) atapci0: Promise PDC20267 UDMA100 controller port 0xdf00-0xdf3f,0xdfa8-0xdfab,0xdfa0-0xdfa7,0xdfac-0xdfaf,0xdfe0-0xdfe7 mem 0xfeaa-0xfeab irq 31 at device 3.0 on pci0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 isab0: PCI-ISA bridge port 0x580-0x58f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci1: ServerWorks ROSB4 UDMA33 controller port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 ohci0: OHCI (generic) USB controller mem 0xfeafc000-0xfeafcfff irq 10 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: MPTable Host-PCI bridge pcibus 1 on motherboard pci1: PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xef00-0xef3f mem 0xfebe-0xfebf irq 23 at device 3.0 on pci1 em0: Ethernet address: 00:07:e9:1a:a8:7f em0: Speed:N/A Duplex:N/A cpu0 on motherboard cpu1 on motherboard orm0: ISA Option ROMs at iomem 0xc8000-0xc,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) unknown: PNP0c02 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) Timecounters tick every 10.000 msec acd0: CDRW LITE-ON LTR-40125S/ZS0J at ata0-master UDMA33 ad4: 76319MB WDC WD800JB-00DUA3/75.13B75 [155061/16/63] at ata2-master UDMA100 ad6: 76319MB WDC WD800JB-00DUA3/75.13B75 [155061/16/63] at ata3-master UDMA100 ar0: 76319MB ATA RAID1 array [9729/255/63] status: READY subdisks: disk0 READY on ad6 at ata3-master disk1 READY on ad4 at ata2-master SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ar0s1a WARNING: / was not properly dismounted WARNING: /mnt/media was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /usr/home was not properly dismounted WARNING: /var was not properly dismounted em0: Link is up 1000 Mbps Full Duplex lock order reversal 1st 0xc162e3b4 em0 (network driver) @ /usr/src/sys/dev/em/if_em.c:980 2nd 0xc0663d80 Giant (Giant) @ /usr/src/sys/vm/vm_contig.c:538 KDB: stack backtrace: kdb_backtrace(c0619e00,c0663d80,c0615a3e,c0615a3e,c06270aa) at kdb_backtrace+0x2e witness_checkorder(c0663d80,9,c06270aa,21a,d403d964) at witness_checkorder+0x6a6 _mtx_lock_flags(c0663d80,0,c06270aa,21a,c04b9b5f) at _mtx_lock_flags+0x8a contigmalloc(1000,c063d760,1,0,) at contigmalloc+0x42 alloc_bounce_pages(c1737d00,4,101,c18ac100,c162e000) at alloc_bounce_pages+0x83
Re: HAS_CONFIGURE error?
On Tue, Apr 26, 2005 at 07:31:32PM +0200, Emanuel Strobl wrote:
Hello, from the Mk/bsd.port.mk I read:
# CONFIGURE_ARGS
# - Pass these args to configure if ${HAS_CONFIGURE} is set.
# Default: --prefix=${PREFIX} ${CONFIGURE_TARGET} if
# GNU_CONFIGURE is set, CC=${CC} CCFLAGS=${CFLAGS}
# PREFIX=${PREFIX} INSTALLPRIVLIB=${PREFIX}/lib
# INSTALLARCHLIB=${PREFIX}/lib if PERL_CONFIGURE is set,
# empty otherwise.
The first sentence isn't true on 5.4-RC3. If I define HAS_CONFIGURE=yes
without CONFIGURE_ENV=--prefix=${PREFIX} the configure script doesn't get
--prefix set right.
First, note CONFIGURE_ARGS not CONFIGURE_ENV. I expect that setting
CONFIGURE_ENV as you suggested would not do anything sensible. Can
you confirm what you meant?
Is the description outdated or is this behaviour not intended?
You could check later in the bsd.port.mk file to confirm what it
actually does.
Kris
P.S. Discussion of the ports tree should happen on freebsd-ports.
pgpqcAshTmVlU.pgp
Description: PGP signature
Re: NFS client/buffer cache deadlock
On Tue, Apr 26, 2005 at 06:43:46PM +0200, Marc Olzheim wrote: [changed cc: from standards@ back to stable@ again.] On Tue, Apr 26, 2005 at 12:25:49PM -0400, Brian Fundakowski Feldman wrote: You can assure that this happens in only two ways: 1. Make a complete copy of the data. This is what currently occurs: it gets stuffed into the buffer cache as the write happens. 2. Keep the data around synchronously -- by virtue of the write system call being used synchronously, the thread's VM context is around, and duplication need not occur. It seems as though FreeBSD 4.x either used 2) or does something wrong indeed. Why would 2) be a problem on FreeBSD 5.x ? Can't the pages written from be locked during the write, instead of copied internally ? I'm still guessing that for whatever reason your writes on the FreeBSD 4.x NFS client are not using NFSv3/transactions. The second method I just now implemented; it works fine except for being slower since all data is acknowledged synchronously. Are you using one writev() instead of many writes so you can atomically write a large sparse data structure? If so, you will probably just have to cope with the lower performance than for reasonably-sized writes. If not: why are you trying to write it atomically? Just use multiple normal-sized write() calls. Btw. running the writev program with 20 * 100 MB on UFS on a 512MB FreeBSD 6-CURRENT system practicly locks the filesystem down _and_ causes all processes to be swapped out in favor of the buffer cache. 'top' however, doesnt' show a rise in BUF usage. On FreeBSD 4.x, the system performance as usual during the writev to UFS. That's certainly not very optimal. I don't know anything about it, sorry. -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL in FreeBSD jails
Marc G. Fournier wrote: On Tue, 26 Apr 2005, Bill Moran wrote: Alexander Rusinov [EMAIL PROTECTED] wrote: Hi, I need to run a number of PostgreSQL servers in different FreeBSD jails. I managed to run a first instance of PostgreSQL server in a jail, but after I launch a new server in another jail the first one starts to return an error messages like the following: semctl(1507328, 4, SETVAL, 0) failed: Invalid argument The problem in general is: only one instance of PostgreSQL server processes clients' connections, all of the others return semctl errors. I had this exact same problem. I never found a solution. The cause appears to be that, since shared memory is not segregated between jails, the newly launched Postgres instances corrupt the shared memory of previously running Postgres instances. I'm running 9 jails on a server right now, each with their own instance: and never noticed any issues ... but, this is with 4.11, not 5.x, so maybe something has changed? Can you tell please what version of PostgreSQL are you running? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
apsfilter 7.2.6 - warning about unknown option 'hostname'
Hello, I'm using apsfilter with FreeBSD stable: apsfilter-7.2.6 = up-to-date with port [EMAIL PROTECTED] uname -a FreeBSD kg-work.kg4.no 5.3-STABLE FreeBSD 5.3-STABLE #1: Sun Nov 14 20:19:11 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SS51G i386 when my pdf printer (pdfwrite) stopped working, I noticed in the printer logfiles (/var/spool/lpdPRINTERNAME/log) that I had the same problem as described here: http://lists.freebsd.org/mailman/htdig/freebsd-stable/2003-April/000792.html I have that message for all defined printers that I use. Did anybody find a solution to this problem? -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
VIA M1000 mini-itx system installation woes - WRITE_DMA error - cabling?
Hi all, I am attempting to install 5.3-R from cd (iso image download) and sysinstall is failing to write the chosen (Auto Layout) filesystem to disk, the Toshiba 80G on the primary ide channel as master. The error on vty1 is (from memory) ad0: WRITE_DMA, error=84. The drive is detected by BIOS as a UDMA100 device. There is nothing else on this IDE channel, and only a cd drive on the other IDE slot. A search of -questions reveals this error is a UDMA mismatch, possible caused by 80-pin cabling, and fixable with atacontrol ad0 udma33 pio bla bla bla. However, I do not yet have a running system to run atacontrol from, as I am installing. I have rooted around in the bios for an option to force the drive to UDMA33 speed, to no avail. Does anyone know how I can work around this problem and install FreeBSD to this neat little system? Do I have bad cabling, a bad drive, or ??? Thanks for any follow-up questions, pointers, rants, RTFM's, etc. Woody _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA M1000 mini-itx system installation woes - WRITE_DMA error - cabling?
On Tue, 2005-04-26 at 14:31 -0700, W C wrote: Hi all, I am attempting to install 5.3-R from cd (iso image download) and sysinstall is failing to write the chosen (Auto Layout) filesystem to disk, the Toshiba 80G on the primary ide channel as master. The error on vty1 is (from memory) ad0: WRITE_DMA, error=84. The drive is detected by BIOS as a UDMA100 device. There is nothing else on this IDE channel, and only a cd drive on the other IDE slot. A search of -questions reveals this error is a UDMA mismatch, possible caused by 80-pin cabling, and fixable with atacontrol ad0 udma33 pio bla bla bla. However, I do not yet have a running system to run atacontrol from, as I am installing. I have rooted around in the bios for an option to force the drive to UDMA33 speed, to no avail. Does anyone know how I can work around this problem and install FreeBSD to this neat little system? Do I have bad cabling, a bad drive, or ??? Thanks for any follow-up questions, pointers, rants, RTFM's, etc. Woody I was installing FreeBSD 5.3-Release on an VIA EPIA M1 a while ago and I has no problems at all. My harddisk was a Fujitsu MHT2040AT UDMA-100 2.5, so your problem could be cable or harddisk related. Maybe you have a spare disk/cable at hand to test it. Good luck, Andreas -- GnuPG key : 0xD25FCC81 | http://cyb.websimplex.de/pubkey.asc Fingerprint: D182 6F22 7EEC DD4C 0F6E 564C 691B 0372 D25F CC81 signature.asc Description: This is a digitally signed message part
Re: VIA M1000 mini-itx system installation woes - WRITE_DMA error - cabling?
El Martes, 26 de Abril de 2005 23:31, W C escribi: Hi all, I am attempting to install 5.3-R from cd (iso image download) and sysinstall is failing to write the chosen (Auto Layout) filesystem to disk, the Toshiba 80G on the primary ide channel as master. The error on vty1 is (from memory) ad0: WRITE_DMA, error=84. The drive is detected by BIOS as a UDMA100 device. There is nothing else on this IDE channel, and only a cd drive on the other IDE slot. A search of -questions reveals this error is a UDMA mismatch, possible caused by 80-pin cabling, and fixable with atacontrol ad0 udma33 pio bla bla bla. However, I do not yet have a running system to run atacontrol from, as I am installing. I have rooted around in the bios for an option to force the drive to UDMA33 speed, to no avail. Does anyone know how I can work around this problem and install FreeBSD to this neat little system? Do I have bad cabling, a bad drive, or ??? Ther're two types of 80pins ribbons, and found that you can interchange them in some scenarios. As a first aid, try change the cable, loocking for the presence (or not) of a cut cable. Also, you may use a 40pins ribbon, that will get you in UDMA33 . -- josemi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Headsup: USB MFCs to 4.x
I have just merged in most of the lowest level changes to 4.x from 6.x. If you use USB on 4.x machines and are planning on following RELENG_4 then I suggest you test the latest sources to avoid nasty surprises later. I will probably merge some of the actual device drivers as well, though I have limited resources for testing them.. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA M1000 mini-itx system installation woes - WRITE_DMA error - cabling?
W C wrote: Hi all, I am attempting to install 5.3-R from cd (iso image download) and sysinstall is failing to write the chosen (Auto Layout) filesystem to disk, the Toshiba 80G on the primary ide channel as master. The error on vty1 is (from memory) ad0: WRITE_DMA, error=84. The drive is detected by BIOS as a UDMA100 device. There is nothing else on this IDE channel, and only a cd drive on the other IDE slot. A search of -questions reveals this error is a UDMA mismatch, possible caused by 80-pin cabling, and fixable with atacontrol ad0 udma33 pio bla bla bla. However, I do not yet have a running system to run atacontrol from, as I am installing. I have rooted around in the bios for an option to force the drive to UDMA33 speed, to no avail. Does anyone know how I can work around this problem and install FreeBSD to this neat little system? Do I have bad cabling, a bad drive, or ??? Thanks for any follow-up questions, pointers, rants, RTFM's, etc. Woody _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] My experience with these boards is that they are very picky about RAM. I had similar problems as you have described. I ordered Crucial's recommended stick and it worked fine after that. Aaron ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Wireless hardware support
I recently purchased a Netgear WG311 card based on the fact that the manpage for ath(4) says it is a supported card. As it turns out, at least version 2 (the version I had) of this card is not supported - it appears to be based on a Texas Instruments chipset that it not supported by anything other than Windows. I was able to use the card with the ndis wrapper, however it didn't work very well; console messages stated that the driver was buggy and in fact my system would panic randomly with the driver loaded. I returned the card this afternoon and swapped it out for another card, a D-Link DWL-G520. While this particular model number is not listed on the ath(4) manpage, it is listed as a supported ath(4) device on the 5.3-RELEASE hardware notes for i386. Also, it is listed at the atheros webpage linked from that same document. However, at least revision B3 of this card ALSO is not supported by the ath driver. I get the following error message when I try to load the driver: ath0: Atheros 5212 mem 0xd000-0xd000 irq 16 at device 6.0 on pci5 ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I am able to use this card via the ndis wrapper, however I get numerous console messages like these (I renamed the device ath with ndiscvt): ath0: set filter failed: 45 ath0: couldn't change DS config to 2417000kHz: 19 NDIS: open file /compat/ndis/regAdd.txt failed: 2 I fixed the latter by touching the file. I have no idea what it is supposed to do - there is no file by that name on the CD that came with the card and I am not sure what it is for. Interestingly, the DWL-G520 is supposed to be an 802.11b/g part only however the NDIS driver 'detects' 802.11a modes. Also the NDIS driver does not detect the 108Mbps 'Super' mode that the card advertises on the box. Thankfully, no panics yet with the D-Link card and the NDIS driver. Does anyone have a suggestion for a PCI wireless card that is natively supported by FreeBSD? -Will -- Will Saxon Systems Programmer, Network Services University of Florida Department of Housing Phone: (352) 392-2171 x10148 Email: [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: Wireless hardware support
I have had some degree of success with the Netgear WG311T (note the T on the end -- this is a very different beast from the humble WG311). I've brought it up a couple of times at a ridiculously slow speed (1Mb/s), then changed some setting to try to get a faster connection, forgot what I changed, and haven't been able to bring it up since. But I *have* had it up using the ath driver. Once or twice. Slowly. I mostly use that machine for gaming, so rarely boot it to freebsd, so haven't had much motivation to try again since. FWIW, at the time it was running 5.3-RELEASE. On 4/27/05, Will Saxon [EMAIL PROTECTED] wrote: I recently purchased a Netgear WG311 card based on the fact that the manpage for ath(4) says it is a supported card. As it turns out, at least version 2 (the version I had) of this card is not supported - it appears to be based on a Texas Instruments chipset that it not supported by anything other than Windows. I was able to use the card with the ndis wrapper, however it didn't work very well; console messages stated that the driver was buggy and in fact my system would panic randomly with the driver loaded. I returned the card this afternoon and swapped it out for another card, a D-Link DWL-G520. While this particular model number is not listed on the ath(4) manpage, it is listed as a supported ath(4) device on the 5.3-RELEASE hardware notes for i386. Also, it is listed at the atheros webpage linked from that same document. However, at least revision B3 of this card ALSO is not supported by the ath driver. I get the following error message when I try to load the driver: ath0: Atheros 5212 mem 0xd000-0xd000 irq 16 at device 6.0 on pci5 ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 I am able to use this card via the ndis wrapper, however I get numerous console messages like these (I renamed the device ath with ndiscvt): ath0: set filter failed: 45 ath0: couldn't change DS config to 2417000kHz: 19 NDIS: open file /compat/ndis/regAdd.txt failed: 2 I fixed the latter by touching the file. I have no idea what it is supposed to do - there is no file by that name on the CD that came with the card and I am not sure what it is for. Interestingly, the DWL-G520 is supposed to be an 802.11b/g part only however the NDIS driver 'detects' 802.11a modes. Also the NDIS driver does not detect the 108Mbps 'Super' mode that the card advertises on the box. Thankfully, no panics yet with the D-Link card and the NDIS driver. Does anyone have a suggestion for a PCI wireless card that is natively supported by FreeBSD? -Will -- Will Saxon Systems Programmer, Network Services University of Florida Department of Housing Phone: (352) 392-2171 x10148 Email: [EMAIL PROTECTED] ___ 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]
