search for: urgh

On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: > On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > > Urgh, is for some mysterious reason the __bug_table section of modules > > ending up in RO memory? > > > > I forever get lost in that link magic :/ > > +1 > > drm.ko >  20 __bug_table   00000630  0000000000000000  0000000000000000  0004bff3  2**0 >                 ...

...t_CrashRecoveryContext.cpp_00000000_BFDB511124CrashRecoveryContextImplEEE > --- >> N4llvm3sys11ThreadLocalIKN144_GLOBAL__N__usr_home_erik_freebsd_head_src_lib_clang_libllvmsupport_.._.._.._contrib_llvm_lib_Support_CrashRecoveryContext.cpp_00000000_A7307A7424CrashRecoveryContextImplEEE > Urgh, are we using random elements in the unnamed namespace symbol generation? Sebastian

Hello LLVM'ers I have noticed that two consecutive builds of clang, clang++ and tblgen don't produce identical binaries (as in md5 sums) on identical source code (I'm on FreeBSD). I ran strings(1) on the two clang binaries, and I get the following: 248400,248403c248400,248403 <

...display logic (when flipping between the two drivers). Perhaps this Native EFI mode does something along those lines as well. (Although in those cases, running the VBIOS didn't help... although each VBIOS is a unique snowflake. In some other cases, double-running the VBIOS leads to a hung GPU. Urgh.) -ilia

...text.cpp_00000000_BFDB511124CrashRecoveryContextImplEEE >> --- >>> N4llvm3sys11ThreadLocalIKN144_GLOBAL__N__usr_home_erik_freebsd_head_src_lib_clang_libllvmsupport_.._.._.._contrib_llvm_lib_Support_CrashRecoveryContext.cpp_00000000_A7307A7424CrashRecoveryContextImplEEE >> > Urgh, are we using random elements in the unnamed namespace symbol > generation? This is definitely not the direct output of clang. We mangle anonymous namespaces the same way that GCC does, i.e. 12_GLOBAL__N_1. If there's a compiler that mangles filenames into anonymous namespace names — or...

...root.... > > 19d436268dde95389c616bb3819da73f0a8b28a8 is the first bad commit > commit 19d436268dde95389c616bb3819da73f0a8b28a8 > Author: Peter Zijlstra <peterz at infradead.org> > Date: Sat Feb 25 08:56:53 2017 +0100 > > debug: Add _ONCE() logic to report_bug() Urgh, is for some mysterious reason the __bug_table section of modules ending up in RO memory? I forever get lost in that link magic :/

Urgh... I misrouted this to vorbs@xiph.org... sorry for this. -------------- next part -------------- An embedded message was scrubbed... From: Maik Merten <maikmerten@gmx.net> Subject: Re: [Vorbis-dev] Low level optimization Date: Thu, 10 Feb 2005 16:39:25 +0100 Size: 959 Url: http://lists.xiph.o...

...text.cpp_00000000_BFDB511124CrashRecoveryContextImplEEE >> --- >>> N4llvm3sys11ThreadLocalIKN144_GLOBAL__N__usr_home_erik_freebsd_head_src_lib_clang_libllvmsupport_.._.._.._contrib_llvm_lib_Support_CrashRecoveryContext.cpp_00000000_A7307A7424CrashRecoveryContextImplEEE >> > Urgh, are we using random elements in the unnamed namespace symbol > generation? > > Sebastian > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvm...

...TOPOLOGY isn't selected, the call to > virt_dma_configure() is compiled out. > > As long as the information is consistent, platforms can provide both a > device-tree and a built-in topology, and the IOMMU infrastructure is > able to deal with multiple DMA configuration methods. Urgh, it's already been established[1] that having IOMMU setup tied to DMA configuration at driver probe time is not just conceptually wrong but actually broken, so the concept here worries me a bit. In a world where of_iommu_configure() and friends are being called much earlier around iommu_pro...

Urgh? I modified the FreeBSD kernel to allow all_xx_fd() calls on O_PATH descriptors and that seems make vfs_zfsacl to work fine. Not 100% tested but I could atleast view and modify the ACL on some stuff from a Windows client via Samba that way. I?m not sure I?ll be able to get them to implement this...

> On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote: > >> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote: >> I was hoping to hear this from you :-) If I am to suggest how we can >> move forward I'd propose: >> - Check if pure TSC can be used on SkyLake+ systems (where TSC scaling >> is supported). >> -

> On Oct 4, 2018, at 1:11 AM, Peter Zijlstra <peterz at infradead.org> wrote: > >> On Thu, Oct 04, 2018 at 09:54:45AM +0200, Vitaly Kuznetsov wrote: >> I was hoping to hear this from you :-) If I am to suggest how we can >> move forward I'd propose: >> - Check if pure TSC can be used on SkyLake+ systems (where TSC scaling >> is supported). >> -

