On 07/18/10 12:41, Kostik Belousov wrote:
> On Sun, Jul 18, 2010 at 12:21:00PM -0700, Doug Barton wrote:
>> On 07/18/10 03:30, Kostik Belousov wrote:
>>> On Sun, Jul 18, 2010 at 01:14:41AM -0700, Doug Barton wrote:
On Sat, 17 Jul 2010, Kostik Belousov wrote:
> Run top in the mode wher
: : Stop in /usr/local/tinderbox/jails/9-HEAD.i386/src/etc.
: :
: : Full build and distribution logs avaliable on
: : http://levsha.me/tmp/20100718/world.txt (20M)
: : http://levsha.me/tmp/20100718/distribution.txt (7.4K)
: :
: : Reverting r209510 fixes this problem
:
: It works for me.
:
: on an amd6
[NB] Obviously, I didn't click "reply ALL" last time, so here are missing part
> > > > -if(vap->iv_opmode == IEEE80211_M_HOSTAP){
> > > >
> > > > -RUN_LOCK(sc);
> > > > +if (vap->iv_opmode == IEEE80211_M_HOSTAP)
> > > >
> > > > sc->cmdq_key_set = RUN_CMDQ_GO;
> > > >
> > > > -RUN_UNLOCK(sc)
o such file or directory
: *** Error code 71
:
: Stop in /usr/local/tinderbox/jails/9-HEAD.i386/src/etc/sendmail.
: *** Error code 1
:
: Stop in /usr/local/tinderbox/jails/9-HEAD.i386/src/etc.
:
: Full build and distribution logs avaliable on
: http://levsha.me/tmp/20100718/world.txt (20M)
o such file or directory
: *** Error code 71
:
: Stop in /usr/local/tinderbox/jails/9-HEAD.i386/src/etc/sendmail.
: *** Error code 1
:
: Stop in /usr/local/tinderbox/jails/9-HEAD.i386/src/etc.
:
: Full build and distribution logs avaliable on
: http://levsha.me/tmp/20100718/world.txt (20M)
Ivan Voras writes:
Hello Ivan,
> I'm not a Solaris guy but from
> http://hub.opensolaris.org/bin/view/Project+comstar/ it looks like
> COMSTAR does something similar to what FreeBSD's GEOM does now.
Ok.
It seems to me that COMSTAR provides one functionality that GEOM misses,
a generic SCSI tar
.
*** Error code 1
Stop in /usr/local/tinderbox/jails/9-HEAD.i386/src/etc.
Full build and distribution logs avaliable on
http://levsha.me/tmp/20100718/world.txt (20M)
http://levsha.me/tmp/20100718/distribution.txt (7.4K)
Reverting r209510 fixes this problem
--
LEFT-(UANIC|RIPE)
JID: lev...@jabber.net.ua
In the last episode (Jul 18), Dan Nelson said:
> In the last episode (Jul 18), Doug Barton said:
> > On 07/18/10 12:41, Kostik Belousov wrote:
> > > When intr time starts accumulating again, try to do
> > > "procstat -kk " and correlate the clock thread tid
> > > with the backtrace. Might be, it he
In the last episode (Jul 18), Doug Barton said:
> On 07/18/10 12:41, Kostik Belousov wrote:
> > When intr time starts accumulating again, try to do
> > "procstat -kk " and correlate the clock thread tid
> > with the backtrace. Might be, it helps to guess what callouts are eating
> > the CPU.
>
> W
On 07/18/10 12:41, Kostik Belousov wrote:
> When intr time starts accumulating again, try to do
> "procstat -kk " and correlate the clock thread tid
> with the backtrace. Might be, it helps to guess what callouts are eating
> the CPU.
Will do, thanks!
Doug
--
... and that's just a lit
On Sun, Jul 18, 2010 at 12:21:00PM -0700, Doug Barton wrote:
> On 07/18/10 03:30, Kostik Belousov wrote:
> > On Sun, Jul 18, 2010 at 01:14:41AM -0700, Doug Barton wrote:
> >> On Sat, 17 Jul 2010, Kostik Belousov wrote:
> >>
> >>> Run top in the mode where all system threads are shown separately
> >
Hello list,
im running two freebsd dists , each one in a diferent notebook..
i have a freebsd 8.1 rc2 running in amd64 with 2 cores 2MB mem.. (my old
hp), and a freebsd 9-current running on
a intel i3 (2 cores + 2 logical cores) with 4 MB ram.. and im was noting
that the amd notebook was performi
On 07/18/10 03:30, Kostik Belousov wrote:
> On Sun, Jul 18, 2010 at 01:14:41AM -0700, Doug Barton wrote:
>> On Sat, 17 Jul 2010, Kostik Belousov wrote:
>>
>>> Run top in the mode where all system threads are shown separately
>>> (e.g. top -HS seems to do it), then watch what thread eats the process
TB --- 2010-07-18 16:56:36 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-07-18 16:56:36 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-07-18 16:56:36 - cleaning the object tree
TB --- 2010-07-18 16:56:52 - cvsupping the source tree
TB --- 2010-07-18 16:56:52 - /usr
TB --- 2010-07-18 17:03:19 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-07-18 17:03:19 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-07-18 17:03:19 - cleaning the object tree
TB --- 2010-07-18 17:03:30 - cvsupping the source tree
TB --- 2010-07-18 17:03:30 - /usr/b
TB --- 2010-07-18 16:59:15 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-07-18 16:59:15 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-07-18 16:59:15 - cleaning the object tree
TB --- 2010-07-18 16:59:27 - cvsupping the source tree
TB --- 2010-07-18 16:59:27 - /usr
On 2010-07-16 at 12:31, Ståle Kristoffersen wrote:
> On 2010-07-15 at 19:52, Ståle Kristoffersen wrote:
> > On 2010-07-15 at 18:00, Marius Strobl wrote:
> > > On Thu, Jul 15, 2010 at 02:34:23PM +0200, Stle Kristoffersen wrote:
> > > > Upgraded to from stable to current yesterday and very quickly re
On Sat, 17 Jul 2010, Gavin Atkinson wrote:
> Semi-regularly (every two-three days) I'm seeing what appears to be some
> sort of filesystem wedge. I usually see it initially with web browsers,
> but it's possible that's only because it's what produces most disk
> activity on this machine. I've
On Sat, 17 Jul 2010 12:51:34 +0200 Marco van Lienen
wrote:
> On Sat, Jul 17, 2010 at 12:25:56PM +0200, you (Stefan Bethke) sent
> the following to the -current list:
> > Am 17.07.2010 um 12:14 schrieb Marco van Lienen:
> >
> > > # zpool list pool1
> > > NAMESIZE USED AVAILCAP HEALTH
On Fri, Jul 16, 2010 at 12:31:26PM +0200, Stle Kristoffersen wrote:
> On 2010-07-15 at 19:52, St?le Kristoffersen wrote:
> > On 2010-07-15 at 18:00, Marius Strobl wrote:
> > > On Thu, Jul 15, 2010 at 02:34:23PM +0200, Stle Kristoffersen wrote:
> > > > Upgraded to from stable to current yesterday an
Am 17.07.2010 um 16:30 schrieb Marco van Lienen:
> I also posted the example of creating a test raidz pool based on 3 65Mb files.
> On osol there is more available space being reported by 'zfs list' on that
> test raidz pool
> When I created a similar test raidz pool also based on 3 65Mb files, '
On Sun, Jul 18, 2010 at 01:14:41AM -0700, Doug Barton wrote:
> On Sat, 17 Jul 2010, Kostik Belousov wrote:
>
> >Run top in the mode where all system threads are shown separately
> >(e.g. top -HS seems to do it), then watch what thread eats the processor.
>
> And the winner is!
>
>11 root
On Sat, Jul 17, 2010 at 10:21:28PM +0300, Kostik Belousov wrote:
> On Sat, Jul 17, 2010 at 12:10:26PM -0700, Doug Barton wrote:
> > On Sat, 17 Jul 2010, Rui Paulo wrote:
> >
> > >This doesn't indicate any problem. I suggest you try to figure out what
> > >interrupt is causing this by adding print
On Sat, 17 Jul 2010, Kostik Belousov wrote:
Run top in the mode where all system threads are shown separately
(e.g. top -HS seems to do it), then watch what thread eats the processor.
And the winner is!
11 root -32- 0K 168K WAIT0 0:28 18.02% {swi4: clock}
11 root
24 matches
Mail list logo
