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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]