Re: Re: userland program panics freebsd 4.3

2002-01-03 Thread Michael Scheidell
Subject: Re: Re: userland program panics freebsd 4.3 On 2002-01-01 19:59 +, John Rochester [EMAIL PROTECTED] wrote: Stefan Esser wrote: Instead of the for loop, I'd rather have: while(waitpid(pid, NULL, WNOHANG) == EINTR) This should be while (waitpid(pid, NULL, WNOHANG) 0

Re: Re: userland program panics freebsd 4.3

2002-01-02 Thread Michael Scheidell
Message - From: Stefan Esser [EMAIL PROTECTED] To: John Rochester [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; Stefan Esser [EMAIL PROTECTED] Sent: Tuesday, January 01, 2002 5:25 PM Subject: Re: Re: userland program panics freebsd 4.3 On 2002-01-01 19:59 +, John Rochester [EMAIL PROTECTED

Re: Re: Re: userland program panics freebsd 4.3

2002-01-01 Thread Stefan Esser
On 2001-12-31 11:31 -0500, Michael Scheidell [EMAIL PROTECTED] wrote: (The second method, used only if there is no PROCFS, is to call kill(PID, 0), which will check if a signal could be delivered. That method should probably be prefered to the reading of procfs anyway, since the latter

Re: userland program panics freebsd 4.3

2002-01-01 Thread John Rochester
Stefan Esser wrote: Instead of the for loop, I'd rather have: while(waitpid(pid, NULL, WNOHANG) == EINTR) This should be while (waitpid(pid, NULL, WNOHANG) 0 errno == EINTR) /* do nothing */; return kill(pid, 0) == 0; -- John Rochester Software Architect, Merus

Re: Re: userland program panics freebsd 4.3

2002-01-01 Thread Stefan Esser
On 2002-01-01 19:59 +, John Rochester [EMAIL PROTECTED] wrote: Stefan Esser wrote: Instead of the for loop, I'd rather have: while(waitpid(pid, NULL, WNOHANG) == EINTR) This should be while (waitpid(pid, NULL, WNOHANG) 0 errno == EINTR) Yes, obviously ... ;-) STefan To

Re: userland program panics freebsd 4.3

2001-12-31 Thread Stefan Esser
On 2001-12-18 15:29 -0500, Michael Scheidell [EMAIL PROTECTED] wrote: I have a userland program that canpanic/reboot a freebsd 4.3 system. Hardware is Intel isp1100 (mbx440 motherboard) 850MHZ pIII, 256mb ram, 640mb swapfile software is 'nessusd' (network security scanner) hits the ethernet

Re: userland program panics freebsd 4.3

2001-12-31 Thread Michael Scheidell
I've had similar problems running nessus against a range of 32 class B networks (i.e. 2mio addresses) with some 1 hosts expected to be found. Since I need to complete the scan during the next two weeks (it's running in batch mode right now; but I had trouble with hanging nessusd

Re: Re: userland program panics freebsd 4.3

2001-12-31 Thread Stefan Esser
On 2001-12-31 10:29 -0500, Michael Scheidell [EMAIL PROTECTED] wrote: as for hanging processes, this is probaly due to the bug in the FBSD distributer libpcap, hanging on pcap_next(). IIRC, most processes were sleeping in select(). But truss revealed, that some processes were running in a loop

Re: Re: userland program panics freebsd 4.3

2001-12-31 Thread Michael Scheidell
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=32681 The cause is a NULL pointer dereference in that fstatfs system call, where some pointer hanging off a vnode is cleared. Nessusd tries to read from /proc/PID (for PID = process IDs of plugins spawned) in order to see whether some

Re: userland program panics freebsd 4.3

2001-12-27 Thread Michael Scheidell
Just an update: userland probram panic's FBSD 4.3-REL, FBSD 4.4-REL and FBSD 4.4-STABLE. its not hardware (unless two completly identicle systems have some type of chip problem not known yet) its not thermal problem (I can do make buildworld's all day long) If I do find it, its easy to tell: I

Re: userland program panics freebsd 4.3

2001-12-27 Thread Alfred Perlstein
* Michael Scheidell [EMAIL PROTECTED] [011227 14:26] wrote: Just an update: userland probram panic's FBSD 4.3-REL, FBSD 4.4-REL and FBSD 4.4-STABLE. its not hardware (unless two completly identicle systems have some type of chip problem not known yet) Can you provide this program or a kernel

Re: userland program panics freebsd 4.3 (now 4.4 also)

2001-12-27 Thread Michael Scheidell
- Original Message - From: Alfred Perlstein [EMAIL PROTECTED] To: Michael Scheidell [EMAIL PROTECTED] Cc: David Malone [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 3:31 PM Subject: Re: userland program panics freebsd 4.3 * Michael Scheidell

Re: userland program panics freebsd 4.3 (now 4.4 also)

2001-12-27 Thread Alfred Perlstein
* Michael Scheidell [EMAIL PROTECTED] [011227 14:34] wrote: * Michael Scheidell [EMAIL PROTECTED] [011227 14:26] wrote: Just an update: userland probram panic's FBSD 4.3-REL, FBSD 4.4-REL and FBSD 4.4-STABLE. its not hardware (unless two completly identicle systems have some type of

Re: userland program panics freebsd 4.3

2001-12-27 Thread Michael Scheidell
- Original Message - From: Alfred Perlstein [EMAIL PROTECTED] To: Michael Scheidell [EMAIL PROTECTED] Cc: David Malone [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 3:31 PM Subject: Re: userland program panics freebsd 4.3 * Michael Scheidell

Re: userland program panics freebsd 4.3

2001-12-27 Thread Alfred Perlstein
* Michael Scheidell [EMAIL PROTECTED] [011227 14:48] wrote: same place as before: 0 fstatfs (p=0xce1bd260, uap=0xce216f80) at ../../kern/vfs_syscalls.c:684 684 error = VFS_STATFS(mp, sp, p); 680 if ((error = getvnode(p-p_fd, SCARG(uap, fd), fp)) != 0) 681

Re: userland program panics freebsd 4.3

2001-12-27 Thread Michael Scheidell
- Original Message - From: Alfred Perlstein [EMAIL PROTECTED] To: Michael Scheidell [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 4:00 PM Subject: Re: userland program panics freebsd 4.3 *mp, *sp, *p, *((struct vnode *)fp-f_data) print *mp: $1 = {mnt_list

Re: userland program panics freebsd 4.3

2001-12-27 Thread Alfred Perlstein
* Michael Scheidell [EMAIL PROTECTED] [011227 15:11] wrote: - Original Message - From: Alfred Perlstein [EMAIL PROTECTED] To: Michael Scheidell [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 27, 2001 4:00 PM Subject: Re: userland program panics freebsd 4.3 ok

Re: userland program panics freebsd 4.3

2001-12-23 Thread David Malone
I did this, and instead of crashing in 15 ins, its still running after 3 hours. I will rerun tests and report back. Thanks for the suggestion (now, if I cvsup RELENG_4_3 do I get the OLD param.h?) I think with cvsup you will get the old one back again. If you use cvs it would preserve the

Re: userland program panics freebsd 4.3

2001-12-21 Thread Michael Scheidell
- Original Message - From: Paul Halliday [EMAIL PROTECTED] To: Kris Kennaway [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 20, 2001 10:08 PM Subject: Re: userland program panics freebsd 4.3 On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45

Re: userland program panics freebsd 4.3

2001-12-21 Thread Peter Wemm
Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:10:14AM -0500, Michael Scheidell wrote: I doubt hardware related I can get it to do it on two seperate boxes. OK, then you need to get more details as explained. My gut reaction tells me that this is either a kernel stack overflow or out of

Re: userland program panics freebsd 4.3

2001-12-21 Thread Michael Scheidell
Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:10:14AM -0500, Michael Scheidell wrote: I doubt hardware related I can get it to do it on two seperate boxes. OK, then you need to get more details as explained. My gut reaction tells me that this is either a kernel stack overflow

Re: userland program panics freebsd 4.3

2001-12-21 Thread Ted Faber
On Thu, Dec 20, 2001 at 07:14:08PM -0800, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:08:36PM -0600, Paul Halliday wrote: On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke

Re: userland program panics freebsd 4.3

2001-12-21 Thread David Malone
On Fri, Dec 21, 2001 at 12:51:38PM -0500, Michael Scheidell wrote: My gut reaction tells me that this is either a kernel stack overflow or out of KVM. The kernel stack overflow problem was fixed in 4.4-STABLE some time back (change UPAGES from 2 to 3 in the kernel) so that the kernel stack

Re: userland program panics freebsd 4.3

2001-12-21 Thread Michael Scheidell
- Original Message - From: David Malone [EMAIL PROTECTED] To: Michael Scheidell [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, December 21, 2001 1:18 PM Subject: Re: userland program panics freebsd 4.3 On Fri, Dec 21, 2001 at 12:51:38PM -0500, Michael

Re: userland program panics freebsd 4.3

2001-12-20 Thread Michael Scheidell
I doubt hardware related I can get it to do it on two seperate boxes. Updating to freebsd 4.4 is a bad option, with all the reported ports and services broken. -- Michael Scheidell Secnap Network Security, LLC [EMAIL PROTECTED] 1+(561) 368-9561 See updated IT Security News at http://www.fdma.com/

Re: userland program panics freebsd 4.3

2001-12-20 Thread Mike Barcroft
Michael Scheidell [EMAIL PROTECTED] writes: I doubt hardware related I can get it to do it on two seperate boxes. Updating to freebsd 4.4 is a bad option, with all the reported ports and services broken. I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? Best

Re: userland program panics freebsd 4.3

2001-12-20 Thread Michael Scheidell
I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? scan through freebsd-questions, freebsd-mobile and freebsd-ports as for moving to fbsd 4.4 for a 'maybe' fix of something that might still show up in 4.4 (according to other posts) this seems to be in the

Re: userland program panics freebsd 4.3

2001-12-20 Thread Kris Kennaway
On Thu, Dec 20, 2001 at 09:10:14AM -0500, Michael Scheidell wrote: I doubt hardware related I can get it to do it on two seperate boxes. OK, then you need to get more details as explained. Updating to freebsd 4.4 is a bad option, with all the reported ports and services broken. I'm not

Re: userland program panics freebsd 4.3

2001-12-20 Thread Kris Kennaway
On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? scan through freebsd-questions, freebsd-mobile and freebsd-ports That's completely non-helpful. I read -questions and -ports, and don't

Re: userland program panics freebsd 4.3

2001-12-20 Thread Alfred Perlstein
* Kris Kennaway [EMAIL PROTECTED] [011220 19:56] wrote: On Thu, Dec 20, 2001 at 09:10:14AM -0500, Michael Scheidell wrote: I doubt hardware related I can get it to do it on two seperate boxes. OK, then you need to get more details as explained. Updating to freebsd 4.4 is a bad option,

Re: userland program panics freebsd 4.3

2001-12-20 Thread Paul Halliday
On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? scan through freebsd-questions, freebsd-mobile and freebsd-ports That's completely

Re: userland program panics freebsd 4.3

2001-12-20 Thread Mike Barcroft
Paul Halliday [EMAIL PROTECTED] writes: My soundcard on my lappy has been broken since 4.4. And to be brutally honest, it's really starting to piss me off. Enough to open a PR? Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers

Re: userland program panics freebsd 4.3

2001-12-20 Thread Kris Kennaway
On Thu, Dec 20, 2001 at 09:08:36PM -0600, Paul Halliday wrote: On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke between 4.3 and 4.4. Care to elaborate? scan through

Re: userland program panics freebsd 4.3

2001-12-20 Thread Paul Halliday
On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 09:08:36PM -0600, Paul Halliday wrote: On Thu, 20 Dec 2001, Kris Kennaway wrote: On Thu, Dec 20, 2001 at 12:45:51PM -0500, Michael Scheidell wrote: I'm not aware of any services that broke between 4.3 and 4.4.

Re: userland program panics freebsd 4.3

2001-12-20 Thread Mike Barcroft
Paul Halliday [EMAIL PROTECTED] writes: Due to my limited intelligence and poor cognitive skills I consider a PR to be a waste until someone that actually knows what they are doing reports the same problem. The card compiles, works like a charm. However, No mixer control with

Re: userland program panics freebsd 4.3

2001-12-20 Thread Kris Kennaway
On Thu, Dec 20, 2001 at 09:26:53PM -0600, Paul Halliday wrote: My soundcard on my lappy has been broken since 4.4. And to be brutally honest, it's really starting to piss me off. Which PR contains your bug report? I couldn't see one. Kris Due to my limited intelligence

Re: userland program panics freebsd 4.3

2001-12-20 Thread Matthew Dillon
:I have a userland program that canpanic/reboot a freebsd 4.3 system. :Hardware is Intel isp1100 (mbx440 motherboard) 850MHZ pIII, 256mb ram, 640mb :swapfile :software is 'nessusd' (network security scanner) hits the ethernet port :pretty hard when running. :If I read the dumpdev right, it is

Re: userland program panics freebsd 4.3

2001-12-20 Thread Lars Eggert
Kris Kennaway wrote: OK, so what you're saying is that you haven't even tried to report the problem such that it can be fixed. I don't think it's fair to hold your lack of communication about your problem against the FreeBSD sound developers; if you want this to get fixed then you really

Re: userland program panics freebsd 4.3

2001-12-19 Thread Kris Kennaway
On Tue, Dec 18, 2001 at 03:29:17PM -0500, Michael Scheidell wrote: I have a userland program that canpanic/reboot a freebsd 4.3 system. Can you upgrade to 4.4-STABLE and test whether the problem persists? Chances are it's either a) fixed, or b) hardware-related. Kris msg30305/pgp0.pgp

userland program panics freebsd 4.3

2001-12-18 Thread Michael Scheidell
I have a userland program that canpanic/reboot a freebsd 4.3 system. Hardware is Intel isp1100 (mbx440 motherboard) 850MHZ pIII, 256mb ram, 640mb swapfile software is 'nessusd' (network security scanner) hits the ethernet port pretty hard when running. If I read the dumpdev right, it is crashing