From: Ben Greear <greearb@candelatech.com>
To: Pink <pink@Informatik.TU-Cottbus.DE>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Question about debugging mac80211 without printk
Date: Thu, 25 Sep 2014 09:55:55 -0700 [thread overview]
Message-ID: <5424491B.4000402@candelatech.com> (raw)
In-Reply-To: <542448C0.9040505@Informatik.TU-Cottbus.DE>
On 09/25/2014 09:54 AM, Pink wrote:
> Hi,
>
> actually if have the following problem, if have a lot of debug messages using printk inside the mac layer but if there is a
> critical bug in the source code of the mac80211 module
> the system goes into kernel panic state during execution. Unfortunately so far i now, it isn't possible
> after a system restart to identify the rough position of the bug looking for the debug msg's written before the bug has occured in
> dmesg or syslog because the messages were not saved in follow of the crash.
>
> Now i thought user mode linux (uml) is maybe a potential solution to identify the bug, if the kernel running the mac layer
> is executed as virtual machine in uml. But i didn't found any kind of description how to forward the physical wireless card except using TAP/TUN device to the
> vm so
> that the kernel inside the vm can run its mac layer directly on the card.
>
> Now my question what tools are you use for the development and testing of the ath wireless driver
> as well as the complete wireless stack including mac80211. Is it user mode linux or something else?
> If user mode linux is used, is there any howto available to forward the atheros card to the vm.
Have you tried using a serial-console? That is usually adequate for getting
crash dumps and resolving most issues.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-09-25 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 16:54 Question about debugging mac80211 without printk Pink
2014-09-25 16:55 ` Ben Greear [this message]
2014-09-26 6:15 ` Michal Kazior
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=5424491B.4000402@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pink@Informatik.TU-Cottbus.DE \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.