Bug 18992
| Summary: | warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | rocko (rockorequin) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | CLOSED DUPLICATE | ||
| Severity: | normal | CC: | florian, linville, maciej.rutecki, rjw, wey-yi.w.guy |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.36-rc5 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 16444 | ||
| Attachments: | syslog showing warn_slowpath_common | ||
There are some very recent changes submit by Stanislaw Gruszka in this area. 3a160a5b5fc7d45fa2f869b23f8fcd27a4c05f8f iwlwifi: apply settings when finishing scan 7cf24421292d92556d53630e6973b34324c94103 iwlwifi: use IWL_DEBUG_SCAN for debug scanning 74d81b259d6c8493f066e34c939cb6fb7d3129e5 iwlwifi: cleanup scan initiate check edeb78a7fa838b7fb9c2043680bd8da7cb5cb0e5 mac80211: wait for scan work complete before restarting hw e7e16b90b477a07d17af37dceb2e8af1ddbd9712 iwlwifi: do not force complete scan too early 6bd1758d978f917dc0804f44e3528ef1a80d9d43 iwlwifi: assure we complete scan in scan_abort and scan_check works f5354c17dc29681c241f2774f3ef9478fb586673 iwlwifi: force scan complete after timeout 02d8c14b590f583fd6e8c16fe779f845845effd9 iwlwifi: rewrite scan completion e693a802f06f538b711333a32a83e2732dc4773d iwlwifi: rework iwl_scan_cancel_timeout cd44600fdd89832c0bc898189270a81be0db01cd iwlwifi: report scan completion when abort fail d745d472afcbc6354ebfee008123894a7f37e97e iwlwifi: cancel scan when down the device b62177a0aa0521fd07cd7501534c0c3b256ebce6 iwlwifi: fix canceling monitor_recover timer c240879f3488ae0904a7ba5bdaaa54638b2d8852 iwlwifi: make scan workqueue functions static d28232b461b8d54b09e59325dbac8b0913ce2049 iwlwifi: fix scan abort Wey That is a long list of patches to consider for 2.6.36. Is it possible we could have a targetted fix for that release? rocko, would you care to do a bisect to determine what may be causing this message? Should those commits be the /linux/kernel/git/torvalds/linux-2.6 tree? The only one I can find there is the last one (fix scan abort). The kernel I'm using is built from the 2.6.36-rc5 source tarball, not from git. Is the tarball based on a different tree? FWIW, it also happens in 2.6.36-rc3. I don't have the source for 2.6.36-rc2, so I can't do much else unless someone can point me to the right tree to bisect against. Can check the patch attached to bug 17722? *** This bug has been marked as a duplicate of bug 17722 *** On Tuesday, September 28, 2010, Rocko Requin wrote:
>
> Yes, this bug should still be listed as a regression.
>
> >
> > This message has been generated automatically as a part of a summary report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.35. Please verify if it still should be listed and let the
> tracking team
> > know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18992
> > Subject : warn_slow_path_common in iwlagn/mac80211 in
> 2.6.36-rc5
> > Submitter : rocko <rockorequin@hotmail.com>
> > Date : 2010-09-23 03:07 (4 days old)
Pleae do bisection against this tree: git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git |
Created attachment 31062 [details] syslog showing warn_slowpath_common See attached log. The problem only appears in 2.6.36, not in 2.6.35 or earlier, and it happens fairly regularly. It doesn't seem to break anything, though. The hardware is an Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) 11N card.