Re: mountroot> while booting r255342 memstick

2013-09-12 Thread Joel Dahl 
On Thu, Sep 12, 2013 at 12:32:12AM +, Uzumaki Naruto wrote:
> Hi,
> I downloaded FreeBSD-10.0-CURRENT-amd64-20130907-r255342-memstick.img and dd 
> into KINGSTON DT 101 G2 1.00 USB pendrive

Looks similar to what I reported back in February:
http://lists.freebsd.org/pipermail/freebsd-current/2013-February/039542.html

mav@ committed a fix for this here:
http://lists.freebsd.org/pipermail/svn-src-head/2013-February/045143.html

Perhaps a quirk is needed for your USB pendrive as well. 

-- 
Joel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make release fails...

2013-09-12 Thread Glen Barber 
In part, yes.

Glen

On Fri, Sep 13, 2013 at 11:41:54AM +0900, Lundberg, Johannes wrote:
> Is this perhaps related to the 20130905 post in UPDATING, regarding the
> Capsicum framework?
> 
> --
> Johannes Lundberg
> Project leader and lead developer of Mirama OS (previously Viking OS)
> BRILLIANTSERVICE CO., LTD.
> 
> My blog 
> Mirama homepage 
> blog
> Company homepage 
> 
> 
> On Fri, Sep 13, 2013 at 11:37 AM, Lundberg, Johannes <
> johan...@brilliantservice.co.jp> wrote:
> 
> > Oh.. Thanks a lot!
> >
> > But please tell me, how can I upgrade the build environment? Do I have to
> > rebuild world and kernel on the host system?
> >
> > --
> > Johannes Lundberg
> > Project leader and lead developer of Mirama OS (previously Viking OS)
> > BRILLIANTSERVICE CO., LTD.
> >
> > My blog 
> > Mirama homepage  
> > blog
> > Company homepage 
> >
> >
> > On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber  wrote:
> >
> >> On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote:
> >> > # sysctl -n kern.osreldate
> >> > 145
> >> >
> >> > The system is 10.0. I used it before to build custom distribution.
> >> > What I've done since last time is basically removing /usr/src and
> >> grabbing
> >> > a new one from head.
> >>
> >> Recent changes in head/ (unfortunately) require the build system
> >> revision to be at least 155 or greater, due to some backward
> >> compatibility issues introduced recently.
> >>
> >> If you upgrade the build environment and retry the build, you should be
> >> fine.
> >>
> >> (And yes, I am serious, as I've just spent several hours on exactly
> >> these types of issues...)
> >>
> >> Glen
> >>
> >>
> >


pgppIC6i58N_J.pgp
Description: PGP signature

Re: make release fails...

2013-09-12 Thread Glen Barber 
Yes, the buildworld/buildkernel.

Glen

On Fri, Sep 13, 2013 at 11:37:38AM +0900, Lundberg, Johannes wrote:
> Oh.. Thanks a lot!
> 
> But please tell me, how can I upgrade the build environment? Do I have to
> rebuild world and kernel on the host system?
> 
> --
> Johannes Lundberg
> Project leader and lead developer of Mirama OS (previously Viking OS)
> BRILLIANTSERVICE CO., LTD.
> 
> My blog 
> Mirama homepage 
> blog
> Company homepage 
> 
> 
> On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber  wrote:
> 
> > On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote:
> > > # sysctl -n kern.osreldate
> > > 145
> > >
> > > The system is 10.0. I used it before to build custom distribution.
> > > What I've done since last time is basically removing /usr/src and
> > grabbing
> > > a new one from head.
> >
> > Recent changes in head/ (unfortunately) require the build system
> > revision to be at least 155 or greater, due to some backward
> > compatibility issues introduced recently.
> >
> > If you upgrade the build environment and retry the build, you should be
> > fine.
> >
> > (And yes, I am serious, as I've just spent several hours on exactly
> > these types of issues...)
> >
> > Glen
> >
> >


pgpivCirxcKq9.pgp
Description: PGP signature

Re: make release fails...

2013-09-12 Thread Lundberg, Johannes 
Oh.. Thanks a lot!

But please tell me, how can I upgrade the build environment? Do I have to
rebuild world and kernel on the host system?

--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.

My blog 
Mirama homepage 
blog
Company homepage 


On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber  wrote:

