Re: External toolchain support

[Baptiste Daroussin]

On Mon, Dec 01, 2014 at 10:05:29PM -0700, Warner Losh wrote:
> 
> > On Nov 29, 2014, at 8:04 AM, Baptiste Daroussin  wrote:
> > 
> > Hi all,
> > 
> > It is now possible to use an external toolchain to build the kernel and base
> > (tested with gcc 4.9.1 and latest binutils)
> > 
> > Of course a lot of work is needed to make it build cleanly (aka lots of 
> > warning
> > to fix).
> > 
> > What have been tested so far:
> > - sparc64 kernel + world
> > - amd64 kernel + world
> > - powerpc64 kernel + world
> > 
> > mips cannot be tested because upstream gcc never heard of FreeBSD running on
> > mips, and I did not receive any patches for mips.
> 
> I have patches for 4.8 or so knocking around somewhere...

Seems like kan@ have patches for 4.9.1 and was able to build world with it!
(that is mips64)
> 
[...snip...]
> > 
> > also notes that for the kernel a lots of warnings are disabled in
> > share/sys/kern.mk so do not hesitate to remove yourself those -Wno-error= 
> > and
> > fix the issue they are hidding!
> 
> Cool. Please coordinate with me before removing the -Wno-error because they 
> vary by
> architecture.
> 
Sure that was implied or build with all supported toolchains.

regards,
Bapt


pgpgvcrj4Oyt0.pgp
Description: PGP signature

Re: Intel i915 GPU hung

[Lundberg, Johannes]

Waking up an old thread here but I thought I'd share what I've learned.

I think I found out what caused both tearing and crashing when I used
OpenGL.
Since I changed from using xcompmgr to compton with following options

compton --backend glx --vsync opengl-swc --paint-on-overlay
--glx-no-stencil -b

I have never had a crash or tearing. Have no idea why this is but I am just
happy I don't get hung GPU anymore.


--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.

On Fri, Sep 12, 2014 at 2:07 PM, Lundberg, Johannes <
johan...@brilliantservice.co.jp> wrote:

> Now with only "sna" enabled (which I think I read somewhere should be the
> default and that's why I didn't enable it before) I got GPU hung again.
>
> uname -a:
> FreeBSD bsd 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16
> 22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/
> obj/usr/src/sys/GENERIC  amd64
>
> dmesg, error_state, pciconf, pkginfo and Xorg.0.log can be downloaded here
>
> https://dl.dropboxusercontent.com/u/10335306/GPU_hung_logs.zip
>
>
>
> --
> Johannes Lundberg
> BRILLIANTSERVICE CO., LTD.
>
> On Fri, Sep 12, 2014 at 10:14 AM, Garrett Cooper 
> wrote:
>
>> On Thu, Sep 11, 2014 at 6:08 PM, Lundberg, Johannes
>>  wrote:
>> > First try with sna+swapbufferswait+tearfree gave me this after a while
>> >
>> > Xorg.log
>> >
>> > [  1901.000] (EE) intel(0): sna_mode_redisplay: page flipping failed,
>> > disabling CRTC:3 (pipe=0)
>> > [  1901.365] (EE) intel(0): sna_mode_redisplay: page flipping failed,
>> > disabling CRTC:5 (pipe=1)
>> > [  1901.441] (EE) intel(0): Detected a hung GPU, disabling acceleration.
>> > [  2841.578] (II) UnloadModule: "mouse"
>> > [  2841.578] (II) UnloadModule: "kbd"
>> > [  2841.579] (II) intel(0): switch to mode 1366x768@60.0 on pipe 0
>> using
>> > LVDS1, position (0, 0), rotation normal
>> > [  2841.632] (EE) intel(0): failed to set mode: Unknown error: -22
>> > [  2841.632] (II) intel(0): switch to mode 1280x720@60.3 on pipe 1
>> using
>> > VGA1, position (0, 0), rotation normal
>> > [  2841.683] (EE) intel(0): failed to set mode: Unknown error: -22
>>
>> This looks off -- it's the Linux kernel error code for EINVAL
>> (FreeBSD error codes in the kernel being positive).
>> Cheers,
>> -Garrett
>>
>
>

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
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: Intel i915 GPU hung

[Ivan Klymenko]

В Tue, 2 Dec 2014 18:51:53 +0900
"Lundberg, Johannes"  пишет:

