| 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: <m1d3lpbrr3.fsf@fess.ebiederm.org> Date: Thu, 17 Mar 2011 10:07:12 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Cyril Hrubis <metan@....cz> Cc: Eric Miao <eric.y.miao@...il.com>, Pavel Machek <pavel@....cz>, rpurdie@...ys.net, lenz@...wisc.edu, kernel list <linux-kernel@...r.kernel.org>, arminlitzel@....de, thommycheck@...il.com, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, dbaryshkov@...il.com, omegamoon@...il.com, utx@...guin.cz, zaurus-devel@....linuxtogo.org, Marek Vasut <marek.vasut@...il.com> Subject: Re: reboot/kexec in 2.6.38 Cyril Hrubis <metan@....cz> writes: > Hi! >> > I got report that reboot/kexec does not work in recent kernels. >> > >> > I tried both kexec and reboot in 2.6.38, and it worked ok. Maybe >> > config issue? >> >> I think it's config issue. Never heard of this. >> > > I've seen that on my zaurus a month or two ago. When kexeced to pxa-linux-2.6 > then tried to kexec again. The last thing I've seen was Bye on the framebuffer > console and the machine freezed. The basic kexec code has been stable and solid for a long time so kexec failures are almost always hardware interaction problems. Someone not stopping dma, or someone not putting the hardware in a state that the next kernel can figure out how to initialize it. Eric -- 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