msnk...@mail.ru wrote:
Is any plans to backport ZFSv13 from CURRENT to RELENG7 branxh or not?
AFAIR Pawel explained that he intends to backport it to
RELENG7, but it will take some time because it is a huge
amount of code. Also, it depends on other merges from
-current by other people that are
On Sun, 2009-01-11 at 17:16 +, Pete French wrote:
Here is a better set of images. This machine was compiled
with the following config file:
include GENERIC
ident DEBUG
options KDB
options DDB
options SW_WATCHDOG
options
Oliver Fromme wrote:
On the other hand, 8-current seems to run quite stable at
the moment; I have it running on a workstation for several
weeks without problems.
What date of CURRENT are you running? I tracked down crashes related to
changes in SMBFS, but I am still experiencing almost
On Fri, Jan 9, 2009 at 6:22 PM, Mars G Miro s...@anarchy.in.the.ph wrote:
On Fri, Jan 9, 2009 at 6:14 PM, Mars G Miro s...@anarchy.in.the.ph wrote:
On Fri, Jan 9, 2009 at 5:15 PM, Jack Vogel jfvo...@gmail.com wrote:
[snip]
If you have a back to back connection to another NIC on Port 0, no
I've updagraded a test-webserver to 7.1 when it was released. After a
few days I upgraded a production-webserver to 7.1 on Jan. 8'th and it
has been running without any problems. The webserver is not heavily
loaded (load at 2-3 on average). I have made a buildworld -j 8 and it
runs fine.
If
Andrew Snow wrote:
Oliver Fromme wrote:
On the other hand, 8-current seems to run quite stable at
the moment; I have it running on a workstation for several
weeks without problems.
What date of CURRENT are you running? I tracked down crashes related to
changes in SMBFS, but I
I am also surprised that this isn't more widely reported, as
the hardware is very common. The only oddity with ym compile
is that I set the CPUTYPE to 'core2' - that shouldnt have an effect, but
I will remove it anyway, just so I am actually building a completely
vanilla amd64. That way I
Andrew Snow wrote:
Oliver Fromme wrote:
On the other hand, 8-current seems to run quite stable at
the moment; I have it running on a workstation for several
weeks without problems.
What date of CURRENT are you running? I tracked down crashes related to
changes in SMBFS, but I am still
Is there any plans to include NFSv4 server into FreeBSD?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
System: stable/7 some time before New Year (sorry if this issue has
already been acted upon).
I have a system with perhaps sufficiently rare configuration:
it has fsck_y_enable=YES and it has multiple filesystems mounted
(UFS2), some RW, some RO.
Today I had a chance to see fsck_y_enable in
You don't want WITNESS_KDB, but WITNESS_SKIPSPIN would probably be
sensible to include.
OK, I will take out the WITNESS_KDB. I am reluctant to add in
WITNESS_SKIPSPIN though, as I understand it stops witnessing spin
locks, is that right ? As the only error message I have ever got out
of all fo
It has performed a buildworld without problems and I'll be doing some
buildworlds throughout the day.
This is on a HP c-class-blade with 8 GB ram, 2 x quad-core and the
build-in p200-controller with 64 MB ram.
I've performed five buildworlds decrementing -j from 16 to 6 and I
can't lock up
I've performed five buildworlds decrementing -j from 16 to 6 and I
can't lock up the server.
Mine never lock up doing buildworlds either. They only lock up when they are
sitting there more of less idle! The machines which have never locked up
are the webservers, which are fairly heavlt loaded.
On Fri, 9 Jan 2009, Garance A Drosihn wrote:
At 2:39 PM -0500 1/9/09, Robert Blayzor wrote:
On Jan 8, 2009, at 8:58 PM, Pete French wrote:
I have a number of HP 1U servers, all of which were running 7.0 perfectly
happily. I have been testing 7.1 in it's various incarnations for the last
On Sat, 10 Jan 2009, Pete French wrote:
FWIW, the other guy I know who is having this problem had already switched
to using ULE under 7.0-release, and did not have any problems with it. So
*his* problem was probably not related to SCHED_ULE, unless something has
recently changed there.
I'm not sure if you've done this already, but the normal suggestions apply:
have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do
any results / panics / etc result? Sometimes these debugging tools are able
to convert hangs into panics, which gives us much more ability
On 2009-01-12 07:41, Pyun YongHyeon wrote:
I see, Unfortunately the issue was fixed in the end of 7.1-R
release process so I wanted to get more exposure before MFC.
I'll make sure to MFC to stable/7 after more testing.
I'm also having problems with re's, in my case the interfaces take about
10
Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE make installworld. I think
this implies it's a kernel driver issue.
r187106 syncs the Makefiles with HEAD so that RELENG_7 has the same set
of build knobs. Let me know if you see any oddities that you can trace
to this commit.
Sam
___
freebsd-stable@freebsd.org mailing list
Hello,
I am attempting to get by broadcom wifi card up and running, am sick of
trying to get ndis working, and am attempting to use the bwi driver
(originating in dragonflyBSD). I'm hoping others here have tried to do the
same and have some pointers. I'm using 7.1-RELEASE (system/source are
Hello, FreeBSD-stable.
Last week I have a lot of kernel panics like:
[r...@router1 /usr/obj/usr/src/sys/TINCOKERNEL2]# kgdb kernel.debug
/var/crash/vmcore.20
[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
On 1/12/09, Neal Hogan nealho...@gmail.com wrote:
Hello,
I am attempting to get by broadcom wifi card up and running, am sick of
trying to get ndis working, and am attempting to use the bwi driver
(originating in dragonflyBSD). I'm hoping others here have tried to do the
same and have
firmware_get: failed to load firmware image bwi_v3_ucode4
bwi0: request firmware bwi_v3_ucode4 failed
bwi0: bwi_stop
looks like here is a problem
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
At 2:55 PM + 1/12/09, Robert Watson wrote:
On Fri, 9 Jan 2009, Garance A Drosihn wrote:
At 2:39 PM -0500 1/9/09, Robert Blayzor wrote:
On Jan 8, 2009, at 8:58 PM, Pete French wrote:
I have a number of HP 1U servers, all of which were running 7.0
perfectly happily. I have been testing 7.1
I'm not sure if you've done this already, but the normal suggestions apply:
have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do
any results / panics / etc result? Sometimes these debugging tools are able
to convert hangs into panics, which gives us much more ability
Just to followup on this: My friend did switch back to a 7.1 kernel with
SCHED_4BSD, and he still ran into problems. The error messages weren't
Acually, I dont know if I posted it, but that was the same for me too.
The scheduler makes no difference, nor do CPU copile settings.
-pete.
I installed the firmware stuff from the dragonfly bwi(4) man page, yet I
have the same issue. Is there a way to tell whether the firmware they
provide supports my card? Like I said, I can locate my access point (and
others that are around) and ask for an IP . . . it seems as though I'm so
close.
On Mon, Jan 12, 2009 at 8:08 PM, Neal Hogan nealho...@gmail.com wrote:
I installed the firmware stuff from the dragonfly bwi(4) man page, yet I
have the same issue. Is there a way to tell whether the firmware they
provide supports my card? Like I said, I can locate my access point (and
others
Hello,
I have similar problems. The last good kernel I have from stable
brach, october the 8. Then in next upgrade, I saw big problems with
performance.
I tried ULE, 4BSD etc, but nothing helps, only downgrading system back.
Now I am trying 7.1-p1 and problems are here again. Mysql is
I have similar problems. The last good kernel I have from stable brach,
october the 8. Then in next upgrade, I saw big problems with performance.
I tried ULE, 4BSD etc, but nothing helps, only downgrading system back.
Now I am trying 7.1-p1 and problems are here again. Mysql is waiting a lot
Pyun,
I was able to perform a full source downgrade to 7.0 and all the
problems went away. Curiously, re0 and re1 have reversed names --
what was re0 is now re1, and vice versa. I need my box to be up and
working so I can't throw 7.1 on it again. If I can offer any data
from 7.0, please let me
Hi,
Fabio Checconi and myself have developed a GEOM-based disk scheduler
for FreeBSD. The scheduler is made of a GEOM kernel module, the
corresponding userland claas library, and other loadable kernel
modules that implement the actual scheduling algorithm.
At the URL below you can find a tarball
Pyun YongHyeon a écrit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is 7.0-RELEASE-p7 completely alleviates all
WV problems. I believe this roundly confirms that this is
On Mon, 12 Jan 2009, Tomas Randa wrote:
I have similar problems. The last good kernel I have from stable brach,
october the 8. Then in next upgrade, I saw big problems with performance. I
tried ULE, 4BSD etc, but nothing helps, only downgrading system back.
Now I am trying 7.1-p1 and
On Mon, 12 Jan 2009, Pete French wrote:
I'm not sure if you've done this already, but the normal suggestions apply:
have you compiled with INVARIANTS/WITNESS/DDB/KDB/BREAK_TO_DEBUGGER, and do
any results / panics / etc result? Sometimes these debugging tools are
able to convert hangs into
On Mon, 12 Jan 2009, Garance A Drosihn wrote:
He is not eager to do a whole lot of experiments to track down the problem,
since this is happening on busy production machines and he can't afford to
have a lot of downtime on them (especially now that the semester at RPI has
started up). The
Ivan Voras wrote:
Andrew Snow wrote:
Oliver Fromme wrote:
On the other hand, 8-current seems to run quite stable at
the moment; I have it running on a workstation for several
weeks without problems.
What date of CURRENT are you running? I tracked down crashes related to
changes in SMBFS, but
TB --- 2009-01-12 23:22:06 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-01-12 23:22:06 - starting RELENG_7 tinderbox run for powerpc/powerpc
TB --- 2009-01-12 23:22:06 - cleaning the object tree
TB --- 2009-01-12 23:22:27 - cvsupping the source tree
TB --- 2009-01-12 23:22:27 -
Andriy Gapon wrote:
To me it seems like fsck_y passes suboptimal flags to fsck, it doesn't
have to examine each and every filesystem in fstab.
I think think this is because it does a quick check first to see if it
can run the fsck in background after boot into multi-user mode.
If it
On Mon, Jan 12, 2009 at 05:11:02PM -0500, FreeBSD wrote:
Pyun YongHyeon a ?crit :
On Sun, Jan 11, 2009 at 07:22:06PM +0300, Eugene Gladchenko wrote:
Walter,
Thursday, January 8, 2009, 2:50:40 AM, you wrote:
WV Booting kernel.old, which is 7.0-RELEASE-p7 completely
On Monday 12 January 2009 12:21 pm, Sascha Holzleiter wrote:
Walter Venable wrote:
FreeBSD 7.1 upgrade broke my network access, machine is totally
offline (powered-on and I can play inside it at the terminal, but
absolutely 0 network access):
This happened AFTER make kernel but BEFORE
TB --- 2009-01-13 00:31:07 - tinderbox 2.6 running on freebsd-stable.sentex.ca
TB --- 2009-01-13 00:31:07 - starting RELENG_7 tinderbox run for sparc64/sparc64
TB --- 2009-01-13 00:31:07 - cleaning the object tree
TB --- 2009-01-13 00:31:22 - cvsupping the source tree
TB --- 2009-01-13 00:31:22 -
On Mon, Jan 12, 2009 at 2:00 PM, Luigi Rizzo ri...@icir.org wrote:
Hi,
Fabio Checconi and myself have developed a GEOM-based disk scheduler
for FreeBSD. The scheduler is made of a GEOM kernel module, the
corresponding userland claas library, and other loadable kernel
modules that implement
I tried to export/unmount my zpool:
# zpool export tank
cannot unmount '/tank': Device busy
# zfs unmount /tank
cannot unmount '/tank': Device busy
but it wouldn't, so, after closing everything that could be using it, I
tried again. No luck. Then I tried to see if I forgot something:
#
On Mon, Jan 12, 2009 at 05:37:39PM +0100, Dimitry Andric wrote:
On 2009-01-12 07:41, Pyun YongHyeon wrote:
I see, Unfortunately the issue was fixed in the end of 7.1-R
release process so I wanted to get more exposure before MFC.
I'll make sure to MFC to stable/7 after more testing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Garrett Cooper wrote:
On Mon, Jan 12, 2009 at 2:00 PM, Luigi Rizzo ri...@icir.org wrote:
Hi,
Fabio Checconi and myself have developed a GEOM-based disk scheduler
for FreeBSD. The scheduler is made of a GEOM kernel module, the
corresponding
David Ehrmann wrote:
# fstat -m /tank
I guess I should have used a different flag, but no luck there, either
USER CMD PID FD MOUNT INUM MODE SZ|DV R/W
NAME
# lsof | grep tank
nothing
I did fix it. I had a runaway bash process (that kill -s HUP fixed,
oddly
On Mon, Jan 12, 2009 at 06:45:13PM -0800, Garrett Cooper wrote:
On Mon, Jan 12, 2009 at 2:00 PM, Luigi Rizzo ri...@icir.org wrote:
Hi,
Fabio Checconi and myself have developed a GEOM-based disk scheduler
for FreeBSD. The scheduler is made of a GEOM kernel module, the
corresponding
48 matches
Mail list logo
