Re: perf: bisected sampling bug in Linux 4.11-rc1

On Tue, 18 Jul 2017, Ingo Molnar wrote: > > Ok, great - if this works then I'll pick up this fix instead of the revert > that > I've queued up earlier today. sorry for the delay, I was out of town for a few days. I've tried the patch and it looks like it fixes the test in question and

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Tue, 18 Jul 2017, Ingo Molnar wrote: > > Ok, great - if this works then I'll pick up this fix instead of the revert > that > I've queued up earlier today. sorry for the delay, I was out of town for a few days. I've tried the patch and it looks like it fixes the test in question and

Re: perf: bisected sampling bug in Linux 4.11-rc1

* Alexander Shishkin wrote: > Vince Weaver writes: > > > I was tracking down some regressions in my perf_event_test testsuite. > > Some of the tests broke in the 4.11-rc1 timeframe. > > > > I've bisected one of them, this report is

Re: perf: bisected sampling bug in Linux 4.11-rc1

* Alexander Shishkin wrote: > Vince Weaver writes: > > > I was tracking down some regressions in my perf_event_test testsuite. > > Some of the tests broke in the 4.11-rc1 timeframe. > > > > I've bisected one of them, this report is about > > tests/overflow/simul_oneshot_group_overflow > >

Re: perf: bisected sampling bug in Linux 4.11-rc1

Vince Weaver writes: > I was tracking down some regressions in my perf_event_test testsuite. > Some of the tests broke in the 4.11-rc1 timeframe. > > I've bisected one of them, this report is about > tests/overflow/simul_oneshot_group_overflow > This test creates

Re: perf: bisected sampling bug in Linux 4.11-rc1

Vince Weaver writes: > I was tracking down some regressions in my perf_event_test testsuite. > Some of the tests broke in the 4.11-rc1 timeframe. > > I've bisected one of them, this report is about > tests/overflow/simul_oneshot_group_overflow > This test creates an event group containing

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Sat, 15 Jul 2017, Vince Weaver wrote: > Although there is a separate issue also introduced in 4.11-rc1 that still > fails a different testcase. I'm in the middle of bisecting that one and > probably won't have the result of the bisect until Monday. I went and bisected the other issue

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Sat, 15 Jul 2017, Vince Weaver wrote: > Although there is a separate issue also introduced in 4.11-rc1 that still > fails a different testcase. I'm in the middle of bisecting that one and > probably won't have the result of the bisect until Monday. I went and bisected the other issue

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Sat, 15 Jul 2017, Ingo Molnar wrote: > > * Vince Weaver wrote: > > > 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit > > > > commit 487f05e18aa4efacee6357480f293a5afe6593b5 > > Author: Alexander Shishkin > >

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Sat, 15 Jul 2017, Ingo Molnar wrote: > > * Vince Weaver wrote: > > > 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit > > > > commit 487f05e18aa4efacee6357480f293a5afe6593b5 > > Author: Alexander Shishkin > > Date: Thu Jan 19 18:43:30 2017 +0200 > > > > perf/core:

Re: perf: bisected sampling bug in Linux 4.11-rc1

* Vince Weaver wrote: > 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit > > commit 487f05e18aa4efacee6357480f293a5afe6593b5 > Author: Alexander Shishkin > Date: Thu Jan 19 18:43:30 2017 +0200 > > perf/core:

Re: perf: bisected sampling bug in Linux 4.11-rc1

* Vince Weaver wrote: > 487f05e18aa4efacee6357480f293a5afe6593b5 is the first bad commit > > commit 487f05e18aa4efacee6357480f293a5afe6593b5 > Author: Alexander Shishkin > Date: Thu Jan 19 18:43:30 2017 +0200 > > perf/core: Optimize event rescheduling on active contexts BTW., just to

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Fri, 14 Jul 2017, Alexander Shishkin wrote: > Vince Weaver writes: > > > I was tracking down some regressions in my perf_event_test testsuite. > > Some of the tests broke in the 4.11-rc1 timeframe. > > > > I've bisected one of them, this report is about > >

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Fri, 14 Jul 2017, Alexander Shishkin wrote: > Vince Weaver writes: > > > I was tracking down some regressions in my perf_event_test testsuite. > > Some of the tests broke in the 4.11-rc1 timeframe. > > > > I've bisected one of them, this report is about > >

