rfork problem
Hello, Combining flags RFNOWAIT and RFPPWAIT in rfork(2) under 4.6-RELEASE makes the parent process sleeping on channel ppwait forever. Regards, Igor. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel malloc usage
Hi all, I have a question concerning the use of malloc to allocate small amounts of memory for packet wrappers for certain packets. Basically, I'm using malloc in much the same way as one would use it in a standard userland program: allocating small chunks and freeing them again a short(ish) time later. A colleague said this was a bad idea, since malloc should only really be used to allocate larger chunks (PAGE_SIZE and over) at driver initialisation. Management and partition of the allocated space should be done by the driver. His reason was that over time, the kernel heap memory gets progressively more fragmented until it becomes difficult to get larger blocks. Is this true? I seem to remember that FreeBSD has a slab allocator, which IIRC is particularly good at allocating small chunks. Is it a better idea to write my own allocators which use a larger block of memory allocated by malloc at driver start-time, or can I use malloc as in userland? Cheers, Gerald -- S y s K o n n e c t G m b H A Marvell Company Siemensstr. 23 D-76275 Ettlingen, Germany - Gerald Heinig Software Engineer - phone: + 49 (0) 7243 502 354 fax:+49 (0) 7243 502 364 email: [EMAIL PROTECTED] http://www.syskonnect.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel malloc usage
On Mon, Nov 03, 2003 at 10:51:58AM +0100, Gerald Heinig wrote: Is this true? I seem to remember that FreeBSD has a slab allocator, which IIRC is particularly good at allocating small chunks. You don't specify which version of the kernel you're programming to; so I'll assume 5.x. If your allocations are of similar size, then consider using the zone allocator; I believe this implements a slab-like algorithm. BMS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1-p10 reproducible crash with Apache2
* Branko F. Gra?nar ([EMAIL PROTECTED]) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Today i added the following lines in my kernel config and i recompiled kernel: makeoptionsDEBUG=-g optionsDDB optionsINVARIANTS optionsINVARIANT_SUPPORT optionsWITNESS I reran apache2 ssl test with jmeter. Machine stopped responding after 3-4 seconds (keyboard and console are unresponsible, machine doesn't respond to ping, sshd stops responding...) [ I couldn't find this thread on the archives so I'm jumping in blind. ] Perhaps you're being livelocked by so many interrupts hitting the system that it doesn't do anything productive and only stays there handling interrupts. Can you try polling (http://info.iet.unipi.it/~luigi/polling/) ? -- Giovanni P. Tirloni gpt at tirloni.org Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1-p10 reproducible crash with Apache2
* Branko F. Grac(nar ([EMAIL PROTECTED]) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | | [ I couldn't find this thread on the archives so I'm jumping in blind. ] | | Perhaps you're being livelocked by so many interrupts hitting the | system that it doesn't do anything productive and only stays there | handling interrupts. | | Can you try polling (http://info.iet.unipi.it/~luigi/polling/) ? This is SMP machine... So polling shouldn't even work. That's true. Although I remember someone here got it working but I can't remember his name. -- Giovanni P. Tirloni gpt at tirloni.org Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: spambouncer tags much freebsd list mail as spam
C. Kukulies wrote: I installed the spambouncer.org procmail script and before I was switching the behaviour from SILENT to COMPLAIN I took a look at my spam.incoming folder and found a lot of messages from freebsd-bugs and freebsd-mobile in there. Both lists are not directed to folders prior to spambouncer coming into effect so they are trapped by spambouncer and I suspect that other freebsd lists would be trapped as well. Anyone experienced similar? The spambouncer script makes the same incorrect assumption that the EarthLink SPAM stuff makes, which is that any mail not explicitly addressed to you is SPAM. In other words, they expect mailing lists to violate the draft RFC that prohibits header rewriting by mailing lists, and they expect all mailing list servers to eat the overhead of expanding each message to a single recipient message, instead of sending the messages in bulk if the destination domain is identical. At least the spambouncer script can be modified to respect the Sender: header, which EarthLink fails to respect in their list of allowed senders. This is pretty much how you should modify the spambouncer code to handle mailing lists (and how EarthLink should modify their anti-SPAM system, as well, but probably won't). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Sound Blaster Audigy LS problem
Dear @hackers, i recently bought a soundblaster audigy ls card hoping that it would just work with freebsd, but sadly this is not the case. at boot, i see that we recognize that there is a sound card, but that's not adequate. pciconf -l -v: [EMAIL PROTECTED]:7:0: class=0x040100 card=0x10021102 chip=0x00071102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' class= multimedia subclass = audio /sys/dev/sound/pci/emu10k1.c defines the following: #define EMU10K1_PCI_ID 0x00021102 #define EMU10K2_PCI_ID 0x00041102 from this, i've concluded that either a) this card has an audigy-compatible chipset and the freebsd driver just doesn't recognize it, b) this card has an audigy-compatible chipset and the freebsd driver not only doesn't recognize it, biut it might even be slightly different, or c) this audigy ls card really isn't that similar at all to other audigy cards. so, i tried just changing the PCI_ID defines above to match my card's id, but writes to the device through mpg123 and xmms give me: pcm0:play:0: play interrupt timeout, channel dead so the question afer all of this is: has anyone been able to push sound out of an audigy ls card? does anyone know what the chipset is (emu10k1, emu10k2...)? would it be trivial for me to hack emu10k1 into compatibility? thank you in advance. -Anthony. P.S. FreeBSD pickle 5.1-RELEASE-p10 FreeBSD 5.1-RELEASE-p10 #0: Mon Nov 3 19:10:54 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/PICKLE i386 P.P.S. also, someone may want to look at sys/dev/sound/pcm/channel.c (lines 279-282): timeout = (hz * sndbuf_getblksz(bs)) / (sndbuf_getspd(bs) * sndbuf_getbps(bs)); if (timeout 1) timeout = 1; timeout = 1; seems like overkill... pgp0.pgp Description: PGP signature
Re: FreeBSD 5.1-p10 reproducible crash with Apache2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. Today i added the following lines in my kernel config and i recompiled kernel: makeoptionsDEBUG=-g optionsDDB optionsINVARIANTS optionsINVARIANT_SUPPORT optionsWITNESS I reran apache2 ssl test with jmeter. Machine stopped responding after 3-4 seconds (keyboard and console are unresponsible, machine doesn't respond to ping, sshd stops responding...) after reboot machine does not save core (panic didn't happen), so i'm unable to give you any kernel dump. # savecore /var/crash /dev/ar0s1b savecore: no dumps found /etc/rc.conf: dumpdev=/dev/ar0s1b # Device name to crashdump to (or NO). dumpdir=/var/crash# Directory where crash dumps are to be stored savecore_flags= # Used if dumpdev is enabled above, and present. Brane -BEGIN PGP SIGNATURE- iD8DBQE/plv0fiC/E+t8hPcRAovOAJ47Yv9qk0/7E43dZFtMf7vAJ694agCfUtm8 xWCjwkSpilNcTUW3cvs1330= =EmbK -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1-p10 reproducible crash with Apache2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | | Can you try polling (http://info.iet.unipi.it/~luigi/polling/) ? Hi. I just disabled SMP support, enabled polling (i've also set sysctl variable to 1) and reran the test. Machine locked up in about 5 seconds (this is 1u p4 xeon 2.4 GHz, 2GB of ~ ram). This only accours if Apache2 SSLMutex is set to 'sem' and SSLSessionCache is set to 'shm:/path(size)'. So... there are possible problems with shared memory implementation in 5.1-RELEASE Brane -BEGIN PGP SIGNATURE- iD8DBQE/pmfzfiC/E+t8hPcRAqGzAJ4vTHkq/CH9Z/t9JzoQmyrra7kGkQCgkNNY /ymFJanS5jNGBkypPc6t4Ts= =cxx4 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.1-p10 reproducible crash with Apache2
On Mon, 3 Nov 2003, [ISO-8859-1] Branko F. Grac(nar wrote: Machine locked up in about 5 seconds (this is 1u p4 xeon 2.4 GHz, 2GB of ~ ram). This only accours if Apache2 SSLMutex is set to 'sem' and SSLSessionCache is set to 'shm:/path(size)'. So... there are possible problems with shared memory implementation in 5.1-RELEASE Brane Can you try updating to 5.1-current and see if the situation changes at all? A lot has changed since 5.1-release. If it's still broken in 5.1-current, we can take a look into it. Thanks, Mike Silby Silbersack ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
