hi sorry for being late in reply but I had some problems in the last week. I
hope u still remeber what I was talking about :)
@chargen
Thanx for ur reply.
Embedded computer systems permeate all aspects of our daily lives.
Alarm clocks, coffee makers, digital watches, cell phones, and automobiles
ar
On Wed, Jun 23, 2010 at 08:45:31AM -0700, Ted Faber wrote:
> On Wed, Jun 23, 2010 at 11:03:45AM -0400, Ryan Stone wrote:
> > I have to admit that I'm more than a little surprised that this
> > problem does not affect modules that in src, but maybe that's because
> > I don't know all that much about
On Wed, Jun 23, 2010 at 01:47:33PM -0700, Xin LI wrote:
> >
> > panic: _sx_xlock_hard: recursed on non-recursive sx
> > buf_hash_table.ht_locks[i].ht_lock @
> > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c
> > ommon/fs/zfs/arc.c:1626
>
> Any chance to obtain a backtrace for the
On Wed, 2010-06-23 at 15:00 -0500, Alexander Motin wrote:
> hint.atrtc.0.clock=0
> hint.attimer.0.clock=0
> hint.hpet.0.legacy_route=1
after adding those to the VM:
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi, Ben,
On 2010/06/23 09:44, ben wilber wrote:
> Hi,
>
> Since at least r208174, I've been getting the following panic every few days
> on
> my fairly heavily loaded amd64 machine:
>
> panic: _sx_xlock_hard: recursed on non-recursive sx
> buf_h
Sean Bruno wrote:
> With the large amount of churn in key parts of FreeBSD ongoing, I
> thought I'd post a dmesg from a booting FreeBSD Current instance I use
> all the time. This is under KVM/QEMU on Fedora 12.
>
> there's some interesting things relating to timers and such.
Thanks. I've noti
I can't help you with the problems with gprof, but Fabien Thomas has
been working on support for software-triggered pmc events. He posted
a patch here:
http://groups.google.com/group/pmctools-discuss/browse_thread/thread/1eb4fa78c7ab8522
You could try this out to use pmcstat to profile your appl
Yes. Using it as we speak.
"config -p" *seems* to be ok at the moment on 7 and -Current
Sean
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre
On Wed, 2010-06-23 at 13:00 -0500, Matthew Jacob wrote:
> On 6/23/2010 10:53 AM, Sean Bruno wrote:
> > Trying to track down a nasty with regard to Xen stuff and am now
> > experiencing deadlocks on -current with a kernel configured with -g
> > -ppp.
> >
> > The lockup will happen when I attempt to
On 6/23/2010 10:53 AM, Sean Bruno wrote:
Trying to track down a nasty with regard to Xen stuff and am now
experiencing deadlocks on -current with a kernel configured with -g
-ppp.
The lockup will happen when I attempt to get the profiling data via
kgmon -p.
Not sure when this broke, but it's de
Trying to track down a nasty with regard to Xen stuff and am now
experiencing deadlocks on -current with a kernel configured with -g
-ppp.
The lockup will happen when I attempt to get the profiling data via
kgmon -p.
Not sure when this broke, but it's definitely broken in stable-7 as well
as -cur
With the large amount of churn in key parts of FreeBSD ongoing, I
thought I'd post a dmesg from a booting FreeBSD Current instance I use
all the time. This is under KVM/QEMU on Fedora 12.
there's some interesting things relating to timers and such.
booted with boot.config set to -v
Sean
Copy
Hi,
Since at least r208174, I've been getting the following panic every few days on
my fairly heavily loaded amd64 machine:
panic: _sx_xlock_hard: recursed on non-recursive sx
buf_hash_table.ht_locks[i].ht_lock @
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c
ommon/fs/zfs/arc.c:1
On Wed, Jun 23, 2010 at 3:15 PM, Tom Evans wrote:
> Top of the '[TESTING] Clang..' email:
>
>> hi,
>>
>> ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to
>> import
>> into HEAD in roughly a week. We would like the initial import to be as
>> painless
>> as possible and
On Wed, Jun 23, 2010 at 11:03:45AM -0400, Ryan Stone wrote:
> I have to admit that I'm more than a little surprised that this
> problem does not affect modules that in src, but maybe that's because
> I don't know all that much about FreeBSD's build infrastructure. Are
> the src modules being linke
on 23/06/2010 18:03 Ryan Stone said the following:
> On Wed, Jun 23, 2010 at 3:10 AM, Andriy Gapon wrote:
>> Which also brings the question - what arch(s) is affected?
>> I tested on amd64.
>
> This should explain it. It looks to me like i386 uses kern/link_elf.c
> as its linker, while amd64 use
On 06/23/2010 10:55, Hans Petter Selasky wrote:
Hi,
Not unless there is a bug in my module. I'm a little bit busy right now,
though I think that other modules like "fuse.ko" might be affected aswell.
Could you try to make a cuse4bsd build on a stock 8-stable and compare the
resulting cuse4bsd.
On Wed, Jun 23, 2010 at 3:10 AM, Andriy Gapon wrote:
>
> Which also brings the question - what arch(s) is affected?
> I tested on amd64.
This should explain it. It looks to me like i386 uses kern/link_elf.c
as its linker, while amd64 uses kern/link_elf_obj.c. link_elf.c can
only find the sectio
On Wed, Jun 23, 2010 at 10:10:59AM +0300, Andriy Gapon wrote:
> on 23/06/2010 10:02 Andriy Gapon said the following:
> > I don't dispute that it is found broken in particular environments, I just
> > think
> > that the analysis could be incorrect.
>
> Which also brings the question - what arch(s)
On Wednesday 23 June 2010 16:43:31 Kris Moore wrote:
> On 06/23/2010 02:52, Hans Petter Selasky wrote:
> > On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote:
> >> on 23/06/2010 03:38 Hans Petter Selasky said the following:
> >>> Hi,
> >>>
> >>> I'm creating a new thread on this issue.
> >>>
> >
On 06/23/2010 02:52, Hans Petter Selasky wrote:
On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote:
on 23/06/2010 03:38 Hans Petter Selasky said the following:
Hi,
I'm creating a new thread on this issue.
On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
I saw
Anton Shterenlikht writes:
> I think it's possible that at some point, in anger, I did "make
> installworld" after a failed, or otherwise interrupted "make
> buildworld". Perhaps I got an inconsistent set of binaries as a
> result... Would that explain an error like this?
No, because at this poi
On Wed, Jun 23, 2010 at 1:38 PM, Cristiano Deana
wrote:
> # uname -a
> FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38
> CEST 2010 r...@test:/usr/obj/usr/src/sys/GENERIC amd64
>
> # cat /etc/src.conf
> #NO_WERROR=
> #WERROR=
> CC= clang
> CXX= clang++
>
> sources f
2010/6/23 Cristiano Deana :
> # uname -a
> FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38
> CEST 2010 r...@test:/usr/obj/usr/src/sys/GENERIC amd64
>
> # cat /etc/src.conf
> #NO_WERROR=
> #WERROR=
> CC= clang
> CXX= clang++
>
> sources from this morning, i got this
# uname -a
FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38
CEST 2010 r...@test:/usr/obj/usr/src/sys/GENERIC amd64
# cat /etc/src.conf
#NO_WERROR=
#WERROR=
CC= clang
CXX=clang++
sources from this morning, i got this error:
clang -O2 -pipe -I/usr/src/lib/libc/inc
On Mon, Jun 21, 2010 at 01:27:52PM -0700, Marcel Moolenaar wrote:
>
> On Jun 21, 2010, at 8:04 AM, Anton Shterenlikht wrote:
>
> > On Mon, Jun 21, 2010 at 04:45:03PM +0200, Dag-Erling Smørgrav wrote:
> >> jhell writes:
> >>> Anton Shterenlikht writes:
> What do you mean by "updating your h
on 23/06/2010 10:28 Nicholas Mills said the following:
> I was afraid someone would say that, because it's been very difficult to
> reproduce the issue. Happens maybe 1 out of every 8 reboots. I'll give
> it a look tomorrow and see what I can find.
>
> Just to be clear, I should send you the outpu
On Wednesday 23 June 2010 09:10:59 Andriy Gapon wrote:
> on 23/06/2010 10:02 Andriy Gapon said the following:
> > I don't dispute that it is found broken in particular environments, I
> > just think that the analysis could be incorrect.
Ok.
>
> Which also brings the question - what arch(s) is af
I was afraid someone would say that, because it's been very difficult to
reproduce the issue. Happens maybe 1 out of every 8 reboots. I'll give it a
look tomorrow and see what I can find.
Just to be clear, I should send you the output of the "where" command in
ddb?
On Wed, Jun 23, 2010 at 3:15 AM
on 23/06/2010 10:09 Nicholas Mills said the following:
> http://www.parl.clemson.edu/~nlmills/Screenshot.png
Ah, no stack trace. Unfortunately, this looks undebuggable as it is.
Custom kernel with debug options is needed.
--
Andriy Gapon
___
freebsd-c
on 23/06/2010 10:02 Andriy Gapon said the following:
> I don't dispute that it is found broken in particular environments, I just
> think
> that the analysis could be incorrect.
Which also brings the question - what arch(s) is affected?
I tested on amd64.
--
Andriy Gapon
___
I've since disabled the cdrom drive in Parallels as it was causing all sorts
of errors.
On Wed, Jun 23, 2010 at 2:15 AM, Andriy Gapon wrote:
> on 23/06/2010 02:41 Nicholas Mills said the following:
> > Hey all,
> >
> > Screenshot of panic message is attached. Machine is a VM running under
> > Pa
on 23/06/2010 09:52 Hans Petter Selasky said the following:
> On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote:
>> on 23/06/2010 03:38 Hans Petter Selasky said the following:
>>> Hi,
>>>
>>> I'm creating a new thread on this issue.
>>>
>>> On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone w
33 matches
Mail list logo