Re: perf: bisected sampling bug in Linux 4.11-rc1

Vince Weaver writes: > I was tracking down some regressions in my perf_event_test testsuite. > Some of the tests broke in the 4.11-rc1 timeframe. > > I've bisected one of them, this report is about > tests/overflow/simul_oneshot_group_overflow > This test creates

Re: perf: bisected sampling bug in Linux 4.11-rc1

Vince Weaver writes: > I was tracking down some regressions in my perf_event_test testsuite. > Some of the tests broke in the 4.11-rc1 timeframe. > > I've bisected one of them, this report is about > tests/overflow/simul_oneshot_group_overflow > This test creates an event group containing

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Fri, 14 Jul 2017, Vince Weaver wrote: > On a good kernel you get the following: > Event perf::instructions with period 100 > Event perf::instructions with period 200 > fd 3 overflows: 946 (perf::instructions/100) > fd 4 overflows: 473

Re: perf: bisected sampling bug in Linux 4.11-rc1

On Fri, 14 Jul 2017, Vince Weaver wrote: > On a good kernel you get the following: > Event perf::instructions with period 100 > Event perf::instructions with period 200 > fd 3 overflows: 946 (perf::instructions/100) > fd 4 overflows: 473

perf: bisected sampling bug in Linux 4.11-rc1

I was tracking down some regressions in my perf_event_test testsuite. Some of the tests broke in the 4.11-rc1 timeframe. I've bisected one of them, this report is about tests/overflow/simul_oneshot_group_overflow This test creates an event group containing two sampling events, set to

perf: bisected sampling bug in Linux 4.11-rc1

I was tracking down some regressions in my perf_event_test testsuite. Some of the tests broke in the 4.11-rc1 timeframe. I've bisected one of them, this report is about tests/overflow/simul_oneshot_group_overflow This test creates an event group containing two sampling events, set to

Re: Linux 4.11 - broken enlightenment window manager (fixed in 4.12)

