linux-kernel - Re: PROBLEM: 2.6.23.1 Freezes on GB data transfers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4718EAF5.6000700@rtr.ca>
Date:	Fri, 19 Oct 2007 13:35:49 -0400
From:	Mark Lord <lkml@....ca>
To:	Ray Lee <ray-lk@...rabbit.org>
Cc:	Giangiacomo Mariotti <gg.mariotti@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: 2.6.23.1 Freezes on GB data transfers

Ray Lee wrote:
> On 10/19/07, Mark Lord <lkml@....ca> wrote:
>
>> I believe this is now the forth report of blinking-leds lockup with 2.6.23.1.
>>
>> I wonder what's causing it?
>> My system has this as well, totally random, once every day or so.
>> New behaviour since 2.6.23-rc9 (I posted previously about this).
> 
> Boy, there's just not a lot between 2.6.23-rc9 and 2.6.23 proper.
> There are two things that kinda pop out, but this is at best a WAG.

Yeah, I looked at the changes and it's all very innocent looking.
More likely in my case, I suppose, is that the bug was there earlier
and then some timing changed somewhere and now it triggers more often.

One supporting evidence of that, is that with the powertop patches applied,
it crashes much less often.  And all that those do is adjust timings in
various places.

> First, are you on x86-32 and happen to have CONFIG_HIGHPTE set?

Core2Duo, 2GB, x86-32, CONFIG_HIGHPTE is not set.

> Second is another memory thing, where in filemap_fault we now do a
> page_cache_release where we didn't before, but that appears to only be
> in a case where we send a sigbus, so I wouldn't expect that to be
> hitting.

It seems to happen most often here on resume from suspend (RAM),
and when hotplugging hardware.  But it's infrequent enough that this
may not be a reliable clue.

Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/