> On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote:
> > # sysctl -n kern.osreldate
> > 145
> >
> > The system is 10.0. I used it before to build custom distribution.
> > What I've done since last time is basically removing /usr/src and
> grabbing
> > a new one from head.
>
> Recent changes in head/ (unfortunately) require the build system
> revision to be at least 155 or greater, due to some backward
> compatibility issues introduced recently.
>
> If you upgrade the build environment and retry the build, you should be
> fine.
>
> (And yes, I am serious, as I've just spent several hours on exactly
> these types of issues...)
>
> Glen
>
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make release fails...

2013-09-12 Thread Lundberg, Johannes 
Is this perhaps related to the 20130905 post in UPDATING, regarding the
Capsicum framework?

--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.

My blog 
Mirama homepage 
blog
Company homepage 


On Fri, Sep 13, 2013 at 11:37 AM, Lundberg, Johannes <
johan...@brilliantservice.co.jp> wrote:

> Oh.. Thanks a lot!
>
> But please tell me, how can I upgrade the build environment? Do I have to
> rebuild world and kernel on the host system?
>
> --
> Johannes Lundberg
> Project leader and lead developer of Mirama OS (previously Viking OS)
> BRILLIANTSERVICE CO., LTD.
>
> My blog 
> Mirama homepage  
> blog
> Company homepage 
>
>
> On Fri, Sep 13, 2013 at 11:35 AM, Glen Barber  wrote:
>
>> On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote:
>> > # sysctl -n kern.osreldate
>> > 145
>> >
>> > The system is 10.0. I used it before to build custom distribution.
>> > What I've done since last time is basically removing /usr/src and
>> grabbing
>> > a new one from head.
>>
>> Recent changes in head/ (unfortunately) require the build system
>> revision to be at least 155 or greater, due to some backward
>> compatibility issues introduced recently.
>>
>> If you upgrade the build environment and retry the build, you should be
>> fine.
>>
>> (And yes, I am serious, as I've just spent several hours on exactly
>> these types of issues...)
>>
>> Glen
>>
>>
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: mountroot> while booting r255342 memstick

2013-09-12 Thread Glen Barber 
Also, if you can try the 9.2-RC4 image, that would also be appreciated.
If this is a problem only with 10.0, this is something re@ and hselasky@
(bcc'd) needs to be aware of.

Glen

On Fri, Sep 13, 2013 at 11:09:30AM +0900, Lundberg, Johannes wrote:
> Does it work with the 9.1 image? If it does, you probably have the same
> problem as I do with the new Macbook Air.
> Optimisations made to the xhci driver causes it to fail. What I've done is
> to create a new install image with sys/dev/usb/controller/xhci* reverted
> back to 243780.
> 
> --
> Johannes Lundberg
> Project leader and lead developer of Mirama OS (previously Viking OS)
> BRILLIANTSERVICE CO., LTD.
> 
> My blog 
> Mirama homepage 
> blog
> Company homepage 
> 
> 
> On Thu, Sep 12, 2013 at 11:14 AM, Nathan Whitehorn
> wrote:
> 
> > On 09/11/13 20:42, Uzumaki Naruto wrote:
> >
> >> If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't
> >>> support GPT disk type, because OEM Acer only gave GPT supported BIOS for
> >>> model that pre-loaded with Windows 8.
> >>>
> >> Maybe it helps to clarify, this laptop got no UEFI firmware, I could
> >> convert my hard disk to GPT type using diskpart command, but the
> >> functionality to boot from GPT partition is unavailable through BIOS.
> >>
> >>
> > Booting from GPT does not require BIOS support. BIOSes don't (or aren't
> > supposed to -- some broken ones do) parse the partition table at all.
> > -Nathan
> >
> > __**_
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@**
> > freebsd.org "
> >


pgp8ww0zjnw2U.pgp
Description: PGP signature

Re: make release fails...

2013-09-12 Thread Glen Barber 
On Fri, Sep 13, 2013 at 11:30:44AM +0900, Lundberg, Johannes wrote:
> # sysctl -n kern.osreldate
> 145
> 
> The system is 10.0. I used it before to build custom distribution.
> What I've done since last time is basically removing /usr/src and grabbing
> a new one from head.

Recent changes in head/ (unfortunately) require the build system
revision to be at least 155 or greater, due to some backward
compatibility issues introduced recently.

If you upgrade the build environment and retry the build, you should be
fine.

(And yes, I am serious, as I've just spent several hours on exactly
these types of issues...)

