Re: block: oopses on 4.13.*, 4.14.* and 4.15-rc2

2018-02-14 Thread Michele Ballabio
ed in). Michele [Re-added ML on CC:] > On Sat, Dec 9, 2017 at 7:27 AM, Michele Ballabio > wrote: > > On Fri, 8 Dec 2017 13:08:37 -0700 > > Jens Axboe wrote: > > > >> On 12/08/2017 08:38 AM, Michele Ballabio wrote: > >> > Hi, > >> > k

Re: block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected)

2017-12-18 Thread Michele Ballabio
On Mon, 18 Dec 2017 15:46:36 +0800 Ming Lei wrote: > On Sat, Dec 9, 2017 at 7:27 AM, Michele Ballabio > wrote: > > On Fri, 8 Dec 2017 13:08:37 -0700 > > Jens Axboe wrote: > > > >> On 12/08/2017 08:38 AM, Michele Ballabio wrote: > >> > Hi, > &

Re: block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected)

2017-12-08 Thread Michele Ballabio
On Fri, 8 Dec 2017 13:08:37 -0700 Jens Axboe wrote: > On 12/08/2017 08:38 AM, Michele Ballabio wrote: > > Hi, > > kernels 4.13.*, 4.14.* 4.15-rc2 crash on occasion, > > especially on x86-32 systems. To trigger the problem, run as root: > > > > while true

block: oopses on 4.13.*, 4.14.* and 4.15-rc2 (bisected)

2017-12-08 Thread Michele Ballabio
d4 00 00 00 00 eb d6 8d b4 26 00 00 00 00 8b 4d d8 66 83 7b 50 00 8b 73 58 <8b> 41 04 89 45 dc 8b 41 08 89 45 e0 8b 41 0c 89 45 e4 8b 41 10 kernel: [ 38.541297] EIP: bio_uncopy_user+0xab/0x120 SS:ESP: 0068:e85b7ce0 kernel: [ 38.569047] CR2: 0004 kernel: [ 38.596097] ---[ end trace 8f31c2df1c6d39c5 ]--- -- Thanks, Michele Ballabio

Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

2014-04-08 Thread Michele Ballabio
On 08/04/2014 21:14, Michele Ballabio wrote: > On 08/04/2014 14:21, Peter Zijlstra wrote: >> On Mon, Apr 07, 2014 at 08:56:58PM +0200, Peter Zijlstra wrote: >>> On Mon, Apr 07, 2014 at 08:16:24PM +0200, Toralf Förster wrote: >>> >>>> v3.14-10353-g2b3a8fd

Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

2014-04-08 Thread Michele Ballabio
On 08/04/2014 14:21, Peter Zijlstra wrote: > On Mon, Apr 07, 2014 at 08:56:58PM +0200, Peter Zijlstra wrote: >> On Mon, Apr 07, 2014 at 08:16:24PM +0200, Toralf Förster wrote: >> >>> v3.14-10353-g2b3a8fd works fine AFAICS >>> (BTW the fix is stable material, right ?) >> >> I'm fairly sure its not;

Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

2014-04-07 Thread Michele Ballabio
On 07/04/2014 17:07, Peter Zijlstra wrote: > On Mon, Apr 07, 2014 at 05:03:37PM +0200, Peter Zijlstra wrote: >> So what I suspect at this point is that because i386 and x86_64 have a >> difference in current_thread_info() (i386 is stack based), we end up >> setting the TIF_NEED_RESCHED bit on the w

Re: Bisected KVM hang on x86-32 between v3.12 and v3.13

2014-04-06 Thread Michele Ballabio
On 06/04/2014 17:52, Toralf Förster wrote: >> > Reverting either one of them solves the problem reported with kvm, >> > but revert is probably not the correct answer. >> > >> > I wonder if the solution is as simple as this: >> > >> > --->8--- >> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig

Bisected KVM hang on x86-32 between v3.12 and v3.13

2014-04-06 Thread Michele Ballabio
Toralf Förster reported this in http://article.gmane.org/gmane.linux.kernel/1662567 http://article.gmane.org/gmane.linux.kernel/1658422 http://article.gmane.org/gmane.linux.kernel/1657962 "The issue happens here at a 32 bit stable Gentoo Linux if I try to start a KVM image. Kernels 3.12

[PATCH] nouveau: avoid excessive gart aperture for on-board cards

2012-08-19 Thread Michele Ballabio
Commit d0f3c7e41d30859a638083654002b9b6faf7f67b ("drm/nouveau: give a slightly larger pci(e)gart aperture on all chipsets") removed a test: that caused an 8x increase in gart aperture, instead of a 2x one, for on-board cards >= NV_40. Signed-off-by: Michele Ballabio --- Hi,