| 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: <9a8748490609171729y2a17a4f0wad3ed425dbb85425@mail.gmail.com> Date: Mon, 18 Sep 2006 02:29:48 +0200 From: "Jesper Juhl" <jesper.juhl@...il.com> To: "Keith Chew" <keith.chew@...il.com> Cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Crash on boot after abrupt shutdown On 17/09/06, Keith Chew <keith.chew@...il.com> wrote: > 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? > You could start by posting your panic/Oops message. That would give people something to work with. Perhaps also a bit more detail on the system in question - see the REPORTING-BUGS document in the kernel source dir. -- Jesper Juhl <jesper.juhl@...il.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - 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