On Fri, Jun 09, 2017 at 09:35:09AM +0200, Ralph Sennhauser wrote: > Hi Greg, > > With 4.11 the enlightenment window mangers fails to start setuid > children due to commit 64b875f7ac8a ("ptrace: Capture the ptracer's > creds not PT_PTRACE_CAP"). > > Commit c70d9d809fde ("ptrace: Properly

Re: Linux 4.11 - broken enlightenment window manager (fixed in 4.12)

On Fri, Jun 09, 2017 at 09:35:09AM +0200, Ralph Sennhauser wrote: > Hi Greg, > > With 4.11 the enlightenment window mangers fails to start setuid > children due to commit 64b875f7ac8a ("ptrace: Capture the ptracer's > creds not PT_PTRACE_CAP"). > > Commit c70d9d809fde ("ptrace: Properly

Linux 4.11 - broken enlightenment window manager (fixed in 4.12)

Hi Greg, With 4.11 the enlightenment window mangers fails to start setuid children due to commit 64b875f7ac8a ("ptrace: Capture the ptracer's creds not PT_PTRACE_CAP"). Commit c70d9d809fde ("ptrace: Properly initialize ptracer_cred on fork") in Linus tree fixes the issue. Tested with v4.11.4.

Linux 4.11 - broken enlightenment window manager (fixed in 4.12)

Hi Greg, With 4.11 the enlightenment window mangers fails to start setuid children due to commit 64b875f7ac8a ("ptrace: Capture the ptracer's creds not PT_PTRACE_CAP"). Commit c70d9d809fde ("ptrace: Properly initialize ptracer_cred on fork") in Linus tree fixes the issue. Tested with v4.11.4.

[ANNOUNCE] linux-4.11-ck1 / MuQSS CPU scheduler 0.155

These are patches designed to improve system responsiveness and interactivity with specific emphasis on the desktop, but configurable for any workload. The patchset is mainly centred around the Multiple Queue Skiplist Scheduler, MuQSS. linux-4.11-ck1 -ck1 patches: http://ck.kolivas.org

[ANNOUNCE] linux-4.11-ck1 / MuQSS CPU scheduler 0.155

These are patches designed to improve system responsiveness and interactivity with specific emphasis on the desktop, but configurable for any workload. The patchset is mainly centred around the Multiple Queue Skiplist Scheduler, MuQSS. linux-4.11-ck1 -ck1 patches: http://ck.kolivas.org

Linux 4.11

(2): ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram x86/build: convert function graph '-Os' error to warning Linus Torvalds (1): Linux 4.11 Maksim Salau (1): net: can: usb: gs_usb: Fix buffer on stack Maor Gottlieb (1): net/mlx5: Fix UAR memory

Linux 4.11

(2): ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram x86/build: convert function graph '-Os' error to warning Linus Torvalds (1): Linux 4.11 Maksim Salau (1): net: can: usb: gs_usb: Fix buffer on stack Maor Gottlieb (1): net/mlx5: Fix UAR memory

Linux 4.11-rc8

and blk-mq scheduler Johannes Berg (2): mac80211: fix MU-MIMO follow-MAC mode mac80211: reject ToDS broadcast data frames Keith Busch (1): genirq/affinity: Fix calculating vectors to assign Linus Torvalds (1): Linux 4.11-rc8 Mel Gorman (1): Revert "mm, page_alloc:

Linux 4.11-rc8

and blk-mq scheduler Johannes Berg (2): mac80211: fix MU-MIMO follow-MAC mode mac80211: reject ToDS broadcast data frames Keith Busch (1): genirq/affinity: Fix calculating vectors to assign Linus Torvalds (1): Linux 4.11-rc8 Mel Gorman (1): Revert "mm, page_alloc:

Linux 4.11: Reported regressions as of Friday, 2017-04-21

Hi! Find below my fourth regression report for Linux 4.11. It lists 10 regressions I'm currently aware of. 7 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me

Linux 4.11: Reported regressions as of Friday, 2017-04-21

Hi! Find below my fourth regression report for Linux 4.11. It lists 10 regressions I'm currently aware of. 7 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me

Linux 4.11-rc7

tools/power turbostat: update version number Linus Torvalds (2): vfs: don't do RCU lookup of empty pathnames Linux 4.11-rc7 Liping Zhang (6): netfilter: ctnetlink: using bit to represent the ct event netfilter: ctnetlink: make it safer when checking the ct helper

Linux 4.11-rc7

tools/power turbostat: update version number Linus Torvalds (2): vfs: don't do RCU lookup of empty pathnames Linux 4.11-rc7 Liping Zhang (6): netfilter: ctnetlink: using bit to represent the ct event netfilter: ctnetlink: make it safer when checking the ct helper

RE: [Regression Linux 4.11] TPM module not loaded anymore

Dear Robert, Thank you for your reply. On 2017-04-12 23:49, Moore, Robert wrote: On 2017-04-12 17:54, Moore, Robert wrote: > And probably the dmesg if error messages appear in there. Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please find the output of `sudo

RE: [Regression Linux 4.11] TPM module not loaded anymore

Dear Robert, Thank you for your reply. On 2017-04-12 23:49, Moore, Robert wrote: On 2017-04-12 17:54, Moore, Robert wrote: > And probably the dmesg if error messages appear in there. Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please find the output of `sudo

RE: [Regression Linux 4.11] TPM module not loaded anymore

iej.szmigiero.name>; linux-kernel@vger.kernel.org; > Arthur Heymans <art...@aheymans.xyz>; tpmdd-de...@lists.sourceforge.net; > gnu...@no-log.org; Zheng, Lv <lv.zh...@intel.com>; Wysocki, Rafael J > <rafael.j.wyso...@intel.com>; linux-a...@vger.linux.org > Subject: RE: [Reg

RE: [Regression Linux 4.11] TPM module not loaded anymore

; > gnu...@no-log.org; Zheng, Lv ; Wysocki, Rafael J > ; linux-a...@vger.linux.org > Subject: RE: [Regression Linux 4.11] TPM module not loaded anymore > > Dear Robert, > > > Thank you for looking into this. > > > On 2017-04-12 17:54, Moore, Robert wrot

RE: [Regression Linux 4.11] TPM module not loaded anymore

Dear Robert, Thank you for looking into this. On 2017-04-12 17:54, Moore, Robert wrote: And probably the dmesg if error messages appear in there. Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please find the output of `sudo acpidump` attached. […] Kind regards,

RE: [Regression Linux 4.11] TPM module not loaded anymore

Dear Robert, Thank you for looking into this. On 2017-04-12 17:54, Moore, Robert wrote: And probably the dmesg if error messages appear in there. Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please find the output of `sudo acpidump` attached. […] Kind regards,

RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

gt; Cc: Maciej S. Szmigiero <m...@maciej.szmigiero.name>; linux- > ker...@vger.kernel.org; Arthur Heymans <art...@aheymans.xyz>; tpmdd- > de...@lists.sourceforge.net; gnu...@no-log.org; Zheng, Lv > <lv.zh...@intel.com>; Wysocki, Rafael J <rafael.j.wyso...@intel.com> >

RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

Heymans ; tpmdd- > de...@lists.sourceforge.net; gnu...@no-log.org; Zheng, Lv > ; Wysocki, Rafael J > Subject: RE: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > Please post the acpidump for this machine

RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

Rafael J > <rafael.j.wyso...@intel.com> > Subject: Re: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > > Dear Linux folks

RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

ej S. Szmigiero > ; linux-kernel@vger.kernel.org; Arthur > Heymans ; tpmdd-de...@lists.sourceforge.net; > gnu...@no-log.org; Zheng, Lv ; Wysocki, Rafael J > > Subject: Re: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X6

RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

;; Maciej S. Szmigiero > <m...@maciej.szmigiero.name>; linux-kernel@vger.kernel.org; Arthur > Heymans <art...@aheymans.xyz>; tpmdd-de...@lists.sourceforge.net; > gnu...@no-log.org; Zheng, Lv <lv.zh...@intel.com>; Wysocki, Rafael J > <rafael.j.wyso...@intel.com> >

RE: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

t; Heymans ; tpmdd-de...@lists.sourceforge.net; > gnu...@no-log.org; Zheng, Lv ; Wysocki, Rafael J > > Subject: Re: [Regression Linux 4.11] TPM module not loaded anymore (was: > Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot) > > On Sun, Apr 09, 2017 at 07:34:

Re: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > It turns out that stricter checks in the ACPI subsystem, introduced in > commit 57707a9a77 (ACPICA: Resources: Not a valid resource if buffer > length too long) [1], cause the TPM module not to be loaded

Re: [Regression Linux 4.11] TPM module not loaded anymore (was: Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot)

On Sun, Apr 09, 2017 at 07:34:43PM +0200, Paul Menzel wrote: > Dear Linux folks, > > > It turns out that stricter checks in the ACPI subsystem, introduced in > commit 57707a9a77 (ACPICA: Resources: Not a valid resource if buffer > length too long) [1], cause the TPM module not to be loaded

Re: Linux 4.11: Reported regressions as of Sunday, 2017-04-09

On Sun, Apr 09, 2017 at 07:15:49PM +0200, Thorsten Leemhuis wrote: > Desc: i915 gpu hangs under load > Repo: 2017-03-22 > https://www.mail-archive.com/intel-gfx@lists.freedesktop.org/msg116227.html > https://bugs.freedesktop.org/show_bug.cgi?id=100181 >

Re: Linux 4.11: Reported regressions as of Sunday, 2017-04-09

On Sun, Apr 09, 2017 at 07:15:49PM +0200, Thorsten Leemhuis wrote: > Desc: i915 gpu hangs under load > Repo: 2017-03-22 > https://www.mail-archive.com/intel-gfx@lists.freedesktop.org/msg116227.html > https://bugs.freedesktop.org/show_bug.cgi?id=100181 >

Linux 4.11: Reported regressions as of Sunday, 2017-04-09

Hi! Find below my third regression report for Linux 4.11. It lists 15 regressions I'm currently aware of. 5 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me

Linux 4.11: Reported regressions as of Sunday, 2017-04-09

Hi! Find below my third regression report for Linux 4.11. It lists 15 regressions I'm currently aware of. 5 regressions mentioned in last weeks report got fixed. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me

Linux 4.11-rc6

drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl() Liad Kaufman (1): iwlwifi: mvm: support ibss in dqa mode Linus Torvalds (1): Linux 4.11-rc6 Liping Zhang (8): netfilter: nfnl_cthelper: fix incorrect helper->expect_class_max netfilter: invoke synchronize_rcu after se

Linux 4.11-rc6

drm/vmwgfx: fix integer overflow in vmw_surface_define_ioctl() Liad Kaufman (1): iwlwifi: mvm: support ibss in dqa mode Linus Torvalds (1): Linux 4.11-rc6 Liping Zhang (8): netfilter: nfnl_cthelper: fix incorrect helper->expect_class_max netfilter: invoke synchronize_rcu after se

Re: Linux 4.11: Reported regressions as of Tuesday, 2017-04-02

On 02/04/17 10:03 PM, Thorsten Leemhuis wrote: > > == Going to be removed from the list == > > [...] > > Desc: DRM BUG while initializing cape verde (2nd card) > Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 > Stat: n/a > Note: problem was in 4.10 already & reporter

Re: Linux 4.11: Reported regressions as of Tuesday, 2017-04-02

On 02/04/17 10:03 PM, Thorsten Leemhuis wrote: > > == Going to be removed from the list == > > [...] > > Desc: DRM BUG while initializing cape verde (2nd card) > Repo: 2017-03-13 https://bugzilla.kernel.org/show_bug.cgi?id=194867 > Stat: n/a > Note: problem was in 4.10 already & reporter

Linux 4.11-rc5

(3): KVM: nVMX: fix nested EPT detection virtio_balloon: init 1st buffer in stats vq virtio-balloon: use actual number of stats for stats queue buffers Linus Torvalds (1): Linux 4.11-rc5 Liu Bo (1): Btrfs: bring back repair during read Lucas Stach (2): ASoC: si

Linux 4.11-rc5

(3): KVM: nVMX: fix nested EPT detection virtio_balloon: init 1st buffer in stats vq virtio-balloon: use actual number of stats for stats queue buffers Linus Torvalds (1): Linux 4.11-rc5 Liu Bo (1): Btrfs: bring back repair during read Lucas Stach (2): ASoC: si

Linux 4.11: Reported regressions as of Tuesday, 2017-04-02

Hi! Find below my second regression report for Linux 4.11. It lists 13 regressions I'm currently aware of. It lists 6 fixed regressions. Some of them where in the first report from three weeks ago; a few were supposed to go into a second report I prepared last week, but wasn't able to finish

Linux 4.11: Reported regressions as of Tuesday, 2017-04-02

Hi! Find below my second regression report for Linux 4.11. It lists 13 regressions I'm currently aware of. It lists 6 fixed regressions. Some of them where in the first report from three weeks ago; a few were supposed to go into a second report I prepared last week, but wasn't able to finish

Linux 4.11-rc4

pin Lendacky, Thomas (2): amd-xgbe: Fix jumbo MTU processing on newer hardware amd-xgbe: Fix the ECC-related bit position definitions Leon Romanovsky (1): IB/rxe: Update documentation link Leonard Crestez (1): clk: core: Copy connection id Linus Torvalds (1): Linux 4.

Linux 4.11-rc4

pin Lendacky, Thomas (2): amd-xgbe: Fix jumbo MTU processing on newer hardware amd-xgbe: Fix the ECC-related bit position definitions Leon Romanovsky (1): IB/rxe: Update documentation link Leonard Crestez (1): clk: core: Copy connection id Linus Torvalds (1): Linux 4.

Linux 4.11-rc3

remove copyright printing Larry Finger (1): powerpc/pmac: Fix crash in dma-mapping.h with NULL dma_ops Lendacky, Thomas (1): amd-xgbe: Enable IRQs only if napi_complete_done() is true Linus Torvalds (2): mm/swap: don't BUG_ON() due to uninitialized swap slot cache Linux 4.11-rc3

Linux 4.11-rc3

remove copyright printing Larry Finger (1): powerpc/pmac: Fix crash in dma-mapping.h with NULL dma_ops Lendacky, Thomas (1): amd-xgbe: Enable IRQs only if napi_complete_done() is true Linus Torvalds (2): mm/swap: don't BUG_ON() due to uninitialized swap slot cache Linux 4.11-rc3

Re: linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c: 3 bugs

On Mon, Mar 6, 2017 at 4:40 AM, David Binderman <dcb...@hotmail.com> wrote: > > Hello there, > 1 > > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1041] -> > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1037]: (style) Same > expression on both sid

Re: linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c: 3 bugs

On Mon, Mar 6, 2017 at 4:40 AM, David Binderman wrote: > > Hello there, > 1 > > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1041] -> > [linux-4.11-rc1/drivers/gpu/drm/amd/amdgpu/vi.c:1037]: (style) Same > expression on both sides of '|'. > > Maybe the macro A

Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