On Wed, 2017-07-12 at 07:37 -0400, Ilia Mirkin wrote: > On Wed, Jul 12, 2017 at 7:25 AM, Mike Galbraith <efault at gmx.de> wrote: > > On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote: > >> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote: > >> > > >> > Some display stuff did change for 4.13 for GM20x+ boards. If it's not > >>

I'm seeing this on a HP Blade and i'm not sure why this is happning since the nature of the issue is so wierd. I compiled mboot.c with a DEBUG defined in the mboot.c file. In the funciton init_mmap(), it prints the e820 map and on the HP blade this map values come out to be totally random. Some weird numbers which dont make any sense at all. However, if i add a while(1); or a exit(1); at

Hey, On Mon, Feb 27, 2012 at 10:26 PM, Linus van Geuns <linus@vangeuns.name> wrote: > Hey, > > I am currently considering a two machine Xen setup based on AMD Opterons, > more precisely Dell R515s or R415s with dual Opteron 4274HE. > Does anyone has some Xen setup(s) running on top of Opterons 4274HE, Opteron > 4200 or Dell R515 machines and is willing to share some

...0_BFDB511124CrashRecoveryContextImplEEE >>> --- >>>> N4llvm3sys11ThreadLocalIKN144_GLOBAL__N__usr_home_erik_freebsd_head_src_lib_clang_libllvmsupport_.._.._.._contrib_llvm_lib_Support_CrashRecoveryContext.cpp_00000000_A7307A7424CrashRecoveryContextImplEEE >>> >> Urgh, are we using random elements in the unnamed namespace symbol >> generation? >> >> Sebastian >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.ui...

...flipping between the two drivers). > Perhaps this Native EFI mode does something along those lines as well. > (Although in those cases, running the VBIOS didn't help... although > each VBIOS is a unique snowflake. In some other cases, double-running > the VBIOS leads to a hung GPU. Urgh.) I'm open to experiments. I've moved to vanilla 4.8.17 from 4.8.15 and will jump into 4.9.x this weekend. I'll check with and without NvForcePost as I upgrade. Not gonna hold my breath, though -- I first noticed this a couple years ago and it hasn't been a priority. But note,...

...389c616bb3819da73f0a8b28a8 is the first bad commit > > commit 19d436268dde95389c616bb3819da73f0a8b28a8 > > Author: Peter Zijlstra <peterz at infradead.org> > > Date: Sat Feb 25 08:56:53 2017 +0100 > > > > debug: Add _ONCE() logic to report_bug() > > Urgh, is for some mysterious reason the __bug_table section of modules > ending up in RO memory? > > I forever get lost in that link magic :/ +1 drm.ko  20 __bug_table   00000630  0000000000000000  0000000000000000  0004bff3  2**0                   CONTENTS, ALLOC, LOAD, RELOC, READONLY, DAT...

+++ Peter Zijlstra [14/07/17 18:10 +0200]: >On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: >> On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > >> > Urgh, is for some mysterious reason the __bug_table section of modules >> > ending up in RO memory? >> > >> > I forever get lost in that link magic :/ >> >> +1 >> >> drm.ko >>  20 __bug_table   00000630  0000000000000000  0000000000000000  0004bff...

...Fri, Jul 14, 2017 at 06:33:01PM +0200, Mike Galbraith wrote: > On Fri, 2017-07-14 at 18:10 +0200, Peter Zijlstra wrote: > > On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote: > > > On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote: > > > > > > Urgh, is for some mysterious reason the __bug_table section of modules > > > > ending up in RO memory? > > > > > > > > I forever get lost in that link magic :/ > > > > > > +1 > > > > > > drm.ko > > >  20 __bug_table   00...