| 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
| ||
|
Message-ID: <20150629104553.GD16230@pali> Date: Mon, 29 Jun 2015 12:45:53 +0200 From: Pali Rohár <pali.rohar@...il.com> To: Pavel Machek <pavel@....cz> Cc: sre@...ian.org, sre@...g0.de, kernel list <linux-kernel@...r.kernel.org>, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, linux-omap@...r.kernel.org, tony@...mide.com, khilman@...nel.org, aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com, patrikbachan@...il.com Subject: Re: n900 in 4.2-rc0: repeating oopses Hi! On Monday 29 June 2015 11:11:46 Pavel Machek wrote: > Hi! > > Just tried booting 4.2-rc0 on n900 (commit > 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous > -rc0 version worked. This time, there's some output on console, but > too fast for me to read. > What happen after errors are reported? Maybe you can enable R&D mode and disable HW watchdogs to prevent device reboots... > It seems oopses happen before mounting root. If you have serial > console, they should be easy to see. > > I tried booting same kernel in qemu, but it seems to work ok there. > Hm... Maybe problem with HS code? By chance, can you try to disable (omap) sham node in n900 DT file? (same way like omap aes is disabled) > Any ideas? Thanks, > Pavel -- Pali Rohár pali.rohar@...il.com -- 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/
Powered by blists - more mailing lists