[ Moving this sub-thread to the amd-gfx mailing list ] On 14/03/17 07:02 PM, Thorsten Leemhuis wrote: > Hi! Find below my first regression report for Linux 4.11. It lists 9 > regressions I'm currently aware of. [...] > Desc: DRM BUG while initializing cape verde (2nd card) > Repo

Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

[ Moving this sub-thread to the amd-gfx mailing list ] On 14/03/17 07:02 PM, Thorsten Leemhuis wrote: > Hi! Find below my first regression report for Linux 4.11. It lists 9 > regressions I'm currently aware of. [...] > Desc: DRM BUG while initializing cape verde (2nd card) > Repo

Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

Thorsten Leemhuis <regressi...@leemhuis.info> writes: > Hi! Find below my first regression report for Linux 4.11. It lists 9 > regressions I'm currently aware of. > > As always: Are you aware of any other regressions? Then please let me > know (simply CC regressi...@leemh

Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

Thorsten Leemhuis writes: > Hi! Find below my first regression report for Linux 4.11. It lists 9 > regressions I'm currently aware of. > > As always: Are you aware of any other regressions? Then please let me > know (simply CC regressi...@leemhuis.info). And please tell me if ther

Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

On Tue, Mar 14, 2017 at 3:02 AM, Thorsten Leemhuis wrote: > > Desc: PowerPC crashes on boot, bisected to commit 5657933dbb6e > Repo: 2017-03-02 > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1343553.html > Stat: 2017-03-09 >