> Waking up an old thread here but I thought I'd share what I've
> learned.
> 
> I think I found out what caused both tearing and crashing when I used
> OpenGL.
> Since I changed from using xcompmgr to compton with following options
> 
> compton --backend glx --vsync opengl-swc --paint-on-overlay
> --glx-no-stencil -b
> 
> I have never had a crash or tearing. Have no idea why this is but I
> am just happy I don't get hung GPU anymore.
> 
> 


I am afraid that is not the case.
This method helps to reduce hang GPU to a minimum, but I have with all
the same settings for compton - sometimes it hangs timer GPU.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194766
___
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: compiling failed with RSS enabled

[Adrian Chadd]

Ugh!

please file a bug and I'll go take a look at the code soon.

Thanks!


-a


On 1 December 2014 at 22:21, Eric L. Camachat  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> current failed to compile due to queues uninitialized at line 2883 in
> if_igb.c.
> from the context I guess it should be n_queues instead of queues.
>
> Index: sys/dev/e1000/if_igb.c
> ===
> - --- sys/dev/e1000/if_igb.c(revision 275391)
> +++ sys/dev/e1000/if_igb.c  (working copy)
> @@ -2880,7 +2880,7 @@
>
>  #ifdef RSS
> /* If we're doing RSS, clamp at the number of RSS buckets */
> - - if (queues > rss_getnumbuckets())
> +   if (n_queues > rss_getnumbuckets())
> queues = rss_getnumbuckets();
>  #endif
>
>
> Eric
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iF4EAREIAAYFAlR9WmoACgkQSfBQu3oOwYxnrQD6Ah1uhoNaM3YTXHdOpOA7hw4j
> vZUCA9VU6n/jhUEneVkBALETmBfQudmEz9/eqnmsmer8RbulQdqIKTa8InSvE2yw
> =jLcf
> -END PGP SIGNATURE-
___
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: External toolchain support

[Warner Losh]

> On Dec 2, 2014, at 1:31 AM, Baptiste Daroussin  wrote:
> 
> On Mon, Dec 01, 2014 at 10:05:29PM -0700, Warner Losh wrote:
>> 
>>> On Nov 29, 2014, at 8:04 AM, Baptiste Daroussin  wrote:
>>> 
>>> Hi all,
>>> 
>>> It is now possible to use an external toolchain to build the kernel and base
>>> (tested with gcc 4.9.1 and latest binutils)
>>> 
>>> Of course a lot of work is needed to make it build cleanly (aka lots of 
>>> warning
>>> to fix).
>>> 
>>> What have been tested so far:
>>> - sparc64 kernel + world
>>> - amd64 kernel + world
>>> - powerpc64 kernel + world
>>> 
>>> mips cannot be tested because upstream gcc never heard of FreeBSD running on
>>> mips, and I did not receive any patches for mips.
>> 
>> I have patches for 4.8 or so knocking around somewhere...
> 
> Seems like kan@ have patches for 4.9.1 and was able to build world with it!
> (that is mips64)

Cool. I also ported the arm patches as well. I thought I’d sent them to you, 
but it may have only been in the raw form. I also have patches for the extended 
printf checking for the kernel, though those are much more fragile than 
architecture support.

Warner


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: witness and modules.

[Warner Losh]

> On Dec 1, 2014, at 10:08 PM, Julian Elischer  wrote:
> 
> On 12/1/14, 11:39 PM, John Baldwin wrote:
>> On Friday, November 28, 2014 11:08:35 PM Julian Elischer wrote:
>>> Do we need to compile all modules with witness definitions when
>>> linking with a kernel compiled with witness?
>>> This was true at one stage but I remember some work was done to make
>>> them compatible.
>> You should not need this.  modules always call functions in the kernel for
>> lock operations and this functions are what invoke WITNESS.
>> 
> that's what I thought but empirical evidence disagrees.
> I'll try some more cases.

I swap back and forth all the time between the two. Kernel modules don’t
change when you compile them with WITNESS or without.

Warner



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: External toolchain support

[Baptiste Daroussin]

