From: reinette chatre <reinette.chatre@intel.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: Re: Panic in iwl3945 driver
Date: Mon, 30 Nov 2009 13:42:13 -0800 [thread overview]
Message-ID: <1259617333.4653.91.camel@rc-desk> (raw)
In-Reply-To: <1259596551.4090.0.camel@maxim-laptop>
On Mon, 2009-11-30 at 07:55 -0800, Maxim Levitsky wrote:
> > This is some very unpleasant problem.
> > The thing is that this happens very rarely, and while you use X.
> > I had recently few such embarrassing kernel panics (I never had any
> > random and rare kernel panics) and I strongly suspect them to be of same
> > origin.
> >
> > This one is first I captured, due to some code that I wrote recently
> > that saves printk buffer in predefined location in system ram that isn't
> > cleared on reboot in my notebook.
> >
> > I had put some NULL checks in iwl3945_rx_reply_tx, none did trigger yet,
> > nor I had another kernel panic.
Did this problem happen with your NULL checks in place? Can you perhaps
help here with which line the problem occurred? Any idea how to trigger
this?
Thank you
Reinette
next prev parent reply other threads:[~2009-11-30 21:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:49 Panic in iwl3945 driver Maxim Levitsky
2009-11-27 0:00 ` Maxim Levitsky
2009-11-30 15:55 ` Maxim Levitsky
2009-11-30 21:42 ` reinette chatre [this message]
2009-11-30 22:35 ` Maxim Levitsky
2009-12-01 9:28 ` Zhu Yi
2009-12-01 18:52 ` reinette chatre
2009-12-02 2:06 ` Zhu Yi
2009-12-02 5:42 ` Zhu Yi
2009-12-02 17:17 ` Maxim Levitsky
2009-12-21 16:40 ` Maxim Levitsky
2009-12-22 8:57 ` Zhu Yi
2010-01-05 16:56 ` Maxim Levitsky
2010-01-05 22:16 ` [ipw3945-devel] " Cahill, Ben M
2010-01-05 22:26 ` Cahill, Ben M
2010-01-06 3:57 ` Zhu Yi
2010-01-06 5:23 ` Cahill, Ben M
2010-01-06 3:55 ` Zhu Yi
2009-12-02 19:18 ` [ipw3945-devel] " Cahill, Ben M
2009-12-02 19:40 ` Abhijeet Kolekar
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=1259617333.4653.91.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.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;
as well as URLs for NNTP newsgroup(s).