| 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: <20f65d530609161930m2311974esfeaa2fbc2592e49f@mail.gmail.com> Date: Sun, 17 Sep 2006 14:30:16 +1200 From: "Keith Chew" <keith.chew@...il.com> To: linux-kernel <linux-kernel@...r.kernel.org> Subject: Crash on boot after abrupt shutdown Hi We are using linux in quite a harsh mobile environment (high temperatures, unreliable power sources, electrical interference, etc). It has been doing very well, except for this scenario. The wireless interface wlan0 is busy communicating, and the power is disconnected abruptedly. In the next boot, we get a kernel panic when the wlan interface is initialised. We want to know if this is due to linux's journaling file system (we are using ext3)? Does it keep track of the state so closely, even up to the point of the previous abrupt shutdown? If so, what can we do to "cleanup" in the next boot to avoid the kernel panic? 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/
Powered by blists - more mailing lists