On Fri, Oct 08, 2010 at 07:09:48PM -0700, Hac Phan wrote:
Hi,
I'm having trouble with a machine that was recently rebooted and will no
longer
boot correctly.
The boot process hangs with the following screen:
Loading /boot/defaults/loader.conf
It sounds like there is something in
In the last episode (Oct 08), Hac Phan said:
I'm having trouble with a machine that was recently rebooted and will no
longer boot correctly.
The boot process hangs with the following screen:
Loading /boot/defaults/loader.conf
-
The cursor does not move and no other text is displayed.
On Oct 9, 2010, at 10:58 AM, Dan Nelson wrote:
In the last episode (Oct 08), Hac Phan said:
I'm having trouble with a machine that was recently rebooted and will no
longer boot correctly.
The boot process hangs with the following screen:
Loading /boot/defaults/loader.conf
-
The cursor
Hi,
I'm having trouble with a machine that was recently rebooted and will no longer
boot correctly.
The boot process hangs with the following screen:
Loading /boot/defaults/loader.conf
-
The cursor does not move and no other text is displayed. After about 10 minutes,
the boot finishes (without
Robert Jesacher wrote:
On 06.05.2008, at 22:02, Ed Maste wrote:
On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote:
I pulled out one of the raid5 drives to test the functionality and
noticed that FreeBSD didn't seem to notice the disk failure at all. I
was expecting kernel
On 06.05.2008, at 22:02, Ed Maste wrote:
On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote:
I pulled out one of the raid5 drives to test the functionality and
noticed that FreeBSD didn't seem to notice the disk failure at all. I
was expecting kernel messages about it, but got
In the last episode (May 16), Robert Jesacher said:
On 06.05.2008, at 22:02, Ed Maste wrote:
On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote:
I pulled out one of the raid5 drives to test the functionality and
noticed that FreeBSD didn't seem to notice the disk failure at all.
I
Doesn't seem to work with my IBM ServeRAID 8k
CLI open /readonly aac0
Executing: open /readonly=TRUE aac0
Command Error: The current AFAAPI.DLL is too old to work with the
current controller software.
Seems a little odd it's referencing a dll (which doesn't exist on the
system)
Dan Nelson
On Fri, May 16, 2008 at 01:52:50PM -0700, Chris St Denis wrote:
Doesn't seem to work with my IBM ServeRAID 8k
CLI open /readonly aac0
Executing: open /readonly=TRUE aac0
Command Error: The current AFAAPI.DLL is too old to work with the
current controller software.
You can avoid this
I recently setup a new FreeBSD 7.0 AMD64 server with an IBM ServeRAID-8k
configured with a raid5 for data and raid1 for OS.
I pulled out one of the raid5 drives to test the functionality and
noticed that FreeBSD didn't seem to notice the disk failure at all. I
was expecting kernel messages
On Tue, May 06, 2008 at 12:44:02PM -0700, Chris St Denis wrote:
I pulled out one of the raid5 drives to test the functionality and
noticed that FreeBSD didn't seem to notice the disk failure at all. I
was expecting kernel messages about it, but got nothing.
This is missing functionality in
1. try to compile kernel without SMP.
2. Examine hardware.
刘德安 пишет:
FreeBSD GFAOS 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon Jan 7 15:29:50 UTC
2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
when rebooting system
Error messages:
kernel: Fatal trap 12: page fault while in
FreeBSD GFAOS 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon Jan 7 15:29:50 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
when rebooting system
Error messages:
kernel: Fatal trap 12: page fault while in kernel mode
kernel: cpuid = 0; apic id = 00
kernel: fault virtual address =
Dave wrote:
Hello,
I've got a 6.2 or 3 box that i'm wanting to update to 7.0. I've
cvsupped my source, made world, and built a kernel, all went
successfully. This is the GENERIC kernel. When i do a make installkernel
i am getting the error
kldxref: file isn't dynamically linked
Is
Hello,
I've got a 6.2 or 3 box that i'm wanting to update to 7.0. I've cvsupped
my source, made world, and built a kernel, all went successfully. This is
the GENERIC kernel. When i do a make installkernel i am getting the error
kldxref: file isn't dynamically linked
Is this a show
Hi,
you have to exec make installworld before exec make installkernel
..
bye
Norman
Am Montag, den 10.03.2008, 21:11 -0400 schrieb Dave:
Hello,
I've got a 6.2 or 3 box that i'm wanting to update to 7.0. I've cvsupped
my source, made world, and built a kernel, all went successfully. This
]
To: Dave [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Sent: Monday, March 10, 2008 10:40 PM
Subject: Re: kernel error when upgrading to 7.0
Hi,
you have to exec make installworld before exec make installkernel
..
bye
Norman
Am Montag, den 10.03.2008, 21:11 -0400 schrieb Dave:
Hello
On Tue, 11 Mar 2008 at 00:41 -0400, [EMAIL PROTECTED] confabulated:
Hello,
Previously i've done make buildworld, make buildkernel, make
installkernel, shutdown to single user mode, mergemaster -p, make
installworld, mergemaster, boot multiuser. Has this procedure changed?
Thanks.
Dave.
Hi,
Thanks for your reply. What's my issue with this kernel msg?
Thanks.
Dave.
- Original Message -
From: D Hill [EMAIL PROTECTED]
To: Dave [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org; Norman Maurer [EMAIL PROTECTED]
Sent: Tuesday, March 11, 2008 12:58 AM
Subject: Re: kernel
PROTECTED]
Sent: Tuesday, March 11, 2008 12:58 AM
Subject: Re: kernel error when upgrading to 7.0
On Tue, 11 Mar 2008 at 00:41 -0400, [EMAIL PROTECTED] confabulated:
Hello,
Previously i've done make buildworld, make buildkernel, make
installkernel, shutdown to single user mode, mergemaster -p
abhishek singh [EMAIL PROTECTED] writes:
I am getting this kernel: sis0: Applying short cable fix (reg=e8) kernel
error in /var/log/messages what it does mean .I am using FreeBSD 5.4.
It's a recommended workaround from National Semiconductor for
behaviour that I would assume deals
Hey
I am getting this kernel: sis0: Applying short cable fix (reg=e8) kernel
error in /var/log/messages what it does mean .I am using FreeBSD 5.4.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
abhishek singh wrote:
Hey
I am getting this kernel: sis0: Applying short cable fix (reg=e8)
kernel
error in /var/log/messages what it does mean .I am using FreeBSD 5.4.
You can ignore it; it an advisory message only. The chipset used for
sis0 needs some different parameters if you use
Alex Zbyslaw wrote:
abhishek singh wrote:
Hey
I am getting this kernel: sis0: Applying short cable fix (reg=e8)
kernel
error in /var/log/messages what it does mean .I am using FreeBSD 5.4.
You can ignore it; it an advisory message only. The chipset used for
sis0 needs some different
Garrett Cooper wrote:
You can ignore it; it an advisory message only. The chipset used for
sis0 needs some different parameters if you use a short cable - I
believe these come from the manufacturer. In fact, with an sis0
chipset I always get this message even when using a cable which I
Hi,
I upgraded from 5.4-RELEASE-i386 to
6.0-RELEASE-i386 and everything went well but
when I tried to rebuild the kernel, I get these
errors:
# pwd
/usr/src/sys/i386/conf
# config MYKERNEL
../../conf/files: coda/coda_fbsd.c must be
optional, mandatory or standard
# cd ../compile/MYKERNEL
# make
I upgraded from 5.4-RELEASE-i386 to
6.0-RELEASE-i386 and everything went well but
when I tried to rebuild the kernel, I get these
errors:
# pwd
/usr/src/sys/i386/conf
# config MYKERNEL
../../conf/files: coda/coda_fbsd.c must be
optional, mandatory or standard
# cd ../compile/MYKERNEL
# make
On Thu, Nov 17, 2005 at 07:57:59PM +0100, Efren Bravo wrote:
Hi,
I upgraded from 5.4-RELEASE-i386 to
6.0-RELEASE-i386 and everything went well but
when I tried to rebuild the kernel, I get these
errors:
# pwd
/usr/src/sys/i386/conf
# config MYKERNEL
../../conf/files: coda/coda_fbsd.c
Hi,
I am getting this message on FREEBSD /var/log/message file. Please help
me to fix the issue.
Thanks,
Feb 15 08:54:37 prod /kernel: aac0: **Monitor** ID(0:02:0); Unrecovered
Read Error
Feb 15 08:54:37 prod /kernel: aac0: **Monitor** Container 0 failed
REBUILD task: I/O error -
Manu Jha wrote:
Hi,
I am getting this message on FREEBSD /var/log/message file. Please help
me to fix the issue.
Thanks,
Well, at first glance, it certainly looks like one of the disks )0:2:0)
in your RAID array is developing some issues, but IANAE. You
have checked your disks? (Also, you
M [EMAIL PROTECTED] writes:
I occasionally see this on an NFS server under heavy load
ufs_rename: fvp == tvp (can't happen)
Any idea what this means and where I should look to fix it?
It means that somehow the UFS code got a request to rename a file to
itself, and the kernel code didn't
I occasionally see this on an NFS server under heavy load
ufs_rename: fvp == tvp (can't happen)
Any idea what this means and where I should look to fix it?
___
freebsd-questions@freebsd.org mailing list
On Wed, Dec 08, 2004 at 07:33:52PM +0800, Spades wrote:
After I cvsup'd and recompiling my kernel, it came up with this error,
anyone has an idea on how to fix this?
--
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith
Loren M. Lang [EMAIL PROTECTED] writes:
P.S. Is there an easy way to start a buildworld or buildkernel again
without having it auto-clean first for cases like this, or when just
making a minor chance to a source file?
make -DNOCLEAN buildworld will help.
After I cvsup'd and recompiling my kernel, it came up with this error,
anyone has an idea on how to fix this?
--
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions
-ansi -nostdinc -I- -I.
After I cvsup'd and recompiling my kernel, it came up with this error,
anyone has an idea on how to fix this?
--
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions
-ansi -nostdinc -I- -I.
On 2004-12-08 19:11, Spades [EMAIL PROTECTED] wrote:
After I cvsup'd and recompiling my kernel, it came up with this error,
anyone has an idea on how to fix this?
--
{standard input}: cc: Assembler messages:
Internal compiler error: program cc1 got fatal signal 11{standard
input}:1997:
I'm trying to build a kernel for 4.9 Freebsd that will work on a 486 or
pentium machine and can't get past a make depend error.
'don't know how to make bf_enc.c ...Stop
Error code 2
I've done a minimal install of 4.9, used cvsup to get the lastest /sys
directory. Copied GENERIC to my kernel
Jim McIver wrote:
I'm trying to build a kernel for 4.9 Freebsd that will work on a 486 or
pentium machine and can't get past a make depend error.
'don't know how to make bf_enc.c ...Stop
Error code 2
I've done a minimal install of 4.9, used cvsup to get the lastest /sys
directory. Copied
On Thu, Feb 26, 2004 at 09:58:30PM -0800, Michael Dunham wrote:
I tried to build and install a new kernel tonight and got -
freebie# cd /usr/src
freebie# make kernel KERNCONF=FREEBIE
Makefile.inc1, line 712: warning: String comparison operator should be
either == or !=
Makefile.inc1, line
I tried to build and install a new kernel tonight and got -
freebie# cd /usr/src
freebie# make kernel KERNCONF=FREEBIE
Makefile.inc1, line 712: warning: String comparison operator should be
either == or !=
Makefile.inc1, line 712: Malformed conditional ((!defined(NO_RESCUE) ||
On Wed, 3 Dec 2003 15:29:03 -0800 (PST)
Valerian Galeru [EMAIL PROTECTED] wrote:
I get an error when i make the kernel. Here is my config
file(atached).
Valerius, could you please, please see, read and try to
understand Grog's http://www.lemis.com/questions.html
A few day ago I've said:
I get an error when i make the kernel. Here is my config file(atached).
-
Do you Yahoo!?
Free Pop-Up Blocker - Get it now#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
On Wed, Dec 03, 2003 at 03:29:03PM -0800, Valerian Galeru wrote:
I get an error when i make the kernel. Here is my config file(atached).
You forgot to post the error.
Kris
pgp0.pgp
Description: PGP signature
i have error message on my samba server on freebsd 5.1
FreeBSD bsdbro.fc.com 5.1-RELEASE-p2 FreeBSD 5.1-RELEASE-p2 #1: Sun Aug 24
16:48:49 MYT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDKING
i386
kernel: psmintr: delay too long; reseting byte count
kernel: psmintr: out of sync (0008 !=
Norhisham Khalil wrote:
i have error message on my samba server on freebsd 5.1
FreeBSD bsdbro.fc.com 5.1-RELEASE-p2 FreeBSD 5.1-RELEASE-p2 #1: Sun Aug 24
16:48:49 MYT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BSDKING
i386
kernel: psmintr: delay too long; reseting byte count
kernel:
Hi,
These error messages just started appearing in my /var/log/messages file the
other day. Running FreeBSD 4.7 Stable. Can somebody explain why this is
happening - that appear bogus to me?
Apr 4 03:14:35 typhoon /kernel: pid 48518 (rsync), uid 0 on
/mnt/da1-root/var:file system full
Apr 4
Take a look at the /tmp partition. I suspect rsync is using it for scratch
files ...
According to admin2:
These error messages just started appearing in my /var/log/messages file the
other day. Running FreeBSD 4.7 Stable. Can somebody explain why this is
happening - that appear bogus to me?
Doh! Never mind, I forgot the meaning of the % column in df!!!
Rich
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Sun, 24 Nov 2002 08:42:50 -0800 (PST)
Casey Luttrull [EMAIL PROTECTED] wrote:
Hi,
I compiled my new kernal and called in MYKERNEL. Then
I issue the command
make buildkernel KERNCONF=MYKERNEL.
Everything seems to go fine until the end of the
process it gives my this error:
linking
On Sun, Nov 24, 2002 at 08:42:50AM -0800, Casey Luttrull wrote:
I compiled my new kernal and called in MYKERNEL. Then
I issue the command
make buildkernel KERNCONF=MYKERNEL.
Everything seems to go fine until the end of the
process it gives my this error:
[...]
# SCSI peripherals
#device
On 2002-11-24 17:52, Miguel Mendez [EMAIL PROTECTED] wrote:
On Sun, 24 Nov 2002 08:42:50 -0800 (PST)
Casey Luttrull [EMAIL PROTECTED] wrote:
umass.o(.text+0x1999): undefined reference to `xpt_done'
*** Error code 1
The error is caused by having umass but no scsi...
device
I compiled my new kernal and called in MYKERNEL. Then
I issue the command
make buildkernel KERNCONF=MYKERNEL.
Everything seems to go fine until the end of the
process it gives my this error:
linking kernel
umass.o: In function `umass_cam_attach_sim':
umass.o(.text+0x12bf): undefined reference
53 matches
Mail list logo
