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] [day] [month] [year] [list]

Message-ID: <20f65d530609172203o566ab327i6ca5bb9817d905a4@mail.gmail.com>
Date:	Mon, 18 Sep 2006 17:03:55 +1200
From:	"Keith Chew" <keith.chew@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Crash on boot after abrupt shutdown

Hi Alan

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

Thank you very much for your diagnostic. The stack traces are not as
consistent as our driver crashes, so we have not posted them yet
before digging a bit deeper. We are now looking at the
startup/shutdown process of the driver, and there could be some
critical timing issues, but we will check and test.

Thanks again, will report back soon.

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/