On 4. des. 2005, at 23.44, Frode Nordahl wrote:
Hello,
After almost 6 months of problem-free operation one of my NFS
servers has suddenly started to panic and do a automatic reboot
regularly, about every 24 hours.
This is a dual Xeon (with UP kernel for the time being) SE7501HG2
with 4
Oliver Fromme <[EMAIL PROTECTED]> writes:
> That looks like your rpcbind(8) process died. Can you
> check that with ps? Also, are there any warnings or
> errors reported in /var/log/messages?
No, it's still running. It shows up in rpcinfo (as does nfsd), and
rpcbind itself also replies to pin
> Is a minor update to the handbook needed in order avoid confusion then?
> e.g. I have been commenting out CPU_I586 on all my PIII systems in the
> (mistaken it would seem) belief that having CPU_I686 only was better.
I've been doing the same thing myself - removing the CPU_I586 on PIII and
new
On Thu, Dec 15, 2005 at 12:17:21AM -0500, Mike Jakubik wrote:
> Mark Kirkwood wrote:
> >Is a minor update to the handbook needed in order avoid confusion
> >then? e.g. I have been commenting out CPU_I586 on all my PIII systems
> >in the (mistaken it would seem) belief that having CPU_I686 only wa
On Wednesday 14 December 2005 10:55 pm, Scott Long wrote:
> Jonathan Noack wrote:
> > Kevin Oberman wrote:
> >> Scott Long wrote:
> >>> Also, taking out CPU_I586 is usually a bad idea. It offers no
> >>> performance penalties (unlike CPU_I386 and maybe CPU_I486), but
> >>> enables things like opti
Mike Jakubik wrote:
Mark Kirkwood wrote:
Is a minor update to the handbook needed in order avoid confusion
then? e.g. I have been commenting out CPU_I586 on all my PIII systems
in the (mistaken it would seem) belief that having CPU_I686 only was
better.
Agreed, i have always just used I686,
Mark Kirkwood wrote:
Is a minor update to the handbook needed in order avoid confusion
then? e.g. I have been commenting out CPU_I586 on all my PIII systems
in the (mistaken it would seem) belief that having CPU_I686 only was
better.
Agreed, i have always just used I686, assuming it inherited
Scott Long wrote:
Jonathan Noack wrote:
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never real
Scott Long wrote:
Jonathan Noack wrote:
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never realized
Jonathan Noack wrote:
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never realized. Is there anythi
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never realized. Is there anything in
the handbook that co
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Is that documented? In /sys/i386/conf/NOTES I see:
# You must specify at least one CPU (the one you intend to
Peter Jeremy said the following on 12/13/05 02:00:
Note that PS/2 keyboards aren't hot-pluggable and attempts to do so
can have deleterious effects on your keyboard and/or motherboard. In
any case, the probe/attach sequence relies on the kernel being in a
reasonably sane state (and I'm not sure
On Wed, Dec 14, 2005 at 04:45:47PM -0800, Kevin Oberman wrote:
> > Date: Wed, 14 Dec 2005 19:34:04 -0500
> > From: Kris Kennaway <[EMAIL PROTECTED]>
> >
> > On Wed, Dec 14, 2005 at 04:26:18PM -0800, Kevin Oberman wrote:
> >
> > > I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm,
> Date: Wed, 14 Dec 2005 19:34:04 -0500
> From: Kris Kennaway <[EMAIL PROTECTED]>
>
> On Wed, Dec 14, 2005 at 04:26:18PM -0800, Kevin Oberman wrote:
>
> > I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm,
> > atkbd0 and ichsmb) that are still marked as GIANT-LOCKED, but I'm not
On Wed, Dec 14, 2005 at 04:26:18PM -0800, Kevin Oberman wrote:
> I am attaching a dmesg. I do have a few of drivers (uhci, pcm, psm,
> atkbd0 and ichsmb) that are still marked as GIANT-LOCKED, but I'm not
> using the USB very often. And I'm not using pcm or ichsmb during the
> dump, either. I thin
> Date: Wed, 14 Dec 2005 16:17:38 -0700
> From: Scott Long <[EMAIL PROTECTED]>
>
> Kevin Oberman wrote:
>
> > I recently upgraded my last desktop system from 4.11-Stable to
> > 6.0-Stable. I did an update to 5.3 then to RELENG_5,
> > RELENG_6_0_0_RELEASE and on to RELENG6_0.
> >
> > This system
Kevin Oberman wrote:
I recently upgraded my last desktop system from 4.11-Stable to
6.0-Stable. I did an update to 5.3 then to RELENG_5,
RELENG_6_0_0_RELEASE and on to RELENG6_0.
This system has been updated regularly from the days of at least 4.1.
The hardware is a 1GHz PIII with an ICH2 chips
I recently upgraded my last desktop system from 4.11-Stable to
6.0-Stable. I did an update to 5.3 then to RELENG_5,
RELENG_6_0_0_RELEASE and on to RELENG6_0.
This system has been updated regularly from the days of at least 4.1.
The hardware is a 1GHz PIII with an ICH2 chipset. 256 MB of memory.
In the last episode (Dec 14), Colin Farley said:
> Thanks for the reply. I have found as suspected that apache is
> responsible. Since these servers are redundant using UCARP I am
> planning to shut down the services, unmount /var and run fsck, one at
> a time. I'm just not sure why I cannot see
Thanks for the reply. I have found as suspected that apache is
responsible. Since these servers are redundant using UCARP I am planning
to shut down the services, unmount /var and run fsck, one at a time. I'm
just not sure why I cannot see these files but hopefully fsck will make
them visable or
> Have a machine that once we upgraded to 6 Stable the machine would freeze at
> the bootup menu.
>
> Strangely enough we have a second machine with the same motherboard, same
> amount of memory, same 3Ware controller, but with different drives. the
> machine that is Freezing has 10K RPM SATA rapto
Have a machine that once we upgraded to 6 Stable the machine would freeze at
the bootup menu.
We tried disabling ACPI and AIPC and it did not help. Usually the freezing occurs
after 2 or 3 seconds out of the 10 second countdown.
To make it more interesting... if we press enter right after the
On Wed, Dec 14, 2005 at 05:32:34PM +0100, Fabian Keil wrote:
> I guess you're right. I can fill a 256MB swap-backed disk without panic
> and without swapping.
FYI, this is documented in the manpage.
Kris
pgpJ4IsKT7ayY.pgp
Description: PGP signature
I have a HP Vectra running
FreeBSD acesfbsd 6.0-STABLE FreeBSD 6.0-STABLE #0: Fri Dec 9 14:44:30
CST 2005
that has trouble with nfs mounts (amd home directory) from a Solaris 8
box.
It started life as 4.x went through a lot of 5.x all with no problems.
However, since upgrading to 6.0, occasio
Neal Nelson wrote:
Has anyone got FreeBSD 6.0 to work as a wireless access point using WPA?
I'm running a Prism 2.5 based wireless card and have been using it as an
access point for years. It stills works OK but I installed the hostapd
port in order to add WPA authentication. Unfortunately thi
Has anyone got FreeBSD 6.0 to work as a wireless access point using WPA?
I'm running a Prism 2.5 based wireless card and have been using it as
an access point for years. It stills works OK but I installed the
hostapd port in order to add WPA authentication. Unfortunately this
doesn't seem to w
On Wed, 2005-Dec-14 08:28:26 -0400, fredthetree wrote:
>i've only used the generic 6.0 kernel
>
># kgdb kernel.debug /var/crash/vmcore.1
...
>#6 0xc07f6dca in calltrap () at /usr/src/sys/i386/i386/exception.s:139
>#7 0xc0a7cf08 in ?? ()
Unfortunately, it's frame 7 and below that is crucial. Was
In the last episode (Dec 14), Colin Farley said:
> I'm running FreeBSD 4.10-RELEASE-p16 on a couple of production mail
> relays/web servers. Today I noticed that one had a lot more space in
> /var used. I figured that a log was growing and started to
> investigate. After running du -h /var and s
Scott Long <[EMAIL PROTECTED]> wrote:
> Gleb Smirnoff wrote:
>
> > On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote:
> > F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE.
> > F>
> > F> I created a ramdisk with:
> > F>
> > F> /sbin/mdconfig -a -t malloc -s 256M
Gleb Smirnoff wrote:
On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote:
F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE.
F>
F> I created a ramdisk with:
F>
F> /sbin/mdconfig -a -t malloc -s 256M -u 10
F> /sbin/newfs -U /dev/md10
F> /sbin/mount
I'm running FreeBSD 4.10-RELEASE-p16 on a couple of production mail
relays/web servers. Today I noticed that one had a lot more space in /var
used. I figured that a log was growing and started to investigate. After
running du -h /var and seeing it come up with a total usage much less than
what
Gleb Smirnoff <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote:
> F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE.
> F>
> F> I created a ramdisk with:
> F>
> F> /sbin/mdconfig -a -t malloc -s 256M -u 10
> F> /sbin/newfs -U /
On Wed, Dec 14, 2005 at 01:25:30PM +0100, Fabian Keil wrote:
F> I triggered a few reproducible panics on FreeBSD 6.0-STABLE.
F>
F> I created a ramdisk with:
F>
F> /sbin/mdconfig -a -t malloc -s 256M -u 10
F> /sbin/newfs -U /dev/md10
F> /sbin/mount /dev/md10 /mnt/ramdisk
F
On Dec 6, 2005, at 03:20 , Joshua Coombs wrote:
#optionsZERO_COPY_SOCKETS
What's the status of this in 6.0-R and 6-stable? The idea of
avoiding memory copies when possible seems really appealing for my
386, on which any little boost is significant. : )
Hoi,
let me know h
i've only used the generic 6.0 kernel
# kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the
I triggered a few reproducible panics on FreeBSD 6.0-STABLE.
I created a ramdisk with:
/sbin/mdconfig -a -t malloc -s 256M -u 10
/sbin/newfs -U /dev/md10
/sbin/mount /dev/md10 /mnt/ramdisk
The system has "avail memory = 515932160 (492 MB)"
and 1GB swap space.
While copy
Opps forgot to say running 6.0-RELEASE.
Steve
- Original Message -
From: "Steven Hartland" <[EMAIL PROTECTED]>
Just spotted the following in the logs of one of our machines
There seems to errors across too many disks for it to be disk issues.
Any one seen this before / got any adv
Just spotted the following in the logs of one of our machines
There seems to errors across too many disks for it to be disk issues.
Any one seen this before / got any advice?
ad4: timeout waiting to issue command
ad4: error issueing WRITE_DMA command
ar0: WARNING - mirror protection lost. RAID0+1
[LoN]Kamikaze wrote:
> Because of the devfs discussion I had a look into
> sys/fs/devfs/devfs_rules.c .
^ without 's'
>
> Somewhere in the sourcecode he/she's asking a question and I would like
> to answer it. There just is no email address provided.
[...]
You can use th
Hi,
I have a setup with an 5.4-STABLE (July, 10th 2005) NFS server and about
10 FreeBSD clients. Most of the clients are still running on RELENG_5,
but I recently started updating to RELENG_6. Shortly after updating the
first client I ran into a problem with a spinning rpc.lockd on the NFS
ser
On Mon, 12 Dec 2005, Paul Herman wrote:
Just installed 6.0-STABLE/amd64 (cvsup from within the last day) onto a K8
Sempron with IPSEC compiled in and I get a kernel panic when I try to run
racoon. Anyone else seen this?
(Replying to myself...)
Just saw this is PR 89261. Sorry for the redun
Because of the devfs discussion I had a look into
sys/fs/devfs/devfs_rules.c .
Somewhere in the sourcecode he/she's asking a question and I would like
to answer it. There just is no email address provided.
The question is as follows:
/*
* XXX: Does it matter whether we do
Michael Sperber <[EMAIL PROTECTED]> wrote:
> I'm running 5.4-STABLE (about two weeks old), and have just set up an
> NFS server for the first time. Remote mounts sometimes work fine, and
> sometimes fail.
>
> The symptoms are that "showmount -e" sez
>
> showmount: can't do exports rpc
>
44 matches
Mail list logo
