Re: panics after upgrading to -STABLE Aug 9, 2002

2002-08-09 Thread Mike Murphree


> On Fri, Aug 09, 2002 at 09:41:38PM -0400, Scott Lambert wrote:
> > I've been getting regular panics today after CVSuping and following the
> > UPDATING procedure.  I think all of the panics are happening as various
> > network apps are tearing down their connections.  I've had it trap while
> > in the kernel on the behalf of fetchmail, ppp, and nfsd (when I
kill -9'd
> > nfsd to try to make sure I wouldn't panic during a buildkernel, and
during
> > a shutdown.).

Same here, it has died during fetchmail, nfsd, mutt, and ssh...

>
> This is the only kernel related commit that looks, to unknowlegable me,
> like a likely candidate to have caused these problems today:
>
> >Message-Id: <[EMAIL PROTECTED]>
> >ru  2002/08/09 07:49:23 PDT
> >
> >  Modified files:(Branch: RELENG_4)
> >sys/netinet  in_rmx.c ip_input.c ip_var.h
> >  Log:
> >  MFC: in_rmx.c,v 1.39, ip_input.c,v 1.165, and ip_var.h,v 1.54:

That's the last files I got, and rebuilt this morning about 10 A.M.
Prior to that it was broken because of the uvisor files last night...

Mike W4LNA




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: ports: www/mod_php4 dependency problem with graphics/png

2001-09-26 Thread Mike Murphree

On Wed, Sep 26, 2001 at 02:57:48PM +0200, -R- wrote:
> >png.5 is made, but not png.4 .. which is a required dependency for
> >mod_php4 .. any tips?
> 
> apparently symlinking libpng.so.4 to libpng.so.5 solves it.
> but the Makefile for mod_phph4 in ports is still probably wrong.
> 

I've seen the same problem with gphoto port too...

Mike

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: FreeBSD and Athlon Processors

2001-08-31 Thread Mike Murphree

On Thursday 30 August 2001 08:17 pm, Darryl Okahata wrote:
> "Juha Saarinen" <[EMAIL PROTECTED]> wrote:
> > It's probably not the Athlon CPU that's the issue for either FreeBSD or
> > Linux, but the motherboard chip sets. From personal experience, the
> > first Linux 2.4 kernels weren't very happy with VIA chip sets, which are
> > commonly used for Athlon boards. It's mainly IDE issues (e.g.
> > UDMA-66/100 support).
>
>  Yeah.  As long as you avoid motherboards with the VIA KT133A/KT133
> chipset and the VIA 686B Southbridge, you're probably fine (not all such
> motherboards supposedly have problems, but how do you tell the
> difference?).  For more info, check out:
>
>   http://www.au-ja.de/review-kt133a-1-en.html

Funny, but I've had one of those for a few months with no problems at all.
Then again, I don't have one of those piece of crap SoundBlaster Live!
cards they mention in my system either

Mike

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message



Re: mt broken?

2000-08-19 Thread Mike Murphree

Mike Harding wrote:
> 
> The man page is incorrect - it specifies /dev/nsa0.

But what was below wasn't the man page but the output of
the command. From /usr/src/sys/sys/mtio.h :

#ifndef _KERNEL
#define DEFTAPE "/dev/nsa0"
#endif 


It appears to be set wrong.

Mike

>Date: Fri, 18 Aug 2000 23:57:35 -0500
>From: Mike Murphree <[EMAIL PROTECTED]>
>X-Accept-Language: en
>Content-Type: text/plain; charset=iso-8859-15
>Sender: [EMAIL PROTECTED]
>X-Loop: FreeBSD.ORG
>Precedence: bulk
>X-RULES: lists
> 
>Ok, what happened to this:
> 
>%mt status
>mt: /dev/nsa0: No such file or directory
> 
>It's missing an 'r' in the device.
> 
>>From dmesg:
> 
>FreeBSD 4.1-STABLE #0: Mon Aug 14 02:23:31 CDT 2000
> 
>Waiting 2 seconds for SCSI devices to settle
>sa0 at ncr0 bus 0 target 5 lun 0
>sa0:  Removable Sequential Access SCSI-2 device
>sa0: 10.000MB/s transfers (10.000MHz, offset 7)
> 
>As expected, the following works normally:
> 
>mt -f /dev/nrsa0 status
> 
>Thanks,
>Mike
> 
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-stable" in the body of the message
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message