Glen



pgpMRrq2veMKk.pgp
Description: PGP signature

Re: make release fails...

2013-09-12 Thread Lundberg, Johannes 
# sysctl -n kern.osreldate
145

The system is 10.0. I used it before to build custom distribution.
What I've done since last time is basically removing /usr/src and grabbing
a new one from head.


--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.

My blog 
Mirama homepage 
blog
Company homepage 


On Fri, Sep 13, 2013 at 11:27 AM, Glen Barber  wrote:

> On Fri, Sep 13, 2013 at 11:21:43AM +0900, Lundberg, Johannes wrote:
> > Trying to create a custom install image which has been successful before
> > but suddenly fails during make release/memstick.
> >
> > Procedure
> >
> > 1) cd /usr/src
> > 2) make buildworld
> > 3) make buildkernel
> > 4) cd release
> > 5) make release
> >
> > and I get the error
> >
> > ...
> > gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg
> > make[8]: exec(gencat) failed (no such file or directory)
> > 
> >
>
> This is not enough context.
>
> Also, what is output of 'sysctl -n kern.osreldate' on the build host,
> and which branch and revision are you trying to build?
>
> Glen
>
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: mountroot> while booting r255342 memstick

2013-09-12 Thread Lundberg, Johannes 
Does it work with the 9.1 image? If it does, you probably have the same
problem as I do with the new Macbook Air.
Optimisations made to the xhci driver causes it to fail. What I've done is
to create a new install image with sys/dev/usb/controller/xhci* reverted
back to 243780.

--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.

My blog 
Mirama homepage 
blog
Company homepage 


On Thu, Sep 12, 2013 at 11:14 AM, Nathan Whitehorn
wrote:

> On 09/11/13 20:42, Uzumaki Naruto wrote:
>
>> If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't
>>> support GPT disk type, because OEM Acer only gave GPT supported BIOS for
>>> model that pre-loaded with Windows 8.
>>>
>> Maybe it helps to clarify, this laptop got no UEFI firmware, I could
>> convert my hard disk to GPT type using diskpart command, but the
>> functionality to boot from GPT partition is unavailable through BIOS.
>>
>>
> Booting from GPT does not require BIOS support. BIOSes don't (or aren't
> supposed to -- some broken ones do) parse the partition table at all.
> -Nathan
>
> __**_
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@**
> freebsd.org "
>
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

make release fails...

2013-09-12 Thread Lundberg, Johannes 
Hi

Trying to create a custom install image which has been successful before
but suddenly fails during make release/memstick.

Procedure

1) cd /usr/src
2) make buildworld
3) make buildkernel
4) cd release
5) make release

and I get the error

...
gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg
make[8]: exec(gencat) failed (no such file or directory)



--
Johannes Lundberg
Project leader and lead developer of Mirama OS (previously Viking OS)
BRILLIANTSERVICE CO., LTD.

My blog 
Mirama homepage 
blog
Company homepage 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make release fails...

2013-09-12 Thread Glen Barber 
On Fri, Sep 13, 2013 at 11:21:43AM +0900, Lundberg, Johannes wrote:
> Trying to create a custom install image which has been successful before
> but suddenly fails during make release/memstick.
> 
> Procedure
> 
> 1) cd /usr/src
> 2) make buildworld
> 3) make buildkernel
> 4) cd release
> 5) make release
> 
> and I get the error
> 
> ...
> gencat be_BY.UTF-8.cat /usr/src/lib/libc/nls/be_BY.UTF-8.msg
> make[8]: exec(gencat) failed (no such file or directory)
> 
> 

This is not enough context.

Also, what is output of 'sysctl -n kern.osreldate' on the build host,
and which branch and revision are you trying to build?

Glen



pgpWdgLPdVDMT.pgp
Description: PGP signature

Re: dns/libidn puzzle

2013-09-12 Thread Matthias Andree 
Am 12.09.2013 23:44, schrieb Walter Hurry:
> On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config', I 
> get a dialog asking me whether I want DOCS and/or NLS.
> 
> However, on 10-CURRENT (r255358) I get this:
> 
> $ cd /usr/ports/dns/libidn
> $ sudo make config
> ===> Options unchanged
> $ 
> 
> Why the difference?

Is dialog4ports installed on your 10-CURRENT?

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

dns/libidn puzzle

2013-09-12 Thread Walter Hurry 
On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config', I 
get a dialog asking me whether I want DOCS and/or NLS.

