linux-kernel - Re: x86 instability with 2.6.1{8,9}

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <45C10BDE.80801@redhat.com>
Date:	Wed, 31 Jan 2007 16:36:30 -0500
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Ken Moffat <zarniwhoop@...world.com>
CC:	Randy Dunlap <randy.dunlap@...cle.com>,
	Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}

Ken Moffat wrote:
> On Mon, Jan 15, 2007 at 04:29:11PM +0000, Ken Moffat wrote:
>   
>>  Today, I've built 2.6.19.2 without highmem (the box only has 1GB,
>> dunno why I'd included that in the original config) and I will
>> continue to wait patiently for either a week without problems, or
>> something that I can manage to note - although I think at the moment
>> that the second coming of the great prophet Zarquon is more likely.
>>
>>     
>  Bizarre - it panic'd again last Thursday while I was in X, but I
> still didn't manage to log any output.  At the weekend, I had the
> bright idea of using chattr +j on the syslog to try to journal any
> data, since then it has been fine.  So, it isn't down to highmem, and
> I still can't trigger it reliably, or get any trace.  Tried running
> as x86_64 this morning (because cold starts on Thursdays seem
> particularly problematic, perhaps it's a time/power-supply-noise
> problem), then x86 from a cold start this afternoon.
>
>  Time to hope it won't bite me too often, and move on to testing
> 2.6.20-rc6.
>
> Ken
>   
Try disabling preempt.

-
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/