Re: Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

On Tue, Mar 14, 2017 at 3:02 AM, Thorsten Leemhuis wrote: > > Desc: PowerPC crashes on boot, bisected to commit 5657933dbb6e > Repo: 2017-03-02 > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1343553.html > Stat: 2017-03-09 >

Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

Hi! Find below my first regression report for Linux 4.11. It lists 9 regressions I'm currently aware of. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me if there is anything in the report that shouldn't

Linux 4.11: Reported regressions as of Tuesday, 20176-03-14

Hi! Find below my first regression report for Linux 4.11. It lists 9 regressions I'm currently aware of. As always: Are you aware of any other regressions? Then please let me know (simply CC regressi...@leemhuis.info). And please tell me if there is anything in the report that shouldn't

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 09:15:21AM -0700, Linus Torvalds wrote: On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer wrote: Yes. A git pull just grabbed it for me. The 'view diff' link on kernel.org still fails with bad object, but I'm guessing that will catch up at some

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 09:15:21AM -0700, Linus Torvalds wrote: On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer wrote: Yes. A git pull just grabbed it for me. The 'view diff' link on kernel.org still fails with bad object, but I'm guessing that will catch up at some point too. Hmm. I pushed

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer wrote: > > Yes. A git pull just grabbed it for me. The 'view diff' link on > kernel.org still fails with bad object, but I'm guessing that will > catch up at some point too. Hmm. I pushed those before the announcement, so

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 9:05 AM, Josh Boyer wrote: > > Yes. A git pull just grabbed it for me. The 'view diff' link on > kernel.org still fails with bad object, but I'm guessing that will > catch up at some point too. Hmm. I pushed those before the announcement, so over 18 hours ago by now. If

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 11:57 AM, Linus Torvalds wrote: > On Mon, Mar 13, 2017 at 6:19 AM, Josh Boyer wrote: >> >> I thought it might just be me, but at least one other person doesn't >> see the v4.11-rc2 tag in git yet. The patch is on

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 11:57 AM, Linus Torvalds wrote: > On Mon, Mar 13, 2017 at 6:19 AM, Josh Boyer wrote: >> >> I thought it might just be me, but at least one other person doesn't >> see the v4.11-rc2 tag in git yet. The patch is on kernel.org though, >> so it's confusing. Did you forget

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 6:19 AM, Josh Boyer wrote: > > I thought it might just be me, but at least one other person doesn't > see the v4.11-rc2 tag in git yet. The patch is on kernel.org though, > so it's confusing. Did you forget to push it out? It's definitely

