poor sound quality in 5.3 stable
Hi folks, I recently installed FreeBSD 5.3 stable. I got my sound blaster live 5.1 sound card working with FreeBSD by adding device sound device emu10k1 in the kernel configuration file. However the quality of sound produced is of poor quality (not very clear) as compared to that produced under Linux 2.6 series kernel. I remember having similar quality sound when OSS was used with Linux Kernel. Is this poor quality because of OSS ? Is ALSA ported to FreeBSD ? Or am I just using wrong driver ? Tejas Kokje University of Southern California ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: poor sound quality in 5.3 stable
Tejas Kokje wrote: Hi folks, I recently installed FreeBSD 5.3 stable. I got my sound blaster live 5.1 sound card working with FreeBSD by adding device sound device emu10k1 hmmm... the 5.3 handbook has : device snd_emu10k1 or /boot/loader.conf : snd_emu10k1_load=YES regards Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-RELEASE crashes during make buildworld (and other problems)
On Mon, 17 Jan 2005, Vivek Khera wrote: On Jan 13, 2005, at 4:46 AM, Peter Jeremy wrote: That doesn't totally rule out hardware. Pattern-sensitive memory problems may not show up on different operating systems (or even different kernels). That said, based on the trap information, I'd look at a software cause first. Indeed. I once had a box that would run Linux 100% stable under any load for months on end, but with BSD/OS it would crap out (random processes fail) after a max of 3 weeks requiring a reboot. Never rule out bad hardware, especially with PC crap. Even minor OS revisions can reveal or hide memory problems. For example, for quite a while one of my Pentium (1!) server boxes had a single bit error (a stuck on bit) that fell into a section of memory that always held pinned kernel pages, and in particular, ended up holding a fairly obscure kernel code branch in a module that was loaded. Then one day kernel memory layout got chaged a bit, and the page ended up being paged into user memory, resulting in frequent application segfaults and data corruption. I was sure it was the OS upgrade, since backing out to the previous kernel/modules fixed it reliably ... until I ran a memory test and figured out what was actually happening. It was pretty frustrating to try to debug, and reinforces the conclusion that doing a bit of legwork on a badly behaving system to confirm it's not a hardware fault that can be easily ruled out can go a long way. Which isn't to say that the problem in this thread is hardware, but you don't want to spend two weeks tracking a kernel bug to find out that swapping out the memory with a seemingly identical DIMM fixes it. Checking ethernet cabling and link negotiation, a decent memory test run, checking SCSI termination, checking ATA cable type, etc, as first steps to debugging a problem that would have similar symptoms is a good strt. Oh, and if it's your parents calling on the phone at 6:30am with a printer problem, the first thing to ask is whether their printer is plugged in. :-) Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Purpose of CD9660_ROOT
RELENG_4 documents a config option: options CD9660_ROOT #ISO 9660 Filesystem usable as root but I am unable to find any other reference to this option. I can confirm that CD9660_ROOT is _not_ necessary for 4.10 (at least) boot off a CD-ROM and use it as root. The last reference I can find is in ARCH/ARCH/autoconf.c from whence it was deleted well before RELENG_4_BP. Have I missed something or is this option a total no-op? -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum Raid5 Init question
I've installed Vinum RAID5 on a 4-disk setup. Since I don't have much experience I installed my plex through the example in the Vinum manual. I used 'setupstate' to put the disks into 'up'-status. Quote from the manual of the 4th example of the chapter HOW TO SET UP VINUM: In addition, the volume specification includes the keyword setupstate, which ensures that all plexes are up after creation. But a couple of weeks later I read the following in the manual: Note that you must use the init command with RAID-5 plexes: otherwise extreme data corruption will result if one subdisk fails. I read this to my horror after I filled the volume with data. You'll probably noticed I didn't init my volume. The disks are in good condition. The volume is almost filled to the maximum capacity. So a backup is a bit difficult due to the size of it. Are there any other options? If one disks fails, do I still get corrupted data? I don't know if any manual maintainer is reading this, but is it possible to add this warning to the RAID5 example at the end of vinum(8)? Regards, David Elsing Vinum create file: drive d1 device /dev/ad4s1e drive d2 device /dev/ad5s1e drive d3 device /dev/ad6s1e drive d4 device /dev/ad7s1e volume raid setupstate plex org raid5 1024k sd length 0 drive d1 sd length 0 drive d2 sd length 0 drive d3 sd length 0 drive d4 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: remaining FreeBSD 4.11-RC3 bugs
Ken Smith [EMAIL PROTECTED] writes: On Mon, Jan 17, 2005 at 10:28:53AM +0100, Matthias Andree wrote: critical: kern/60313 (silent data corruption on block devices) still open, may be FreeBSD 4 specific after the GEOM flurry in FreeBSD 5 and 6. I took a look at that one. The patch provided doesn't map exactly into RELENG_4 but I gave this a try: Some (similar) attempts are in the mailing list archives, but none ended as a complete fix and stopped halfway for various reasons, usually lack of time or interest. I know too little about kernel internals as to be of any help here, besides testing. With that in place the kernel won't boot because the stuff dealing with disk labels in at least two places on my machine didn't set the offset properly in the buf structures it used. Once I fixed that the machine booted but *some* executables wouldn't start because spec_getpages() was doing reads with an offset of 256 (DEV_BSIZE is 512). These some executables may well have been reading the wrong data since the block devices have become unbuffered... if unaligned, the seek offset is silently rounded down to the previous block margin. I'll see if I can follow up on this and eventually get RELENG_4 fixed (and perhaps even an Errata) but there is no way I'd be comfortable with a fix for this going into 4.11 unless an expert worked on it and we did an RC4. I can understand that. serious: bin/71453 (tcpdump ipv6 crash, trivial fix -- MFC sufficient) still open It looks like the right way to fix this is with a fresh vendor import if I'm understanding things correctly. Again something that would require more time than we have and might be best handled as an Errata item after the release. If the FreeBSD 4.11-RC tcpdump is essentially the same as the FreeBSD tcpdump around 5.3, the import of a single fix may be sufficient. It's only that the tcpdump executable does The Wrong Thing when encountering PPP packets to negotiate IPv6 - it faults, rather than reporting an unknown packet and moving on. The patch quoted in the PR fixes only that bogus abort. bin/46866 (false data from getpwent, easy to fix) still open There has been ongoing disagreements about how best to handle this one, as far as I can tell the disagreements are still ongoing. If FreeBSD prefers non-deterministic results with all non-repeatable and hard to debug consequences such as mail bouncing, users denied login and so on, well. The only reason brought forth in support of the current behavior was the measly we've always done it this way and perhaps we don't know what will break if. Neither is a valid justification to keep the bug in. Note this change need only happen for functions with insufficient interfaces, i. e. those that cannot report a difference between temporary and permanent error, such as getpwent(), and AFAICT the lookups happen in user-space, so SIGINT would work. -- Matthias Andree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
strange ucom (uplcom) error
Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have ucom0, also I can receive signal but not transmit. When I connect the (more expensive) adopter to a serial console (FreeBSD comconsole) I can see all kernel messages but I can't type any charecter when I see the login. If I change to the cheaper adopter everything is working fine. I compared 'stty -a -f /dev/ucom0' and both adaptors show the same settings. I'm using tip (ucom0:dv=/dev/ucom0:br#115200:pa=none:) on RELENG_5 (from this weekend) Here is usbdevfs output and the corresponding dmesg line for both adapters, the 2nd (ATEN) is the working one (cheaper one), the first the more expensive not working one! port 1 addr 2: full speed, power 100 mA, config 1, USB-Serial Controller(0x2303), Prolific Technology Inc.(0x067b), rev 3.00 __dmesg: ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 port 1 addr 2: full speed, power 100 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 __dmesg: ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 Any help highly appreciated! -Harry pgpO2z73raAXs.pgp Description: PGP signature
ruby and portupgrade
i am trying to do a portupgrade and after it running for 7 hrs and not doing anything it quits with this error message. black-buity# portupgrade -aRrcCv --- Reading default options: -v -D -l /var/tmp/portupgrade.results -L /var/tmp/portupgrade-%s::%s.log --- Session started at: Sat, 15 Jan 2005 12:07:25 -0800 [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 110 packages found (-0 +23) ... done] --- Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 black-buity# black-buity# ruby --version ruby 1.8.2 (2004-07-29) [i386-freebsd5] black-buity# uname -a FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Dec 10 14:50:33 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/VAMPEXTREAM i386 black-buity# i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby from 1.6 to 1.8 .. so my quistions are 1. what would be causeing this?? 2. how do i fix this? and thanks inadvance for any help on this issue/ error message If you play the WindowsXP CD backwards, you get a Satanic message . That's nothing. If you play it forwards, it installs WindowsXP! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ruby and portupgrade
On Tue, Jan 18, 2005 at 03:01:46AM -0800, whitevamp wrote: i am trying to do a portupgrade and after it running for 7 hrs and not doing anything it quits with this error message. black-buity# portupgrade -aRrcCv --- Reading default options: -v -D -l /var/tmp/portupgrade.results -L /var/tmp/portupgrade-%s::%s.log --- Session started at: Sat, 15 Jan 2005 12:07:25 -0800 [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 110 packages found (-0 +23) ... done] --- Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 black-buity# black-buity# ruby --version ruby 1.8.2 (2004-07-29) [i386-freebsd5] black-buity# uname -a FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Dec 10 14:50:33 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/VAMPEXTREAM i386 black-buity# i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby from 1.6 to 1.8 .. so my quistions are 1. what would be causeing this?? 2. how do i fix this? and thanks inadvance for any help on this issue/ error message Database seems to be corrupted, rebuild it with 'pkgdb -fu' -Kirill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Raid5 Init question
On Tue, Jan 18, 2005 at 12:21:59PM +0100, David Elsing wrote: Quote from the manual of the 4th example of the chapter HOW TO SET UP VINUM: In addition, the volume specification includes the keyword setupstate, which ensures that all plexes are up after creation. But a couple of weeks later I read the following in the manual: Note that you must use the init command with RAID-5 plexes: otherwise extreme data corruption will result if one subdisk fails. Yes, this particular gotcha bit me a while back and I lost quite a bit of data (my fault for not having good backups) due to it. IMO, I still consider it a documentation bug though. That particular bit is buried in a command reference section rather than being in bold in the HOW TO guide. I read this to my horror after I filled the volume with data. You'll probably noticed I didn't init my volume. The disks are in good condition. The volume is almost filled to the maximum capacity. So a backup is a bit difficult due to the size of it. Are there any other options? If one disks fails, do I still get corrupted data? Yes, if one disk fails for any reason, every third sector will be garbage and it's unlikely you'll be able to recover anything useful from it. I would highly recommend backing up whatever is critically important to you asap. If you like living dangerously and all the drives are in good health, the parity data can be (theoretically) repaired with the vinum rebuildparity command, but do so at your own risk... That did allow me to recover a couple of my partitions that hadn't been trashed yet. Also, if a good disk gets marked as down somehow before you can correct this, whatever you do, do NOT issue a vinum start command on it. In the current state of the array, that would be destructive and irreversible. That's what happened to me: ATA timeout caused one of the drives to temporarily detach, corrupt filesystems caused a panic. If this happens, you're better off using setstate to force it to up, as wrong as that would normally be. I've also noticed that sometimes the parity gets out of sync on its own, but I don't know the cause. I used to have a cron job that ran vinum checkparity once a month in the background and occasionally it would find sectors that needed to be rebuilt. Unfortunately this doesn't seem to be implemented with gvinum (5.3) yet. ...know if any manual maintainer is reading this, but is it possible to add this warning to the RAID5 example at the end of vinum(8)? I'll second this idea, at least for 4.x. I'm not sure how gvinum handles things as I haven't built any RAID5 volumes from scratch using it. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ruby and portupgrade
i am trying to do a portupgrade and after it running for 7 hrs and not doing anything it quits with this error message. black-buity# portupgrade -aRrcCv --- Reading default options: -v -D -l /var/tmp/portupgrade.results -L /var/tmp/portupgrade-%s::%s.log --- Session started at: Sat, 15 Jan 2005 12:07:25 -0800 [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 110 packages found (-0 +23) ... done] --- Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 black-buity# black-buity# ruby --version ruby 1.8.2 (2004-07-29) [i386-freebsd5] black-buity# uname -a FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Dec 10 14:50:33 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/VAMPEXTREAM i386 black-buity# i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby from 1.6 to 1.8 .. so my quistions are 1. what would be causeing this?? The 7 hours were taken up by rebuilding the INDEX. The failure will be because your portupgrade is too old. 20041113: AUTHOR: [EMAIL PROTECTED] Since INDEX version in CVS is always too old, portmgr decided to remove it. You will still be able to build your own INDEX or use 'fetchindex' target in /usr/ports/. 2. how do i fix this? pkg_delete portupgrade-\* (cd /usr/ports/sysutils/portupgrade; make install clean) and thanks inadvance for any help on this issue/ error message If you play the WindowsXP CD backwards, you get a Satanic message . That's nothing. If you play it forwards, it installs WindowsXP! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: strange ucom (uplcom) error
On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have ucom0, also I can receive signal but not transmit. [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer revision chip (tested under 4.10). -Harry Andrew. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Building your own FreeBSD installation CD-ROM
List, (I asked this question last week on -questions but received zero answers. My apologies if this is the second time you are seeing this question). how does one go about creating a FreeBSD install CD-ROM? I'd like to be able to build my own CD-ROM with as much as possible of the install process done automatically. For instance, what parts of FreeBSD to install: X or not, games or not, etc. etc. And which ports to install straight away. I could also set up cfengine so that as soon as the machine came to life it could go and connect to my cfengine repository and download all the latest configurations to move into operational status. E.g., I'd like to just have to specify the partition layout, the name and IP of the machine, and its role(s): (web, dns, squid, mta, samba...) This would make rebuilding so much faster if a machine was catastrophically trashed. I could just hand someone a CD and a sheet of paper and they should be able to work it out by themselves without knowing too much about the ins and outs of FreeBSD. I could go on holidays without being stressed out. Thanks for any pointers to documentation on the subject, I'm sure people have done this before, but I can't coax the results out from my web searches. Thanks, David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building your own FreeBSD installation CD-ROM
On Tue, Jan 18, 2005 at 06:14:52PM +0100, David Landgren wrote: how does one go about creating a FreeBSD install CD-ROM? I'd like to be able to build my own CD-ROM with as much as possible of the install process done automatically. For instance, what parts of FreeBSD to install: X or not, games or not, etc. etc. And which ports to install straight away. I could also set up cfengine so that as soon as the machine came to life it could go and connect to my cfengine repository and download all the latest configurations to move into operational status. There is some documentation in /usr/src/release on how to build a custom release (I did it successfully around 4.4 time). It is also possible to script the installer via a configuration file. Look at sysinstall(8) manpage for details. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building your own FreeBSD installation CD-ROM
On 18 January 2005, David Landgren wrote: : how does one go about creating a FreeBSD install CD-ROM? I'd like to be : able to build my own CD-ROM with as much as possible of the install : process done automatically. The latter question I can't answer, but I made my own generic install CDs for 4.8-PRERELEASE in 2003 and got some help from the list. I wrote up what I did here, in the 18 April 2003 entry: http://www.miskatonic.org/freebsd.html (Sorry, no direct link to that entry.) I don't know how different things are for 5, and what I did was basic, but perhaps it'll be of use. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: poor sound quality in 5.3 stable
On Tue, Jan 18, 2005 at 12:07:03AM -0800, Tejas Kokje wrote: Hi folks, I recently installed FreeBSD 5.3 stable. I got my sound blaster live 5.1 sound card working with FreeBSD by adding device sound device emu10k1 in the kernel configuration file. However the quality of sound produced is of poor quality (not very clear) as compared to that produced under Linux 2.6 series kernel. I remember having similar quality sound when OSS was used with Linux Kernel. Is this poor quality because of OSS ? Is ALSA ported to FreeBSD ? Or am I just using wrong driver ? I'm using latest OSS from opensound.org and the sound quality is perfect. -ip -- He who laughs last -- probably didn't get the joke. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange ucom (uplcom) error
On Tue, 18 Jan 2005, Andrew L. Neporada wrote: The not working (more expensive) one gets recognized as ucom0 and I have ucom0, also I can receive signal but not transmit. [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer revision chip (tested under 4.10). Hmmm... That could explain something I saw. I've got two cables, bought from different vendors (same chipset). Both worked under 4.10, only one under 5.3 (different platforms). I'll try it when I get a moment. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: backporting tail from HEAD to RELENG_5
Date: Mon, 17 Jan 2005 21:19:05 +0100 (CET) From: Oliver Fromme [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Xin LI [EMAIL PROTECTED] wrote: On Thu, Jan 13, 2005 at 01:01:44PM -0600, Doug Poland wrote: Cool, I currently get this functionality from misc/xtail. xtail was on my short list of must-have ports. Would you please share the list with us? I think it would be helpful if we know the needs :-) I'm surprised that nobody else replied. This is a list of small non-X11 ports that I install on most machines (even non-FreeBSD if applicable). This list is certainly not complete, and everyone probably has his/her own favourite tools. - cpdup(great to copy/sync directory trees) - cvsup-without-gui (cannot use FreeBSD without it) - elinks (nice text web browser, better than lynx) - fping(useful to ping multiple hosts/nets at once) - joe (my fav. editor, though I can cope with vi, too) - logsurfer (useful tool to watch your logs) - lsof (can't live without it) - lynx-ssl (sometimes useful) - netcat (well-known) - nmap (well-known) - omi (I use this one to mirror stuff via FTP) - par (I use this often for mail / news) - screen (can't live without it) - strace (better than ktrace and truss, IMO) - super(better than sudo, in my opinion) - trafshow (very nice tool to watch network activity) - zsh (my favourite shell, very powerful) Of course, lots of people will probably have different opinions about some of those tools. But that's one of the big advantages of FreeBSD and its ports collection: You have enough things to chose from, so go and try them to find the one which suits you best. :-) Excellent. I've used swatch for a long time, but I had missed logsurfer. I'll see how it does. One absolute requirement for me is most(1) which is more(1) than less(1). It handles binary files and has a number of very nice capabilities that less lacks, but wraps lines with a '\' at the wrap point which I find very annoying. But I still prefer it and, even when I try to type more, my fingers insist on most at least once. Guess it's because I've been using most(1) for at least 15 years and probably closer to 20. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange ucom (uplcom) error
Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have ucom0, also I can receive signal but not transmit. [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately also breakes the 2.02 version :( Perhaps there's a goog guy out there who can refurbish the uplcom driver with this information (akiyama?)? Thanks a lot, -Harry revision chip (tested under 4.10). -Harry Andrew. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgpUJhVUkj8T3.pgp Description: PGP signature
Fatal trap 12 on 5.3-Stable system
On the command: ping6 -m -s 1460 node I get a panic with the following (hand transcribed): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present inruction pointer = 0x8:0xc052dc52 stack pointer = 0x10:0xdb31cc08 frame pointer = 0x10:-xdb31c44 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume IOPL = 0 current process = 1043 (ping6) [thread pid 1043 tid 100095 ] Stopped at soreceive+0x556:movl0x4(%eax),%eax db trace Tracing pid 1043 tid 100095 td 0xc21a47d0 soreceive(c2151b64,db31cc6c,db31cc78,0,c1c38500) at soreceive+0x556 recvit(c21a47d0,3,db31ccc0,0,c1b3d930) at recvit+0x1c7 recvmsg(c21a47d0,db31cd14,3,1,292) at recvmsg+0x5f syscall(bfbf002f,2f,bfbf002f,bfbfe82c,8077800,) at syscall+0x27b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (27, FreeBSD ELF32, recvmsg), eip = 0x280fb3d3, esp = 0xbfbfe76c,ebp = 0xbfbfecf4 --- Looks a lot like the large size might be over-writing something. Reproducable at will. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make -jN test
(warning long post) Hi all, A recent thread on a I subscribe to in regard to the usefullness of using the -j flag on a make world led me to run a test over the weekend just to see it's effectiveness. This is the section of the handbook that started it all for me: (from: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html) It is now possible to specify a -j option to make which will cause it to spawn several simultaneous processes. This is most useful on multi-CPU machines. However, since much of the compiling process is IO bound rather than CPU bound it is also useful on single CPU machines. On a typical single-CPU machine you would run: # make -j4 buildworld make(1) will then have up to 4 processes running at any one time. Empirical evidence posted to the mailing lists shows this generally gives the best performance benefit. If you have a multi-CPU machine and you are using an SMP configured kernel try values between 6 and 10 and see how they speed things up. So to test this out I wrote a shell script to time a make -jN buildworld where N = a number from 1-8. The idea is to see if there is any speedup between running make -j1 and make -j8 on a dual proc box. Now this is not scientific, altho maybe the findings are typical for a low system load box. I also had the box sleep for 60 secs between each build. Here are my timings: building world with 1 jobs... real95m20.543s user83m18.550s sys 13m20.120s cleaning /usr/src building world with 2 jobs... real54m15.856s user84m42.337s sys 16m39.216s cleaning /usr/src building world with 3 jobs... real53m53.239s user85m12.189s sys 17m13.039s cleaning /usr/src building world with 4 jobs... real53m56.539s user85m22.767s sys 17m22.433s cleaning /usr/src building world with 5 jobs... real54m10.993s user85m30.995s sys 17m14.160s cleaning /usr/src building world with 6 jobs... real54m10.814s user85m24.063s sys 17m27.437s cleaning /usr/src building world with 7 jobs... real54m15.289s user85m25.479s sys 17m27.751s cleaning /usr/src building world with 8 jobs... real54m23.526s user85m27.173s sys 17m28.891s As you can tell there does not seem to be a rampup after a make -j2 buildworld. This is a SMP system, with stripped scisi disks (altho the controller is GIANT lockedmaybe this is preventing additional gains?). For completness here is my dmesg: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #1: Tue Jan 4 19:06:52 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU - S 1266MHz (1263.08-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b4 Stepping = 4 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1610530816 (1535 MB) avail memory = 1568518144 (1495 MB) MPTable: IBM ENSW NF 4100R SMP FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 3 cpu1 (AP): APIC ID: 0 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic1 Version 1.1 irqs 16-31 on motherboard ioapic0 Version 1.1 irqs 0-15 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) fxp0: Intel 82559 Pro/100 Ethernet port 0x2200-0x223f mem 0xfea0-0xfeaf,0xfeb7f000-0xfeb7 irq 27 at device 2.0 on pci0 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:09:6b:9a:12:13 fxp1: Intel 82559 Pro/100 Ethernet port 0x2240-0x227f mem 0xfe90-0xfe9f,0xfeb7e000-0xfeb7efff irq 25 at device 10.0 on pci0 miibus1: MII bus on fxp1 inphy1: i82555 10/100 media interface on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:09:6b:9a:12:14 isab0: PCI-ISA bridge port 0x440-0x44f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 UDMA33 controller port 0x700-0x70f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: OHCI (generic) USB controller mem 0xfeb7d000-0xfeb7dfff irq 7 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: 2 ports with 2 removable, self powered pcib1: MPTable Host-PCI bridge pcibus 1 on motherboard pci1: PCI bus on pcib1 pci1: mass storage, SCSI at device 3.0 (no driver attached) ips0:
Re: poor sound quality in 5.3 stable
Hi, Do you mean that the sound seems unclear all the time? I've also had some problems with sound on my FreeBSD 5.3-STABLE, but a different kind of. Sometimes I hear crakings while playing mp3 files with XMMS, although my computer's load is very low. I use snd_emu10k1 sound module as you do with a Creative Sound Blaster Live! 5.1. There is another driver that may be worth trying here: http://chibis.persons.gfk.ru/audigy/. I'll give it a pick when I get more time. Cheers, Olivier ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Possible Problem w/4.10-stable And SMBFS?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am seeing a number of intermittent problems with SMBFS-mounted partitions and am wondering if these are know FBSD problems or problems with the Win32 servers: 1) After running for a very long time (weeks), SMBFS-connected directories ~ become very slow/sluggish for read/write. A reboot of the FBSD machine ~ fixes this. Error log shows: ~Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid 15734 ~Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid 15736 ~This machine is running 4.11-PRERELEASE as of 12/14/2004 2) Again, after running for a long time (several weeks), attempts to ~ to long running I/O against an SBMFS-mounted partition, I get ~ a bus error and the following entries in /var/log/messages: ~Jan 18 16:45:49 xyz /kernel: smb_iod_recvall: drop resp with mid 34907 ~Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid 39329 ~Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid 42496 ~ This seems to be a problem primarily with very large files (100s of ~ megs to several gigs) - at least I've not seen this problem w/small ~ files. ~ This machine is running 4.10-STABLE as of 11/30/2004 Ideas would be appreciated... - -- - Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFB7ZjpyjgA+Mact+YRAgmVAJ9V90kdxogkmixMGGL259Phz75tuQCdEmu+ hdSY/kUNVsvpBiGlil/kiko= =psGE -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: poor sound quality in 5.3 stable
On Wed, 19 Jan 2005 00:03:20 +0100, Olivier Certner [EMAIL PROTECTED] wrote: Hi, Do you mean that the sound seems unclear all the time? I've also had some problems with sound on my FreeBSD 5.3-STABLE, but a different kind of. Sometimes I hear crakings while playing mp3 files with XMMS, although my computer's load is very low. I use snd_emu10k1 sound module as you do with a Creative Sound Blaster Live! 5.1. There is another driver that may be worth trying here: http://chibis.persons.gfk.ru/audigy/. I'll give it a pick when I get more time. I have problems also with sb live. There was discussion before that increasing some buffer in the driver made the problem less. And enabling PREEMPTION would help also. But since the last discussion I got my onboard audio (ESS) working, which is ok for me. I also wondered that the snd_emu10k1 is marked as MPSAFE, while other sound drivers aren't, but the others perform better. But I don't know if it has anything to do with it. Search the archives for more discussion about this. Ronald. -- Ronald Klop, Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible Problem w/4.10-stable And SMBFS?
On Tue, 18 Jan 2005 17:16:57 -0600, Tim Daneliuk [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am seeing a number of intermittent problems with SMBFS-mounted partitions and am wondering if these are know FBSD problems or problems with the Win32 servers: 1) After running for a very long time (weeks), SMBFS-connected directories ~ become very slow/sluggish for read/write. A reboot of the FBSD machine ~ fixes this. Error log shows: ~Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid 15734 ~Jan 18 16:36:28 yzx /kernel: smb_iod_recvall: drop resp with mid 15736 ~This machine is running 4.11-PRERELEASE as of 12/14/2004 2) Again, after running for a long time (several weeks), attempts to ~ to long running I/O against an SBMFS-mounted partition, I get ~ a bus error and the following entries in /var/log/messages: ~Jan 18 16:45:49 xyz /kernel: smb_iod_recvall: drop resp with mid 34907 ~Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid 39329 ~Jan 18 16:46:06 xyz /kernel: smb_iod_recvall: drop resp with mid 42496 ~ This seems to be a problem primarily with very large files (100s of ~ megs to several gigs) - at least I've not seen this problem w/small ~ files. ~ This machine is running 4.10-STABLE as of 11/30/2004 Ideas would be appreciated... Do you have any statistics about memory consumption/swapping? top/vmstat/netstat -m What is the cpu usage? What is the number of open files in your system? -- Ronald Klop, Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Raid5 Init question
On Tuesday, 18 January 2005 at 8:33:03 -0600, Craig Boston wrote: On Tue, Jan 18, 2005 at 12:21:59PM +0100, David Elsing wrote: Quote from the manual of the 4th example of the chapter HOW TO SET UP VINUM: In addition, the volume specification includes the keyword setupstate, which ensures that all plexes are up after creation. Where does it tell you to do that? From the man page: setstate state [volume | plex | subdisk | drive] setstate sets the state of the specified objects to the specified state. This bypasses the usual consistency mechanism of vinum and should be used only for recovery purposes. It is possible to crash the system by incorrect use of this command. But a couple of weeks later I read the following in the manual: Note that you must use the init command with RAID-5 plexes: otherwise extreme data corruption will result if one subdisk fails. Yes, this particular gotcha bit me a while back and I lost quite a bit of data (my fault for not having good backups) due to it. IMO, I still consider it a documentation bug though. That particular bit is buried in a command reference section rather than being in bold in the HOW TO guide. Yes, it could be clearer. Put in a PR. I read this to my horror after I filled the volume with data. You'll probably noticed I didn't init my volume. The disks are in good condition. The volume is almost filled to the maximum capacity. So a backup is a bit difficult due to the size of it. Are there any other options? If one disks fails, do I still get corrupted data? Yes, if one disk fails for any reason, every third sector will be garbage and it's unlikely you'll be able to recover anything useful from it. I would highly recommend backing up whatever is critically important to you asap. If you like living dangerously and all the drives are in good health, the parity data can be (theoretically) repaired with the vinum rebuildparity command, but do so at your own risk... That did allow me to recover a couple of my partitions that hadn't been trashed yet. This should work. Make sure the volume is not be mounted when you do so. Also, if a good disk gets marked as down somehow before you can correct this, whatever you do, do NOT issue a vinum start command on it. In the current state of the array, that would be destructive and irreversible. No, that's the correct way to do it. That's what happened to me: ATA timeout caused one of the drives to temporarily detach, corrupt filesystems caused a panic. If this happens, you're better off using setstate to force it to up, as wrong as that would normally be. I can't recall seeing a problem report. Greg -- See complete headers for address and phone numbers. pgpwjAvca7PjY.pgp Description: PGP signature
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
I have been compiling ports using -O2 since I started using FreeBSD back in 2003 and only port that has had issues with this is lang/ezm3 in FreeBSD 5.2.1 it needed -O. Chris On Tue, 18 Jan 2005 08:46:24 +0100, Matthias Buelow [EMAIL PROTECTED] wrote: Mike Tancsa wrote: At 05:48 PM 17/01/2005, Kris Kennaway wrote: Like I said before, switching back to -O makes the system stable once again. I let it run continuous buildworlds without issue for 24hrs along with burnP6, and memtest running in the background. No problem. Then I'd leave it at that. The difference between gcc -O2 and -O is marginal at best. Think of it as -O being the large axe that chops off a huge slab, and -O2 being the large axe, followed by some scratching with a nail-file. Most of the time it isn't worth the effort. mkb. ___ 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]
User's cron job creates zombie process on 5.3
Hi,
As a regular user, I have a cron job; 'crontab -l' says:
-
SHELL=/bin/sh
MAILTO=
# run at bootup and then every 5 minutes
@reboot $HOME/bin/ssh_tunnel
*/5 * * * * $HOME/bin/ssh_tunnel
-
The ssh_tunnel is an sh-script, which checks whether a particular
ssh-tunnel still exists, and if not regenerates it, as follows:
#!/bin/sh
# ssh_tunnel script -
tunnel=-L 55110:localhost:110 pop3.univ.net
tunnel_up=`pgrep -f -- ${tunnel}`
[ ${tunnel_up} = ] /usr/bin/ssh -N -f ${tunnel}
It works beautifully, but why does this also generate one zombie process:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
rob 655 0.0 0.0 00 ?? ZSat02PM 0:00.01 defunct
The STARTED time, is when the PC rebooted last time.
When I remove the cronjob and reboot, the zombie process is not
created anymore. Any idea what's the problem here?
Thanks,
Rob.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum Raid5 Init question
On Wed, Jan 19, 2005 at 09:55:25AM +1030, Greg 'groggy' Lehey wrote: Yes, it could be clearer. Put in a PR. I'm more than willing to submit a patch if it will help, but will it do any good this late in the release cycle? Especially if there will be no 4.12 release. Also, if a good disk gets marked as down somehow before you can correct this, whatever you do, do NOT issue a vinum start command on it. In the current state of the array, that would be destructive and irreversible. No, that's the correct way to do it. Normally it would be, yes. However in this case (at least it was for me), all of the normal blocks are fine, but the parity blocks are random garbage since init was never run. If a drive goes into the down state for some reason but is physically fine, starting the subdisk will begin reconstructing the data from the bogus parity, wiping out any hope of recovering the good data. If a drive does get detached somehow, it's likely that the system won't stay up very long -- from its point of view at least one filesystem has suddenly become very corrupt. The setstate is dangerous and will probably result in a somewhat inconsistent filesystem, but it's still preferable to a total loss... I can't recall seeing a problem report. There wasn't one. I had encountered the problem on several machines in a short timespan (fortunately only one had anything important) so I asked you about in in private mail. I didn't think the problem was with FreeBSD or vinum itself -- it was more of a what am I doing wrong? question. After a couple rounds you determined that it was likely I hadn't run vinum init, and sure enough that's what it was. Sorry, I can't provide a time reference. At the time of the exchange my mail archive was down (that's what was on the doomed filesystem :). Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
On Tue, Jan 18, 2005 at 11:30:19PM +, Chris wrote: I have been compiling ports using -O2 since I started using FreeBSD back in 2003 and only port that has had issues with this is lang/ezm3 in FreeBSD 5.2.1 it needed -O. Do yourself a favour and use -O2 -fno-strict-alias instead, because some ports *are broken* with plain -O2. Kris pgphXnQMvTCbt.pgp Description: PGP signature
User's cron job creates zombie process on 5.3
Hi,
As a regular user, I have a cron job; 'crontab -l' says:
-
SHELL=/bin/sh
MAILTO=
# run at bootup and then every 5 minutes
@reboot $HOME/bin/ssh_tunnel
*/5 * * * * $HOME/bin/ssh_tunnel
-
The ssh_tunnel is an sh-script, which checks whether a particular
ssh-tunnel still exists, and if not regenerates it, as follows:
#!/bin/sh
# ssh_tunnel script -
tunnel=-L 55110:localhost:110 pop3.univ.net
tunnel_up=`pgrep -f -- ${tunnel}`
[ ${tunnel_up} = ] /usr/bin/ssh -N -f ${tunnel}
It works beautifully, but why does this also generate one zombie process:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
rob 655 0.0 0.0 00 ?? ZSat02PM 0:00.01 defunct
The STARTED time, is when the PC rebooted last time.
When I remove the cronjob and reboot, the zombie process is not
created anymore. Any idea what's the problem here?
Thanks,
Rob.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3-STABLE kernel panic at boot-time
Hi there! I have gladly installed FreeBSD5 on my laptop to be free from M$ !! :D And soon I will install it on my worksation aswell. Here is (In my eyes) an unusual bootup error. When I start my laptop everything is fine untill I have to choose how I want to boot FreeBSD. As a first try I choosed the default option just to see everything is working with the new kernel. It didn't.. I then tryed to boot with ACPI (choise nr 2 at the bootmenu), and everything started upp nicely. I normally only want to run with ACPI enabled, so it's not a large problem for me.. but maby for someone else? I have two questions.. 1: Is there something wrong with my kernelconfig or is it a bug? 2: How do I change the default boot procedure from menu nr 1 (w/o ACPI) to menu nr 2 (w/ ACPI)? I left some useful information at the bottom of this message. And here are a webpage that shows some information about my harware: http://support.packardbell.com/se/mypc/index.php?sernr=105601500123# Thanks! Anders --- START OF Boot without ACPI (default) --- Jan 19 03:05:38 laptop syslogd: kernel boot file is /boot/kernel/kernel Jan 19 03:05:38 laptop kernel: Copyright (c) 1992-2005 The FreeBSD Project. Jan 19 03:05:38 laptop kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 19 03:05:38 laptop kernel: The Regents of the University of California. All rights reserved. Jan 19 03:05:38 laptop kernel: FreeBSD 5.3-STABLE #0: Sat Jan 15 21:23:58 CET 2005 Jan 19 03:05:38 laptop kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HAGGE Jan 19 03:05:38 laptop kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Jan 19 03:05:38 laptop kernel: CPU: mobile AMD Athlon(tm) XP 1600+ Processor (1400.06-MHz 686-class CPU) Jan 19 03:05:38 laptop kernel: Origin = AuthenticAMD Id = 0x680 Stepping = 0 Jan 19 03:05:38 laptop kernel: Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE Jan 19 03:05:38 laptop kernel: AMD Features=0xc048MP,AMIE,DSP,3DNow! Jan 19 03:05:38 laptop kernel: real memory = 234815488 (223 MB) Jan 19 03:05:38 laptop kernel: avail memory = 224317440 (213 MB) Jan 19 03:05:38 laptop kernel: npx0: [FAST] Jan 19 03:05:38 laptop kernel: npx0: math processor on motherboard Jan 19 03:05:38 laptop kernel: npx0: INT 16 interface Jan 19 03:05:38 laptop kernel: pcib0: Host to PCI bridge pcibus 0 on motherboard Jan 19 03:05:38 laptop kernel: pir0: PCI Interrupt Routing Table: 5 Entries on motherboard Jan 19 03:05:38 laptop kernel: $PIR: BIOS IRQ 5 for 0.17.INTC is not valid for link 0x3 Jan 19 03:05:38 laptop kernel: $PIR: BIOS IRQ 11 for 0.11.INTA is not valid for link 0x3 Jan 19 03:05:38 laptop kernel: $PIR: BIOS IRQ 10 for 0.18.INTA is not valid for link 0x3 Jan 19 03:05:38 laptop kernel: pci0: PCI bus on pcib0 Jan 19 03:05:38 laptop kernel: agp0: VIA 82C8363 (Apollo KT133A) host to PCI bridge mem 0xa000-0xa3ff at device 0.0 on pci0 Jan 19 03:05:38 laptop kernel: pcib1: PCI-PCI bridge at device 1.0 on pci0 Jan 19 03:05:38 laptop kernel: pci1: PCI bus on pcib1 Jan 19 03:05:38 laptop kernel: pci1: display, VGA at device 0.0 (no driver attached) Jan 19 03:05:38 laptop kernel: cbb0: TI1410 PCI-CardBus Bridge at device 8.0 on pci0 Jan 19 03:05:38 laptop kernel: cardbus0: CardBus bus on cbb0 Jan 19 03:05:38 laptop kernel: pccard0: 16-bit PCCard bus on cbb0 Jan 19 03:05:38 laptop kernel: Jan 19 03:05:38 laptop kernel: Jan 19 03:05:38 laptop kernel: Fatal trap 12: page fault while in kernel mode Jan 19 03:05:38 laptop kernel: fault virtual address= 0xe7fe6 Jan 19 03:05:38 laptop kernel: fault code = supervisor read, page not present Jan 19 03:05:38 laptop kernel: instruction pointer = 0x8:0xc00e9eb5 Jan 19 03:05:38 laptop kernel: stack pointer= 0x10:0xc082193c Jan 19 03:05:38 laptop kernel: frame pointer= 0x10:0xc082193c Jan 19 03:05:38 laptop kernel: code segment = base 0x0, limit 0xf, type 0x1b Jan 19 03:05:38 laptop kernel: = DPL 0, pres 1, def32 1, gran 1 Jan 19 03:05:38 laptop kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jan 19 03:05:38 laptop kernel: current process = 0 (swapper) Jan 19 03:05:38 laptop kernel: trap number = 12 Jan 19 03:05:38 laptop kernel: panic: page fault Jan 19 03:05:38 laptop kernel: Uptime: 1s Jan 19 03:05:38 laptop kernel: Automatic reboot in 15 seconds - press a key on the console to abort Jan 19 03:05:38 laptop kernel: Rebooting... --- END OF Boot without ACPI (default) --- --- START OF Boot with ACPI (Choise nr 2) --- Jan 19 03:05:38 laptop kernel: Copyright (c) 1992-2005 The FreeBSD Project. Jan 19 03:05:38 laptop kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 19 03:05:38 laptop kernel: The Regents of the University of California. All rights reserved. Jan 19 03:05:38 laptop kernel: FreeBSD 5.3-STABLE #0: Sat Jan 15 21:23:58 CET 2005 Jan 19 03:05:38 laptop kernel:
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
On Tuesday 18 January 2005 01:46 am, Matthias Buelow wrote: Then I'd leave it at that. The difference between gcc -O2 and -O is marginal at best. Sometimes. I recently switched to -O2 -fno-strict-alias on my small Alpha machine and got an increase of well over 100% in the OpenSSL benchmarks. -- Kirk Strauser pgpZr2iHTkB9h.pgp Description: PGP signature
Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit
straight boot, no patches or extra debug. -mjm 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-STABLE #14: Thu Jan 13 23:55:20 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/web7 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xf51 Stepping = 1 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 6442450944 (6144 MB) avail memory = 5963796480 (5687 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard acpi0: PTLTDXSDT on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 6.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD 8111 UDMA133 controller port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: serial bus, SMBus at device 7.2 (no driver attached) pci0: bridge, PCI-unknown at device 7.3 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd00-0xfd00 irq 27 at device 3.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 bge1: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd01-0xfd01 irq 27 at device 4.0 on pci2 miibus1: MII bus on bge1 brgphy1: BCM5703 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 atapci1: Promise PDC20319 SATA150 controller port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd02-0xfd03,0xfd04-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 pci0: base peripheral, interrupt controller at device 10.1 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0 pci3: ACPI PCI bus on pcib3 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: 3ware 9000 series Storage Controller port 0x4000-0x40ff mem 0xfd80-0xfdff,0xfd10-0xfd1000ff irq 30 at device 2.0 on pci3 twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 twa0: [GIANT-LOCKED] pci0: base peripheral, interrupt controller at device 11.1 (no driver attached) atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: floppy drive controller port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ppc0: ECP parallel printer port port 0x778-0x77f,0x378-0x37f irq 7 drq 4 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: ISA Option ROMs at iomem 0xcb000-0xcc7ff,0xc9800-0xcafff,0xc8000-0xc97ff,0xc-0xc7fff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled acd0: DVDROM IDE DVD-ROM
Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit
boot with twa_r5.diff patch and options TWA_DEBUG=10 -mjm Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #15: Tue Jan 18 23:58:45 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/web7 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xf51 Stepping = 1 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard acpi0: PTLTDXSDT on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 twa_probe: entered pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0 pci1: ACPI PCI bus on pcib1 twa_probe: entered pci1: display, VGA at device 6.0 (no driver attached) twa_probe: entered isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 twa_probe: entered atapci0: AMD 8111 UDMA133 controller port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: serial bus, SMBus at device 7.2 (no driver attached) twa_probe: entered pci0: bridge, PCI-unknown at device 7.3 (no driver attached) twa_probe: entered pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0 pci2: ACPI PCI bus on pcib2 twa_probe: entered bge0: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd00-0xfd00 irq 27 at device 3.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd01-0xfd01 irq 27 at device 4.0 on pci2 miibus1: MII bus on bge1 brgphy1: BCM5703 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: Promise PDC20319 SATA150 controller port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd02-0xfd03,0xfd04-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: base peripheral, interrupt controller at device 10.1 (no driver attached) twa_probe: entered pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0 pci3: ACPI PCI bus on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: 3ware 9000 series Storage Controller port 0x4000-0x40ff mem 0xfd80-0xfdff,0xfd10-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0:
Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit
using twa_patch1.diff: needed to add int error to twa_alloc_req_pkts -mjm Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #16: Wed Jan 19 00:29:26 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/web7 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xf51 Stepping = 1 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard acpi0: PTLTDXSDT on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 twa_probe: entered pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0 pci1: ACPI PCI bus on pcib1 twa_probe: entered pci1: display, VGA at device 6.0 (no driver attached) twa_probe: entered isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 twa_probe: entered atapci0: AMD 8111 UDMA133 controller port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: serial bus, SMBus at device 7.2 (no driver attached) twa_probe: entered pci0: bridge, PCI-unknown at device 7.3 (no driver attached) twa_probe: entered pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0 pci2: ACPI PCI bus on pcib2 twa_probe: entered bge0: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd00-0xfd00 irq 27 at device 3.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd01-0xfd01 irq 27 at device 4.0 on pci2 miibus1: MII bus on bge1 brgphy1: BCM5703 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: Promise PDC20319 SATA150 controller port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd02-0xfd03,0xfd04-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: base peripheral, interrupt controller at device 10.1 (no driver attached) twa_probe: entered pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0 pci3: ACPI PCI bus on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: 3ware 9000 series Storage Controller port 0x4000-0x40ff mem 0xfd80-0xfdff,0xfd10-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 17f2da000, len = 4 twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0:
Trials and tribulations on mirroring....
Hi folks; I've been running 4.x quite happily for some time, and am trying to set up a box with 5.3 that hopefully will end up being a viable platform to move over to. Tried on both 5.3-RELEASE and 5.3-STABLE (built this evening) Having some problems here... First, I discovered that vinum isn't quite right with 5.3. Ok, so I moved to gvinum, but ran into some really bizarre behavior there too, where it was detaching subdisks apparently at random and on a rebuild would occasionally crash with some really wild results. It also doesn't load-balance reads (barf). All this was discovered after I spent an afternoon getting it set up properly with the shadow root and all. Bummer The instability is a real deal-breaker - this is supposed to (eventually) be a production server, so it can't be squirrelly. So, my next attempt (with a new, fresh load) was to give gmirror a shot instead, since I only need Raid 1, and this looks like a better option from that perspective given gvinum's squirrely and not-all-there status at the moment. We.. the manual page (and the archives on the list here) implies that I can do the following: 1. Set up the system on one of the two mirror disks. 2. In single user mode, use gmirror label -v -b round-robin disk ad4 to set up the pre-existing disk (with data on it), which I booted from, as the primary. 3. Then use gmirror insert disk ad6 to add the secondary (mirrored) disk, which will automatically sync it and bring them into a consistent state. Only one small problem - the first command (in #2) fails, with: Can't store metadata on ad4: Operation not permitted This is true if the system is mounted read-only (in single user mode) or read-write (in multiuser, with all filesystems mounted) Attempting to label the SECOND (bare) disk works, but of course that's backwards and an insert would immediately destroy the running system (I assume it would also fail with the same permission error, but I've not tried it) - so that's not an option. I also tried it from the fixit disk, but the KLD cannot be loaded from the fixit disk, and none of the commands work - so that appears to not be an option either. How do you get this thing set up? The archives here (and man pages) strongly imply that this works for a root filesystem and boot drive - what am I missing? Need a Raid 1 solution that works to move over to the 5.x world out here... -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twa breakage on AMD64 with 9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit
twa_patch2.diff, had to add the int error; in twa_alloc_req_pkts -mjm Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #17: Wed Jan 19 00:44:33 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/web7 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 240 (1403.19-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xf51 Stepping = 1 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 6442450944 (6144 MB) avail memory = 5963784192 (5687 MB) ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard acpi0: PTLTDXSDT on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 twa_probe: entered pcib1: ACPI PCI-PCI bridge at device 6.0 on pci0 pci1: ACPI PCI bus on pcib1 twa_probe: entered pci1: display, VGA at device 6.0 (no driver attached) twa_probe: entered isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 twa_probe: entered atapci0: AMD 8111 UDMA133 controller port 0x1020-0x102f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 twa_probe: entered pci0: serial bus, SMBus at device 7.2 (no driver attached) twa_probe: entered pci0: bridge, PCI-unknown at device 7.3 (no driver attached) twa_probe: entered pcib2: ACPI PCI-PCI bridge at device 10.0 on pci0 pci2: ACPI PCI bus on pcib2 twa_probe: entered bge0: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd00-0xfd00 irq 27 at device 3.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:50:45:5b:8e:76 twa_probe: entered bge1: Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfd01-0xfd01 irq 27 at device 4.0 on pci2 miibus1: MII bus on bge1 brgphy1: BCM5703 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:50:45:5b:8e:77 twa_probe: entered atapci1: Promise PDC20319 SATA150 controller port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xfd02-0xfd03,0xfd04-0xfd040fff irq 25 at device 5.0 on pci2 atapci1: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 ata4: channel #2 on atapci1 ata5: channel #3 on atapci1 twa_probe: entered pci0: base peripheral, interrupt controller at device 10.1 (no driver attached) twa_probe: entered pcib3: ACPI PCI-PCI bridge at device 11.0 on pci0 pci3: ACPI PCI bus on pcib3 twa_probe: entered 3ware device driver for 9000 series storage controllers, version: 2.50.02.011 twa0: 3ware 9000 series Storage Controller port 0x4000-0x40ff mem 0xfd80-0xfdff,0xfd10-0xfd1000ff irq 30 at device 2.0 on pci3 unknown: twa_attach: entered. twa0: [GIANT-LOCKED] twa0: twa_setup: entered. twa0: twa_setup_request_dmamap: entered. twa0: twa_setup_request_dmamap: error = 0, segs[0].addr = 17f2da000, len = 4 twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request: entered. twa0: twa_release_request:
Re: Trials and tribulations on mirroring....
On Tuesday 18 January 2005 09:46 pm, Karl Denninger wrote: Hi folks; I've been running 4.x quite happily for some time, and am trying to set up a box with 5.3 that hopefully will end up being a viable platform to move over to. Tried on both 5.3-RELEASE and 5.3-STABLE (built this evening) Having some problems here... First, I discovered that vinum isn't quite right with 5.3. Ok, so I moved to gvinum, but ran into some really bizarre behavior there too, where it was detaching subdisks apparently at random and on a rebuild would occasionally crash with some really wild results. It also doesn't load-balance reads (barf). All this was discovered after I spent an afternoon getting it set up properly with the shadow root and all. Bummer The instability is a real deal-breaker - this is supposed to (eventually) be a production server, so it can't be squirrelly. So, my next attempt (with a new, fresh load) was to give gmirror a shot instead, since I only need Raid 1, and this looks like a better option from that perspective given gvinum's squirrely and not-all-there status at the moment. We.. the manual page (and the archives on the list here) implies that I can do the following: 1. Set up the system on one of the two mirror disks. 2. In single user mode, use gmirror label -v -b round-robin disk ad4 to set up the pre-existing disk (with data on it), which I booted from, as the primary. 3. Then use gmirror insert disk ad6 to add the secondary (mirrored) disk, which will automatically sync it and bring them into a consistent state. Only one small problem - the first command (in #2) fails, with: Can't store metadata on ad4: Operation not permitted This is true if the system is mounted read-only (in single user mode) or read-write (in multiuser, with all filesystems mounted) Attempting to label the SECOND (bare) disk works, but of course that's backwards and an insert would immediately destroy the running system (I assume it would also fail with the same permission error, but I've not tried it) - so that's not an option. I also tried it from the fixit disk, but the KLD cannot be loaded from the fixit disk, and none of the commands work - so that appears to not be an option either. How do you get this thing set up? The archives here (and man pages) strongly imply that this works for a root filesystem and boot drive - what am I missing? Need a Raid 1 solution that works to move over to the 5.x world out here... I had a pentium 166 with four matched ide drives set up as Striped plexes that had better disk access than my current 1ghz system. I sure miss that! The only time FreeBSD let me down when they let stopped supporting vinum. Guess no OS is perfect sigh -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trials and tribulations on mirroring....
On 01/18/05 23:46, Karl Denninger wrote: snip backstory and gvinum stuff So, my next attempt (with a new, fresh load) was to give gmirror a shot instead, since I only need Raid 1, and this looks like a better option from that perspective given gvinum's squirrely and not-all-there status at the moment. We.. the manual page (and the archives on the list here) implies that I can do the following: 1. Set up the system on one of the two mirror disks. 2. In single user mode, use gmirror label -v -b round-robin disk ad4 to set up the pre-existing disk (with data on it), which I booted from, as the primary. 3. Then use gmirror insert disk ad6 to add the secondary (mirrored) disk, which will automatically sync it and bring them into a consistent state. Only one small problem - the first command (in #2) fails, with: Can't store metadata on ad4: Operation not permitted This is true if the system is mounted read-only (in single user mode) or read-write (in multiuser, with all filesystems mounted) Attempting to label the SECOND (bare) disk works, but of course that's backwards and an insert would immediately destroy the running system (I assume it would also fail with the same permission error, but I've not tried it) - so that's not an option. I also tried it from the fixit disk, but the KLD cannot be loaded from the fixit disk, and none of the commands work - so that appears to not be an option either. How do you get this thing set up? The archives here (and man pages) strongly imply that this works for a root filesystem and boot drive - what am I missing? Need a Raid 1 solution that works to move over to the 5.x world out here... If any filesystem is mounted then GEOM will not allow metadata updates for the drive. Here's a solution given over on the geom@ list: http://lists.freebsd.org/pipermail/freebsd-geom/2004-November/000379.html I converted to gmirror from ataraid, so I already had 2 disks with identical contents. I worked around this problem as outlined here (the instructions have errors that are corrected later in the thread): http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039907.html I wish we handled this in the installer, but as I can't produce the code to do it I'll shut up now... Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: Assertion besttd != NULL failed at ../../../kern/subr_sleepqueue.c:676
Got this while running a Java proxy server under libthr:
FreeBSD dan.emsphone.com 5.3-STABLE FreeBSD 5.3-STABLE #387: Thu Jan 13
14:43:03 CST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DANSMP i386
panic: Assertion besttd != NULL failed at ../../../kern/subr_sleepqueue.c:676
cpuid = 1
KDB: stack backtrace:
panic(c07822b6,c078843f,c078825f,2a4,) at panic+0x1cf
sleepq_signal(c3a9b4b0,0,,e7461ce0,c05a74eb) at sleepq_signal+0xf0
wakeup_one(c3a9b4b0,0,c07863e3,12e,be3173f0) at wakeup_one+0x20
thr_wake(c2bb84b0,e7461d14,4,16,1) at thr_wake+0xdb
syscall(3123002f,2f,4c98002f,811bfc0,83f4400) at syscall+0x137
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (443, FreeBSD ELF32, thr_wake), eip = 0x280e658f, esp = 0xbe3173ec,
ebp = 0xbe317418 ---
panic: mi_switch: switch in a critical section
cpuid = 1
The last two lines repeated forever until I reset the box, so no
coredump, but the stack is almost identical to a panic I got back in
November and did get a trace on (the crashdump is long gone though).
#0 doadump () at pcpu.h:159
#1 0xc059aa86 in boot (howto=260) at ../../../kern/kern_shutdown.c:397
#2 0xc059a55b in panic (fmt=0xc077e446 Assertion %s failed at %s:%d) at
../../../kern/kern_shutdown.c:553
#3 0xc05bcb5c in sleepq_remove_thread (sq=0xc3394dc0, td=0x0) at
../../../kern/subr_sleepqueue.c:594
#4 0xc05bd47d in sleepq_signal (wchan=0xc2c5d7d0, flags=0, pri=-1) at
../../../kern/subr_sleepqueue.c:675
#5 0xc05a1d80 in wakeup_one (ident=0x0) at ../../../kern/kern_synch.c:266
#6 0xc05a5dab in thr_wake (td=0xc38abaf0, uap=0x0) at
../../../kern/kern_thr.c:303
#7 0xc072a797 in syscall (frame={tf_fs = 819527727, tf_es = 1285816367, tf_ds
= -1078001617, tf_edi = 135378944, tf_esi = 137891840, tf_ebp = -1173986296,
tf_isp = -419791500, tf_ebx = 671700552, tf_edx = 138204160, tf_ecx = 0, tf_eax
= 443, tf_trapno = 22, tf_err = 2, tf_eip = 672032143, tf_cs = 31, tf_eflags =
582, tf_esp = -1173986340, tf_ss = 47}) at ../../../i386/i386/trap.c:1001
#8 0xc07168af in Xint0x80_syscall () at ../../../i386/i386/exception.s:201
--
Dan Nelson
[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: User's cron job creates zombie process on 5.3
On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote:
tunnel=-L 55110:localhost:110 pop3.univ.net
tunnel_up=`pgrep -f -- ${tunnel}`
[ ${tunnel_up} = ] /usr/bin/ssh -N -f ${tunnel}
It works beautifully, but why does this also generate one zombie process:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
rob 655 0.0 0.0 00 ?? ZSat02PM 0:00.01 defunct
You get a zombie when a process has exited and the parent hasn't issued
a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process
is and that might give you an idea as to what is going wrong.
--
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: User's cron job creates zombie process on 5.3
Peter Jeremy wrote:
On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote:
tunnel=-L 55110:localhost:110 pop3.univ.net
tunnel_up=`pgrep -f -- ${tunnel}`
[ ${tunnel_up} = ] /usr/bin/ssh -N -f ${tunnel}
It works beautifully, but why does this also generate one zombie process:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
rob 655 0.0 0.0 00 ?? ZSat02PM 0:00.01 defunct
You get a zombie when a process has exited and the parent hasn't issued
a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process
is and that might give you an idea as to what is going wrong.
Sorry, can you tell me how to do this?
How can I find out what's the parent process of a Zombie process?
I have a user crontab, which calls a sh-shell script; so I have no
clue where to start investigating
Thanks,
Rob.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trials and tribulations on mirroring....
Thanks that should do the trick (and explains why it fails) -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.comMusings Of A Sentient Mind On Wed, Jan 19, 2005 at 12:10:14AM -0600, Jon Noack wrote: On 01/18/05 23:46, Karl Denninger wrote: snip backstory and gvinum stuff So, my next attempt (with a new, fresh load) was to give gmirror a shot instead, since I only need Raid 1, and this looks like a better option from that perspective given gvinum's squirrely and not-all-there status at the moment. We.. the manual page (and the archives on the list here) implies that I can do the following: 1. Set up the system on one of the two mirror disks. 2. In single user mode, use gmirror label -v -b round-robin disk ad4 to set up the pre-existing disk (with data on it), which I booted from, as the primary. 3. Then use gmirror insert disk ad6 to add the secondary (mirrored) disk, which will automatically sync it and bring them into a consistent state. Only one small problem - the first command (in #2) fails, with: Can't store metadata on ad4: Operation not permitted This is true if the system is mounted read-only (in single user mode) or read-write (in multiuser, with all filesystems mounted) Attempting to label the SECOND (bare) disk works, but of course that's backwards and an insert would immediately destroy the running system (I assume it would also fail with the same permission error, but I've not tried it) - so that's not an option. I also tried it from the fixit disk, but the KLD cannot be loaded from the fixit disk, and none of the commands work - so that appears to not be an option either. How do you get this thing set up? The archives here (and man pages) strongly imply that this works for a root filesystem and boot drive - what am I missing? Need a Raid 1 solution that works to move over to the 5.x world out here... If any filesystem is mounted then GEOM will not allow metadata updates for the drive. Here's a solution given over on the geom@ list: http://lists.freebsd.org/pipermail/freebsd-geom/2004-November/000379.html I converted to gmirror from ataraid, so I already had 2 disks with identical contents. I worked around this problem as outlined here (the instructions have errors that are corrected later in the thread): http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039907.html I wish we handled this in the installer, but as I can't produce the code to do it I'll shut up now... Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] %SPAMBLOCK-SYS: Matched [freebsd], message ok ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: User's cron job creates zombie process on 5.3
Peter Jeremy writes:
On Wed, 2005-Jan-19 09:16:59 +0900, Rob Lahaye wrote:
tunnel=-L 55110:localhost:110 pop3.univ.net
tunnel_up=`pgrep -f -- ${tunnel}`
[ ${tunnel_up} = ] /usr/bin/ssh -N -f ${tunnel}
It works beautifully, but why does this also generate one zombie process:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
rob 655 0.0 0.0 00 ?? ZSat02PM 0:00.01 defunct
You get a zombie when a process has exited and the parent hasn't issued
a wait(2) (or SIG_IGN'd SIGCHLD). Have a look at what the parent process
is and that might give you an idea as to what is going wrong.
Ancient Perl did not collect for children started via the
backtick operator - is this a possible issue for /bin/sh as well? It
should be harmless to call wait just after the use of the backtick
operator above; does that change anything? I.e:
tunnel_up=`pgrep -f -- ${tunnel}`; wait
To see the parent pid, add -O ppid to the arguments to ps;
e.g,
ps axww -O ppid
--
Raymond WikerMail: [EMAIL PROTECTED]
Senior Software Engineer Web: http://www.fast.no/
Fast Search Transfer ASA Phone: +47 23 01 11 60
P.O. Box 1677 Vika Fax: +47 35 54 87 99
NO-0120 Oslo, NORWAY Mob: +47 48 01 11 60
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
