Hi, This linked images are the printed error messages when the kernel is in panic. http://www.mwnl.snu.ac.kr/~ohlee/1.jpg http://www.mwnl.snu.ac.kr/~ohlee/2.jpg Thank you for your help. Okhwan -- Okhwan Lee Sent with Airmail 켜짐 2014년 10월 24일 에서 오후 4:49:23, Michal Kazior (michal.kazior@xxxxxxxxx(mailto:michal.kazior@xxxxxxxxx)) 작성됨: > On 23 October 2014 08:57, Okhwan Lee wrote: > > Hi, > > > > Thank you for your answer. > > > >> The panic printout would be most helpful. My best guess is this > >> crashes in ath10k_dbg() at the very beginning of ath10k_config_chan > >> because ar->chandef.chan is NULL. This is probably the case since you > >> use monitor_chandef which is probably "empty" at the point you invoke > >> your code. > > > > First, we confirm that ar->chandef.chan is not NULL. > > We find out the the error occurs when "wait_for_completion_timeout" is called. > > Ath10k is trying to stop vdev (monitor_dev) when change the channel setting. > > We have no idea about the details of function, but it make waiting > > time duration for previous event. > > We also test by replacing wait_for_completion_timeout to > > wait_for_completion (i.e., it use maximum timeout value) > > But the kernel panic is still there. > > > > However, it is not easy to printout the messages when the panic is occurred, > > because the system stop (similar to bluescreen in widnows?). > > After reboot the system, the log messagess from panic is not recored > > in kernel log messages (/var/log/syslog, dmesg, kernel_llog) . > > Can you at least do a photo of the panic, post it to an image hosting > site and link it, please? > > > Michał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
