Linux wireless drivers development
 help / color / mirror / Atom feed
From: Okhwan Lee <ohlee@mwnl.snu.ac.kr>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Change channel bandwidth without iw command
Date: Fri, 24 Oct 2014 20:30:19 +0900	[thread overview]
Message-ID: <etPan.544a384b.74b0dc51.8406@Mac-Pro.local> (raw)
In-Reply-To: <CA+BoTQn0iEYEQJ4AdO7xfRSHjX1CfO_uovPaxbtxSWQw0vPS+Q@mail.gmail.com>

 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@tieto.com(mailto:michal.kazior@tieto.com)) 작성됨:

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


  reply	other threads:[~2014-10-24 11:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 10:14 Change channel bandwidth without iw command Okhwan Lee
2014-10-22 10:40 ` Michal Kazior
2014-10-23  6:57   ` Okhwan Lee
2014-10-24  7:49     ` Michal Kazior
2014-10-24 11:30       ` Okhwan Lee [this message]
2014-10-24 11:38         ` Michal Kazior
2014-10-26  9:10           ` Okhwan Lee

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=etPan.544a384b.74b0dc51.8406@Mac-Pro.local \
    --to=ohlee@mwnl.snu.ac.kr \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.com \
    /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