However, on 10-CURRENT (r255358) I get this:

$ cd /usr/ports/dns/libidn
$ sudo make config
===> Options unchanged
$ 

Why the difference?

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread Dimitry Andric 
On Sep 12, 2013, at 21:47, S.N.Grigoriev  wrote:
> after upgrading to r255423 (make buildworld && make buildkernel && make 
> installkernel && make installworld && reboot; make delete-old && make 
> delete-old-libs) I cannot build the system with the WITH_GCC=yes and 
> WITH_GNUCXX=yes options in my src.conf. The following error occures:
> 
> --- libgssapi_krb5.so.10 ---
> building shared library libgssapi_krb5.so.10
> --- gnu/lib__L ---
> /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/list.cc:61:3: 
> error: use of undeclared identifier '_List_node_base'
>  _List_node_base::swap(_List_node_base& __x, _List_node_base& __y)
>  ^

I just sent a mail to re@ to get approval for a fix for this.  In the
mean time, please apply the attached patch.

-Dimitry


fix-libstdc++-build.diff
Description: Binary data




signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread S . N . Grigoriev 
Hi list,

after upgrading to r255423 (make buildworld && make buildkernel && make 
installkernel && make installworld && reboot; make delete-old && make 
delete-old-libs) I cannot build the system with the WITH_GCC=yes and 
WITH_GNUCXX=yes options in my src.conf. The following error occures:

--- libgssapi_krb5.so.10 ---
building shared library libgssapi_krb5.so.10
--- gnu/lib__L ---
/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/list.cc:61:3: error: 
use of undeclared identifier '_List_node_base'
  _List_node_base::swap(_List_node_base& __x, _List_node_base& __y)
  ^
/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/list.cc:61:25: error: 
use of undeclared identifier '_List_node_base'; did you mean '__list_node_base'?
  _List_node_base::swap(_List_node_base& __x, _List_node_base& __y)
^~~
__list_node_base
/usr/obj/usr/src/tmp/usr/include/c++/v1/list:190:8: note: '__list_node_base' 
declared here
struct __list_node_base
   ^
/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/list.cc:61:25: error: 
no template named '_List_node_base'; did you mean '__list_node_base'?
  _List_node_base::swap(_List_node_base& __x, _List_node_base& __y)
^~~
__list_node_base
/usr/obj/usr/src/tmp/usr/include/c++/v1/list:190:8: note: '__list_node_base' 
declared here
struct __list_node_base
   ^
/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/list.cc:61:25: error: 
use of class template '__list_node_base' requires template arguments
  _List_node_base::swap(_List_node_base& __x, _List_node_base& __y)
^
/usr/obj/usr/src/tmp/usr/include/c++/v1/list:190:8: note: template is declared 
here
struct __list_node_base
   ^

Without options listed above all works fine.

-- 
Regards,
Serguey.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Intermittent hangs in vmem_periodic()

2013-09-12 Thread hiren panchasara 
+jeff


On Thu, Sep 12, 2013 at 11:17 AM, Gleb Smirnoff  wrote:

> On Thu, Sep 12, 2013 at 09:31:17AM -0700, hiren panchasara wrote:
> h> > > h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885
> unresolved
> h> > > h>
> h> > > h> %SAMP CALLTREE
> h> > > h>  75.9 fork_exit@kernel taskqueue_thread_loop
> taskqueue_run_locked
> h> > > h> vmem_periodic(75.9%)
> h> > >
> h> > > You probably got DIAGNOSTIC in your kernel config.
> h> >
> h> > Yes. And I've always had that. Never been a problem before. What has
> h> > changed?
> h> >
> h>
> h> Thanks Gleb.
> h> I've removed DIAGNOSTIC and the problem is gone now.
> h>
> h> But the way system was behaving with DIAGNOSTIC, its unusable.
>
> Please report that to Jeff. With DIAGNOSTIC the system can be slower,
> more chatty on console, but should be usable.
>

Exactly.

Thanks Gleb.

Jeff: Not sure if you are subscribed to this list.
http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044487.html

cheers,
Hiren
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Intermittent hangs in vmem_periodic()

