Re: [regression] Re: Linux 4.3-rc1

quot;drm/i915: Add primary plane to mask if it's visible" is the correct fix. Did not try it. - sed@ - [1] http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes=721a09f7393de6c28a07516dccd654c6e995944a > thanks, > -- Shuah >> >> On Tue, Sep 15, 2015 at 03:2

Re: [Linux-v4.2-10463-g9a9952bbd76a] i915: WARNING: intel_display.c:1377 assert_planes_disabled

On Sun, Sep 13, 2015 at 9:06 AM, Sedat Dilek wrote: > On Wed, Sep 9, 2015 at 4:42 AM, Sedat Dilek wrote: >> [ TO INTEL DRM DRIVERS maintainers ] >> >> Hi, >> >> out of curiosity and to play with the new bindeb-pkg make-target I >> built pre-v4.3-rc1 (git

Re: [Linux-v4.2-10463-g9a9952bbd76a] i915: WARNING: intel_display.c:1377 assert_planes_disabled

On Sun, Sep 13, 2015 at 9:06 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Wed, Sep 9, 2015 at 4:42 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> [ TO INTEL DRM DRIVERS maintainers ] >> >> Hi, >> >> out of curiosity and to play with the new b

Re: [regression] Re: Linux 4.3-rc1

On Wed, Sep 23, 2015 at 10:48 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Wed, Sep 23, 2015 at 3:31 PM, Shuah Khan <shua...@osg.samsung.com> wrote: >> On 09/23/2015 02:56 AM, Daniel Vetter wrote: >>> Another regression for Jairo to track. >>> -Danie

Re: [regression] Re: [Linux-v4.2-10463-g9a9952bbd76a] i915: WARNING: intel_display.c:1377 assert_planes_disabled

issue here. - sed@ - [1] http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes=721a09f7393de6c28a07516dccd654c6e995944a > -Daniel > > On Wed, Sep 23, 2015 at 08:23:04AM +0200, Sedat Dilek wrote: >> On Sun, Sep 13, 2015 at 9:06 AM, Sedat Dilek <sedat.di...@gmail.com>

Re: [Linux 4.2-rc8+...v4.3-rc2] REGRESSION: ppp: circular locking dependency detected: [pppd] ppp_dev_uninit() | rtnl_lock()

On Wed, Sep 23, 2015 at 10:46 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Wed, Sep 23, 2015 at 12:38 PM, Guillaume Nault <g.na...@alphalink.fr> > wrote: >> On Wed, Sep 23, 2015 at 08:06:16AM +0200, Sedat Dilek wrote: >>> Without reverting the below culpri

Re: [regression] Re: Linux 4.3-rc1

. > Looks like the patch "drm/i915: Add primary plane to mask if it's visible" is the correct fix. Did not try it. - sed@ - [1] http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes=721a09f7393de6c28a07516dccd654c6e995944a > thanks, > -- Shuah >> >>

Re: [Linux 4.2-rc8+...v4.3-rc2] REGRESSION: ppp: circular locking dependency detected: [pppd] ppp_dev_uninit() | rtnl_lock()

On Wed, Sep 23, 2015 at 12:38 PM, Guillaume Nault <g.na...@alphalink.fr> wrote: > On Wed, Sep 23, 2015 at 08:06:16AM +0200, Sedat Dilek wrote: >> Without reverting the below culprit ppp patch... >> >> commit/?id=8cb775bc0a34dc596837e7da03fd22c747be618b >> (&qu

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

f Can you look at this? - Sedat - > Hi Sedat Dilek > > [ 24.705704] irq event stamp: 19968 > [ 24.705706] hardirqs last enabled at (19967): [] > _raw_spin_unlock_irq+0x32/0x60 > [ 24.705713] hardirqs last disabled at (19968): [] > del_timer_sync+0x37/0x110 > >

Re: [PATCH] kbuild: llvmlinux: Set appropriate compiler-flag for CONFIG_CC_OPTIMIZE_FOR_SIZE

file in Documentation-dir? - Sedat - > > On 09/14/15 21:19, Sedat Dilek wrote: >> >> Based on a patch of Behan Webster (see [1]). >> >> CLANG (here: v3.7) requires '-Oz' as OptLevel to be set. >> >> A Linux v4.3-rc1 kernel built fine with CONFIG_CC_OPTIMI

[PATCH] kbuild: llvmlinux: Set appropriate compiler-flag for CONFIG_CC_OPTIMIZE_FOR_SIZE

Based on a patch of Behan Webster (see [1]). CLANG (here: v3.7) requires '-Oz' as OptLevel to be set. A Linux v4.3-rc1 kernel built fine with CONFIG_CC_OPTIMIZE_FOR_SIZE=y and boots on bare metal. This is a Ubuntu/precise AMD64 system. Tested against Linux v4.3-rc1 and a refreshed llvmlinux

[PATCH] kbuild: llvmlinux: Fix -fno-delete-null-pointer-checks compiler-flag

CLANG (here: v3.7) does not support '-fno-delete-null-pointer-checks' as a compiler-flag. Fix the HOSTCFLAGS and KBUILD_CFLAGS settings accordingly. Furthermore, move and correct the $HOSTCC check. Tested against Linux v4.3-rc1 and a refreshed llvmlinux patchset. --- Makefile | 8 +--- 1

Re: Linux 4.3-rc1

Hi, I have reported the same issue in [0]... You write in [1]... [ cut here ] WARNING: CPU: 3 PID: 24 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xe4/0x150 [i915]() plane A assertion failure, should be disabled but not ... I can confirm this was

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

On Mon, Sep 14, 2015 at 4:00 PM, Sedat Dilek wrote: > On Thu, Sep 10, 2015 at 3:04 AM, Lai Jiangshan wrote: >> Hi, TJ >> >> I think we need to add might_sleep() on the top of __cancel_work_timer(). >> The might_sleep() on the start_flush_work() doe

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

On Fri, Sep 11, 2015 at 6:12 PM, Sedat Dilek wrote: > On Thu, Sep 10, 2015 at 4:53 PM, Tejun Heo wrote: >> On Thu, Sep 10, 2015 at 10:52:27AM -0400, Tejun Heo wrote: >>> Hey, >>> >>> On Thu, Sep 10, 2015 at 09:04:27AM +0800, Lai Jiangshan wrote: >

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 11:59 AM, Ingo Molnar wrote: > > * Sedat Dilek wrote: > >> From my side... How can the correbolation be improved...? > > The best workflow would be for someone to send patches that are considered > clean > enough. > What do you mean by &quo

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 11:35 AM, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > >> > I invite you to join the discussion at LLVMLinux... As I know... "YES, you >> > can." Linux x86/x86_64 (assembler) Kung-Fu. ( I admit I have not these >> > skillz. >> > ) >> >> Its a matter of time for me; I

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 9:35 AM, Sedat Dilek wrote: > On Mon, Sep 14, 2015 at 9:12 AM, Peter Zijlstra wrote: >> On Sun, Sep 13, 2015 at 04:33:39AM +0200, Sedat Dilek wrote: >>> > It looks like an inline-optimization bug in CLANG when the compiler's >>> > opti

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 9:12 AM, Peter Zijlstra wrote: > On Sun, Sep 13, 2015 at 04:33:39AM +0200, Sedat Dilek wrote: >> > It looks like an inline-optimization bug in CLANG when the compiler's >> > optimization-level is higher than -O2. > >> > [1] >> >

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 9:12 AM, Peter Zijlstra wrote: > On Sun, Sep 13, 2015 at 04:33:39AM +0200, Sedat Dilek wrote: >> > It looks like an inline-optimization bug in CLANG when the compiler's >> > optimization-level is higher than -O2. > >> > [1] >> >

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

On Fri, Sep 11, 2015 at 6:12 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Thu, Sep 10, 2015 at 4:53 PM, Tejun Heo <t...@kernel.org> wrote: >> On Thu, Sep 10, 2015 at 10:52:27AM -0400, Tejun Heo wrote: >>> Hey, >>> >>> On Thu, Sep 10, 2015 a

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

On Mon, Sep 14, 2015 at 4:00 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Thu, Sep 10, 2015 at 3:04 AM, Lai Jiangshan <jiangshan...@gmail.com> wrote: >> Hi, TJ >> >> I think we need to add might_sleep() on the top of __cancel_work_timer(). >> Th

Re: Linux 4.3-rc1

Hi, I have reported the same issue in [0]... You write in [1]... [ cut here ] WARNING: CPU: 3 PID: 24 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xe4/0x150 [i915]() plane A assertion failure, should be disabled but not ... I can confirm this was

[PATCH] kbuild: llvmlinux: Set appropriate compiler-flag for CONFIG_CC_OPTIMIZE_FOR_SIZE

Based on a patch of Behan Webster (see [1]). CLANG (here: v3.7) requires '-Oz' as OptLevel to be set. A Linux v4.3-rc1 kernel built fine with CONFIG_CC_OPTIMIZE_FOR_SIZE=y and boots on bare metal. This is a Ubuntu/precise AMD64 system. Tested against Linux v4.3-rc1 and a refreshed llvmlinux

[PATCH] kbuild: llvmlinux: Fix -fno-delete-null-pointer-checks compiler-flag

CLANG (here: v3.7) does not support '-fno-delete-null-pointer-checks' as a compiler-flag. Fix the HOSTCFLAGS and KBUILD_CFLAGS settings accordingly. Furthermore, move and correct the $HOSTCC check. Tested against Linux v4.3-rc1 and a refreshed llvmlinux patchset. --- Makefile | 8 +--- 1

Re: [PATCH] kbuild: llvmlinux: Set appropriate compiler-flag for CONFIG_CC_OPTIMIZE_FOR_SIZE

vmlinux (clang). Do you have a doc-file in Documentation-dir? - Sedat - > > On 09/14/15 21:19, Sedat Dilek wrote: >> >> Based on a patch of Behan Webster (see [1]). >> >> CLANG (here: v3.7) requires '-Oz' as OptLevel to be set. >> >> A Linux v4.3-rc1 kernel

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 9:35 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Mon, Sep 14, 2015 at 9:12 AM, Peter Zijlstra <pet...@infradead.org> wrote: >> On Sun, Sep 13, 2015 at 04:33:39AM +0200, Sedat Dilek wrote: >>> > It looks like an inline-optimization

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 9:12 AM, Peter Zijlstra <pet...@infradead.org> wrote: > On Sun, Sep 13, 2015 at 04:33:39AM +0200, Sedat Dilek wrote: >> > It looks like an inline-optimization bug in CLANG when the compiler's >> > optimization-level is higher than

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 9:12 AM, Peter Zijlstra <pet...@infradead.org> wrote: > On Sun, Sep 13, 2015 at 04:33:39AM +0200, Sedat Dilek wrote: >> > It looks like an inline-optimization bug in CLANG when the compiler's >> > optimization-level is higher than

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 11:35 AM, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > >> > I invite you to join the discussion at LLVMLinux... As I know... "YES, you >> > can." Linux x86/x86_64 (assembler) Kung-Fu. ( I admit I have not these >> > skillz. >>

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Mon, Sep 14, 2015 at 11:59 AM, Ingo Molnar <mi...@kernel.org> wrote: > > * Sedat Dilek <sedat.di...@gmail.com> wrote: > >> From my side... How can the correbolation be improved...? > > The best workflow would be for someone to send patches that are considered

Re: Use (two) different compilers at build-time?

On Thu, Sep 10, 2015 at 2:25 AM, Fengguang Wu wrote: > On Mon, Sep 07, 2015 at 09:12:58PM +0200, Sedat Dilek wrote: >> Hi, >> >> is it possible to use a different compiler at build-time? > > btw, it'd be great if clang can just work on mainline kernel. > I am not a

Re: [Linux-v4.2-10463-g9a9952bbd76a] i915: WARNING: intel_display.c:1377 assert_planes_disabled

On Wed, Sep 9, 2015 at 4:42 AM, Sedat Dilek wrote: > [ TO INTEL DRM DRIVERS maintainers ] > > Hi, > > out of curiosity and to play with the new bindeb-pkg make-target I > built pre-v4.3-rc1 (git-describe says v4.2-10463-g9a9952bbd76a) > Debian-kernel packages. > >

Re: [Linux-v4.2-10463-g9a9952bbd76a] i915: WARNING: intel_display.c:1377 assert_planes_disabled

On Wed, Sep 9, 2015 at 4:42 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > [ TO INTEL DRM DRIVERS maintainers ] > > Hi, > > out of curiosity and to play with the new bindeb-pkg make-target I > built pre-v4.3-rc1 (git-describe says v4.2-10463-g9a9952bbd76a) > Debian

Re: Use (two) different compilers at build-time?

On Thu, Sep 10, 2015 at 2:25 AM, Fengguang Wu <fengguang...@intel.com> wrote: > On Mon, Sep 07, 2015 at 09:12:58PM +0200, Sedat Dilek wrote: >> Hi, >> >> is it possible to use a different compiler at build-time? > > btw, it'd be great if clang can just work on main

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 2:54 PM, Peter Zijlstra wrote: > On Wed, Sep 09, 2015 at 12:05:50PM +0200, Sedat Dilek wrote: >> I can boot into a CLANG v3.7 compiled Linux-kernel when lib/bitmap is >> compiled with GCC (here: v4.9). >> >> CONFIG_OPTIMIZE_INLINING has no eff

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 2:54 PM, Peter Zijlstra <pet...@infradead.org> wrote: > On Wed, Sep 09, 2015 at 12:05:50PM +0200, Sedat Dilek wrote: >> I can boot into a CLANG v3.7 compiled Linux-kernel when lib/bitmap is >> compiled with GCC (here: v4.9). >> >> CONFI

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

On Thu, Sep 10, 2015 at 4:53 PM, Tejun Heo wrote: > On Thu, Sep 10, 2015 at 10:52:27AM -0400, Tejun Heo wrote: >> Hey, >> >> On Thu, Sep 10, 2015 at 09:04:27AM +0800, Lai Jiangshan wrote: >> > I think we need to add might_sleep() on the top of __cancel_work_timer(). >> > The might_sleep() on the

Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680

On Thu, Sep 10, 2015 at 4:53 PM, Tejun Heo wrote: > On Thu, Sep 10, 2015 at 10:52:27AM -0400, Tejun Heo wrote: >> Hey, >> >> On Thu, Sep 10, 2015 at 09:04:27AM +0800, Lai Jiangshan wrote: >> > I think we need to add might_sleep() on the top of __cancel_work_timer(). >> > The

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 9:14 AM, Baoquan He wrote: > On 09/09/15 at 08:56am, Sedat Dilek wrote: > >> None of the force-inlining patches helped. >> >> cpumask: Force inlining of cpumask_weight function >> nodemask: Force inlining of __nodes_weight fun

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 9:14 AM, Baoquan He <b...@redhat.com> wrote: > On 09/09/15 at 08:56am, Sedat Dilek wrote: > >> None of the force-inlining patches helped. >> >> cpumask: Force inlining of cpumask_weight function >> nodemask: Force inlining o

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 5:25 AM, Baoquan He wrote: > Hi Sedat, > > On 09/09/15 at 04:51am, Sedat Dilek wrote: >> On Wed, Sep 9, 2015 at 4:29 AM, Baoquan He wrote: >> commit 1a1d48a4a8fde49aedc045d894efe67173d59fe0 >> "linux/bitmap: Force inlining of bitmap w

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 5:04 AM, Sedat Dilek wrote: > On Wed, Sep 9, 2015 at 4:51 AM, Sedat Dilek wrote: >> On Wed, Sep 9, 2015 at 4:29 AM, Baoquan He wrote: >>> >>> Seems it happened when call num_possible_cpus() which is a inline >>> function to call __bitma

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 4:29 AM, Baoquan He wrote: > > Seems it happened when call num_possible_cpus() which is a inline > function to call __bitmap_weight(). So did you check > lib/bitmap.c:__bitmap_weight() by objdump? > > setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:1 nr_node_ids:1

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 5:04 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Wed, Sep 9, 2015 at 4:51 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> On Wed, Sep 9, 2015 at 4:29 AM, Baoquan He <b...@redhat.com> wrote: >>> >>> Seems it happened wh

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 4:29 AM, Baoquan He wrote: > > Seems it happened when call num_possible_cpus() which is a inline > function to call __bitmap_weight(). So did you check > lib/bitmap.c:__bitmap_weight() by objdump? > > setup_percpu: NR_CPUS:256 nr_cpumask_bits:256

Re: [llvmlinux] percpu | bitmap issue? (Cannot boot on bare metal due to a kernel NULL pointer dereference)

On Wed, Sep 9, 2015 at 5:25 AM, Baoquan He <b...@redhat.com> wrote: > Hi Sedat, > > On 09/09/15 at 04:51am, Sedat Dilek wrote: >> On Wed, Sep 9, 2015 at 4:29 AM, Baoquan He <b...@redhat.com> wrote: >> commit 1a1d48a4a8fde49aedc045d894efe67173d59fe0 >> "l

Re: Use (two) different compilers at build-time?

On Tue, Sep 8, 2015 at 7:45 AM, Sedat Dilek wrote: > On Tue, Sep 8, 2015 at 12:30 AM, Sedat Dilek wrote: >> On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek wrote: >>> On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds >>> wrote: >>>> On Mon, Sep

Re: Use (two) different compilers at build-time?

On Tue, Sep 8, 2015 at 12:30 AM, Sedat Dilek wrote: > On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek wrote: >> On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds >> wrote: >>> On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote: >>>> >>>> That does n

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek wrote: > On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds > wrote: >> On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote: >>> >>> That does not work. >> >> .. because you didn't do what I told you to d

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds wrote: > On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek wrote: >> >> That does not work. > > .. because you didn't do what I told you to do. > >> I copied a gcc-compiled percpu.o OR deleted/renamed percpu.o and &g

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 10:42 PM, Linus Torvalds wrote: > On Mon, Sep 7, 2015 at 1:31 PM, Sedat Dilek wrote: >> >> So, how do I do that conveniently? > > For a single file? Just compile everything with the primary compiler, > and then delete the single object f

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 10:15 PM, Linus Torvalds wrote: > On Mon, Sep 7, 2015 at 12:12 PM, Sedat Dilek wrote: >> >> is it possible to use a different compiler at build-time? >> >> I have here a problem with mm/percpu.c and wanted to build everything >> wit

Use (two) different compilers at build-time?

Hi, is it possible to use a different compiler at build-time? I have here a problem with mm/percpu.c and wanted to build everything with LLVM/Clang but this single file with GCC. Is that possible? Regards, - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: Use (two) different compilers at build-time?

On Tue, Sep 8, 2015 at 7:45 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Tue, Sep 8, 2015 at 12:30 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: >>> On Mon, Sep 7, 2015 at

Re: Use (two) different compilers at build-time?

On Tue, Sep 8, 2015 at 12:30 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds >> <torva...@linux-foundation.org> wrote: >>> O

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 11:20 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds > <torva...@linux-foundation.org> wrote: >> On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: >>> >&

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 10:42 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > On Mon, Sep 7, 2015 at 1:31 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> >> So, how do I do that conveniently? > > For a single file? Just compile everything with the pr

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 10:59 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > On Mon, Sep 7, 2015 at 1:53 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> >> That does not work. > > .. because you didn't do what I told you to do. > >> I copied

Re: Use (two) different compilers at build-time?

On Mon, Sep 7, 2015 at 10:15 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > On Mon, Sep 7, 2015 at 12:12 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> >> is it possible to use a different compiler at build-time? >> >> I have here a probl

Use (two) different compilers at build-time?

Hi, is it possible to use a different compiler at build-time? I have here a problem with mm/percpu.c and wanted to build everything with LLVM/Clang but this single file with GCC. Is that possible? Regards, - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: [Linux 4.2-rc8+] circular locking dependency detected: [pppd] ppp_dev_uninit() | rtnl_lock()

> Could this be caused by this commit...? > > commit 8cb775bc0a34dc596837e7da03fd22c747be618b > "ppp: fix device unregistration upon netns deletion" > With the Revert "ppp: fix device unregistration upon netns deletion" I do not see any lockdep issues. - Sedat - -- To unsubscribe from this list:

Re: [Linux 4.2-rc8+] circular locking dependency detected: [pppd] ppp_dev_uninit() | rtnl_lock()

> Could this be caused by this commit...? > > commit 8cb775bc0a34dc596837e7da03fd22c747be618b > "ppp: fix device unregistration upon netns deletion" > With the Revert "ppp: fix device unregistration upon netns deletion" I do not see any lockdep issues. - Sedat - -- To unsubscribe from this list:

Re: [Intel-gfx] [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Fri, Aug 14, 2015 at 10:24 AM, Hans de Goede wrote: > Hi, > > > On 13-08-15 16:33, Hans de Goede wrote: >> >> Hi, >> >> On 12-08-15 21:26, Ville Syrjälä wrote: >>> >>> On Mon, Aug 10, 2015 at 08:29:00PM +0200, Sedat Dilek wrote: >>>

Re: [Intel-gfx] [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Fri, Aug 14, 2015 at 10:24 AM, Hans de Goede hdego...@redhat.com wrote: Hi, On 13-08-15 16:33, Hans de Goede wrote: Hi, On 12-08-15 21:26, Ville Syrjälä wrote: On Mon, Aug 10, 2015 at 08:29:00PM +0200, Sedat Dilek wrote: On Sat, Aug 1, 2015 at 2:23 PM, Sedat Dilek sedat.di

Re: [Intel-gfx] [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Thu, Aug 13, 2015 at 4:33 PM, Hans de Goede wrote: > Hi, > > On 12-08-15 21:26, Ville Syrjälä wrote: >> >> On Mon, Aug 10, 2015 at 08:29:00PM +0200, Sedat Dilek wrote: >>> >>> On Sat, Aug 1, 2015 at 2:23 PM, Sedat Dilek >>> wrote: >>

Re: [Intel-gfx] [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Wed, Aug 12, 2015 at 9:26 PM, Ville Syrjälä wrote: > On Mon, Aug 10, 2015 at 08:29:00PM +0200, Sedat Dilek wrote: >> On Sat, Aug 1, 2015 at 2:23 PM, Sedat Dilek wrote: >> > On Mon, Jul 27, 2015 at 12:33 AM, Sedat Dilek >> > wrote: >> >> Hi, >> &g

Re: [Intel-gfx] [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Wed, Aug 12, 2015 at 9:26 PM, Ville Syrjälä ville.syrj...@linux.intel.com wrote: On Mon, Aug 10, 2015 at 08:29:00PM +0200, Sedat Dilek wrote: On Sat, Aug 1, 2015 at 2:23 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jul 27, 2015 at 12:33 AM, Sedat Dilek sedat.di...@gmail.com wrote

Re: [Intel-gfx] [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Thu, Aug 13, 2015 at 4:33 PM, Hans de Goede hdego...@redhat.com wrote: Hi, On 12-08-15 21:26, Ville Syrjälä wrote: On Mon, Aug 10, 2015 at 08:29:00PM +0200, Sedat Dilek wrote: On Sat, Aug 1, 2015 at 2:23 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jul 27, 2015 at 12:33 AM

Re: [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Mon, Jul 27, 2015 at 12:33 AM, Sedat Dilek wrote: > Hi, > > this my first build of a 4.2-rcN Linux-kernel and I see this... > Just FYI: I am *not* seeing this with drm-intel-nightly from below url. Also, I plan to test Linux v4.2-rc5. - Sedat - [1] http://kernel.ubuntu.com

Re: [4.2-rc4] acpi|drm|i915: circular locking dependency: acpi_video_get_backlight_type

On Mon, Jul 27, 2015 at 12:33 AM, Sedat Dilek sedat.di...@gmail.com wrote: Hi, this my first build of a 4.2-rcN Linux-kernel and I see this... Just FYI: I am *not* seeing this with drm-intel-nightly from below url. Also, I plan to test Linux v4.2-rc5. - Sedat - [1] http

Re: mmotm 2015-05-22-14-48 uploaded

On Fri, May 22, 2015 at 11:48 PM, wrote: [...] > You will need quilt to apply these patches to the latest Linus release (3.x > or 3.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > http://ozlabs.org/~akpm/mmotm/series > [...] Should be updated to "4.x" and "4.x-rcY". -

Re: mmotm 2015-05-22-14-48 uploaded

On Fri, May 22, 2015 at 11:48 PM, a...@linux-foundation.org wrote: [...] You will need quilt to apply these patches to the latest Linus release (3.x or 3.x-rcY). The series file is in broken-out.tar.gz and is duplicated in http://ozlabs.org/~akpm/mmotm/series [...] Should be updated to 4.x

Re: [PATCH] MODSIGN: Change default key details [ver #2]

On Sat, May 2, 2015 at 6:12 AM, Linus Torvalds wrote: > On Fri, May 1, 2015 at 2:41 PM, Abelardo Ricart III > wrote: >> >> Here's my two-line patch strictly defining the build order, for your perusal. > > Ok, so this looks possible and sounds like it could explain the issues. > > But I'd like

Re: [PATCH] MODSIGN: Change default key details [ver #2]

On Sat, May 2, 2015 at 6:12 AM, Linus Torvalds torva...@linux-foundation.org wrote: On Fri, May 1, 2015 at 2:41 PM, Abelardo Ricart III aric...@memnix.com wrote: Here's my two-line patch strictly defining the build order, for your perusal. Ok, so this looks possible and sounds like it could

Re: [PATCH] MODSIGN: Change default key details [ver #2]

On Thu, Apr 30, 2015 at 4:50 PM, David Howells wrote: > Sedat Dilek wrote: > >> This happened a 2nd time with a different kernel-series! >> Not sure why this was the case. >> It did not happen when rebuilding with the same kernel-config again. >> Not sure if paral

Re: [PATCH] MODSIGN: Change default key details [ver #2]

On Thu, Apr 30, 2015 at 4:50 PM, David Howells dhowe...@redhat.com wrote: Sedat Dilek sedat.di...@gmail.com wrote: This happened a 2nd time with a different kernel-series! Not sure why this was the case. It did not happen when rebuilding with the same kernel-config again. Not sure

Re: [Intel-gfx] [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()

On Fri, Mar 27, 2015 at 12:06 PM, Takashi Iwai wrote: > At Fri, 27 Mar 2015 12:01:33 +0100, > Sedat Dilek wrote: >> >> On Wed, Mar 25, 2015 at 3:34 PM, Takashi Iwai wrote: >> > At Wed, 25 Mar 2015 14:26:50 +0100, >> > Daniel Vetter wrote: >> >>

Re: [Intel-gfx] [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()

On Wed, Mar 25, 2015 at 3:34 PM, Takashi Iwai wrote: > At Wed, 25 Mar 2015 14:26:50 +0100, > Daniel Vetter wrote: >> >> On Tue, Mar 24, 2015 at 07:09:03PM +0100, Sedat Dilek wrote: >> > On Mon, Mar 23, 2015 at 9:25 AM, Daniel Vetter wrote: >> > > On Mon,

Re: [Intel-gfx] [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()

On Fri, Mar 27, 2015 at 12:06 PM, Takashi Iwai ti...@suse.de wrote: At Fri, 27 Mar 2015 12:01:33 +0100, Sedat Dilek wrote: On Wed, Mar 25, 2015 at 3:34 PM, Takashi Iwai ti...@suse.de wrote: At Wed, 25 Mar 2015 14:26:50 +0100, Daniel Vetter wrote: On Tue, Mar 24, 2015 at 07:09:03PM

Re: [Intel-gfx] [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()

On Wed, Mar 25, 2015 at 3:34 PM, Takashi Iwai ti...@suse.de wrote: At Wed, 25 Mar 2015 14:26:50 +0100, Daniel Vetter wrote: On Tue, Mar 24, 2015 at 07:09:03PM +0100, Sedat Dilek wrote: On Mon, Mar 23, 2015 at 9:25 AM, Daniel Vetter dan...@ffwll.ch wrote: On Mon, Mar 23, 2015 at 07:25:27AM

Re: [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()

On Mon, Mar 23, 2015 at 9:25 AM, Daniel Vetter wrote: > On Mon, Mar 23, 2015 at 07:25:27AM +0100, Sedat Dilek wrote: >> Hi, >> >> I did my weekly update of the Linux RC (here: v4.0-rc5) and fell over >> some warning in the drm area. >> >> Please have a l

Re: [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()

On Mon, Mar 23, 2015 at 9:25 AM, Daniel Vetter dan...@ffwll.ch wrote: On Mon, Mar 23, 2015 at 07:25:27AM +0100, Sedat Dilek wrote: Hi, I did my weekly update of the Linux RC (here: v4.0-rc5) and fell over some warning in the drm area. Please have a look... Hi Daniel, Just to confirm

Re: linux-3.18.y: Add "kconfig: Fix warning "‘jump’ may be used uninitialized""

On Fri, Feb 6, 2015 at 4:50 PM, Greg Kroah-Hartman wrote: > On Fri, Feb 06, 2015 at 04:40:28PM +0100, Sedat Dilek wrote: >> Hi, >> >> I see the following... >> >> $ yes "" | make oldconfig && make silentoldconfig > HOSTCC scripts/basic/f

Re: linux-3.18.y: Add kconfig: Fix warning ‘jump’ may be used uninitialized

On Fri, Feb 6, 2015 at 4:50 PM, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: On Fri, Feb 06, 2015 at 04:40:28PM +0100, Sedat Dilek wrote: Hi, I see the following... $ yes | make oldconfig make silentoldconfig /dev/null HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig

Re: Linux 4.0-rc1 out..

On Mon, Feb 23, 2015 at 6:15 AM, Stephen Rothwell wrote: > Hi all, > > As usual, the executive friendly graph is at > http://neuling.org/linux-next-size.html :-) > > I haven't done these for a while, so I haven't included a previous > release for comparison. > > (No merge commits counted,

Re: Linux 4.0-rc1 out..

On Mon, Feb 23, 2015 at 6:15 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) I haven't done these for a while, so I haven't included a previous release for comparison. (No merge commits

Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0

On Mon, Feb 23, 2015 at 5:33 AM, Jens Axboe wrote: > On 02/22/2015 12:12 PM, Sedat Dilek wrote: >> >> On Sun, Feb 22, 2015 at 9:04 PM, Jens Axboe wrote: >>> >>> On Feb 22, 2015, at 12:02 PM, Sedat Dilek wrote: >>>> >>>>

Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0

On Sun, Feb 22, 2015 at 5:06 PM, Jens Axboe wrote: > On 02/22/2015 06:09 AM, Sedat Dilek wrote: >> >> Hi, >> >> when testing Linux-next (upcoming v3.20) I fell over similiar messages >> when running fio here. >> >> This commit hel

Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0

On Sun, Feb 22, 2015 at 3:09 PM, Sedat Dilek wrote: > Hi, > > when testing Linux-next (upcoming v3.20) I fell over similiar messages > when running fio here. > > This commit helped which is now upstream [1]... > > commit 9f9ee1f2b2f94f19437ae2def7c0d6636d7fe02e > &quo

Re: [git pull] more vfs bits

On Sun, Feb 22, 2015 at 10:37 AM, Al Viro wrote: > On Sun, Feb 22, 2015 at 10:32:02AM +0100, Sedat Dilek wrote: > >> How do you test? > > Mostly xfstests and LTP, plus assorted tests depending on the areas touched... > Any extra testing is welcome - the more, the merrier

Re: [git pull] more vfs bits

On Sun, Feb 22, 2015 at 10:37 AM, Al Viro wrote: > On Sun, Feb 22, 2015 at 10:32:02AM +0100, Sedat Dilek wrote: > >> How do you test? > > Mostly xfstests and LTP, plus assorted tests depending on the areas touched... > Any extra testing is welcome - the more, the merrier

Re: [git pull] more vfs bits

On Sun, Feb 22, 2015 at 9:51 AM, Al Viro wrote: > On Sat, Feb 21, 2015 at 07:16:16PM -0800, Linus Torvalds wrote: >> On Sat, Feb 21, 2015 at 6:51 PM, Al Viro wrote: >> > >> > Umm... Works for me. Let's do it this way, then: >> > * rename those guys through the whole series >> >

Re: [git pull] more vfs bits

On Sun, Feb 22, 2015 at 10:37 AM, Al Viro v...@zeniv.linux.org.uk wrote: On Sun, Feb 22, 2015 at 10:32:02AM +0100, Sedat Dilek wrote: How do you test? Mostly xfstests and LTP, plus assorted tests depending on the areas touched... Any extra testing is welcome - the more, the merrier... My

Re: [git pull] more vfs bits

On Sun, Feb 22, 2015 at 10:37 AM, Al Viro v...@zeniv.linux.org.uk wrote: On Sun, Feb 22, 2015 at 10:32:02AM +0100, Sedat Dilek wrote: How do you test? Mostly xfstests and LTP, plus assorted tests depending on the areas touched... Any extra testing is welcome - the more, the merrier

Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0

On Sun, Feb 22, 2015 at 3:09 PM, Sedat Dilek sedat.di...@gmail.com wrote: Hi, when testing Linux-next (upcoming v3.20) I fell over similiar messages when running fio here. This commit helped which is now upstream [1]... commit 9f9ee1f2b2f94f19437ae2def7c0d6636d7fe02e block: Quiesce

Re: [git pull] more vfs bits

On Sun, Feb 22, 2015 at 9:51 AM, Al Viro v...@zeniv.linux.org.uk wrote: On Sat, Feb 21, 2015 at 07:16:16PM -0800, Linus Torvalds wrote: On Sat, Feb 21, 2015 at 6:51 PM, Al Viro v...@zeniv.linux.org.uk wrote: Umm... Works for me. Let's do it this way, then: * rename those guys

Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0

On Sun, Feb 22, 2015 at 5:06 PM, Jens Axboe ax...@fb.com wrote: On 02/22/2015 06:09 AM, Sedat Dilek wrote: Hi, when testing Linux-next (upcoming v3.20) I fell over similiar messages when running fio here. This commit helped which is now upstream [1]... commit

Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0

On Mon, Feb 23, 2015 at 5:33 AM, Jens Axboe ax...@fb.com wrote: On 02/22/2015 12:12 PM, Sedat Dilek wrote: On Sun, Feb 22, 2015 at 9:04 PM, Jens Axboe ax...@fb.com wrote: On Feb 22, 2015, at 12:02 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Sun, Feb 22, 2015 at 5:06 PM, Jens Axboe ax

Re: [PATCH] MODSIGN: Change default key details

Hi, docs need some update, too? Regards, - Sedat - http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/module-signing.txt#n118 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More

<    5   6   7   8   9   10   11   12   13   14   >