Re: amd64/71644: amd64 5.3-BETA4 crash when heavy load
Hi, Robert, Would you please take a look at kern/71644? Since the submitter have 24G of RAM so it might be difficult for him to obtain a crashdump, will the backtrace provided helpful to track down what is happening? On Thu, Dec 02, 2004 at 12:29:04PM +0800, Wei-Kai Wu wrote: Here is the panic messages: (If this is not what you want, could you tell me what I shall do? thanks!) Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x18 fault code= supervisor read, page not present instruction pointer = 0x8:0x8026ece0 stack pointer = 0x10:0xd2d6f8b0 frame pointer = 0x10:0xd2d6f920 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 46 (swi1: net) [thread 100025] Stopped at m_copym+0x40:incl %ebp db trace m_copym() at m_copym+0x40 tcp_output() at tcp_output+0xdf1 tcp_input() at tcp_input+0x1d2b netisr_processqueue() at netisr_processqueue+0xd2 swi_net() at swi_net+0x13c ithread_loop() at ithread_loop+0x1b8 fork_exit() at fork_exit+0xaa fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffd2d6fd00, rbp = 0 --- Cheers, -- Xin LI delphij frontfree net http://www.delphij.net/ See complete headers for GPG key and other information. pgpDSZgoLliVR.pgp Description: PGP signature
Re: Making a data DVD with 4.10 and dvd+rw-format
Scott Sewall wrote: I'm running FreeBSD 4.10 and trying to make a data DVD. I've following the procedure outlined in the handbook without any success. Any hints or advise would be grealty appreciated. -- Scott lilo# growisofs -dvd-compat -Z /dev/cd0 -J -R blitz10 :-( unable to open(/dev/cd0,O_RDONLY): No such file or directory lilo# growisofs -dvd-compat -Z /dev/cd0a -J -R blitz10 :-( unable to open(/dev/cd0a,O_RDONLY): Device not configured lilo# growisofs -dvd-compat -Z /dev/cd0c -J -R blitz10 :-( unable to open(/dev/cd0c,O_RDONLY): Device not configured lilo# growisofs -dvd-compat -Z /dev/rcd0a -J -R blitz10 :-( unable to open(/dev/rcd0a,O_RDONLY): Device not configured lilo# lilo# uname -a FreeBSD lilo.redlinenetworks.com 4.10-RELEASE-p3 FreeBSD 4.10-RELEASE-p3 #1: Thu Nov 11 20:54:12 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/LILO i386 lilo# lilo# dmesg -a | grep ^cd cd0 at ata1 bus 0 target 0 lun 0 cd0: SONY DVD RW DW-U18A UYS1 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present lilo# lilo# sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 lilo# ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Did you recompilled your kernel? check the atapicam device on [url] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html [/url] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10 - 5.3 migration; what happens to vinum volumes?
On Wed, 1 Dec 2004 22:42:23 +, Ceri Davies [EMAIL PROTECTED] wrote: On Wed, Dec 01, 2004 at 11:38:38PM +0100, Lukas Ertl wrote: Your config looks sane enough that it shouldn't be a problem to switch to gvinum. Edit your fstab and put geom_vinum_load=YES into /boot/loader.conf, that's enough. Cool. I'll be taking backups anyway so I'll try it that way; do you want a bug report if it doesn't work? Yes, please. cheers, le ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Unkillable zombie sshd-s?
I found out today that I have two zombie sshd processes on a busy server (dozen or so users over ssh, many other services), and I can't kill them. sshd38653 0.0 0.0 00 ?? ZMon08AM 0:00.03 defunct sshd75851 0.0 0.0 00 ?? Z 7:33PM 0:00.08 defunct kill -9 doesn't complain, but doesn't do the job either. Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.x can't read 5.x dump?
At 2004-12-02 02:40:53+, Ken Smith writes: On Thu, Dec 02, 2004 at 10:48:43AM +1000, Joel Hatton wrote: I'm backing up a 5.x machine at the moment with this command: dump -0Lau -b128 -f - /var | gzip -2 | ssh FreeBSD4 dd of=aacd0s1f.gz After the dump finishes, I try to read the file on the 4.x destination: # gzip -dc aacd0s1a.gz | restore -ivf - Verify tape and initialize maps Tape is not a dump tape I can scp the file back to the 5.x machine and it loads just fine, so what gives? This type of failure is somewhat scary for me right now, given that I may have to restore files to another destination that may not be 5.x based. This is, unfortunately, something that you should not expect to work for any *nix variant. There's no theoretical reason why the formats used by dump and restore shouldn't be forward and backward compatible, allowing an older restore (to an older filesystem type) to pick out the parts of the dump which make sense to it while ignoring parts which it doesn't understand. But they aren't, so it can't, so you're out of luck. [In theory, the filesystem could package itself, so an old restore binary running on a newer filesystem and given a newer dump would DTRT]. Bikeshed, bikeshed. Nick B ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable zombie sshd-s?
I found out today that I have two zombie sshd processes on a busy server (dozen or so users over ssh, many other services), and I can't kill them. sshd38653 0.0 0.0 00 ?? ZMon08AM 0:00.03 defunct sshd75851 0.0 0.0 00 ?? Z 7:33PM 0:00.08 defunct kill -9 doesn't complain, but doesn't do the job either. Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) You can't kill them because they are already dead. They are just holding state so that the parent process can know how they died. Once the parent process wait()'s on them (or the parent dies) they will disappear. This is a FAQ that is over 20 years old. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Making a data DVD with 4.10 and dvd+rw-format
I had the same exact problem a few weeks ago. Did you make sure the pass through devices are configured? Check to see what pass device is needed by issuing the folowing command (as root of course): camcontrol devlist For example, mine was on pass4. I had to run: /dev/ sh MAKEDEV pass5 (I had pass1, pass2, and pass3 already. Note the indexing. sh MAKEDEV passN will create the device passN-1. Learned that the hard way). Also, do a search on the web. There are several people who have had had similar experiences and share their success stories. Lastly, did you modify your kernel to accomodate ATAPICAM (and the other required changes)? My Sony (710A) is working great now. Best of luck, Donald - Original Message - From: Scott Sewall [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 01, 2004 9:50 PM Subject: Making a data DVD with 4.10 and dvd+rw-format I'm running FreeBSD 4.10 and trying to make a data DVD. I've following the procedure outlined in the handbook without any success. Any hints or advise would be grealty appreciated. -- Scott lilo# growisofs -dvd-compat -Z /dev/cd0 -J -R blitz10 :-( unable to open(/dev/cd0,O_RDONLY): No such file or directory lilo# growisofs -dvd-compat -Z /dev/cd0a -J -R blitz10 :-( unable to open(/dev/cd0a,O_RDONLY): Device not configured lilo# growisofs -dvd-compat -Z /dev/cd0c -J -R blitz10 :-( unable to open(/dev/cd0c,O_RDONLY): Device not configured lilo# growisofs -dvd-compat -Z /dev/rcd0a -J -R blitz10 :-( unable to open(/dev/rcd0a,O_RDONLY): Device not configured lilo# lilo# uname -a FreeBSD lilo.redlinenetworks.com 4.10-RELEASE-p3 FreeBSD 4.10-RELEASE-p3 #1: Thu Nov 11 20:54:12 PST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/LILO i386 lilo# lilo# dmesg -a | grep ^cd cd0 at ata1 bus 0 target 0 lun 0 cd0: SONY DVD RW DW-U18A UYS1 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present lilo# lilo# sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 lilo# ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 4.x can't read 5.x dump?
There's no theoretical reason why the formats used by dump and restore shouldn't be forward and backward compatible, allowing an older restore (to an older filesystem type) to pick out the parts of the dump which make sense to it while ignoring parts which it doesn't understand. But they aren't, so it can't, so you're out of luck. This is a pretty interesting issue that I didn't realize. I've regularly restored dumps from a Solaris 8 machine to my FreeBSD 4.x machines. (We had data volumes on some old Solaris machines that I replaced with FreeBSD.) I guess FreeBSD and Solaris volumes are similar enough that the restore just worked. Jaime Bozza ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable zombie sshd-s?
Mark Andrews wrote: Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) You can't kill them because they are already dead. They are just holding state so that the parent process can know how they died. Once the parent process wait()'s on them (or the parent dies) they will disappear. I knew that (except the bit that they're ukillable by design :) ), but I was hoping it's a known ssh problem - this is the first time I saw sshd processes as zombies (and it seems they've been zombies for a long time, so parents are probably in error). Can I find out what their parent processes are? (something like tree-shaped ps?) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable zombie sshd-s?
On Thu, 02 Dec 2004 15:06:21 +0100, Ivan Voras [EMAIL PROTECTED] wrote: Can I find out what their parent processes are? (something like tree-shaped ps?) /usr/ports/sysutils/pstree and ps can display the ppid (parent pid). -- Ronald Klop, Amsterdam, The Netherlands ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable zombie sshd-s?
On Thu, 2 Dec 2004, Ivan Voras wrote: Mark Andrews wrote: Is there a way to find out what has happened and why does the situation occur? (I can't reboot the server for testing) You can't kill them because they are already dead. They are just holding state so that the parent process can know how they died. Once the parent process wait()'s on them (or the parent dies) they will disappear. I knew that (except the bit that they're ukillable by design :) ), but I was hoping it's a known ssh problem - this is the first time I saw sshd processes as zombies (and it seems they've been zombies for a long time, so parents are probably in error). Can I find out what their parent processes are? (something like tree-shaped ps?) No tree, but try ps -axl. PPID = parent process ID -- Lars Eighner [EMAIL PROTECTED] -finger for geek code- http://www.io.com/~eighner/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[TEST] netgraph callout interface
Dear collegues, we are working on making netgraph ISR mpsafe. To do it we need to fix all (ab)users of bare timeout(9) in src/sys/netgraph. These timeout calls are running in synch with netgraph now because timeout(9) is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), which runs scheduled callouts in netgraph context: http://people.freebsd.org/~glebius/totest/netgraph_callout It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches the following nodes: ng_bridge.c ng_l2tp.c ng_lmi.c ng_ppp.c ng_pppoe.c ng_tty.c If you are using at least one of them, then I'm asking you to test the patch and respond. Thanks in advance! P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with loader
Hi, this is RELENG_5 as of today, but I notice this several days before. Right now, I can't load modules from loader via module_load=YES on /boot/loader.conf Only kernel and acpi module loaded. Notice this with snd_via8233_load=YES This is a known issue? thanks in advance, -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unkillable zombie sshd-s?
Ronald Klop wrote: On Thu, 02 Dec 2004 15:06:21 +0100, Ivan Voras [EMAIL PROTECTED] wrote: Can I find out what their parent processes are? (something like tree-shaped ps?) /usr/ports/sysutils/pstree and ps can display the ppid (parent pid). Thanks, parents were stuck and had to be killed. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: More geom classes?
Terje Elde wrote: ggate would be one option, but it'd be much nicer to have it as a 'real' geom module. It would, but I don't know enough to make a kernel module. A password will still be required, for generating the random sequence... *cringe* The only point of using such a XOR is to end up with an effective OTP (One Time Pad). If you use a password as seed for a simple PRNG, then you're throwing away all the gain, and would be better off with GEOM BDE instead. FreeBSD 5 has a seemingly very good yarrow-based entropy source. Why not use that? I think I misunderstood something. Do you propose this (for 2 disks): for each block to be written: a) generate a block of random data b) write random data to first disk c) write random data xor user data to second disk So, as long as any person has both disks, the data can be recovered. Where's the security in that? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Java/Tomcat
Hi, I need to serve .jsp's with jakarta. Read somewhere that compiling the jdk and getting it to work with jakarta isn't the eaysiest thing to do. Is Linux prefered for this task, or will i do better with FreeBSD? Thanks. -- alex bustamante - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Java/Tomcat
alex bustamante wrote: Hi, I need to serve .jsp's with jakarta. Read somewhere that compiling the jdk and getting it to work with jakarta isn't the eaysiest thing to do. Is Linux prefered for this task, or will i do better with FreeBSD? Thanks. We regularly compile Jakarta/Tomcat from ports without any issues. -- Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Java/Tomcat
Matt Rudderham wrote: alex bustamante wrote: Hi, I need to serve .jsp's with jakarta. Read somewhere that compiling the jdk and getting it to work with jakarta isn't the eaysiest thing to do. Is Linux prefered for this task, or will i do better with FreeBSD? Thanks. We regularly compile Jakarta/Tomcat from ports without any issues. I think the difficulty comes primarily from compiling Java. You need to manually fetch a couple of pieces and go through the Sun registration dance. But after that, it's pretty smooth. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Java/Tomcat
alex bustamante wrote: Hi, I need to serve .jsp's with jakarta. Read somewhere that compiling the jdk and getting it to work with jakarta isn't the eaysiest thing to do. Is Linux prefered for this task, or will i do better with FreeBSD? Thanks. We regularly compile Jakarta/Tomcat from ports without any issues. -- Matt Both Linux and FreeBSD are quite able to run Jakarta. Besides the need to make linux java prior to making native FreeBSD java, there is little difference between running Jakarta in FreeBSD than running it in Linux. You can consult with documents such as: http://ezine.daemonnews.org/200203/tomcat-jakarta.html for pointers on installing Jakarta in FreeBSD. Jeff Love Burgh Gaming ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Java/Tomcat
alex bustamante wrote: Hi, I need to serve .jsp's with jakarta. Read somewhere that compiling the jdk and getting it to work with jakarta isn't the eaysiest thing to do. Is Linux prefered for this task, or will i do better with FreeBSD? Thanks. We regularly compile Jakarta/Tomcat from ports without any issues. -- Matt What about performance/stability? (compared to linux) -- alex bustamante - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with loader
Hi, Jose! In /boot/defaults/loader.conf : module_path=/boot/modules You can override it with: module_path=/boot/kernel 02 2004 18:47 Jose M Rodriguez (a): Hi, this is RELENG_5 as of today, but I notice this several days before. Right now, I can't load modules from loader via module_load=YES on /boot/loader.conf Only kernel and acpi module loaded. Notice this with snd_via8233_load=YES This is a known issue? thanks in advance, -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Konstantin Volevatch [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with loader
El Jueves, 2 de Diciembre de 2004 19:06, Konstantin Volevatch escribi: Hi, Jose! In /boot/defaults/loader.conf : module_path=/boot/modules You can override it with: module_path=/boot/kernel tried. doesn' work. Anyone else see this? 02 2004 18:47 Jose M Rodriguez (a): Hi, this is RELENG_5 as of today, but I notice this several days before. Right now, I can't load modules from loader via module_load=YES on /boot/loader.conf Only kernel and acpi module loaded. Notice this with snd_via8233_load=YES This is a known issue? thanks in advance, -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Timecounter problems on 5.3 - things take twice as long
Hi, I have a weird problem on a dual Xeon 550MHz system running 5.3-RELEASE. Everything takes twice as long as it should. Example: winston% time sleep 2 sleep 2 0.00s user 0.00s system 0% cpu 4.006 total The same for pings, the scsi delay when booting, etc. The time of the system itself doesn't seem to be affected (but maybe ntpd takes care of that). I tried changing the kern.timecounter.hardware sysctl from ACPI-safe to TSC and i8254, but that didn't help. Any other suggestions on how to fix this? Do I have to provide more information? Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with loader
From: Jose M Rodriguez [EMAIL PROTECTED] Date: Thu, 2 Dec 2004 19:30:50 +0100 Sender: [EMAIL PROTECTED] El Jueves, 2 de Diciembre de 2004 19:06, Konstantin Volevatch escribió: Hi, Jose! In /boot/defaults/loader.conf : module_path=/boot/modules You can override it with: module_path=/boot/kernel tried. doesn' work. Anyone else see this? Still sounds like a broken module path to me. But the correct fix is in UPDATING. See the entry for 20040806. -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Java/Tomcat
* alex bustamante [EMAIL PROTECTED] [1206 18:06]: alex bustamante wrote: Hi, I need to serve .jsp's with jakarta. Read somewhere that compiling the jdk and getting it to work with jakarta isn't the eaysiest thing to do. Is Linux prefered for this task, or will i do better with FreeBSD? Thanks. We regularly compile Jakarta/Tomcat from ports without any issues. -- Matt What about performance/stability? (compared to linux) yes, we have those. -- The pie is ready. You guys like swarms of things, right? - Bender Rasputin :: Jack of All Trades - Master of Nuns ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.x can't read 5.x dump?
On Thursday 02 December 2004 05:55, Nick Barnes wrote: There's no theoretical reason why the formats used by dump and restore shouldn't be forward and backward compatible, allowing an older restore (to an older filesystem type) to pick out the parts of the dump which make sense to it while ignoring parts which it doesn't understand. There may be security reasons, though. If you've locked down a filesystem through the extensive use of ACLs, then you wouldn't want to dump/restore it to another system that doesn't support those ACLs and expect your security framework to still be intact - at least not without *lots* of warnings. -- Kirk Strauser pgpPgmSMhN3Us.pgp Description: PGP signature
Re: make -j$n buildworld : use of -j investigated
At 2:08 PM +0900 11/23/04, Rob wrote: Hi, I have tested following with FreeBSD 5.3-Stable. On several different PCs I have used make -j$n buildworld with $n ranging from 1 to 9. Although people suggest -j4 as optimal in general case, I have come to a very different conclusion... So, I finally got around to doing some timings on my newest PC. It is a AMD Athlon(tm) XP 3000+ (2166.43-MHz 686-class CPU) with 1-gig of memory, and fast SATA disks. It was certainly different that what I saw on my previous single-CPU systems. Roughly: Real User Sys Max-LA 2670.86 2071.66 543.49 1.25 buildworld 2751.60 2085.95 603.69 1.35 -j1 buildworld 2825.87 2137.19 637.15 5.58 -j2 buildworld 2887.03 2158.60 648.37 11.85 -j3 buildworld 2856.75 2156.48 647.43 19.06 -j4 buildworld 2851.71 2154.39 647.19 25.43 -j5 buildworld 2850.92 2155.40 646.19 31.59 -j6 buildworld 2850.07 2153.77 648.41 36.19 -j7 buildworld 2852.64 2155.74 647.82 47.00 -j8 buildworld 2851.66 2153.43 650.23 53.51 -j9 buildworld (I've actually done multiple runs of each, but they all show about the same numbers). I had a separate session doing 'uptime's every 30 seconds, and the Max-LA column is the maximum load-average that was seen by that separate session. Apparently the faster disks made a much bigger difference than I had expected to see. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Loader Too Fragile
First, thanks for your reply. My complaint about fragility was actually directed at the Loader's inability to usefully indicate what it was unable to deal with. I realize that there is precious little code space for elaborate error messages, but it's inability to keep the console directed at the serial port, thus preventing capture of the error messages that were generated, seemed worthy of attention. Yes, at first glance it appears your BIOS is completely braindead. Yet no so braindead that FreeBSD 4.10 fails to find it serviceable. + BIOS 509kB/130048kB available memory Those memory numbers don't make sense. How much physical RAM is in the system? They're exactly the same numbers reported for memory when booting FreeBSD 4.10. There is one stick of 128MB memory on the system. Dunno. Either the BIOS in that machine is completely whacked out or you have more serious hardware problems. Based on the age of the machine and the fact that DEC is dead I'd probably give up on this. Pretty much any other 440LX based mother board would be around the same age. There is no indication that the 440LX chipset has been deliberately desupported. The fact that DEC was acquired, twofold, also seems irrelevant as HP has the same level of support, i.e., old BIOS files and manuals available on their web site, that can be found for 440LX based motherboards whose manufacturer has managed keep the same name. The machine is quite functional with respect to FreeBSD 4.10 and ran March 25th 5-Current fine as well. I was unfortunately over optimistic and wrote over that installation but hope to recover to that state. I guess I'll have to embark on a binary search to find what lines of code raised the BIOS requirements for FreeBSD 5. Here is the serial console capture for a FreeBSD 4.10 boot: Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 509kB/130048kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Tue May 25 21:22:31 GMT 2004) Loading /boot/defaults/loader.conf /kernel text=0x338df5 data=0x4b7a4+0x34a50 syms=[0x4+0x46970+0x4+0x4f611 ] Hit [Enter] to boot immediately, or any other key for command prompt. ^MBooting [kernel] in 9 seconds... ^MBooting [kernel] in 8 seconds... ^M Booting [kernel] in 7 seconds... ^MBooting [kernel] in 6 seconds... ^MBo oting [kernel] in 5 seconds... ^MBooting [kernel] in 4 seconds... ^MBoot ing [kernel] in 3 seconds... ^MBooting [kernel] in 2 seconds... ^MBootin g [kernel] in 1 second... ^MBooting [kernel]... Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved . FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0x650 Stepping = 0 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PG E,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134217728 (131072K bytes) config di bt0 config di aic0 config di aha0 config di adv0 config q avail memory = 125054976 (122124K bytes) Preloaded elf kernel kernel at 0xc0551000. Preloaded userconfig_script /boot/kernel.conf at 0xc055109c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 13 entries at 0xc00fdef0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443LX (440 LX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: Intel 82443LX (440 LX) host to PCI bridge mem 0xf400-0xf7fff fff at device 0.0 on pci0 pcib1: Intel 82443LX (440 LX) PCI-PCI (AGP) bridge at device 1.0 on pc i0 pci1: PCI bus on pcib1 pci1: VGA-compatible display device at 0.0 irq 9 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xecd0-0xecdf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xece0-0xecff irq 11 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip0: Intel 82371AB Power management controller port 0x9000-0x900f at device 7.3 on pci0 ahc0: Adaptec 2940 Ultra2 SCSI adapter port 0xe800-0xe8ff mem 0xfedff0 00-0xfedf irq 9 at device 11.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs pcib2: DEC 21152 PCI-PCI bridge at device 13.0 on pci0 pci2: PCI bus on pcib2 dc0: Intel 21143 10/100BaseTX port 0x7c00-0x7c7f mem 0xfbfff800-0xfbff f87f irq 10 at device 7.0 on pci2 dc0: Ethernet address: 00:00:f8:7a:6c:af miibus0: MII bus on dc0 dcphy0: Intel 21143 NWAY media interface on miibus0 dcphy0: 10baseT, 10baseT-FDX, auto pcib3: DEC 21154 PCI-PCI bridge at device 14.0
Re: problems with loader
El Jueves, 2 de Diciembre de 2004 19:57, Kevin Oberman escribió: From: Jose M Rodriguez [EMAIL PROTECTED] Date: Thu, 2 Dec 2004 19:30:50 +0100 Sender: [EMAIL PROTECTED] El Jueves, 2 de Diciembre de 2004 19:06, Konstantin Volevatch escribió: Hi, Jose! In /boot/defaults/loader.conf : module_path=/boot/modules You can override it with: module_path=/boot/kernel tried. doesn' work. Anyone else see this? Still sounds like a broken module path to me. But the correct fix is in UPDATING. See the entry for 20040806. I install a brand new /boot from fresh build. I tried put module_path=/boot/kernl. no look. After that, I try a /boot/loader.conf: loader_color=YES verbose_loading=YES beastie_disable=YES snd_via8233_load=YES After kernel load, I can see a: snd_via8233...failed breaking into the loader, show: module_path=/boot/kernel;/boot/modules After boot, kldload snd_via8233 works without problems. I only can see minor changes fron ru@ (3 weeks) and iedowse@ (2 month). But no clues on this. Any help on this is welcome -- josemi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault panic in 4.10-STABLE ...
Just as a follow up ... right now, we suspect that the trigger for this
panic is svnadmin ... a client reported running it just before all three
crashes ... I'm going to test the theory on sat, to see if it does, in
fact, trigger it ... if so, something svnadmin is doing on creating a new
repository seems to be interacting with unionfs ...
I've tried this on 5.x, and can't seem to reproduce, but right now its
purely a theory based on what looks just t much like a coincidence ...
On Wed, 1 Dec 2004, Marc G. Fournier wrote:
Since it looks like a 4.11 is happening, here is a quick bug report about a
panic that I seem to be getting out of the blue on one of my servers ...
I've got two *good* core dumps from it, here is a bt of one of them:
(kgdb) where
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0x801650bb in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0x8016552d in panic (fmt=0x80299959 %s) at
/usr/src/sys/kern/kern_shutdown.c:595
#3 0x8025ba41 in trap_fatal (frame=0xb8319754, eva=0) at
/usr/src/sys/i386/i386/trap.c:974
#4 0x8025b6ad in trap_pfault (frame=0xb8319754, usermode=0, eva=0) at
/usr/src/sys/i386/i386/trap.c:867
#5 0x8025b20b in trap (frame={tf_fs = -1976500200, tf_es = -1995046896,
tf_ds = -1995046896, tf_edi = -1386893312, tf_esi = 0, tf_ebp = -1204709440,
tf_isp = -1204709504,
tf_ebx = 4096, tf_edx = -1386893312, tf_ecx = 1024, tf_eax =
-1386893312, tf_trapno = 12, tf_err = 0, tf_eip = -2145016810, tf_cs = 8,
tf_eflags = 66054, tf_esp = -1204709200,
tf_ss = -1204709228}) at /usr/src/sys/i386/i386/trap.c:466
#6 0x8025a416 in generic_bcopy ()
#7 0x80207a95 in ffs_write (ap=0xb8319858) at
/usr/src/sys/ufs/ufs/ufs_readwrite.c:547
#8 0x801a3255 in union_write (ap=0xb831989c) at vnode_if.h:363
#9 0x8021ebd8 in vnode_pager_generic_putpages (vp=0xba70e240, m=0xb8319970,
bytecount=4096, flags=12, rtvals=0xb8319940) at vnode_if.h:363
#10 0x801a30c6 in union_putpages (ap=0xb8319904) at
/usr/src/sys/miscfs/union/union_vnops.c:1047
#11 0x8021e9fa in vnode_pager_putpages (object=0xc091d564, m=0xb8319970,
count=1, sync=12, rtvals=0xb8319940) at vnode_if.h:1147
#12 0x8021b93f in vm_pageout_flush (mc=0xb8319970, count=1, flags=12) at
/usr/src/sys/vm/vm_pager.h:147
#13 0x802188ab in vm_object_page_collect_flush (object=0xc091d564,
p=0x83ddb5f0, curgeneration=73, pagerflags=12) at
/usr/src/sys/vm/vm_object.c:806
#14 0x80218489 in vm_object_page_clean (object=0xc091d564, start=0, end=0,
flags=4) at /usr/src/sys/vm/vm_object.c:605
#15 0x801959d8 in vfs_msync (mp=0x8b12e200, flags=2) at
/usr/src/sys/kern/vfs_subr.c:2731
#16 0x80196b50 in sync (p=0x802d9720, uap=0x0) at
/usr/src/sys/kern/vfs_syscalls.c:582
#17 0x80164e56 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:235
#18 0x8016552d in panic (fmt=0x80299959 %s) at
/usr/src/sys/kern/kern_shutdown.c:595
#19 0x8025ba41 in trap_fatal (frame=0xb8319bc4, eva=0) at
/usr/src/sys/i386/i386/trap.c:974
#20 0x8025b6ad in trap_pfault (frame=0xb8319bc4, usermode=0, eva=0) at
/usr/src/sys/i386/i386/trap.c:867
#21 0x8025b20b in trap (frame={tf_fs = -1975451624, tf_es = 1812135952, tf_ds
= -1204748272, tf_edi = -1525469184, tf_esi = 0, tf_ebp = -1204708304, tf_isp
= -1204708368,
tf_ebx = 8192, tf_edx = -1525469184, tf_ecx = 2048, tf_eax =
-1525469184, tf_trapno = 12, tf_err = 0, tf_eip = -2145016810, tf_cs = 8,
tf_eflags = 66054, tf_esp = -1204708064,
tf_ss = -1204708092}) at /usr/src/sys/i386/i386/trap.c:466
#22 0x8025a416 in generic_bcopy ()
#23 0x80207a95 in ffs_write (ap=0xb8319cc8) at
/usr/src/sys/ufs/ufs/ufs_readwrite.c:547
#24 0x801a3255 in union_write (ap=0xb8319d0c) at vnode_if.h:363
#25 0x8021ebd8 in vnode_pager_generic_putpages (vp=0xc041aa80, m=0xb8319de4,
bytecount=8192, flags=12, rtvals=0xb8319db0) at vnode_if.h:363
#26 0x801a30c6 in union_putpages (ap=0xb8319d74) at
/usr/src/sys/miscfs/union/union_vnops.c:1047
#27 0x8021e9fa in vnode_pager_putpages (object=0xc09133f4, m=0xb8319de4,
count=2, sync=12, rtvals=0xb8319db0) at vnode_if.h:1147
#28 0x8021b93f in vm_pageout_flush (mc=0xb8319de4, count=2, flags=12) at
/usr/src/sys/vm/vm_pager.h:147
#29 0x802188ab in vm_object_page_collect_flush (object=0xc09133f4,
p=0x83f147f0, curgeneration=20, pagerflags=12) at
/usr/src/sys/vm/vm_object.c:806
#30 0x80218489 in vm_object_page_clean (object=0xc09133f4, start=0, end=0,
flags=4) at /usr/src/sys/vm/vm_object.c:605
#31 0x801959d8 in vfs_msync (mp=0x8b12e200, flags=2) at
/usr/src/sys/kern/vfs_subr.c:2731
#32 0x80195da6 in sync_fsync (ap=0xb8319f7c) at
/usr/src/sys/kern/vfs_subr.c:2992
#33 0x8019408f in sched_sync () at vnode_if.h:558
(kgdb) up 7
#7 0x80207a95 in ffs_write (ap=0xb8319858) at
/usr/src/sys/ufs/ufs/ufs_readwrite.c:547
547 error =
(kgdb) list
542
543 size = BLKSIZE(fs, ip, lbn) - bp-b_resid;
544 if (size xfersize)
545 xfersize = size;
546
547
