From: reinette chatre <reinette.chatre@intel.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Zhu, Yi" <yi.zhu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mmotm 2009-04-27-15-45 uploaded - iwl3945 oops
Date: Thu, 30 Apr 2009 15:46:53 -0700 [thread overview]
Message-ID: <1241131613.10498.80.camel@rc-desk> (raw)
In-Reply-To: <24133.1241020608@turing-police.cc.vt.edu>
On Wed, 2009-04-29 at 08:56 -0700, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 28 Apr 2009 13:39:44 PDT, reinette chatre said:
>
> > Could you please revert this and test again?
> >
> > If this does not help, could you please bisect?
>
> Same kernel that oopsed 2 nights ago failed to do so in 8 or 9 hours last
> night - so it isn't a "fire up wpa_supplicant and know inside 20 or 30 seconds
> if the kernel tested is good" candidate for bisection. Will collect what
> info I can.
Do you perhaps still have the original logs of this problem? The log you
sent initially started with some errors. Were there perhaps any other
driver status or error messages printed before that?
Thank you
Reinette
prev parent reply other threads:[~2009-04-30 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904272305.n3RN51mu031395@imap1.linux-foundation.org>
2009-04-28 4:24 ` [PATCH -mmotm] ecryptfs: fix printk format warning Randy Dunlap
2009-04-28 17:14 ` mmotm 2009-04-27-15-45 uploaded - iwl3945 oops Valdis.Kletnieks
2009-04-28 20:39 ` reinette chatre
2009-04-28 20:38 ` John W. Linville
2009-04-28 20:55 ` reinette chatre
2009-04-29 15:56 ` Valdis.Kletnieks
2009-04-30 22:46 ` reinette chatre [this message]
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=1241131613.10498.80.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=yi.zhu@intel.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