If you want to flush the ram issues back to disk,
that may be a good idea otherwise I would just
close this discussion.
Cheers Nick
On Tue, Jun 24, 2014 at 11:24 PM, Josh Hunt wrote:
> On 06/24/2014 07:45 PM, David Rientjes wrote:
>>
>> On Tue, 24 Jun 2014, Josh Hunt wrote:
>>
>>> Anyone you'd su
On 06/24/2014 07:45 PM, David Rientjes wrote:
On Tue, 24 Jun 2014, Josh Hunt wrote:
Anyone you'd suggest adding to this thread to get other feedback about
tracking page allocation failures? I could also spin up a patch and cc them.
Page allocation failures happen all the time, mostly because
I second David, there is no reason for this if there is a bug due to
page allocation
failure it will be probably at the point of kernel panic or in the
trace statements
at panic.
Cheers Nick
On Tue, Jun 24, 2014 at 10:19 PM, Nick Krause wrote:
> I second David, this is no reason for this if th
On Tue, 24 Jun 2014, Josh Hunt wrote:
> Anyone you'd suggest adding to this thread to get other feedback about
> tracking page allocation failures? I could also spin up a patch and cc them.
>
Page allocation failures happen all the time, mostly because of
large-order allocations (more than PAGE
On Tue, Jun 24, 2014 at 11:06:15AM -0400, Dave Jones wrote:
>
> For things like the fuzz test runs I do, I'd have to patch this out.
>
> Things like migrate_pages() with bad arguments will trigger a page
> allocation failure rather easily. Likewise set_mempolicy(), and a
> handful of other v
On Tue, Jun 24, 2014 at 09:22:20AM -0500, Josh Hunt wrote:
> >> In addition to adding the softlockup taint flag, do you think it'd be
> >> reasonable to add another flag for page allocation failures? I think
> >> it'd be nice to be able to account for these conditions somehow without
> >> hav
On 06/23/2014 05:51 PM, Andrew Morton wrote:
On Mon, 23 Jun 2014 17:45:00 -0500 Josh Hunt wrote:
On 06/23/2014 05:11 PM, Andrew Morton wrote:
On Tue, 3 Jun 2014 22:12:35 -0400 Josh Hunt wrote:
This taint flag will be set if the system has ever entered a softlockup
state. Similar to TAINT_
On 06/23/2014 05:11 PM, Andrew Morton wrote:
On Tue, 3 Jun 2014 22:12:35 -0400 Josh Hunt wrote:
This taint flag will be set if the system has ever entered a softlockup
state. Similar to TAINT_WARN it is useful to know whether or not the system
has been in a softlockup state when debugging.
.
On Mon, 23 Jun 2014 17:45:00 -0500 Josh Hunt wrote:
> On 06/23/2014 05:11 PM, Andrew Morton wrote:
> > On Tue, 3 Jun 2014 22:12:35 -0400 Josh Hunt wrote:
> >
> >> This taint flag will be set if the system has ever entered a softlockup
> >> state. Similar to TAINT_WARN it is useful to know wheth
On Tue, 3 Jun 2014 22:12:35 -0400 Josh Hunt wrote:
> This taint flag will be set if the system has ever entered a softlockup
> state. Similar to TAINT_WARN it is useful to know whether or not the system
> has been in a softlockup state when debugging.
>
> ...
>
> @@ -329,6 +329,7 @@ static enum
This taint flag will be set if the system has ever entered a softlockup
state. Similar to TAINT_WARN it is useful to know whether or not the system
has been in a softlockup state when debugging.
Signed-off-by: Josh Hunt
---
Documentation/oops-tracing.txt |2 ++
Documentation/sysctl/kernel.t
11 matches
Mail list logo