2013-09-12 Thread Gleb Smirnoff 
On Thu, Sep 12, 2013 at 09:31:17AM -0700, hiren panchasara wrote:
h> > > h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved
h> > > h>
h> > > h> %SAMP CALLTREE
h> > > h>  75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
h> > > h> vmem_periodic(75.9%)
h> > >
h> > > You probably got DIAGNOSTIC in your kernel config.
h> >
h> > Yes. And I've always had that. Never been a problem before. What has
h> > changed?
h> >
h> 
h> Thanks Gleb.
h> I've removed DIAGNOSTIC and the problem is gone now.
h> 
h> But the way system was behaving with DIAGNOSTIC, its unusable.

Please report that to Jeff. With DIAGNOSTIC the system can be slower,
more chatty on console, but should be usable.

-- 
Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Intermittent hangs in vmem_periodic()

2013-09-12 Thread hiren panchasara 
On Thu, Sep 12, 2013 at 8:16 AM, hiren panchasara <
hiren.panchas...@gmail.com> wrote:

>
> On Sep 12, 2013 2:27 AM, "Gleb Smirnoff"  wrote:
> >
> > On Wed, Sep 11, 2013 at 09:51:16PM -0700, hiren panchasara wrote:
> > h> I am seeing really weird system freeze for 2-3 seconds every minute
> or so.
> > h>
> > h> % uname -a
> > h> FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD
> 10.0-CURRENT #2
> > h> r255423M: Mon Sep  9 12:29:22 PDT 2013 root@flymocko
> > h> ur-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC  amd64
> > h>
> > h> Simple comands like "man top" hangs and this is what I see in ctrl+T
> > h>  % man top
> > h>  load: 1.59  cmd: zcat 76574 [*kmem arena] 2.16r 0.00u 1.82s 16% 2000k
> > h>  load: 1.70  cmd: zcat 76574 [*kmem arena] 7.19r 0.00u 1.82s 7% 2000k
> > h>  load: 1.89  cmd: zcat 76574 [*kmem arena] 12.58r 0.00u 1.82s 3% 2000k
> > h>  load: 1.90  cmd: zcat 76574 [*kmem arena] 14.58r 0.00u 1.82s 2% 2000k
> > h>
> > h> I see similar things while trying to "exit" a terminal window.
> > h>
> > h> I see following in pmcstat:
> > h>
> > h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved
> > h>
> > h> %SAMP CALLTREE
> > h>  75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
> > h> vmem_periodic(75.9%)
> >
> > You probably got DIAGNOSTIC in your kernel config.
>
> Yes. And I've always had that. Never been a problem before. What has
> changed?
>

Thanks Gleb.
I've removed DIAGNOSTIC and the problem is gone now.

But the way system was behaving with DIAGNOSTIC, its unusable.

Thanks again,
Hiren
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ia64 r255472: /usr/src/sys/kern/uipc_syscalls.c:2196: warning: obj_size may be used uninitialized in this function

2013-09-12 Thread Dimitry Andric 
On Sep 12, 2013, at 10:37, Anton Shterenlikht  wrote:
> ia64 r255472 buildkernel gives this error:
> 
> cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
> -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
> -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
> -Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. 
> -I/usr/src/sys -I/usr/src/sys/contrib/altq 
> -I/usr/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS 
> -include opt_global.h -fno-common -finline-limit=15000 --param 
> inline-unit-growth=100 --param large-function-growth=1000  -mconstant-gp 
> -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror  
> /usr/src/sys/kern/uipc_syscalls.c
> cc1: warnings being treated as errors
> /usr/src/sys/kern/uipc_syscalls.c: In function 'vn_sendfile':
> /usr/src/sys/kern/uipc_syscalls.c:2196: warning: 'obj_size' may be used 
> uninitialized in this function
> /usr/src/sys/kern/uipc_syscalls.c:2192: warning: 'pg' may be used 
> uninitialized in this function
> *** [uipc_syscalls.o] Error code 1

Kostik fixed this in r255475.  You're just 3 revs short. :-)

-Dimitry




signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Intermittent hangs in vmem_periodic()

