On Sat, Oct 08, 2016 at 03:02:00AM -0400, Zygo Blaxell wrote:
> On Sat, Oct 08, 2016 at 02:10:08AM -0400, Zygo Blaxell wrote:
> [...]
> > The "write half" of the bug seems to appear first somewhere between v3.8
> > and v3.9. I have not been able to reproduce it with v3.8.13, v3.7.10, or
> > v3.6.1
Hi,
I have a raid10 array that occasionally causes the kernel to write kernel bug
messages and to take down the router that this machine is plugged into.
It’s a pretty standard install of Ubuntu 16.04.1 LTS (GNU/Linux
4.4.0-38-generic x86_64); the only kernel taint is the ZFS on Linux package
On Sat, Oct 08, 2016 at 07:29:03PM +0100, Al Viro wrote:
> On Sat, Oct 08, 2016 at 02:08:06PM -0400, Dave Jones wrote:
> > That code: matches this dissembly:
> >
> > for (i = seg + 1; i < iter->nr_segs; i++) {
>
> *whoa*
>
> OK, that loop in check_direct_IO() should be do
I'm not sure if this is related to the same issue or not, but I just
started getting a new BUG, followed by a panic. (I'm also enabled
network console capture so that you won't have to squint at photos.)
Original BUG is:
[14740.444257] [ cut here ]
[14740.444293] kernel
main difference between the system where oom happens is:
- Single Xeon => no OOM
- Dual Xeon / NUMA => OOM
both 64GB mem.
Am 07.10.2016 um 11:33 schrieb Holger Hoffstätte:
> On 10/07/16 09:17, Wang Xiaoguang wrote:
>> Hi,
>>
>> On 10/07/2016 03:03 PM, Stefan Priebe - Profihost AG wrote:
>>> Dear
On Sat, Oct 08, 2016 at 02:08:06PM -0400, Dave Jones wrote:
> That code: matches this dissembly:
>
> for (i = seg + 1; i < iter->nr_segs; i++) {
*whoa*
OK, that loop in check_direct_IO() should be done *ONLY* for
iovec iter - even for a bvec one it's completely bogus, and
for pip
Found this in logs this morning. First time I've seen this one.
Might be related to some direct IO related changes I made in Trinity
that is tickling some new path.
Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
CPU: 2 PID: 25313 Comm: trinity-c18 Not tainted 4.8.0-think+ #7
task: 88040f7b1c00 t
On Sat, Oct 08, 2016 at 02:10:08AM -0400, Zygo Blaxell wrote:
[...]
> The "write half" of the bug seems to appear first somewhere between v3.8
> and v3.9. I have not been able to reproduce it with v3.8.13, v3.7.10, or
> v3.6.11. I can reproduce it in v3.9.11, v3.12.64, and v3.18.13..v4.7.5.
Afte