Re: Linux 4.11-rc2

On Mon, Mar 13, 2017 at 6:19 AM, Josh Boyer wrote: > > I thought it might just be me, but at least one other person doesn't > see the v4.11-rc2 tag in git yet. The patch is on kernel.org though, > so it's confusing. Did you forget to push it out? It's definitely there, but it might have taken

Re: Linux 4.11-rc2

On Sun, Mar 12, 2017 at 6:01 PM, Linus Torvalds wrote: > As usual, the week after rc1 tends to be fairly quiet when people are > still looking for bugs and taking a breather after the merge window. > But we've got a healthy number of fixes in, and there's some >

Re: Linux 4.11-rc2

On Sun, Mar 12, 2017 at 6:01 PM, Linus Torvalds wrote: > As usual, the week after rc1 tends to be fairly quiet when people are > still looking for bugs and taking a breather after the merge window. > But we've got a healthy number of fixes in, and there's some > cleanup/prep patches for the

Linux 4.11-rc2

sched/headers: fix up header file dependency on overlayfs: remove now unnecessary header file include Linux 4.11-rc2 Marc Zyngier (2): arm64: KVM: VHE: Clear HCR_TGE when invalidating guest TLBs KVM: arm/arm64: vgic-v3: Don't pretend to support IRQ/FIQ bypass Marek Vasut

