mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Keith Chew" <keith.chew@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Crash on boot after abrupt shutdown
Date: Mon, 18 Sep 2006 02:29:48 +0200	[thread overview]
Message-ID: <9a8748490609171729y2a17a4f0wad3ed425dbb85425@mail.gmail.com> (raw)
In-Reply-To: <20f65d530609161930m2311974esfeaa2fbc2592e49f@mail.gmail.com>

On 17/09/06, Keith Chew <keith.chew@gmail.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@gmail.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

      parent reply	other threads:[~2006-09-18  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  2:30 Keith Chew
2006-09-17 21:21 ` Alan Cox
2006-09-18  5:03   ` Keith Chew
2006-09-18  0:29 ` Jesper Juhl [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a8748490609171729y2a17a4f0wad3ed425dbb85425@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=keith.chew@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®