Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

Hi Rafael, Bug has been filed: Bug 201125 - ohci-pci :00:12.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0006 address=0x0080 flags=0x0020] James On 09/13/2018 10:50 PM, Rafael J. Wysocki wrote: > On 9/13/2018 5:21 PM, James Wang wrote: >> >> On 09/12/2018 11:

Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

Hi Rafael, Bug has been filed: Bug 201125 - ohci-pci :00:12.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0006 address=0x0080 flags=0x0020] James On 09/13/2018 10:50 PM, Rafael J. Wysocki wrote: > On 9/13/2018 5:21 PM, James Wang wrote: >> >> On 09/12/2018 11:

Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

On 09/12/2018 02:41 PM, Pingfan Liu wrote: > Cc James, could you try to enable initcall_debug, and paste the > shutdown seq with 722e5f2b1eec ("driver core: Partially revert "driver > core: correct device's shutdown order"") and without it? OK. And I will scheudule some testing orders, ahah,

Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

On 09/12/2018 02:41 PM, Pingfan Liu wrote: > Cc James, could you try to enable initcall_debug, and paste the > shutdown seq with 722e5f2b1eec ("driver core: Partially revert "driver > core: correct device's shutdown order"") and without it? OK. And I will scheudule some testing orders, ahah,

Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

On 09/11/2018 07:55 PM, Takashi Iwai wrote: > On Tue, 11 Sep 2018 13:01:11 +0200, > Borislav Petkov wrote: >> On Tue, Sep 11, 2018 at 12:51:32PM +0200, Rafael J. Wysocki wrote: >>> that may help in principle, so any chance to try them on the affected >>> systems? >> Right, and I don't recall

Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

On 09/11/2018 07:55 PM, Takashi Iwai wrote: > On Tue, 11 Sep 2018 13:01:11 +0200, > Borislav Petkov wrote: >> On Tue, Sep 11, 2018 at 12:51:32PM +0200, Rafael J. Wysocki wrote: >>> that may help in principle, so any chance to try them on the affected >>> systems? >> Right, and I don't recall

Re: [PATCH blktests v2] loop/002: Regression testing for loop device flush

No problem thank you sir 发自我的 iPhone > 在 2017年8月18日，16:11，Omar Sandoval <osan...@osandov.com> 写道： > >> On Tue, Jun 27, 2017 at 12:01:47PM +0800, James Wang wrote: >> Add a regression testing for loop device. when an unbound device >> be close that take too

Re: [PATCH blktests v2] loop/002: Regression testing for loop device flush

No problem thank you sir 发自我的 iPhone > 在 2017年8月18日，16:11，Omar Sandoval 写道： > >> On Tue, Jun 27, 2017 at 12:01:47PM +0800, James Wang wrote: >> Add a regression testing for loop device. when an unbound device >> be close that take too long time. kernel will

[PATCH blktests v2] loop/002: Regression testing for loop device flush

Add a regression testing for loop device. when an unbound device be close that take too long time. kernel will consume serveral orders of magnitude more wall time than it does for a mounted device. Signed-off-by: James Wang <jnw...@suse.com> --- tests/loop/002

[PATCH blktests v2] loop/002: Regression testing for loop device flush

Add a regression testing for loop device. when an unbound device be close that take too long time. kernel will consume serveral orders of magnitude more wall time than it does for a mounted device. Signed-off-by: James Wang --- tests/loop/002 | 63

Re: [PATCH blktests] loop/002: Regression testing for loop device flush

On 06/27/2017 02:58 AM, Omar Sandoval wrote: > Hi, James, thanks for sending this in. Sorry for the delay, I've been > out of the office for a couple of weeks. A few comments below. > > On Thu, Jun 08, 2017 at 08:28:12PM +0800, James Wang wrote: >> Add a regression testing for

Re: [PATCH blktests] loop/002: Regression testing for loop device flush

On 06/27/2017 02:58 AM, Omar Sandoval wrote: > Hi, James, thanks for sending this in. Sorry for the delay, I've been > out of the office for a couple of weeks. A few comments below. > > On Thu, Jun 08, 2017 at 08:28:12PM +0800, James Wang wrote: >> Add a regression testing for

[PATCH blktests] loop/002: Regression testing for loop device flush

Add a regression testing for loop device. when an unbound device be close that take too long time. kernel will consume serveral orders of magnitude more wall time than it does for a mounted device. Signed-off-by: James Wang <jnw...@suse.com> --- tests/loop/002

[PATCH blktests] loop/002: Regression testing for loop device flush

Add a regression testing for loop device. when an unbound device be close that take too long time. kernel will consume serveral orders of magnitude more wall time than it does for a mounted device. Signed-off-by: James Wang --- tests/loop/002 | 77

Re: [PATCH] Fix loop device flush before configure v3

On 06/08/2017 03:53 PM, Johannes Thumshirn wrote: > On 06/08/2017 08:52 AM, James Wang wrote: >> Test method: >> modprobe loop max_loop=64 >> dd if=/dev/zero of=disk bs=512 count=200K >> for((i=0;i<4;i++))do losetup -f disk; done >> mkfs.ext4 -F /dev/loo

Re: [PATCH] Fix loop device flush before configure v3

On 06/08/2017 03:53 PM, Johannes Thumshirn wrote: > On 06/08/2017 08:52 AM, James Wang wrote: >> Test method: >> modprobe loop max_loop=64 >> dd if=/dev/zero of=disk bs=512 count=200K >> for((i=0;i<4;i++))do losetup -f disk; done >> mkfs.ext4 -F /dev/loo

Re: [PATCH] Fix loop device flush before configure

On 06/08/2017 02:56 PM, Christoph Hellwig wrote: > On Thu, Jun 08, 2017 at 08:45:31AM +0800, James Wang wrote: >> Ok I got it blktests is a suite. I'd like to contribute something. If you >> need, we adapt you,;-)! >> But I have to learn some how to do that, need time. &

Re: [PATCH] Fix loop device flush before configure

On 06/08/2017 02:56 PM, Christoph Hellwig wrote: > On Thu, Jun 08, 2017 at 08:45:31AM +0800, James Wang wrote: >> Ok I got it blktests is a suite. I'd like to contribute something. If you >> need, we adapt you,;-)! >> But I have to learn some how to do that, need time. &

[PATCH] Fix loop device flush before configure v3

more wall time than it does for a mounted device. (Thanks for Mike Galbraith <efa...@gmx.de>, give a changelog review.) Reviewed-by: Hannes Reinecke <h...@suse.com> Reviewed-by: Ming Lei <ming....@redhat.com> Signed-off-by: James Wang <jnw...@suse.com> Fixes: b5dd2f6047ca (&

[PATCH] Fix loop device flush before configure v3

more wall time than it does for a mounted device. (Thanks for Mike Galbraith , give a changelog review.) Reviewed-by: Hannes Reinecke Reviewed-by: Ming Lei Signed-off-by: James Wang Fixes: b5dd2f6047ca ("block: loop: improve performance via blk-mq") --- drivers/block/loop.c | 3 +++ 1 file c

[PATCH] Fix loop device flush before configure

more wall time than it does for a mounted device. (Thanks for Mike Galbraith <efa...@gmx.de>, give a changelog review.) Reviewed-by: Hannes Reinecke <h...@suse.com> Reviewed-by: Ming Lei <ming....@redhat.com> Signed-off-by: James Wang <jnw...@suse.com> Fixes: b5dd2f6047ca (&

[PATCH] Fix loop device flush before configure

more wall time than it does for a mounted device. (Thanks for Mike Galbraith , give a changelog review.) Reviewed-by: Hannes Reinecke Reviewed-by: Ming Lei Signed-off-by: James Wang Fixes: b5dd2f6047ca ("block: loop: improve performance via blk-mq") --- drivers/block/loop.c | 3 +++ 1 file c

Re: [PATCH] Fix loop device flush before configure v2

On 06/08/2017 01:06 PM, Mike Galbraith wrote: > On Thu, 2017-06-08 at 10:17 +0800, James Wang wrote: >> This condition check was exist at before commit b5dd2f6047ca ("block: loop: >> improve performance via blk-mq") When add MQ support to loop device, it be >

Re: [PATCH] Fix loop device flush before configure v2

On 06/08/2017 01:06 PM, Mike Galbraith wrote: > On Thu, 2017-06-08 at 10:17 +0800, James Wang wrote: >> This condition check was exist at before commit b5dd2f6047ca ("block: loop: >> improve performance via blk-mq") When add MQ support to loop device, it be >

[PATCH] Fix loop device flush before configure v2

1.26453 7.2522e-05 >From /dev/loop10 start, loop isn't mounted. but it take more time than mounted devices. And The data differ by several orders of magnitude. Reviewed-by: Hannes Reinecke <h...@suse.com> Signed-off-by: James Wang <jnw...@suse.com> --- drivers/block/l

[PATCH] Fix loop device flush before configure v2

1.26453 7.2522e-05 >From /dev/loop10 start, loop isn't mounted. but it take more time than mounted devices. And The data differ by several orders of magnitude. Reviewed-by: Hannes Reinecke Signed-off-by: James Wang --- drivers/block/loop.c | 3 +++ 1 file changed, 3 insertions

Re: [PATCH] Fix loop device flush before configure

Ok I got it blktests is a suite. I'd like to contribute something. If you need, we adapt you,;-)! But I have to learn some how to do that, need time. James >From subway. 在 2017年6月7日，21:17，Christoph Hellwig 写道： >> Testing steps are following: >> modprobe loop max_loop=64

Re: [PATCH] Fix loop device flush before configure

Ok I got it blktests is a suite. I'd like to contribute something. If you need, we adapt you,;-)! But I have to learn some how to do that, need time. James >From subway. 在 2017年6月7日，21:17，Christoph Hellwig 写道： >> Testing steps are following: >> modprobe loop max_loop=64 >> dd if=/dev/zero

[PATCH] Fix loop device flush before configure

1.26453 7.2522e-05 >From /dev/loop10 start, loop isn't mounted. but it take more time than mounted devices. And The data differ by several orders of magnitude. Reviewed-by: Hannes Reinecke <h...@suse.com> Signed-off-by: James Wang <jnw...@suse.com> --- drivers/block/l

[PATCH] Fix loop device flush before configure

1.26453 7.2522e-05 >From /dev/loop10 start, loop isn't mounted. but it take more time than mounted devices. And The data differ by several orders of magnitude. Reviewed-by: Hannes Reinecke Signed-off-by: James Wang --- drivers/block/loop.c | 3 +++ 1 file changed, 3 insertions