Linux 4.11-rc2

sched/headers: fix up header file dependency on overlayfs: remove now unnecessary header file include Linux 4.11-rc2 Marc Zyngier (2): arm64: KVM: VHE: Clear HCR_TGE when invalidating guest TLBs KVM: arm/arm64: vgic-v3: Don't pretend to support IRQ/FIQ bypass Marek Vasut

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

On 09.03.2017 08:34, Inki Dae wrote: > Hello David, > > Thanks for report. > > 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글: >> Hello there, >> >> linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) >> Result of operator '|' is alwa

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

On 09.03.2017 08:34, Inki Dae wrote: > Hello David, > > Thanks for report. > > 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글: >> Hello there, >> >> linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) >> Result of operator '|' is alwa

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hello David, Thanks for report. 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hello David, Thanks for report. 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hi David, Inki, Thanks for reporting. On 06.03.2017 11:05, David Binderman wrote: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use '&

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hi David, Inki, Thanks for reporting. On 06.03.2017 11:05, David Binderman wrote: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use '&

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

David, Romain, On Tue, 7 Mar 2017 16:17:03 +0100 David Engraf <david.eng...@sysgo.com> wrote: > Am 07.03.2017 um 16:05 schrieb Romain Izard: > > 2017-03-06 12:28 GMT+01:00 Romain Izard <romain.izard@gmail.com>: > >> > >> While looking for another iss

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

David, Romain, On Tue, 7 Mar 2017 16:17:03 +0100 David Engraf wrote: > Am 07.03.2017 um 16:05 schrieb Romain Izard: > > 2017-03-06 12:28 GMT+01:00 Romain Izard : > >> > >> While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 > >> Xplain

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

Am 07.03.2017 um 16:05 schrieb Romain Izard: 2017-03-06 12:28 GMT+01:00 Romain Izard <romain.izard@gmail.com>: While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained board. The boot log contains the following warning: [0.10] [ cu

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

Am 07.03.2017 um 16:05 schrieb Romain Izard: 2017-03-06 12:28 GMT+01:00 Romain Izard : While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained board. The boot log contains the following warning: [0.10] [ cut here ] [0.10] WARNING

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

2017-03-06 12:28 GMT+01:00 Romain Izard <romain.izard@gmail.com>: > > While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained > board. The boot log contains the following warning: > > [0.10] [ cut here ] > [0.100

Re: Warning on boot on SAMA5D2 with Linux 4.11-rc1

2017-03-06 12:28 GMT+01:00 Romain Izard : > > While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained > board. The boot log contains the following warning: > > [0.10] [ cut here ] > [0.10] WARNING: CPU: 0 PID: 1 a

Re: linux-next: stats (Was: Linux 4.11-rc1)

Hi, On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote: > > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out. > Top ten first word of commit summary: ... > 61 btrfs I can comment on the btrfs part. We have lots of cleanups for 4.11 and good part of all

Re: linux-next: stats (Was: Linux 4.11-rc1)

Hi, On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote: > > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out. > Top ten first word of commit summary: ... > 61 btrfs I can comment on the btrfs part. We have lots of cleanups for 4.11 and good part of all

  1   2   >