2013-09-12 Thread hiren panchasara 
On Sep 12, 2013 2:27 AM, "Gleb Smirnoff"  wrote:
>
> On Wed, Sep 11, 2013 at 09:51:16PM -0700, hiren panchasara wrote:
> h> I am seeing really weird system freeze for 2-3 seconds every minute or
so.
> h>
> h> % uname -a
> h> FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT
#2
> h> r255423M: Mon Sep  9 12:29:22 PDT 2013 root@flymocko
> h> ur-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC  amd64
> h>
> h> Simple comands like "man top" hangs and this is what I see in ctrl+T
> h>  % man top
> h>  load: 1.59  cmd: zcat 76574 [*kmem arena] 2.16r 0.00u 1.82s 16% 2000k
> h>  load: 1.70  cmd: zcat 76574 [*kmem arena] 7.19r 0.00u 1.82s 7% 2000k
> h>  load: 1.89  cmd: zcat 76574 [*kmem arena] 12.58r 0.00u 1.82s 3% 2000k
> h>  load: 1.90  cmd: zcat 76574 [*kmem arena] 14.58r 0.00u 1.82s 2% 2000k
> h>
> h> I see similar things while trying to "exit" a terminal window.
> h>
> h> I see following in pmcstat:
> h>
> h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved
> h>
> h> %SAMP CALLTREE
> h>  75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
> h> vmem_periodic(75.9%)
>
> You probably got DIAGNOSTIC in your kernel config.

Yes. And I've always had that. Never been a problem before. What has
changed?

Thanks,
Hiren
>
> --
> Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

IPSEC with IPv6 crashes

2013-09-12 Thread Maciej Milewski 
I'm trying to use IPSEC with IPv6 in transport mode. My configuration is 
simple: IPSEC + racoon from ipsec-utils.
One side is RS(MIPS) with HEAD-r252464 and 2nd side ALIX(i386) with 
9.1-STABLE. This error is visible only on MIPS side.


ipsec.conf:
spdadd [ipv6_addr1] [ipv6_addr2] any -P in ipsec
   esp/transport//require;
spdadd [ipv6_addr2] [ipv6_addr1] any -P out ipsec
   esp/transport//require;

And the error is reproducible with just getting transmission over the IPSEC:

Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
[ thread pid 0 tid 100027 ]
Stopped at  ipsec6_common_input_cb+0x364:   lw  v0,116(v1)
db> bt
Tracing pid 0 tid 100027 td 0x80dc2990
db_trace_thread+30 (?,?,?,?) ra c039f2400018 sp 0 sz 0
80083c3c+114 (0,?,,?) ra c039f2580020 sp 1 sz 1
80082f84+388 (?,?,?,?) ra c039f27800a8 sp 0 sz 0
db_command_loop+70 (?,?,?,?) ra c039f3200018 sp 0 sz 0
80085a80+f4 (?,?,?,?) ra c039f33801a8 sp 0 sz 0
kdb_trap+110 (?,?,?,?) ra c039f4e00030 sp 0 sz 0
trap+f18 (?,?,?,?) ra c039f51000b8 sp 0 sz 0
MipsKernGenException+134 (82bee380,81c84900,0,0) ra c039f5c800c8 sp 
10001 sz 1
ipsec6_common_input_cb+364 (81c84900,?,28,?) ra c039f6900038 sp 
1 sz 1

803c6684+568 (?,?,?,?) ra c039f6c80078 sp 0 sz 0
crypto_done+11c (?,?,?,?) ra c039f7400030 sp 0 sz 0
803fd608+fb4 (?,?,?,?) ra c039f77001a0 sp 0 sz 0
803fb3a8+164 (?,?,?,?) ra c039f9100028 sp 0 sz 0
crypto_dispatch+94 (?,?,?,?) ra c039f9380020 sp 0 sz 0
803c708c+62c (?,?,?,?) ra c039f9580058 sp 0 sz 0
803b2390+52c (?,?,?,?) ra c039f9b00060 sp 0 sz 0
ipsec6_common_input+19c (?,?,?,?) ra c039fa100040 sp 0 sz 0
ip6_input+16d8 (81c84900,?,?,?) ra c039fa500120 sp 1 sz 0
netisr_dispatch_src+134 (?,?,?,?) ra c039fb700040 sp 0 sz 0
netisr_dispatch+14 (?,?,?,?) ra c039fbb00018 sp 0 sz 0
ether_demux+218 (?,81c84900,?,?) ra c039fbc80028 sp 1 sz 0
802d72ec+4a8 (81c84900,?,?,?) ra c039fbf00030 sp 1 sz 0
netisr_dispatch_src+134 (?,?,?,?) ra c039fc200040 sp 0 sz 0
netisr_dispatch+14 (?,?,?,?) ra c039fc600018 sp 0 sz 0
802d6e9c+3c (?,?,?,?) ra c039fc780018 sp 0 sz 0
ieee80211_deliver_data+100 (?,?,?,?) ra c039fc900028 sp 0 sz 0
803387fc+bc4 (?,?,?,ffa0) ra c039fcb80060 sp 0 sz 0
ath_rx_pkt+6c0 (?,?,0,?) ra c039fd180050 sp 0 sz 1
800aa98c+388 (?,1,?,?) ra c039fd680060 sp 1 sz 0
800aaef0+c4 (?,?,?,?) ra c039fdc80020 sp 0 sz 0
8024e34c+e8 (?,?,?,?) ra c039fde80038 sp 0 sz 0
taskqueue_thread_loop+8c (?,?,?,?) ra c039fe200038 sp 0 sz 0
fork_exit+b0 (?,?,?,?) ra c039fe580028 sp 0 sz 0
fork_trampoline+10 (?,?,?,?) ra c039fe80 sp 0 sz 0
pid 0

