linux-kernel - Re: bug or hardware memory error?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20f65d530812211515q63b4c9f1gc5d4325adc74f7e6@mail.gmail.com>
Date:	Mon, 22 Dec 2008 12:15:13 +1300
From:	"Keith Chew" <keith.chew@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: bug or hardware memory error?

Hi Willy

> well, it could be any. 2.6.20.1 is very old, even for the 2.6.20 branch.
> A few hundreds of bugs have been fixed since. If you don't need to stick
> to 2.6.20, you should try 2.6.27.10. If you need to stick to 2.6.20 for
> whatever reason, please at least try with 2.6.20.21 (the latest 2.6.20
> patch). Even with that, there's no guarantee that the present bug will
> be fixed though.
>

Ok, will try the latest kernel to see if that fixes it. 2.6.20.1 was
actually the latest kernel when I rolled it out to these machines. The
IRQ Lockup messages have never caused any problems to the the
application, but only recently I caught the stack trace. Of course I
may have missed catching these stack traces in the past, but they are
rare.

Thanks again for your input.

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