mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: wwguy <wey-yi.w.guy@intel.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 2.6.38-rc7, iwlagn crash
Date: Sat, 05 Mar 2011 15:09:04 +0100	[thread overview]
Message-ID: <1299334144.3826.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTikUE-LLSBNH=cNmPZ+Wenff5RxKcfK0kJXp9Wk+@mail.gmail.com>

On Sat, 2011-03-05 at 09:45 +0000, Mathias Burén wrote:

> I compiled my own kernel (downloaded 2.6.37-rc8 source, applied the
> apparmor patch required for Ubuntu, copied over the config, make
> oldconfig, enabled iwlwifi debug in menuconfig then compiled it),
> booted it and loaded iwlagn with debug=0x43fff. Then I attempted the
> same thing (Ubuntu Adhoc, no wireless security, trying to connect with
> the phone).
> 
> The entire dmesg can be found here:
> http://www.privatepaste.com/download/49e6ead6c7

So the warning is gone now?

johannes


  parent reply	other threads:[~2011-03-05 14:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  3:27 Mathias Burén
2011-03-04 13:46 ` John W. Linville
2011-03-04 15:17   ` wwguy
2011-03-04 22:23     ` Mathias Burén
2011-03-05  3:45       ` Mathias Burén
2011-03-05  9:45         ` Mathias Burén
2011-03-05  9:54           ` Mathias Burén
2011-03-05 14:09           ` Johannes Berg [this message]
2011-03-05 23:45             ` Mathias Burén
2011-03-08 15:17               ` 2.6.38-rc7, iwlagn warning Johannes Berg
2011-03-08 16:22                 ` Mathias Burén
2011-03-08 16:26                   ` Johannes Berg
2011-03-08 15:18               ` 2.6.38-rc7, iwlagn crash Johannes Berg

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=1299334144.3826.8.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ilw@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mathias.buren@gmail.com \
    --cc=wey-yi.w.guy@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

all inboxes | Powered by JetHome®