TECTED]>; "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]> wrote:
> > Stefan Esser wrote:
> >
> > >Ins
- Original 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
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 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
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
>
> 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 so
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 l
>
> 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
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 ether
* 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, De
- 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, *(
* 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)
> 6
- 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, 2
* 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 hav
- 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, 2
* 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 k
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 c
> 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 t
- 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 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 kerne
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
> 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 st
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
- 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 200
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
: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 cras
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 limit
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
>
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 b
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?
> > >
>
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-hacke
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 c
* 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
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
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
>
> 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
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?
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/
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
D
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 i
40 matches
Mail list logo
