This is a really old thread i thought i would bring back to life. I have heard
that the flash card vendor has fessed up to a problem and said there is a
software fix they can create. So far i have no ETA on when that is going to
happen and for the record i don't think i will.
Oh well... here
@freebsd.org
Sent: Tuesday, February 14, 2012 7:57 PM
Subject: Re: 6.2-Release ..ish.. CF + ata == freeze?
2 of the 3 cf cards are very new, like less then 6 months old.
I think around 65-70 percent is in use. This number doesn't change unless the
user dumps data in a home dir, which isn't the case so
On Tue, 2012-02-14 at 00:12 -0500, Jason Hellenthal wrote:
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a
large install base
: Jeremy Chadwick free...@jdc.parodius.com
Date: Mon, 13 Feb 2012 21:18:28
To: john flemingjfleming...@yahoo.com
Cc: freebsd-stable@freebsd.orgfreebsd-stable@freebsd.org
Subject: Re: 6.2-Release ..ish.. CF + ata == freeze?
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
Just thought i
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a large
install base of IPSO checkpoint firewalls, which are based on FreeBSD 6.2. I've
had 3 firewalls hang basically the same way, with something
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a
large install base of IPSO checkpoint firewalls, which are based on FreeBSD
6.2.
On Mon, Feb 13, 2012 at 08:43:08PM -0800, john fleming wrote:
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a
large install base of IPSO checkpoint firewalls, which are based on FreeBSD
6.2.
I can't seem to replicate it at all. I've seen it happen on 3 different IPSO
boxes so far. The last machine it happened on is maybe 4 months old. Basically
on all 3 machines once rebooted the problem doesn't come back. Checkpoint so
far is telling me its a known issue and they don't know what
On Mon, Feb 13, 2012 at 10:43 PM, john fleming jfleming...@yahoo.comwrote:
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a
large install base of IPSO checkpoint firewalls, which are based on
On Mon, Feb 13, 2012 at 11:38:06PM -0600, Adam Vande More wrote:
On Mon, Feb 13, 2012 at 10:43 PM, john fleming jfleming...@yahoo.comwrote:
Just thought i would post over here as i'm not getting a warm fuzzy from
checkpoint about being able to find the root cause of an issue. I have a
On Wednesday 25 April 2007 4:47:48 am Alex Povolotsky wrote:
Hello!
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable shows
cluster-one# mptable -verbose
6.2 is really quite old now, does 7.x or even 8.x work?
Regards
Steve
- Original Message -
From: Alex Povolotsky tark...@webmail.sub.ru
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable shows
On Fri, Feb 08, 2008 at 02:40:41PM +, Primeroz lists wrote:
#7 0x802af5e3 in _sx_xlock (sx=0x802b02bd, file=0x4
Address 0x4 out of bounds, line=-2140937936)
at /usr/src/sys/kern/kern_sx.c:192
192 }
Well, the file and line are nonsense.
#17 0x802b845e in
Server keeps crashing, I maged to have a new coredump that should be
reliable this time.
Here is the debugging of the kernel ... i'm not really an expert in this
topic so if you need any more information just let me know and i will do my
best to provide it.
[GDB will not be able to debug
, Tom Samplonius [EMAIL PROTECTED] wrote:
- Primeroz lists [EMAIL PROTECTED] wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or
2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following
I have a 6.1-release machine that I wanted to upgrade, so I decided I would
upgrade to 6.2-rel, and then to 7-pre.
When I upgraded to 6.2-rel, it fails at mountroot, claiming that it can't
find ad0s1a to boot from. (Entering ? to list all available boot devices
only lists acd0 and ad2*,
- Primeroz lists [EMAIL PROTECTED] wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or
2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
set-variable
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
set-variable= key_buffer=768M
set-variable= table_cache=800
set
On Mon, Feb 04, 2008 at 12:50:32PM +, Primeroz lists wrote:
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
{snip}
There's
Just wanted to point out that anyway our crash is a Kernel panic crash and
not a Mysqld crash.
Platform is AMD64 so , i'm don't think it can be a problem of process size :
$ sudo -u mysql limits
Resource limits (current):
cputime infinity secs
filesize infinity kB
There's additional information needed to help with this:
1) Contents of /boot/loader.conf
empty
2) What scheduler you're using in your kernel configuration
We using the 4bsd Scheduler (ULE is commented out in kernel conf)
3) Your kernel configuration in its entirity, if possible
On Mon, Feb 04, 2008 at 12:50:32PM +, Primeroz lists wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
set
On Mon, Feb 04, 2008 at 02:50:09PM +, Primeroz lists wrote:
Just wanted to point out that anyway our crash is a Kernel panic crash and
not a Mysqld crash.
But the process that's inducing the panic *every time* is mysqld; this
you've already confirmed. To me this means that mysqld is
On Mon, Feb 04, 2008 at 04:35:13PM +, Primeroz lists wrote:
The vm_map.c does not contain a call to the vm_map_unlock() at the
line 3074.
Mine does ... is Revision *1.366.2.3 *on Freebsd CVS for vm_map.c , CVS TAG
RELENG_6_2
Not according to either the kgdb output you included or
We use mysql-server-5.0.45 (fairly old, since newest is 5.0.51a); yours
is a bit older. I'll have to look at the ChangeLog between 5.0.41 and
5.0.51a to see if there's any relevant changes which might give hints to
what's causing it.
I don't see any changes relevant between 5.0.41 and
The vm_map.c does not contain a call to the vm_map_unlock() at the
line 3074.
Mine does ... is Revision *1.366.2.3 *on Freebsd CVS for vm_map.c , CVS TAG
RELENG_6_2
Please, rebuild you kernel from scratch. In case this does not help,
I ask you to show the backtrace from the ddb. Also, to
On Mon, Feb 04, 2008 at 07:04:19AM -0800, Jeremy Chadwick wrote:
But the process that's inducing the panic *every time* is mysqld; this
you've already confirmed. To me this means that mysqld is responsible
for tickling some sort of condition that causes a panic; it could be the
fault of mysqld or
On Mon, Feb 04, 2008 at 02:19:05PM +, Primeroz lists wrote:
We using the 4bsd Scheduler (ULE is commented out in kernel conf)
That's good, as it confirms you're not hitting ULE bugs.
3) Your kernel configuration in its entirity, if possible :-)
attached
I don't see anything in your
Primeroz lists wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
SNIP
$ sudo kgdb /usr/obj/usr/src/sys/PE2950/kernel.debug vmcore.2
SNIP
This back trace will be useless, I
Hi,
It seems you can't recursively use the include rule specification with devfs
in Freebsd 6.2. I couldn't see a note about this in the devfs man page so I'm
not sure whether this is expected behaviour or not.
For example, the devfsrules_jail is defined as the following
in
On Wed, Jan 02, 2008 at 06:23:52PM +1100, Geoff Roberts wrote:
Hi,
It seems you can't recursively use the include rule specification
with devfs in Freebsd 6.2. I couldn't see a note about this in the
devfs man page so I'm not sure whether this is expected behaviour or
not.
The manpages for
FreeBSD 6.2-RELEASE on Intel P4
3.0GHz,
512MB Ram computer.
Its very irritatingly hangs very frequently,
more
than
10 times a day. Do others find FreeBSD
6.2-RELEASE
always hangs? I simply cannot use it for any
serious
use, not even to send a mail, other
Unga wrote:
Mine is also an ATI Radeon card:
ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1
Chipset ATI Radeon 9200PRO 5960 (AGP)
I cannot ssh to the machine while its freezes. It says
'no route to host'. That is, the machine is completely
dead.
The other thing is, FreeBSD
--- Michael Proto [EMAIL PROTECTED] wrote:
Unga wrote:
Hi all
I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz,
512MB Ram computer.
Its very irritatingly hangs very frequently, more
than
10 times a day. Do others find FreeBSD 6.2-RELEASE
always hangs? I simply cannot use
On Thu, 2007-11-29 at 03:28 -0800, Unga wrote:
--- Michael Proto [EMAIL PROTECTED] wrote:
Unga wrote:
Hi all
I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz,
512MB Ram computer.
Its very irritatingly hangs very frequently, more
than
10 times a day. Do others find
From: Tom Evans [EMAIL PROTECTED]
Date: Thu, 29 Nov 2007 12:42:35 +
Sender: [EMAIL PROTECTED]
On Thu, 2007-11-29 at 03:28 -0800, Unga wrote:
--- Michael Proto [EMAIL PROTECTED] wrote:
Unga wrote:
Hi all
I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz,
512MB Ram
On Thu, Nov 29, 2007 at 08:37:05AM -0800, Kevin Oberman wrote:
...
Can you verify that the machine is actually dead? Do you have another
machine that you can hook up either to a serial console, or ssh into the
dead box? Weird X symptoms could lead to an unresponsive keyboard, with
the
Hi all
I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz,
512MB Ram computer.
Its very irritatingly hangs very frequently, more than
10 times a day. Do others find FreeBSD 6.2-RELEASE
always hangs? I simply cannot use it for any serious
use, not even to send a mail, other than browsing web.
I
Unga wrote:
Hi all
I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz,
512MB Ram computer.
Its very irritatingly hangs very frequently, more than
10 times a day. Do others find FreeBSD 6.2-RELEASE
always hangs? I simply cannot use it for any serious
use, not even to send a mail, other
Hi,
Unga wrote:
Hi all
I'm using FreeBSD 6.2-RELEASE on Intel P4 3.0GHz,
512MB Ram computer.
Its very irritatingly hangs very frequently, more than
10 times a day. Do others find FreeBSD 6.2-RELEASE
always hangs? I simply cannot use it for any serious
use, not even to send a mail, other than
On Nov 28, 2007 5:15 PM, Unga [EMAIL PROTECTED] wrote:
10 times a day. Do others find FreeBSD 6.2-RELEASE
always hangs?
no
coincidental. How do I find why it hangs?
hardware problem, i suppose.
broken cpu fan?
--
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org
point.
Unfortunately I did not have the luxury to embroil myself in debug hell
with this problem since this is my mail/web machine and others depend on
it. I can tolerate some downtime, but this was just getting to be too
much. I just backed up the system, and installled FreeBSD 6.2-RELEASE from
Hi,
I just csup'd the sources a few hours ago, and successfully compiled and
installed a new kernel. However, when I go to do a buildworld, this
comes up:
--
stage 2.3: build tools
, assuming that I botched the source
upgrade somehow. After installing FreeBSD 6.2-RELEASE, I was left with a
system that would not boot (similar errors on boot as before). Reverting
the kernel of course was of limited help because userland was all expecting
6.2. So, I had a couple of tarballs
On Nov 11, [LoN]Kamikaze wrote:
That's strange, I've gone right from 5.3 through to RELENG_7 without ever
doing the reboots during the install process (I know that's not
recommended) and I never ran into trouble. Did you accidently turn off
compat6x in the kernel before you built? Did your
Clint Olsen wrote:
I attempted to just do a binary upgrade, assuming that I botched the source
upgrade somehow. After installing FreeBSD 6.2-RELEASE, I was left with a
system that would not boot (similar errors on boot as before).
Any chance you could post some of these error messages
On Nov 11, Dimitry Andric wrote:
Any chance you could post some of these error messages? And if possible,
backtraces, etc?
The messages amounted to page fault while in kernel mode or similar. The
problem is the system attempts to reboot itself within 15 seconds. I know
there is a way to
Quoting Clint Olsen [EMAIL PROTECTED]:
On Nov 11, Dimitry Andric wrote:
Any chance you could post some of these error messages? And if possible,
backtraces, etc?
The messages amounted to page fault while in kernel mode or similar. The
problem is the system attempts to reboot itself within
botched the source
upgrade somehow. After installing FreeBSD 6.2-RELEASE, I was left with a
system that would not boot (similar errors on boot as before). Reverting
the kernel of course was of limited help because userland was all expecting
6.2. So, I had a couple of tarballs from my last backup and I
So I have southbridge VT8237A and two(!) HDDs attached to SATA chanels of this
controller. I Prefer to have RAID on it.
When I install FreeBSD 6.2-RELEASE (from floppies) it`s detected only one HDD
and
write that my RAID storage DEGRADED... I think that it is a bug in the kernel.
I`m right
On Sun, Oct 28, 2007 at 04:57:07PM +0300, ?? wrote:
So I have southbridge VT8237A and two(!) HDDs attached to SATA chanels of
this
controller. I Prefer to have RAID on it.
When I install FreeBSD 6.2-RELEASE (from floppies) it`s detected only one HDD
and
write that my RAID
I have had a couple questions about using the driver that I just put
into STABLE on 6.2 RELEASE.
Right now it won't compile, this is because I put the MSI/X support
in the clear, figuring 'well, this is STABLE so why should I #ifdef :)'.
I should have known better, and of course the driver code
On 10/11/07, Jack Vogel [EMAIL PROTECTED] wrote:
I have had a couple questions about using the driver that I just put
into STABLE on 6.2 RELEASE.
Right now it won't compile, this is because I put the MSI/X support
in the clear, figuring 'well, this is STABLE so why should I #ifdef :)'.
I
On 10/11/07, David Yeske [EMAIL PROTECTED] wrote:
On 10/11/07, Jack Vogel [EMAIL PROTECTED] wrote:
I have had a couple questions about using the driver that I just put
into STABLE on 6.2 RELEASE.
Right now it won't compile, this is because I put the MSI/X support
in the clear, figuring
On 10/11/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 10/11/07, David Yeske [EMAIL PROTECTED] wrote:
On 10/11/07, Jack Vogel [EMAIL PROTECTED] wrote:
I have had a couple questions about using the driver that I just put
into STABLE on 6.2 RELEASE.
Right now it won't compile
I realize now that I need to explain doing this.
I just did a checkin that will allow the latest em code
to work on 6.2, BUT, it will NOT work integrated into
the RELEASE kernel tree, and I am not going to
support that :) To do that would mean changing
conf/files and so forth.
Therefore, if you
Hi:
Im getting a Fatal trap 12 from a freebsd 6.2 release p7, how can i
report it and get help??
Oct 2 02:39:37 freebsd kernel:
Oct 2 02:39:37 freebsd kernel:
Oct 2 02:39:37 freebsd kernel: Fatal trap 12: page fault while in kernel mode
Oct 2 02:39:37 freebsd kernel: cpuid = 0; apic id = 00
On Tue, Oct 02, 2007 at 02:55:08PM -0500, Natham wrote:
Hi:
Im getting a Fatal trap 12 from a freebsd 6.2 release p7, how can i
report it and get help??
Check
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
on how to obtain needed information.
--
Yuri
---
uname -a
FreeBSD x.x.x 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55
UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
i386
---
cat /etc/rc.conf
defaultrouter=x.x.x.x
font8x14=cp865-8x14
font8x16=cp865-8x16
font8x8=cp865-8x8
hostname=x.x.x
ifconfig_em1=inet
Last night I ran freebsd-update install and rebooted. Even thought
the update said -p6, when it rebooted uname -s continues to reboot -
p4 on all systems.
However, since the reboot rrdtool is dumping core periodically. It
doesn't happen on non-updated systems. I've deinstalled and rebuilt
I found the problem here. At some point in the past a rowless-RRA was
added to the files handled by this one process. I have no idea why it
only showed up after the reboot, but it's unrelated to FreeBSD anyway.
On Wed, Aug 01, 2007 at 01:06:08PM -0700, Jo Rhett wrote:
Last night I ran
and test, re-build my
kernel with any options changed and test again.. Just don't Work :((
I have use PF firewall and FreeBSD 6.2-RELEASE-p5.
I Think this problem is from net.inet.tcp.blackhole=2 in my sysctl because
it's work before i do sysctl -w net.inet.tcp.blackhole=2..
but when back
kern.securelevel: -1 and the permessions on /bin and / is the correct :[
2007/6/15, Jeremy Chadwick [EMAIL PROTECTED]:
On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote:
My problem is with the installing new world in my system, this is the
error
=== bin (install)
=== bin/cat
I do chflags noschg /bin and its work :)
2007/6/15, ExTaZyTi [EMAIL PROTECTED]:
kern.securelevel: -1 and the permessions on /bin and / is the correct :[
2007/6/15, Jeremy Chadwick [EMAIL PROTECTED]:
On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote:
My problem is with the
ExTaZyTi wrote:
Hi,
My problem is with the installing new world in my system, this is the error
=== bin (install)
=== bin/cat (install)
install -s -o root -g wheel -m 555 cat /bin
strip: /bin/sthZDAzl: Operation not permitted
install: wait: Operation not permitted
*** Error code 70
Stop in
Hi,
My problem is with the installing new world in my system, this is the error
=== bin (install)
=== bin/cat (install)
install -s -o root -g wheel -m 555 cat /bin
strip: /bin/sthZDAzl: Operation not permitted
install: wait: Operation not permitted
*** Error code 70
Stop in /usr/src/bin/cat.
On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote:
My problem is with the installing new world in my system, this is the error
=== bin (install)
=== bin/cat (install)
install -s -o root -g wheel -m 555 cat /bin
strip: /bin/sthZDAzl: Operation not permitted
install: wait:
Hello!
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable shows
cluster-one# mptable -verbose
===
MPTable
looking for EBDA pointer
Kris Kennaway wrote:
On Fri, Apr 20, 2007 at 12:08:57PM -0700, Kevin Oberman wrote:
Date: Fri, 20 Apr 2007 22:54:52 +0400
From: Alexey Karagodov [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
and what is this, i mean why:
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING:
please, dmesg, mptable -verbose, mptable -grope
2007/4/25, Alex Povolotsky [EMAIL PROTECTED]:
Kris Kennaway wrote:
On Fri, Apr 20, 2007 at 12:08:57PM -0700, Kevin Oberman wrote:
Date: Fri, 20 Apr 2007 22:54:52 +0400
From: Alexey Karagodov [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
and
, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p3 #5: Wed Apr 25 13:37:13 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D
Timecounter i8254 frequency 1193182 Hz
Alex Povolotsky wrote:
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable shows
Hyperthreading is disabled by default in FreeBSD (for
security reasons). You can enable it via sysctl if
you want
On Wednesday 25 April 2007 04:47:48 am Alex Povolotsky wrote:
Hello!
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable shows
cluster-one# mptable -verbose
John Baldwin wrote:
On Wednesday 25 April 2007 04:47:48 am Alex Povolotsky wrote:
Hello!
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable
shows
Hmm. I am running PentiumD 3.0 Ghz on Asus p5p800-vm
motherboard
John Baldwin wrote:
On Wednesday 25 April 2007 04:47:48 am Alex Povolotsky wrote:
Hello!
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running on it, and mptable shows
cluster-one# mptable -verbose
On Wednesday 25 April 2007 03:20:05 pm Alex Povolotsky wrote:
John Baldwin wrote:
On Wednesday 25 April 2007 04:47:48 am Alex Povolotsky wrote:
Hello!
I have a Pentium D box, running 6.2-RELEASE. In dmesg, I see CPU#1
launched, but I never see any process running
Hi,
Just got this panic on a loaded mailserver ... The server was rocking stable
up to this panic, and after we loaded it a bit more recently, it paniced.
Any ideas ?
--
Martin
#0 doadump () at pcpu.h:165
#1 0xc067550a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2
Martin Blapp wrote:
Hi,
Just got this panic on a loaded mailserver ... The server was rocking
stable
up to this panic, and after we loaded it a bit more recently, it paniced.
Any ideas ?
Can you post your kernel configuration file?
Alan
___
The server has two CPUs. The only special thing
is that with the current BIOS ACPI is broken.
--
Martin
FreeBSD 6.2-RELEASE #0: Tue Jan 23 11:13:16 CET 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.13-MHz 686
of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 19 00:19:54 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network stack disabled, expect reduced performance.
Timecounter i8254 frequency 1193182 Hz
, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 19 00:19:54 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D
WARNING: debug.mpsafenet forced to 0
only one.
(from dmesg)
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p3
Date: Fri, 20 Apr 2007 22:54:52 +0400
From: Alexey Karagodov [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
and what is this, i mean why:
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network stack disabled, expect reduced performance.
I thought it was pretty
On Fri, Apr 20, 2007 at 12:08:57PM -0700, Kevin Oberman wrote:
Date: Fri, 20 Apr 2007 22:54:52 +0400
From: Alexey Karagodov [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
and what is this, i mean why:
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network
reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 19 00:19:54 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network stack disabled, expect reduced performance
of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 19 00:19:54 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/P4D
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network stack
We have been having rampant issues using Dummynet's IPv6 support, and
it's been causing panic's every 24-48 hours.
Enabled WITNESS and BREAK_TO_DEBUGGER, and this is the result.
-=-
lock order reversal: (sleepable after non-sleepable)
1st 0xff034809c900 rtentry (rtentry) @
Hello,
I've got these repeatable crashes with:
klon# uname -a
FreeBSD klon.klsp.kharkov.ua 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #7:
Fri Mar 23 11:26:01 EET 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/KLON i386
the system is running quagga and l2tpd built from the yesterday's ports.
I
Gregory Edigarov wrote:
Hello,
I've got these repeatable crashes with:
klon# uname -a
FreeBSD klon.klsp.kharkov.ua 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #7:
Fri Mar 23 11:26:01 EET 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/KLON i386
the system is running quagga and l2tpd built from
On Fri, Mar 23, 2007 at 02:25:44PM +0200, Gregory Edigarov wrote:
Hello,
I've got these repeatable crashes with:
klon# uname -a
FreeBSD klon.klsp.kharkov.ua 6.2-RELEASE-p3 FreeBSD 6.2-RELEASE-p3 #7:
Fri Mar 23 11:26:01 EET 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/KLON i386
Kris Kennaway [EMAIL PROTECTED] writes:
Hello,
Not use kernel ppp, which is known to be broken. I don't know what
this means for your application.
Sorry to hijack this thread but is there any way to mimic the following
pppd invocation with mpd or ppp(8) :
/usr/sbin/pppd
LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
Yes, that would be very useful. But it should also take
any includes into account.
It was very annoying to discover that INCLUDE_CONFIG_FILE
gave me only two lines for
Oliver Fromme wrote:
LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
Yes, that would be very useful. But it should also take
any includes into account.
It was very annoying to discover that INCLUDE_CONFIG_FILE
LI Xin wrote:
Oliver Fromme wrote:
LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
Yes, that would be very useful. But it should also take
any includes into account.
It was very annoying to
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track down what changed! I don't think it should
ever be
Pete French wrote:
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track down what changed! I don't
On Mon, 19 Mar 2007 11:31:54 +
Pete French [EMAIL PROTECTED] wrote:
I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
the GENERIC kernel from RELEASE properly. The kernel
I have running on it is a binary from elsewherre which was built from the 6.2
RELEASE code, but I no longer have the options it was built with (though
I can tell it does not contain IPv6). Hence I want to make sure that the
problem
absolutely
sure that it runs the GENERIC kernel from RELEASE properly. The kernel
I have running on it is a binary from elsewherre which was built from the 6.2
RELEASE code, but I no longer have the options it was built with (though
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
I think this is a very good idea, I've been caught at least once
not being able to recreate a working kernel due to the loss of
the original config file.
Steve
- Original Message -
From: LI Xin [EMAIL PROTECTED]
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
1 - 100 of 218 matches
Mail list logo