I'm open to any hints.
Regards,
Maciej Milewski

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Intermittent hangs in vmem_periodic()

2013-09-12 Thread Gleb Smirnoff 
On Wed, Sep 11, 2013 at 09:51:16PM -0700, hiren panchasara wrote:
h> I am seeing really weird system freeze for 2-3 seconds every minute or so.
h> 
h> % uname -a
h> FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2
h> r255423M: Mon Sep  9 12:29:22 PDT 2013 root@flymocko
h> ur-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC  amd64
h> 
h> Simple comands like "man top" hangs and this is what I see in ctrl+T
h>  % man top
h>  load: 1.59  cmd: zcat 76574 [*kmem arena] 2.16r 0.00u 1.82s 16% 2000k
h>  load: 1.70  cmd: zcat 76574 [*kmem arena] 7.19r 0.00u 1.82s 7% 2000k
h>  load: 1.89  cmd: zcat 76574 [*kmem arena] 12.58r 0.00u 1.82s 3% 2000k
h>  load: 1.90  cmd: zcat 76574 [*kmem arena] 14.58r 0.00u 1.82s 2% 2000k
h> 
h> I see similar things while trying to "exit" a terminal window.
h> 
h> I see following in pmcstat:
h> 
h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved
h> 
h> %SAMP CALLTREE
h>  75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
h> vmem_periodic(75.9%)

You probably got DIAGNOSTIC in your kernel config.

-- 
Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ia64 r255472: /usr/src/sys/kern/uipc_syscalls.c:2196: warning: obj_size may be used uninitialized in this function

2013-09-12 Thread Anton Shterenlikht 

ia64 r255472 buildkernel gives this error:

cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/usr/src/sys 
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ia64/libuwx/src -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000  -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 
-fpic -ffreestanding -Werror  /usr/src/sys/kern/uipc_syscalls.c
cc1: warnings being treated as errors
/usr/src/sys/kern/uipc_syscalls.c: In function 'vn_sendfile':
/usr/src/sys/kern/uipc_syscalls.c:2196: warning: 'obj_size' may be used 
uninitialized in this function
/usr/src/sys/kern/uipc_syscalls.c:2192: warning: 'pg' may be used uninitialized 
in this function
*** [uipc_syscalls.o] Error code 1

Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-12 Thread David Chisnall 
On 11 Sep 2013, at 21:06, "David O'Brien"  wrote:

> It is still very useful for folks to test changes in order to help ensure
> one doesn't break the build on platforms still using GCC.

If you want to do this test, then you should do make universe or make tinderbox 
(you should do one or the other before committing anything already anyway), and 
these will build the cross-gcc toolchains for various architectures.

The GCC in base is not used when build-testing anything except the toolchain 
with our build system.  If you want to test building things with gcc, then you 
need to build WITHOUT_CLANG_IS_CC (which will build gcc and then build world 
with it), or explicitly specify a compiler to use when testing a smaller 
component (which can be a gcc you installed from the base tree, or one from 
ports - Warner is currently working to ensure that we'll have the 
FreeBSD-specific patches forward-ported so that each of the lang/gcc ports will 
be able to build FreeBSD).

The change is only to the default install.  If you are not a FreeBSD developer, 
then you are almost certainly not using our gcc: you're either not a developer 
at all, in which case you're rarely compiling things, or you're a developer of 
other stuff and therefore want a modern compiler (either clang or lang/gcc).  
If you are a developer, then a change to the default install should not be a 
significant obstacle to your configuring the system how you want.

David

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"