On Tue, Dec 02, 2014 at 09:23:00AM -0700, Warner Losh wrote:
> 
> > On Dec 2, 2014, at 1:31 AM, Baptiste Daroussin  wrote:
> > 
> > On Mon, Dec 01, 2014 at 10:05:29PM -0700, Warner Losh wrote:
> >> 
> >>> On Nov 29, 2014, at 8:04 AM, Baptiste Daroussin  wrote:
> >>> 
> >>> Hi all,
> >>> 
> >>> It is now possible to use an external toolchain to build the kernel and 
> >>> base
> >>> (tested with gcc 4.9.1 and latest binutils)
> >>> 
> >>> Of course a lot of work is needed to make it build cleanly (aka lots of 
> >>> warning
> >>> to fix).
> >>> 
> >>> What have been tested so far:
> >>> - sparc64 kernel + world
> >>> - amd64 kernel + world
> >>> - powerpc64 kernel + world
> >>> 
> >>> mips cannot be tested because upstream gcc never heard of FreeBSD running 
> >>> on
> >>> mips, and I did not receive any patches for mips.
> >> 
> >> I have patches for 4.8 or so knocking around somewhere...
> > 
> > Seems like kan@ have patches for 4.9.1 and was able to build world with it!
> > (that is mips64)
> 
> Cool. I also ported the arm patches as well. I thought I’d sent them to you, 
> but it may have only been in the raw form. I also have patches for the 
> extended printf checking for the kernel, though those are much more fragile 
> than architecture support.
> 
The format extension I have them already, otherwise I won't be able to boot the
kernel (provided by kan as well).

See devel/powerp64-gcc/files/*

Regards,
Bapt


pgpscKUJgDowj.pgp
Description: PGP signature

Re: witness and modules.

[Julian Elischer]

On 12/3/14, 12:24 AM, Warner Losh wrote:

On Dec 1, 2014, at 10:08 PM, Julian Elischer  wrote:

On 12/1/14, 11:39 PM, John Baldwin wrote:

On Friday, November 28, 2014 11:08:35 PM Julian Elischer wrote:

Do we need to compile all modules with witness definitions when
linking with a kernel compiled with witness?
This was true at one stage but I remember some work was done to make
them compatible.

You should not need this.  modules always call functions in the kernel for
lock operations and this functions are what invoke WITNESS.


that's what I thought but empirical evidence disagrees.
I'll try some more cases.

I swap back and forth all the time between the two. Kernel modules don’t
change when you compile them with WITNESS or without.

Warner


it's a 10.0 based system.

the zfs kernel module grew a reference to witness_restore and 
witness_save  when it was compiled with witness in opt_global.h.
I certainly wouldn't load with a standard kernel. it may have been 
somethign funny with the zfs compat layer stuff, and I'm pretty sure 
people don't use zfs as a module much, but it was definitely there. 
note: it'd probably work the other way around.. a non-witness module 
would probably load on a witness kernel.. none of the other kernel 
modules had that extra reference so I think it's specific to zfs.   
Maybe to the way it was compiled.. the sources are pretty standard but 
the makefiles are a bit hacked..




___
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: compiling failed with RSS enabled

[Eric L. Camachat]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 12/02/2014 07:30, Adrian Chadd wrote:
> Ugh!
> 
> please file a bug and I'll go take a look at the code soon.
> 
> Thanks!
> 
> 
> -a

Someone already did:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195518

Eric
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREIAAYFAlR9+ScACgkQSfBQu3oOwYyNFQD+OOCF2hxRIrHuXfH00HEtLTwe
DeUYVqyM4ZODqIidD3cA/00teVl3L1CB7OANdNDh+fMSHS3coPZqxT6J/uJhDJ0F
=3sM8
-END PGP SIGNATURE-
___
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: witness and modules.

[Julian Elischer]

On 12/3/14, 12:24 AM, Warner Losh wrote:

On Dec 1, 2014, at 10:08 PM, Julian Elischer  wrote:

On 12/1/14, 11:39 PM, John Baldwin wrote:

On Friday, November 28, 2014 11:08:35 PM Julian Elischer wrote:

Do we need to compile all modules with witness definitions when
linking with a kernel compiled with witness?
This was true at one stage but I remember some work was done to make
them compatible.

You should not need this.  modules always call functions in the kernel for
lock operations and this functions are what invoke WITNESS.


that's what I thought but empirical evidence disagrees.
I'll try some more cases.

I swap back and forth all the time between the two. Kernel modules don’t
change when you compile them with WITNESS or without.

not entirely..
hwpmc.ko: U witness_restore
hwpmc.ko: U witness_save
zfs.ko: U witness_restore
zfs.ko: U witness_save

Warner



___
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"

Jenkins build became unstable: FreeBSD_HEAD-tests2 #361

[jenkins-admin]

See 

___
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"

Jenkins build is back to stable : FreeBSD_HEAD-tests2 #362

[jenkins-admin]

See 

___
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"