linux-kernel - Re: Crash on boot after abrupt shutdown

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1158528078.6069.70.camel@localhost.localdomain>
Date:	Sun, 17 Sep 2006 22:21:17 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Keith Chew <keith.chew@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Crash on boot after abrupt shutdown

Ar Sul, 2006-09-17 am 14:30 +1200, ysgrifennodd Keith Chew:
> 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 

Very unlikely but you don't provide enough information to even guess.

I've seen similar behaviours before and they usually indicate a bug in
the driver that crashed. Eg the setup code for a network card not being
able to cope if the network card is in a particular state but does
enough that next boot it works.

You need to work back from your wireless driver panic to the root cause
of that panic and then back from there.

-
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/