From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Antonio Quartulli <ordex@autistici.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi warn_slowpath with 3.*
Date: Sun, 6 May 2012 12:58:17 +0300 [thread overview]
Message-ID: <CANUX_P25q-CM8WX7R2v5XsPaLa6B72rGFC95dTeaz_EqxLoZ0Q@mail.gmail.com> (raw)
In-Reply-To: <20120506095750.GB21716@ritirata.org>
>> >>> > Can you please test the patch I sent to you (which was good but not enough)
>> >>> > And add this one too ?
>> >>>
>> >>> Ok, I'll also leave the print.patch.
>> >>> I'll report the result.
>> >>>
>> >>
>> >> The WARNING is gone :)
>> >>
>> >> I attached the dmesg log anyway (debug was off, but there
>> >> are all the prints you introduced).
>> >>
>> >> To be sure, I also removed all the IWL_ERR you added and tried to reboot (in
>> >> order to see whether the printings were affecting synchronization).
>> >>
>> >
>> > Glad to hear.
>> >
>> > You can also remove everything. Reapply the second patch, and here is
>> > a new version of this patch after cleaning.
>>
>> I meant, reapply the first patch (the one that zeroes the TBs).
>
> Do you think thise patches should be backported for stable? Doesn't seem to be
> trivial..
>
Well.... it seems that they need to... I will see what to do. For this
kind of things, I have a maintainer :-)
next prev parent reply other threads:[~2012-05-06 9:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 18:29 iwlwifi warn_slowpath with 3.* Antonio Quartulli
2012-04-30 14:58 ` Antonio Quartulli
2012-04-30 17:03 ` John W. Linville
2012-04-30 20:12 ` Emmanuel Grumbach
2012-04-30 20:13 ` Emmanuel Grumbach
2012-05-01 16:52 ` Venkataraman, Meenakshi
2012-05-01 17:13 ` Emmanuel Grumbach
2012-05-01 18:34 ` Antonio Quartulli
2012-05-01 20:56 ` Antonio Quartulli
2012-05-01 21:19 ` Venkataraman, Meenakshi
2012-05-02 7:08 ` Emmanuel Grumbach
2012-05-02 15:31 ` Antonio Quartulli
2012-05-02 15:39 ` John W. Linville
2012-05-02 16:12 ` Antonio Quartulli
2012-05-02 16:21 ` Antonio Quartulli
2012-05-03 6:53 ` Antonio Quartulli
2012-05-03 19:04 ` Emmanuel Grumbach
2012-05-03 19:55 ` Emmanuel Grumbach
2012-05-03 20:09 ` Antonio Quartulli
2012-05-03 20:17 ` Emmanuel Grumbach
2012-05-04 0:21 ` Antonio Quartulli
2012-05-04 5:11 ` Emmanuel Grumbach
2012-05-04 6:36 ` Antonio Quartulli
2012-05-04 6:58 ` Emmanuel Grumbach
2012-05-04 7:28 ` Antonio Quartulli
2012-05-04 14:20 ` Antonio Quartulli
2012-05-05 18:49 ` Emmanuel Grumbach
2012-05-06 5:49 ` Emmanuel Grumbach
2012-05-06 7:54 ` Antonio Quartulli
2012-05-06 8:26 ` Emmanuel Grumbach
2012-05-06 8:56 ` Antonio Quartulli
2012-05-06 9:15 ` Antonio Quartulli
2012-05-06 9:25 ` Emmanuel Grumbach
2012-05-06 9:26 ` Emmanuel Grumbach
2012-05-06 9:40 ` Antonio Quartulli
2012-05-06 9:57 ` Antonio Quartulli
2012-05-06 9:58 ` Emmanuel Grumbach [this message]
2012-05-06 8:59 ` Antonio Quartulli
2012-05-06 9:23 ` Emmanuel Grumbach
2012-05-01 18:33 ` Antonio Quartulli
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=CANUX_P25q-CM8WX7R2v5XsPaLa6B72rGFC95dTeaz_EqxLoZ0Q@mail.gmail.com \
--to=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meenakshi.venkataraman@intel.com \
--cc=ordex@autistici.org \
/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).