Before all upgrade system never crash.
After upgrade system month ago happens every day Kernel panic "rtfree 2" at
rtfree
route_output
sosend_generic
soo_write
dofilewrite
kernwrite
write
syscallenter
syscall
Xfast_syscall
Now I upgraded to FreeBSD 9.0-BETA1 #32 r224760M and problem exist.
__
hi there,
running r224715 i'm having no problems what so ever. after upgrading my kernel
to r224784, i'm experiencing fatal lock ups, where only a hard reset will
resolve the problem.
the lock up happend two times while running chromium with only a decent number
of tabs (~ 5). also the lock up oc
On Aug 12, 2011, at 12:20 AM, Navdeep Parhar wrote:
> On Thu, Aug 11, 2011 at 07:26:36PM -0400, Michael Butler wrote:
>> I'm not seeing any of today's SVN src updates flow through to CVS/CSUP.
>> Is it broken?
>
> Could it be because of r224768? I vaguely recall that "svn mv" bothers
> whatever
It would help to know your configuration. Also, can you furnish us with a core?
On Fri, Aug 12, 2011 at 9:02 AM, Andrey Smagin wrote:
> Before all upgrade system never crash.
> After upgrade system month ago happens every day Kernel panic "rtfree 2" at
> rtfree
> route_output
> sosend_generic
> s
Hi,
thank you very much for your review and related fixes.
On Fri, Aug 12, 2011 at 3:48 AM, Li, Qing wrote:
>> I have no problem with loopback routes when I work with not
>> point-to-point interfaces as I can NOT set same source address on
>> them. However, if the interface is going down and
On 12 Aug 2011, at 13:11, Bjoern A. Zeeb wrote:
>
> On Aug 12, 2011, at 12:20 AM, Navdeep Parhar wrote:
>
>> On Thu, Aug 11, 2011 at 07:26:36PM -0400, Michael Butler wrote:
>>> I'm not seeing any of today's SVN src updates flow through to CVS/CSUP.
>>> Is it broken?
>>
>> Could it be because o
Alexander Best writes:
> hi there,
>
> running r224715 i'm having no problems what so ever. after upgrading my kernel
> to r224784, i'm experiencing fatal lock ups, where only a hard reset will
> resolve the problem.
>
> the lock up happend two times while running chromium with only a decent numb
On Fri Aug 12 11, Test Rat wrote:
> Alexander Best writes:
>
> > hi there,
> >
> > running r224715 i'm having no problems what so ever. after upgrading my
> > kernel
> > to r224784, i'm experiencing fatal lock ups, where only a hard reset will
> > resolve the problem.
> >
> > the lock up happend
on 28/07/2011 17:09 Andriy Gapon said the following:
> $ fgrep -w -r CS drm
> ...
> drm/include/drm/drm_mode.h:#define DRM_MODE_FLAG_NCSYNC (1<<8)
> $ fgrep -w -r CSY drm
> ...
> drm/include/drm/drm_mode.h:#define DRM_MODE_FLAG_NCSYNC (1<<8)
> $ fgrep -w -r CSYN drm
> (exit 1)
> $ fgrep -w -r NCS
12 августа 2011, 16:31 от Kip Macy :
> It would help to know your configuration. Also, can you furnish us with a
> core?
>
This is my kernel conf:
cpu HAMMER
ident SAM
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
options SCHED_ULE # ULE scheduler
options PREEMPTION # Enable ke
On ia64 r221488
# cd /usr/ports/lang/perl5.14/
# make test
isitmychild: rmatrix mismatch between pipe mutex (index 5) and select mtxpool (i
ndex 447): w_rmatrix[5][447] == 1 but w_rmatrix[447][5] == 4
KDB: stack backtrace:
panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/ia64
On Fri, Aug 12, 2011 at 03:19:04PM +0100, Anton Shterenlikht wrote:
> On ia64 r221488
>
> # cd /usr/ports/lang/perl5.14/
> # make test
>
> isitmychild: rmatrix mismatch between pipe mutex (index 5) and select mtxpool
> (i
> ndex 447): w_rmatrix[5][447] == 1 but w_rmatrix[447][5] == 4
> KDB: stac
On Aug 12, 2011, at 11:32 AM, Andrey Smagin wrote:
>
> 12 августа 2011, 16:31 от Kip Macy :
>> It would help to know your configuration. Also, can you furnish us with a
>> core?
>>
> This is my kernel conf:
>
> cpu HAMMER
> ident SAM
>
[snip]
> options RADIX_MPATH
Can you try it without RADI
12 августа 2011, 19:05 от Luiz Otavio O Souza :
On Aug 12, 2011, at 11:32 AM, Andrey Smagin wrote:
>
> 12 августа 2011, 16:31 от Kip Macy :
>> It would help to know your configuration. Also, can you furnish us with a
>> core?
>>
> This is my kernel conf:
>
> cpu HAMMER
> ident SAM
>
[snip]
On Fri Aug 12 11, Test Rat wrote:
> Alexander Best writes:
>
> > hi there,
> >
> > running r224715 i'm having no problems what so ever. after upgrading my
> > kernel
> > to r224784, i'm experiencing fatal lock ups, where only a hard reset will
> > resolve the problem.
> >
> > the lock up happend
I'm not being able to get my DVD-ROM recognized under 9-current,
although I used the 8.2-release DVD to install FreeBSD (and then
subsequently upgraded the system to the "head" version via svn-freebsd).
1) There is no /dev/*cd* ANYTHING at any time.
NOTE: I'm using a kernel (built with clang)
This is pretty bizarre. I have been experimenting with a very simple driver
(see source below) which essentially checks the PCI vendor and Device ID's in
the probe routine. The attach and detach are empty functions. When I run
kldload and load the driver in a system with HBAs which have a valid
On 12.08.2011 22:33, Alexander Burchell wrote:
I'm not being able to get my DVD-ROM recognized under 9-current,
although I used the 8.2-release DVD to install FreeBSD (and then
subsequently upgraded the system to the "head" version via svn-freebsd).
1) There is no /dev/*cd* ANYTHING at any time.
Hi,
I think I know what the problem is. It is due to the RADIX_MPATH code.
I hope to have a fix soon.
--Qing
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Luiz Otavio O Souza
> Sent: Friday, August 12, 2011 8:0
On Aug 12, 2011, at 7:19 AM, Anton Shterenlikht wrote:
> On ia64 r221488
Please update to at least r223700, as that was a major stability fix.
Latest and greatest is preferred though.
FYI,
--
Marcel Moolenaar
mar...@xcllnt.net
___
freebsd-current@
Hi,
Please re-enable RADIX_MPATH option in your kernel config file, and
try the following patch:
http://people.freebsd.org/~qingli/radix_mpath.c.diff
and let me know if it works out for you.
I performed very limited testing.
Thanks,
--Qing
___
21 matches
Mail list logo
