2.6.29-rc8: Reported regressions from 2.6.28

2.6.29-rc8: Reported regressions from 2.6.28

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.28, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.28, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-03-14      124       36          32
  2009-03-03      108       33          28
  2009-02-24       95       32          24
  2009-02-14       85       33          27
  2009-02-08       82       45          36
  2009-02-04       66       51          39
  2009-01-20       38       35          27
  2009-01-11       13       13          10


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL@web.de>
Date		: 2009-03-14 16:42 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2009-03-10 11:23 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
Subject		: 2.6.29-rc "TKIP: replay detected" regression
Submitter	: Hugh Dickins <hugh@veritas.com>
Date		: 2009-03-11 12:07 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
Handled-By	: John W. Linville <linville@tuxdriver.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2009-03-09 20:29 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12861
Subject		: Xorg fails to start "Failed to allocate space for kernel memory manager"
Submitter	: Emil Karlson <jkarlson@cc.hut.fi>
Date		: 2009-03-12 12:06 (3 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12856
Subject		: Thinkpad freezes with X.org and acpi=rsdt
Submitter	: Maciej Piechotka <uzytkownik2@gmail.com>
Date		: 2009-03-11 16:46 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12846
Subject		: Regression issue with kernel 2.6.29-rc6-git1: high power consumption during sleep
Submitter	: Raymond Wooninck <tittiatcoke@gmail.com>
Date		: 2009-03-09 08:18 (6 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12842
Subject		: CCMP: replay detected
Submitter	: Peter Teoh <htmldeveloper@gmail.com>
Date		: 2009-03-08 07:42 (7 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
Date		: 2009-03-04 19:20 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12831
Subject		: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
Submitter	: Matthew <pyther@pyther.net>
Date		: 2009-03-07 10:05 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (16 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12808
Subject		: Suspend regression with 2.6.29-rc
Submitter	: Tino Keitel <tino.keitel@gmx.de>
Date		: 2009-02-24 19:08 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=123550257312112&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
Subject		: i915 broken STR
Submitter	: Harvey Harrison <harvey.harrison@gmail.com>
Date		: 2009-02-28 4:20 (15 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12805
Subject		: QinQ vlan trunking regression
Submitter	: Bart Trojanowski <bart@jukie.net>
Date		: 2009-02-28 18:05 (15 days old)
References	: http://marc.info/?l=linux-kernel&m=123584439115868&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12800
Subject		: x86 PAT invalid vm_insert_pfn assumptions
Submitter	: Thomas Hellstrom <thellstrom@vmware.com>
Date		: 2009-03-02 01:40 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
Subject		: 2.6.29-rc6-git4 boot failure
Submitter	: Sachin P. Sant <sachinp@in.ibm.com>
Date		: 2009-02-27 23:19 (16 days old)
References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy@gmail.com>
Date		: 2009-02-25 09:25 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev@colleduc.ee>
Date		: 2009-02-24 08:35 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject		: i915 VT switch with AIGLX causes X lock up
Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
Date		: 2009-02-21 15:38 (22 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12763
Subject		: Different cpu MHz values for processor0 and processor1
Submitter	: Matthew A. Bockol <mbockol@carleton.edu>
Date		: 2009-02-21 5:42 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123519687807246&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject		: X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter	: Nico Schottelius <nico-linux-20090213@schottelius.org>
Date		: 2009-02-13 9:33 (30 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e806b4957412bf472d826bd8cc571da041248799
References	: http://marc.info/?l=linux-kernel&m=123451768406825&w=4
		  http://marc.info/?l=linux-kernel&m=123479975503827&w=2
Handled-By	: Len Brown <lenb@kernel.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12681
Subject		: s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)
Submitter	: Orivej Desh <smpuj@bk.ru>
Date		: 2009-02-09 13:01 (34 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12680
Subject		: Entropy pool problem
Submitter	: Valentin QUEQUET <v.quequet-techniques@orange.fr>
Date		: 2009-02-09 09:12 (34 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
Date		: 2009-02-08 11:04 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2009-02-08 10:21 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
Date		: 2009-01-29 11:35 (45 days old)
References	: http://lkml.org/lkml/2009/2/9/205


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2009-01-13 18:34 (61 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject		: ath5k related kernel panic in 2.6.29-rc1
Submitter	: Sergey S. Kostyliov <rathamahata@gmail.com>
Date		: 2009-01-12 7:38 (62 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
Handled-By	: Bob Copeland <me@bobcopeland.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12444
Subject		: X hangs following switch from radeonfb console - Bisected
Submitter	: Graham Murray <graham@gmurray.org.uk>
Date		: 2009-01-13 14:03 (61 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12419
Subject		: possible circular locking dependency on i915 dma
Submitter	: Wang Chen <wangchen@cn.fujitsu.com>
Date		: 2009-01-08 14:11 (66 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=546b0974c39657017407c86fe79811100b60700d
References	: http://marc.info/?l=linux-kernel&m=123142399720125&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12418
Subject		: Repeated ioctl(4, 0x40046445, ..) loop in glxgears
Submitter	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
Date		: 2009-01-07 22:43 (67 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a
References	: http://marc.info/?l=linux-kernel&m=123136836213319&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12414
Subject		: iwl4965 cannot use "ap auto" on latest 2.6.28/29?
Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
Date		: 2009-01-05 4:13 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=123112882127823&w=4


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
Subject		: BUG when disabled ipv6 module is unloaded
Submitter	: Thomas Backlund <tmb@mandriva.org>
Date		: 2009-03-10 20:15 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
Handled-By	: John Dykstra <john.dykstra1@gmail.com>
Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12758
Subject		: ACPI exception with 2.6.29-rc6
Submitter	: Heinz Diehl <htd@fancy-poultry.org>
Date		: 2009-02-23 16:46 (20 days old)
References	: http://marc.info/?l=linux-kernel&m=123540758700861&w=4
Handled-By	: Len Brown <lenb@kernel.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=20368&action=view


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo@elte.hu>
Date		: 2009-02-08 14:58 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap@oracle.com>
Patch		: http://lkml.org/lkml/2009/2/15/172


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul@burly.ondioline.org>
Date		: 2009-01-21 7:15 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Patch		: http://lkml.org/lkml/2009/2/16/78


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.28,
unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=12398

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael

[Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12414
Subject		: iwl4965 cannot use "ap auto" on latest 2.6.28/29?
Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
Date		: 2009-01-05 4:13 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=123112882127823&w=4

[Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29?

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12414
Subject		: iwl4965 cannot use "ap auto" on latest 2.6.28/29?
Submitter	: Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-05 4:13 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=123112882127823&w=4

[Bug #12419] possible circular locking dependency on i915 dma

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12419
Subject		: possible circular locking dependency on i915 dma
Submitter	: Wang Chen <wangchen@cn.fujitsu.com>
Date		: 2009-01-08 14:11 (66 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=546b0974c39657017407c86fe79811100b60700d
References	: http://marc.info/?l=linux-kernel&m=123142399720125&w=4

[Bug #12444] X hangs following switch from radeonfb console - Bisected

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12444
Subject		: X hangs following switch from radeonfb console - Bisected
Submitter	: Graham Murray <graham@gmurray.org.uk>
Date		: 2009-01-13 14:03 (61 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a

[Bug #12490] ath5k related kernel panic in 2.6.29-rc1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject		: ath5k related kernel panic in 2.6.29-rc1
Submitter	: Sergey S. Kostyliov <rathamahata@gmail.com>
Date		: 2009-01-12 7:38 (62 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
Handled-By	: Bob Copeland <me@bobcopeland.com>

[Bug #12418] Repeated ioctl(4, 0x40046445, ..) loop in glxgears

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12418
Subject		: Repeated ioctl(4, 0x40046445, ..) loop in glxgears
Submitter	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
Date		: 2009-01-07 22:43 (67 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a
References	: http://marc.info/?l=linux-kernel&m=123136836213319&w=4

[Bug #12419] possible circular locking dependency on i915 dma

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12419
Subject		: possible circular locking dependency on i915 dma
Submitter	: Wang Chen <wangchen-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Date		: 2009-01-08 14:11 (66 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=546b0974c39657017407c86fe79811100b60700d
References	: http://marc.info/?l=linux-kernel&m=123142399720125&w=4

[Bug #12444] X hangs following switch from radeonfb console - Bisected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12444
Subject		: X hangs following switch from radeonfb console - Bisected
Submitter	: Graham Murray <graham-0mDQKtL6jrwDXYZnReoRVg@public.gmane.org>
Date		: 2009-01-13 14:03 (61 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a

[Bug #12490] ath5k related kernel panic in 2.6.29-rc1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject		: ath5k related kernel panic in 2.6.29-rc1
Submitter	: Sergey S. Kostyliov <rathamahata-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-12 7:38 (62 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
Handled-By	: Bob Copeland <me-aXfl/3sk2vNUbtYUoyoikg@public.gmane.org>

[Bug #12418] Repeated ioctl(4, 0x40046445, ..) loop in glxgears

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12418
Subject		: Repeated ioctl(4, 0x40046445, ..) loop in glxgears
Submitter	: Pallipadi, Venkatesh <venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-07 22:43 (67 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a
References	: http://marc.info/?l=linux-kernel&m=123136836213319&w=4

[Bug #12499] Problem with using bluetooth adaper connected to usb port

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2009-01-13 18:34 (61 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4

[Bug #12574] possible circular locking dependency detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
Date		: 2009-01-29 11:35 (45 days old)
References	: http://lkml.org/lkml/2009/2/9/205

[Bug #12667] Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul@burly.ondioline.org>
Date		: 2009-01-21 7:15 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Patch		: http://lkml.org/lkml/2009/2/16/78

[Bug #12668] USB flash disk surprise disconnect

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2009-02-08 10:21 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4

[Bug #12499] Problem with using bluetooth adaper connected to usb port

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: Maciej Rutecki <maciej.rutecki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-13 18:34 (61 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4

[Bug #12574] possible circular locking dependency detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-01-29 11:35 (45 days old)
References	: http://lkml.org/lkml/2009/2/9/205

[Bug #12668] USB flash disk surprise disconnect

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-08 10:21 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4

[Bug #12667] Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul-dsjeNyW6Qm/D+ROgJ3VA+kB+6BGkLq7r@public.gmane.org>
Date		: 2009-01-21 7:15 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/2/16/78

[Bug #12681] s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12681
Subject		: s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)
Submitter	: Orivej Desh <smpuj@bk.ru>
Date		: 2009-02-09 13:01 (34 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594

[Bug #12671] uvc_status_cleanup(): undefined reference to `input_unregister_device'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo@elte.hu>
Date		: 2009-02-08 14:58 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap@oracle.com>
Patch		: http://lkml.org/lkml/2009/2/15/172

[Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
Date		: 2009-02-08 11:04 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4

[Bug #12680] Entropy pool problem

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12680
Subject		: Entropy pool problem
Submitter	: Valentin QUEQUET <v.quequet-techniques@orange.fr>
Date		: 2009-02-09 09:12 (34 days old)

[Bug #12670] BUG: unable to handle kernel paging request at pin_to_kill+0x21

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-08 11:04 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4

[Bug #12671] uvc_status_cleanup(): undefined reference to `input_unregister_device'

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Date		: 2009-02-08 14:58 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Patch		: http://lkml.org/lkml/2009/2/15/172

[Bug #12680] Entropy pool problem

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12680
Subject		: Entropy pool problem
Submitter	: Valentin QUEQUET <v.quequet-techniques-1tsiiZ//OF9QFI55V6+gNQ@public.gmane.org>
Date		: 2009-02-09 09:12 (34 days old)

[Bug #12705] X200: Brightness broken since 2.6.29-rc4-58-g4c098bc

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject		: X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter	: Nico Schottelius <nico-linux-20090213@schottelius.org>
Date		: 2009-02-13 9:33 (30 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e806b4957412bf472d826bd8cc571da041248799
References	: http://marc.info/?l=linux-kernel&m=123451768406825&w=4
		  http://marc.info/?l=linux-kernel&m=123479975503827&w=2
Handled-By	: Len Brown <lenb@kernel.org>

[Bug #12763] Different cpu MHz values for processor0 and processor1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12763
Subject		: Different cpu MHz values for processor0 and processor1
Submitter	: Matthew A. Bockol <mbockol@carleton.edu>
Date		: 2009-02-21 5:42 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123519687807246&w=4

[Bug #12758] ACPI exception with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12758
Subject		: ACPI exception with 2.6.29-rc6
Submitter	: Heinz Diehl <htd@fancy-poultry.org>
Date		: 2009-02-23 16:46 (20 days old)
References	: http://marc.info/?l=linux-kernel&m=123540758700861&w=4
Handled-By	: Len Brown <lenb@kernel.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=20368&action=view

[Bug #12763] Different cpu MHz values for processor0 and processor1

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12763
Subject		: Different cpu MHz values for processor0 and processor1
Submitter	: Matthew A. Bockol <mbockol-dmoCqaWXHRX2fBVCVOL8/A@public.gmane.org>
Date		: 2009-02-21 5:42 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123519687807246&w=4

[Bug #12758] ACPI exception with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12758
Subject		: ACPI exception with 2.6.29-rc6
Submitter	: Heinz Diehl <htd-HjJ2MNWy62to6+H+lsi3Gti2O/JbrIOy@public.gmane.org>
Date		: 2009-02-23 16:46 (20 days old)
References	: http://marc.info/?l=linux-kernel&m=123540758700861&w=4
Handled-By	: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=20368&action=view

[Bug #12705] X200: Brightness broken since 2.6.29-rc4-58-g4c098bc

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject		: X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter	: Nico Schottelius <nico-linux-20090213-xuaVFQXs+5hIG4jRRZ66WA@public.gmane.org>
Date		: 2009-02-13 9:33 (30 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e806b4957412bf472d826bd8cc571da041248799
References	: http://marc.info/?l=linux-kernel&m=123451768406825&w=4
		  http://marc.info/?l=linux-kernel&m=123479975503827&w=2
Handled-By	: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

[Bug #12765] i915 VT switch with AIGLX causes X lock up

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject		: i915 VT switch with AIGLX causes X lock up
Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
Date		: 2009-02-21 15:38 (22 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4

[Bug #12771] Oops in i915_gem_flush

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev@colleduc.ee>
Date		: 2009-02-24 08:35 (19 days old)

[Bug #12778] suspend regression from 29rc5 to 29rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy@gmail.com>
Date		: 2009-02-25 09:25 (18 days old)

[Bug #12765] i915 VT switch with AIGLX causes X lock up

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject		: i915 VT switch with AIGLX causes X lock up
Submitter	: Sitsofe Wheeler <sitsofe-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-21 15:38 (22 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4

[Bug #12771] Oops in i915_gem_flush

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev-KfhB8dnw0QSuvFJfX82//w@public.gmane.org>
Date		: 2009-02-24 08:35 (19 days old)

[Bug #12778] suspend regression from 29rc5 to 29rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-25 09:25 (18 days old)

[Bug #12792] 2.6.29-rc6-git4 boot failure

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
Subject		: 2.6.29-rc6-git4 boot failure
Submitter	: Sachin P. Sant <sachinp@in.ibm.com>
Date		: 2009-02-27 23:19 (16 days old)
References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html

[Bug #12805] QinQ vlan trunking regression

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12805
Subject		: QinQ vlan trunking regression
Submitter	: Bart Trojanowski <bart@jukie.net>
Date		: 2009-02-28 18:05 (15 days old)
References	: http://marc.info/?l=linux-kernel&m=123584439115868&w=4

[Bug #12800] x86 PAT invalid vm_insert_pfn assumptions

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12800
Subject		: x86 PAT invalid vm_insert_pfn assumptions
Submitter	: Thomas Hellstrom <thellstrom@vmware.com>
Date		: 2009-03-02 01:40 (13 days old)

[Bug #12792] 2.6.29-rc6-git4 boot failure

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
Subject		: 2.6.29-rc6-git4 boot failure
Submitter	: Sachin P. Sant <sachinp-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
Date		: 2009-02-27 23:19 (16 days old)
References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html

[Bug #12800] x86 PAT invalid vm_insert_pfn assumptions

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12800
Subject		: x86 PAT invalid vm_insert_pfn assumptions
Submitter	: Thomas Hellstrom <thellstrom-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Date		: 2009-03-02 01:40 (13 days old)

[Bug #12831] Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12831
Subject		: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
Submitter	: Matthew <pyther@pyther.net>
Date		: 2009-03-07 10:05 (8 days old)

[Bug #12808] Suspend regression with 2.6.29-rc

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12808
Subject		: Suspend regression with 2.6.29-rc
Submitter	: Tino Keitel <tino.keitel@gmx.de>
Date		: 2009-02-24 19:08 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=123550257312112&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>

[Bug #12806] i915 broken STR

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
Subject		: i915 broken STR
Submitter	: Harvey Harrison <harvey.harrison@gmail.com>
Date		: 2009-02-28 4:20 (15 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (16 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

[Bug #12809] iozone regression with 2.6.29-rc6

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-27 9:13 (16 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

[Bug #12806] i915 broken STR

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
Subject		: i915 broken STR
Submitter	: Harvey Harrison <harvey.harrison-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-02-28 4:20 (15 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4

[Bug #12808] Suspend regression with 2.6.29-rc

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12808
Subject		: Suspend regression with 2.6.29-rc
Submitter	: Tino Keitel <tino.keitel-Mmb7MZpHnFY@public.gmane.org>
Date		: 2009-02-24 19:08 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=123550257312112&w=4
Handled-By	: Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org>

[Bug #12831] Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12831
Subject		: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
Submitter	: Matthew <pyther-H7dpiqUitzOsTnJN9+BGXg@public.gmane.org>
Date		: 2009-03-07 10:05 (8 days old)

[Bug #12842] CCMP: replay detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12842
Subject		: CCMP: replay detected
Submitter	: Peter Teoh <htmldeveloper@gmail.com>
Date		: 2009-03-08 07:42 (7 days old)

[Bug #12856] Thinkpad freezes with X.org and acpi=rsdt

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12856
Subject		: Thinkpad freezes with X.org and acpi=rsdt
Submitter	: Maciej Piechotka <uzytkownik2@gmail.com>
Date		: 2009-03-11 16:46 (4 days old)

[Bug #12836] 2.6.29-rc breaks STD using Intel 945

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
Date		: 2009-03-04 19:20 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

[Bug #12846] Regression issue with kernel 2.6.29-rc6-git1: high power consumption during sleep

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12846
Subject		: Regression issue with kernel 2.6.29-rc6-git1: high power consumption during sleep
Submitter	: Raymond Wooninck <tittiatcoke@gmail.com>
Date		: 2009-03-09 08:18 (6 days old)

[Bug #12856] Thinkpad freezes with X.org and acpi=rsdt

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12856
Subject		: Thinkpad freezes with X.org and acpi=rsdt
Submitter	: Maciej Piechotka <uzytkownik2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-11 16:46 (4 days old)

[Bug #12846] Regression issue with kernel 2.6.29-rc6-git1: high power consumption during sleep

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12846
Subject		: Regression issue with kernel 2.6.29-rc6-git1: high power consumption during sleep
Submitter	: Raymond Wooninck <tittiatcoke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-09 08:18 (6 days old)

[Bug #12842] CCMP: replay detected

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12842
Subject		: CCMP: replay detected
Submitter	: Peter Teoh <htmldeveloper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date		: 2009-03-08 07:42 (7 days old)

[Bug #12836] 2.6.29-rc breaks STD using Intel 945

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel-F+mm6HnICJmzQB+pC5nmwQ@public.gmane.org>
Date		: 2009-03-04 19:20 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4

[Bug #12861] Xorg fails to start "Failed to allocate space for kernel memory manager"

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12861
Subject		: Xorg fails to start "Failed to allocate space for kernel memory manager"
Submitter	: Emil Karlson <jkarlson@cc.hut.fi>
Date		: 2009-03-12 12:06 (3 days old)

[Bug #12867] 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2009-03-09 20:29 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>

[Bug #12867] 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>
Date		: 2009-03-09 20:29 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org>

[Bug #12861] Xorg fails to start "Failed to allocate space for kernel memory manager"

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12861
Subject		: Xorg fails to start "Failed to allocate space for kernel memory manager"
Submitter	: Emil Karlson <jkarlson-kf+aQKke1yb1KXRcyAk9cg@public.gmane.org>
Date		: 2009-03-12 12:06 (3 days old)

[Bug #12869] BUG when disabled ipv6 module is unloaded

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
Subject		: BUG when disabled ipv6 module is unloaded
Submitter	: Thomas Backlund <tmb@mandriva.org>
Date		: 2009-03-10 20:15 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
Handled-By	: John Dykstra <john.dykstra1@gmail.com>
Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4

[Bug #12869] BUG when disabled ipv6 module is unloaded

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
Subject		: BUG when disabled ipv6 module is unloaded
Submitter	: Thomas Backlund <tmb-4qZELD6Fgxhg9hUCZPvPmw@public.gmane.org>
Date		: 2009-03-10 20:15 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
Handled-By	: John Dykstra <john.dykstra1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4

[Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
Subject		: 2.6.29-rc "TKIP: replay detected" regression
Submitter	: Hugh Dickins <hugh@veritas.com>
Date		: 2009-03-11 12:07 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
Handled-By	: John W. Linville <linville@tuxdriver.com>

[Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
Subject		: 2.6.29-rc "TKIP: replay detected" regression
Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
Date		: 2009-03-11 12:07 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
Handled-By	: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

[Bug #12871] usb bluetooth crashes system

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2009-03-10 11:23 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

[Bug #12872] pwc mmap always fails with EAGAIN

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL@web.de>
Date		: 2009-03-14 16:42 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4

[Bug #12871] usb bluetooth crashes system

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Date		: 2009-03-10 11:23 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

[Bug #12872] pwc mmap always fails with EAGAIN

[Rafael J. Wysocki]

This message has been generated automatically as a part of a report
of recent regressions.

The following bug entry is on the current list of known regressions
from 2.6.28.  Please verify if it still should be listed and let me know
(either way).


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL-S0/GAf8tV78@public.gmane.org>
Date		: 2009-03-14 16:42 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4

Re: [Bug #12805] QinQ vlan trunking regression

[David Miller]

From: "Rafael J. Wysocki" <rjw@sisk.pl>
Date: Sat, 14 Mar 2009 20:05:33 +0100 (CET)

> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12805
> Subject		: QinQ vlan trunking regression
> Submitter	: Bart Trojanowski <bart@jukie.net>
> Date		: 2009-02-28 18:05 (15 days old)
> References	: http://marc.info/?l=linux-kernel&m=123584439115868&w=4

Fixed by:

commit 9d40bbda599def1e1d155d7f7dca14fe8744bd2b
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Mar 4 23:46:25 2009 -0800

    vlan: Fix vlan-in-vlan crashes.
    
    As analyzed by Patrick McHardy, vlan needs to reset it's
    netdev_ops pointer in it's ->init() function but this
    leaves the compat method pointers stale.
    
    Add a netdev_resync_ops() and call it from the vlan code.
    
    Any other driver which changes ->netdev_ops after register_netdevice()
    will need to call this new function after doing so too.
    
    With help from Patrick McHardy.
    
    Tested-by: Patrick McHardy <kaber@trash.net>
    Signed-off-by: David S. Miller <davem@davemloft.net>

Re: [Bug #12869] BUG when disabled ipv6 module is unloaded

[Thomas Backlund]

Rafael J. Wysocki skrev:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
> Subject		: BUG when disabled ipv6 module is unloaded
> Submitter	: Thomas Backlund <tmb@mandriva.org>
> Date		: 2009-03-10 20:15 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
> Handled-By	: John Dykstra <john.dykstra1@gmail.com>
> Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4
> 
> 

Yeah, sorry for the delay testing it...

I confirm the bug is fixed with the above patch...

--
Thomas

Re: [Bug #12869] BUG when disabled ipv6 module is unloaded

[David Miller]

From: Thomas Backlund <tmb@mandriva.org>
Date: Sun, 15 Mar 2009 00:04:42 +0200

> Rafael J. Wysocki skrev:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
> > Subject		: BUG when disabled ipv6 module is unloaded
> > Submitter	: Thomas Backlund <tmb@mandriva.org>
> > Date		: 2009-03-10 20:15 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
> > Handled-By	: John Dykstra <john.dykstra1@gmail.com>
> > Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4
> > 
> 
> Yeah, sorry for the delay testing it...
> 
> I confirm the bug is fixed with the above patch...

Yes and that patch will be on it's way to Linus from the
net-2.6 tree shortly.

Re: [Bug #12869] BUG when disabled ipv6 module is unloaded

[David Miller]

From: Thomas Backlund <tmb-4qZELD6Fgxhg9hUCZPvPmw@public.gmane.org>
Date: Sun, 15 Mar 2009 00:04:42 +0200

> Rafael J. Wysocki skrev:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
> > Subject		: BUG when disabled ipv6 module is unloaded
> > Submitter	: Thomas Backlund <tmb-4qZELD6Fgxhg9hUCZPvPmw@public.gmane.org>
> > Date		: 2009-03-10 20:15 (5 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
> > Handled-By	: John Dykstra <john.dykstra1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4
> > 
> 
> Yeah, sorry for the delay testing it...
> 
> I confirm the bug is fixed with the above patch...

Yes and that patch will be on it's way to Linus from the
net-2.6 tree shortly.

Re: [Bug #12805] QinQ vlan trunking regression

[Rafael J. Wysocki]

On Saturday 14 March 2009, David Miller wrote:
> From: "Rafael J. Wysocki" <rjw@sisk.pl>
> Date: Sat, 14 Mar 2009 20:05:33 +0100 (CET)
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12805
> > Subject		: QinQ vlan trunking regression
> > Submitter	: Bart Trojanowski <bart@jukie.net>
> > Date		: 2009-02-28 18:05 (15 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123584439115868&w=4
> 
> Fixed by:
> 
> commit 9d40bbda599def1e1d155d7f7dca14fe8744bd2b
> Author: David S. Miller <davem@davemloft.net>
> Date:   Wed Mar 4 23:46:25 2009 -0800
> 
>     vlan: Fix vlan-in-vlan crashes.
>     
>     As analyzed by Patrick McHardy, vlan needs to reset it's
>     netdev_ops pointer in it's ->init() function but this
>     leaves the compat method pointers stale.
>     
>     Add a netdev_resync_ops() and call it from the vlan code.
>     
>     Any other driver which changes ->netdev_ops after register_netdevice()
>     will need to call this new function after doing so too.
>     
>     With help from Patrick McHardy.
>     
>     Tested-by: Patrick McHardy <kaber@trash.net>
>     Signed-off-by: David S. Miller <davem@davemloft.net>

Thanks, closed.

Rafael

Re: [Bug #12805] QinQ vlan trunking regression

[Rafael J. Wysocki]

On Saturday 14 March 2009, David Miller wrote:
> From: "Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public.gmane.org>
> Date: Sat, 14 Mar 2009 20:05:33 +0100 (CET)
> 
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12805
> > Subject		: QinQ vlan trunking regression
> > Submitter	: Bart Trojanowski <bart-LIbhotJ4rFdeoWH0uzbU5w@public.gmane.org>
> > Date		: 2009-02-28 18:05 (15 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123584439115868&w=4
> 
> Fixed by:
> 
> commit 9d40bbda599def1e1d155d7f7dca14fe8744bd2b
> Author: David S. Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
> Date:   Wed Mar 4 23:46:25 2009 -0800
> 
>     vlan: Fix vlan-in-vlan crashes.
>     
>     As analyzed by Patrick McHardy, vlan needs to reset it's
>     netdev_ops pointer in it's ->init() function but this
>     leaves the compat method pointers stale.
>     
>     Add a netdev_resync_ops() and call it from the vlan code.
>     
>     Any other driver which changes ->netdev_ops after register_netdevice()
>     will need to call this new function after doing so too.
>     
>     With help from Patrick McHardy.
>     
>     Tested-by: Patrick McHardy <kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
>     Signed-off-by: David S. Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

Thanks, closed.

Rafael

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Linus Torvalds]

On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> Subject		: iozone regression with 2.6.29-rc6
> Submitter	: Lin Ming <ming.m.lin@intel.com>
> Date		: 2009-02-27 9:13 (16 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> Handled-By	: Wu Fengguang <fengguang.wu@intel.com>

I suspect that I should just raise the default dirty limits. Wu reported 
that it fixed the regression, and while he picked some rather high 
percentages, I think we could certainly raise the rather aggressive 
default ones. 

After all, those default percentages were picked (a) with the old dirty 
logic and (b) largely at random and (c) designed to be aggressive. In 
particular, that (a) means that having fixed some of the dirty accounting, 
maybe the real bug is now that it was always too aggressive, just hidden 
by an accounting issue.

If we raised the default ratio from 5/10 to 10/20, what happens to the 
iozone regression?

		Linus

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Sun, Mar 15, 2009 at 3:01 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12414
> Subject         : iwl4965 cannot use "ap auto" on latest 2.6.28/29?
> Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> Date            : 2009-01-05 4:13 (69 days old)
> References      : http://marc.info/?l=linux-kernel&m=123112882127823&w=4

Still not working in linux-2.6.29-rc8. Broken after the commit below.
There were many changes to wireless after this commit, and simply
reverting this commit will break compiling.

Jeff.



commit 41bb73eeac5ff5fb217257ba33b654747b3abf11
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Wed Oct 29 01:09:37 2008 +0100

    mac80211: remove SSID driver code
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Sun, Mar 15, 2009 at 3:01 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12414
> Subject         : iwl4965 cannot use "ap auto" on latest 2.6.28/29?
> Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> Date            : 2009-01-05 4:13 (69 days old)
> References      : http://marc.info/?l=linux-kernel&m=123112882127823&w=4

Still not working in linux-2.6.29-rc8. Broken after the commit below.
There were many changes to wireless after this commit, and simply
reverting this commit will break compiling.

Jeff.



commit 41bb73eeac5ff5fb217257ba33b654747b3abf11
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Wed Oct 29 01:09:37 2008 +0100

    mac80211: remove SSID driver code

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Sun, Mar 15, 2009 at 3:01 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12414
> Subject         : iwl4965 cannot use "ap auto" on latest 2.6.28/29?
> Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> Date            : 2009-01-05 4:13 (69 days old)
> References      : http://marc.info/?l=linux-kernel&m=123112882127823&w=4

Still not working in linux-2.6.29-rc8. Broken after the commit below.
There were many changes to wireless after this commit, and simply
reverting this commit will break compiling.

Jeff.



commit 41bb73eeac5ff5fb217257ba33b654747b3abf11
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Wed Oct 29 01:09:37 2008 +0100

    mac80211: remove SSID driver code

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Sun, Mar 15, 2009 at 10:58 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Sun, Mar 15, 2009 at 3:01 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12414
>> Subject         : iwl4965 cannot use "ap auto" on latest 2.6.28/29?
>> Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
>> Date            : 2009-01-05 4:13 (69 days old)
>> References      : http://marc.info/?l=linux-kernel&m=123112882127823&w=4
>
> Still not working in linux-2.6.29-rc8. Broken after the commit below.
> There were many changes to wireless after this commit, and simply
> reverting this commit will break compiling.
>
> Jeff.
>
>
>
> commit 41bb73eeac5ff5fb217257ba33b654747b3abf11
> Author: Johannes Berg <johannes@sipsolutions.net>
> Date:   Wed Oct 29 01:09:37 2008 +0100
>
>    mac80211: remove SSID driver code
>

The commit below is causing problem with associating with the hidden AP as well.

Thanks,
Jeff.


71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
commit 71c11fb57b924c160297ccd9e1761db598d00ac2
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Tue Oct 28 18:29:48 2008 +0100

    b43/legacy: remove SSID code

    The SSID programmed into the device is used by the ucode only
    to reply to probe requests, a functionality we disable anyway
    because it doesn't fit with the mac80211/hostapd programming
    model. Therefore, it isn't useful to program the SSID into
    device.

    Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

:040000 040000 18109a6ea13da3cd13bfadd625617894c9f91b50
fc2ca13f0efcd9e51403b5b55ed730e2457a29c0 M      drivers

Re: [Bug #12806] i915 broken STR

[Harvey Harrison]

On Sat, 2009-03-14 at 20:05 +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
> Subject		: i915 broken STR
> Submitter	: Harvey Harrison <harvey.harrison@gmail.com>
> Date		: 2009-02-28 4:20 (15 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
> References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4
> 
> 

You can close this, turns out KMS got enabled in my config and userspace
was too old to cope.

Harvey

Re: [Bug #12806] i915 broken STR

[Harvey Harrison]

On Sat, 2009-03-14 at 20:05 +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
> Subject		: i915 broken STR
> Submitter	: Harvey Harrison <harvey.harrison-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-02-28 4:20 (15 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
> References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4
> 
> 

You can close this, turns out KMS got enabled in my config and userspace
was too old to cope.

Harvey

Re: [Bug #12871] usb bluetooth crashes system

[Greg KH]

On Sat, Mar 14, 2009 at 08:05:39PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> Subject		: usb bluetooth crashes system
> Submitter	: Pavel Machek <pavel@ucw.cz>
> Date		: 2009-03-10 11:23 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

I think we need some more information here.

Pavel?

Re: [Bug #12871] usb bluetooth crashes system

[Greg KH]

On Sat, Mar 14, 2009 at 08:05:39PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
> Subject		: usb bluetooth crashes system
> Submitter	: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
> Date		: 2009-03-10 11:23 (5 days old)
> References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4

I think we need some more information here.

Pavel?

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Sun, Mar 15, 2009 at 08:27:08AM +0800, Linus Torvalds wrote:
> 
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.

I second that.

1) The _real_ dirty threshold used to be large.
2) It is a _real_ regression. It impacts real user experiences.

So when introducing Nick's correct-dirty-accounting patch, we'd better
increase the dirty thresholds correspondingly.

> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

Maybe tomorrow. Ling Ming?

In general we should not cater the thresholds for one specific workload.
But this is a case of _regression_, and it would be better to raise the
bars above it.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Sun, Mar 15, 2009 at 08:27:08AM +0800, Linus Torvalds wrote:
> 
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.

I second that.

1) The _real_ dirty threshold used to be large.
2) It is a _real_ regression. It impacts real user experiences.

So when introducing Nick's correct-dirty-accounting patch, we'd better
increase the dirty thresholds correspondingly.

> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

Maybe tomorrow. Ling Ming?

In general we should not cater the thresholds for one specific workload.
But this is a case of _regression_, and it would be better to raise the
bars above it.

Thanks,
Fengguang

Re: [Bug #12792] 2.6.29-rc6-git4 boot failure

[Sachin Sant]

Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
> Subject		: 2.6.29-rc6-git4 boot failure
> Submitter	: Sachin P. Sant <sachinp@in.ibm.com>
> Date		: 2009-02-27 23:19 (16 days old)
> References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html
>   
I can still recreate this with 2.6.29-rc8-git1. Same trace and same
point of failure.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

Re: [Bug #12444] X hangs following switch from radeonfb console - Bisected

[Graham Murray]

I am no longer seeing this problem with 2.6.29-rc8-00090g326d851, but I
have also upgrade various parts of X including the radeon driver to
version 6.12.0. 

> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12444
> Subject		: X hangs following switch from radeonfb console - Bisected
> Submitter	: Graham Murray <graham@gmurray.org.uk>
> Date		: 2009-01-13 14:03 (61 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a

Re: [Bug #12806] i915 broken STR

[Rafael J. Wysocki]

On Sunday 15 March 2009, Harvey Harrison wrote:
> On Sat, 2009-03-14 at 20:05 +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
> > Subject		: i915 broken STR
> > Submitter	: Harvey Harrison <harvey.harrison@gmail.com>
> > Date		: 2009-02-28 4:20 (15 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
> > References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4
> > 
> > 
> 
> You can close this, turns out KMS got enabled in my config and userspace
> was too old to cope.

Thanks, closed.

Rafael

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Rafael J. Wysocki]

On Sunday 15 March 2009, Jeff Chua wrote:
> On Sun, Mar 15, 2009 at 10:58 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> > On Sun, Mar 15, 2009 at 3:01 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12414
> >> Subject         : iwl4965 cannot use "ap auto" on latest 2.6.28/29?
> >> Submitter       : Jeff Chua <jeff.chua.linux@gmail.com>
> >> Date            : 2009-01-05 4:13 (69 days old)
> >> References      : http://marc.info/?l=linux-kernel&m=123112882127823&w=4
> >
> > Still not working in linux-2.6.29-rc8. Broken after the commit below.
> > There were many changes to wireless after this commit, and simply
> > reverting this commit will break compiling.
> >
> > Jeff.
> >
> >
> >
> > commit 41bb73eeac5ff5fb217257ba33b654747b3abf11
> > Author: Johannes Berg <johannes@sipsolutions.net>
> > Date:   Wed Oct 29 01:09:37 2008 +0100
> >
> >    mac80211: remove SSID driver code
> >
> 
> The commit below is causing problem with associating with the hidden AP as well.
> 
> Thanks,
> Jeff.
> 
> 
> 71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
> commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> Author: Johannes Berg <johannes@sipsolutions.net>
> Date:   Tue Oct 28 18:29:48 2008 +0100
> 
>     b43/legacy: remove SSID code
> 
>     The SSID programmed into the device is used by the ucode only
>     to reply to probe requests, a functionality we disable anyway
>     because it doesn't fit with the mac80211/hostapd programming
>     model. Therefore, it isn't useful to program the SSID into
>     device.
> 
>     Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
>     Signed-off-by: John W. Linville <linville@tuxdriver.com>

Thanks for the update.

Rafael

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Rafael J. Wysocki]

On Sunday 15 March 2009, Jeff Chua wrote:
> On Sun, Mar 15, 2009 at 10:58 AM, Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > On Sun, Mar 15, 2009 at 3:01 AM, Rafael J. Wysocki <rjw-KKrjLPT3xs0@public.gmane.org> wrote:
> >> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12414
> >> Subject         : iwl4965 cannot use "ap auto" on latest 2.6.28/29?
> >> Submitter       : Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> Date            : 2009-01-05 4:13 (69 days old)
> >> References      : http://marc.info/?l=linux-kernel&m=123112882127823&w=4
> >
> > Still not working in linux-2.6.29-rc8. Broken after the commit below.
> > There were many changes to wireless after this commit, and simply
> > reverting this commit will break compiling.
> >
> > Jeff.
> >
> >
> >
> > commit 41bb73eeac5ff5fb217257ba33b654747b3abf11
> > Author: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> > Date:   Wed Oct 29 01:09:37 2008 +0100
> >
> >    mac80211: remove SSID driver code
> >
> 
> The commit below is causing problem with associating with the hidden AP as well.
> 
> Thanks,
> Jeff.
> 
> 
> 71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
> commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> Author: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> Date:   Tue Oct 28 18:29:48 2008 +0100
> 
>     b43/legacy: remove SSID code
> 
>     The SSID programmed into the device is used by the ucode only
>     to reply to probe requests, a functionality we disable anyway
>     because it doesn't fit with the mac80211/hostapd programming
>     model. Therefore, it isn't useful to program the SSID into
>     device.
> 
>     Signed-off-by: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
>     Signed-off-by: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

Thanks for the update.

Rafael

Re: [Bug #12444] X hangs following switch from radeonfb console - Bisected

[Rafael J. Wysocki]

On Sunday 15 March 2009, Graham Murray wrote:
> I am no longer seeing this problem with 2.6.29-rc8-00090g326d851, but I
> have also upgrade various parts of X including the radeon driver to
> version 6.12.0. 

This is a code fix anyway, closing. :-)

> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12444
> > Subject		: X hangs following switch from radeonfb console - Bisected
> > Submitter	: Graham Murray <graham@gmurray.org.uk>
> > Date		: 2009-01-13 14:03 (61 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a

Thanks,
Rafael

Re: [Bug #12792] 2.6.29-rc6-git4 boot failure

[Rafael J. Wysocki]

On Sunday 15 March 2009, Sachin Sant wrote:
> Rafael J. Wysocki wrote:
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
> > Subject		: 2.6.29-rc6-git4 boot failure
> > Submitter	: Sachin P. Sant <sachinp@in.ibm.com>
> > Date		: 2009-02-27 23:19 (16 days old)
> > References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html
> >   
> I can still recreate this with 2.6.29-rc8-git1. Same trace and same
> point of failure.

Thanks for the update.

Rafael

Re: [Bug #12792] 2.6.29-rc6-git4 boot failure

[Sachin Sant]

Rafael J. Wysocki wrote:
>> I can still recreate this with 2.6.29-rc8-git1. Same trace and same
>> point of failure.
>>     
This problem seems to have been introduced somewhere during 2.6.28 git3/git4.
I can boot 2.6.28-git2 successfully on this box. Could not confirm with git3
as it had kernel build failure issues. git4 kernel failed to boot with same
backtrace as reported. 

Will try to further narrow down this issue.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

On Sun, 2009-03-15 at 11:06 +0800, Jeff Chua wrote:

> The commit below is causing problem with associating with the hidden AP as well.

> 71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
> commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> Author: Johannes Berg <johannes@sipsolutions.net>
> Date:   Tue Oct 28 18:29:48 2008 +0100
> 
>     b43/legacy: remove SSID code
> 
>     The SSID programmed into the device is used by the ucode only
>     to reply to probe requests, a functionality we disable anyway
>     because it doesn't fit with the mac80211/hostapd programming
>     model. Therefore, it isn't useful to program the SSID into
>     device.

That's not believable, sorry. I know exactly what the microcode uses the
SSID here for, and it never uses it when we're in station mode.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

On Sun, 2009-03-15 at 11:06 +0800, Jeff Chua wrote:

> The commit below is causing problem with associating with the hidden AP as well.

> 71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
> commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> Author: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> Date:   Tue Oct 28 18:29:48 2008 +0100
> 
>     b43/legacy: remove SSID code
> 
>     The SSID programmed into the device is used by the ucode only
>     to reply to probe requests, a functionality we disable anyway
>     because it doesn't fit with the mac80211/hostapd programming
>     model. Therefore, it isn't useful to program the SSID into
>     device.

That's not believable, sorry. I know exactly what the microcode uses the
SSID here for, and it never uses it when we're in station mode.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Linus Torvalds]

On Sun, 15 Mar 2009, Johannes Berg wrote:

> On Sun, 2009-03-15 at 11:06 +0800, Jeff Chua wrote:
> 
> > The commit below is causing problem with associating with the hidden AP as well.
> 
> > 71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
> > commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> > Author: Johannes Berg <johannes@sipsolutions.net>
> > Date:   Tue Oct 28 18:29:48 2008 +0100
> > 
> >     b43/legacy: remove SSID code
> > 
> >     The SSID programmed into the device is used by the ucode only
> >     to reply to probe requests, a functionality we disable anyway
> >     because it doesn't fit with the mac80211/hostapd programming
> >     model. Therefore, it isn't useful to program the SSID into
> >     device.
> 
> That's not believable, sorry. I know exactly what the microcode uses the
> SSID here for, and it never uses it when we're in station mode.

Jeff - can you test the kernels before-and-after this commit (with _no_ 
other changes) and descibe the differences?

Johannes - "not believable" is simply not an argument. If Jeff can show a 
difference, then your disbelief is totally irrelevant, and clearly shows 
that you are basing your beliefs on incorrect assumptions (like some 
specific version of firmware that isn't the whole story).

		Linus

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Linus Torvalds]

On Sun, 15 Mar 2009, Johannes Berg wrote:

> On Sun, 2009-03-15 at 11:06 +0800, Jeff Chua wrote:
> 
> > The commit below is causing problem with associating with the hidden AP as well.
> 
> > 71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
> > commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> > Author: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
> > Date:   Tue Oct 28 18:29:48 2008 +0100
> > 
> >     b43/legacy: remove SSID code
> > 
> >     The SSID programmed into the device is used by the ucode only
> >     to reply to probe requests, a functionality we disable anyway
> >     because it doesn't fit with the mac80211/hostapd programming
> >     model. Therefore, it isn't useful to program the SSID into
> >     device.
> 
> That's not believable, sorry. I know exactly what the microcode uses the
> SSID here for, and it never uses it when we're in station mode.

Jeff - can you test the kernels before-and-after this commit (with _no_ 
other changes) and descibe the differences?

Johannes - "not believable" is simply not an argument. If Jeff can show a 
difference, then your disbelief is totally irrelevant, and clearly shows 
that you are basing your beliefs on incorrect assumptions (like some 
specific version of firmware that isn't the whole story).

		Linus

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On Sun, 2009-03-15 at 11:44 -0700, Linus Torvalds wrote:

> Johannes - "not believable" is simply not an argument. If Jeff can show a 
> difference, then your disbelief is totally irrelevant, and clearly shows 
> that you are basing your beliefs on incorrect assumptions (like some 
> specific version of firmware that isn't the whole story).

Linus, Jeff is totally unbelievable here -- I just realised that the
commit he quotes doesn't even change the driver he's working with.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On Sun, 2009-03-15 at 11:44 -0700, Linus Torvalds wrote:

> Johannes - "not believable" is simply not an argument. If Jeff can show a 
> difference, then your disbelief is totally irrelevant, and clearly shows 
> that you are basing your beliefs on incorrect assumptions (like some 
> specific version of firmware that isn't the whole story).

Linus, Jeff is totally unbelievable here -- I just realised that the
commit he quotes doesn't even change the driver he's working with.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Ingo Molnar]

* Johannes Berg <johannes@sipsolutions.net> wrote:

> On Sun, 2009-03-15 at 11:44 -0700, Linus Torvalds wrote:
> 
> > Johannes - "not believable" is simply not an argument. If 
> > Jeff can show a difference, then your disbelief is totally 
> > irrelevant, and clearly shows that you are basing your 
> > beliefs on incorrect assumptions (like some specific version 
> > of firmware that isn't the whole story).
> 
> Linus, Jeff is totally unbelievable here -- I just realised 
> that the commit he quotes doesn't even change the driver he's 
> working with.

Even if so (bisection is very hard and error-prone) why do you 
shape your reaction to it as a personal attack? Why do you say 
"Jeff is totally unbelievable" - why dont you say something more 
amicable like:

 " Hm, that's weird - that commit does not even seem to affect 
   the driver you are working with. Could you please re-check 
   the final bits of the bisection to make sure you got the 
   right commit ID? "

Instead of this irritated-sounding attack tone you are using. 
It's not helpful. Testers are there to help you, not to annoy 
you. If they annoy you then you are in the wrong business.

	Ingo

Re: [Bug #12574] possible circular locking dependency detected

[Michael S. Tsirkin]

On Sat, Mar 14, 2009 at 08:05:29PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
> Subject		: possible circular locking dependency detected
> Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
> Date		: 2009-01-29 11:35 (45 days old)
> References	: http://lkml.org/lkml/2009/2/9/205
> 

It's still there in rc8.

Re: [Bug #12574] possible circular locking dependency detected

[Michael S. Tsirkin]

On Sat, Mar 14, 2009 at 08:05:29PM +0100, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
> Subject		: possible circular locking dependency detected
> Submitter	: Michael S. Tsirkin <m.s.tsirkin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Date		: 2009-01-29 11:35 (45 days old)
> References	: http://lkml.org/lkml/2009/2/9/205
> 

It's still there in rc8.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Zhang Rui]

On Sun, 2009-03-15 at 03:01 +0800, Rafael J. Wysocki wrote:
> This message contains a list of some regressions from 2.6.28, for which there
> are no fixes in the mainline I know of.  If any of them have been fixed already,
> please let me know.
> 
> If you know of any other unresolved regressions from 2.6.28, please let me know
> either and I'll add them to the list.  Also, please let me know if any of the
> entries below are invalid.
> 
> Each entry from the list will be sent additionally in an automatic reply to
> this message with CCs to the people involved in reporting and handling the
> issue.
> 
> 
> Listed regressions statistics:
> 
>   Date          Total  Pending  Unresolved
>   ----------------------------------------
>   2009-03-14      124       36          32
>   2009-03-03      108       33          28
>   2009-02-24       95       32          24
>   2009-02-14       85       33          27
>   2009-02-08       82       45          36
>   2009-02-04       66       51          39
>   2009-01-20       38       35          27
>   2009-01-11       13       13          10
> 
> 
> Unresolved regressions
> ----------------------

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12831
> Subject         : Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
> Submitter       : Matthew <pyther@pyther.net>
> Date            : 2009-03-07 10:05 (8 days old)

patch is available at
http://bugzilla.kernel.org/show_bug.cgi?id=12831#c11

thanks,
rui

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Zhang Rui]

On Sun, 2009-03-15 at 03:01 +0800, Rafael J. Wysocki wrote:
> This message contains a list of some regressions from 2.6.28, for which there
> are no fixes in the mainline I know of.  If any of them have been fixed already,
> please let me know.
> 
> If you know of any other unresolved regressions from 2.6.28, please let me know
> either and I'll add them to the list.  Also, please let me know if any of the
> entries below are invalid.
> 
> Each entry from the list will be sent additionally in an automatic reply to
> this message with CCs to the people involved in reporting and handling the
> issue.
> 
> 
> Listed regressions statistics:
> 
>   Date          Total  Pending  Unresolved
>   ----------------------------------------
>   2009-03-14      124       36          32
>   2009-03-03      108       33          28
>   2009-02-24       95       32          24
>   2009-02-14       85       33          27
>   2009-02-08       82       45          36
>   2009-02-04       66       51          39
>   2009-01-20       38       35          27
>   2009-01-11       13       13          10
> 
> 
> Unresolved regressions
> ----------------------

> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=12831
> Subject         : Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
> Submitter       : Matthew <pyther@pyther.net>
> Date            : 2009-03-07 10:05 (8 days old)

patch is available at
http://bugzilla.kernel.org/show_bug.cgi?id=12831#c11

thanks,
rui

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Lin Ming]

On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.
> 
> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

echo 10 > /proc/sys/vm/dirty_background_ratio
echo 20 > /proc/sys/vm/dirty_ratio

It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
machine(8G mem).

Lin Ming

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Lin Ming]

On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> 
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > Subject		: iozone regression with 2.6.29-rc6
> > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > Date		: 2009-02-27 9:13 (16 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> 
> I suspect that I should just raise the default dirty limits. Wu reported 
> that it fixed the regression, and while he picked some rather high 
> percentages, I think we could certainly raise the rather aggressive 
> default ones. 
> 
> After all, those default percentages were picked (a) with the old dirty 
> logic and (b) largely at random and (c) designed to be aggressive. In 
> particular, that (a) means that having fixed some of the dirty accounting, 
> maybe the real bug is now that it was always too aggressive, just hidden 
> by an accounting issue.
> 
> If we raised the default ratio from 5/10 to 10/20, what happens to the 
> iozone regression?

echo 10 > /proc/sys/vm/dirty_background_ratio
echo 20 > /proc/sys/vm/dirty_ratio

It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
machine(8G mem).

Lin Ming

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Mon, Mar 16, 2009 at 01:03:42PM +0800, Lin, Ming wrote:
> On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> > 
> > On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > Subject		: iozone regression with 2.6.29-rc6
> > > Submitter	: Lin Ming <ming.m.lin@intel.com>
> > > Date		: 2009-02-27 9:13 (16 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > Handled-By	: Wu Fengguang <fengguang.wu@intel.com>
> > 
> > I suspect that I should just raise the default dirty limits. Wu reported 
> > that it fixed the regression, and while he picked some rather high 
> > percentages, I think we could certainly raise the rather aggressive 
> > default ones. 
> > 
> > After all, those default percentages were picked (a) with the old dirty 
> > logic and (b) largely at random and (c) designed to be aggressive. In 
> > particular, that (a) means that having fixed some of the dirty accounting, 
> > maybe the real bug is now that it was always too aggressive, just hidden 
> > by an accounting issue.
> > 
> > If we raised the default ratio from 5/10 to 10/20, what happens to the 
> > iozone regression?
> 
> echo 10 > /proc/sys/vm/dirty_background_ratio
> echo 20 > /proc/sys/vm/dirty_ratio
> 
> It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
> machine(8G mem).

A quick&coarse calculation: 8G * 15% = 1200M.
This means an iozone process dirtying 1200M data won't be write-blocked.

So the thresholds of 10/20 are just about enough for fixing this regression.

Thanks,
Fengguang

Re: [Bug #12809] iozone regression with 2.6.29-rc6

[Wu Fengguang]

On Mon, Mar 16, 2009 at 01:03:42PM +0800, Lin, Ming wrote:
> On Sun, 2009-03-15 at 08:27 +0800, Linus Torvalds wrote:
> > 
> > On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > > 
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.28.  Please verify if it still should be listed and let me know
> > > (either way).
> > > 
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
> > > Subject		: iozone regression with 2.6.29-rc6
> > > Submitter	: Lin Ming <ming.m.lin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > > Date		: 2009-02-27 9:13 (16 days old)
> > > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
> > > References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
> > > Handled-By	: Wu Fengguang <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> > 
> > I suspect that I should just raise the default dirty limits. Wu reported 
> > that it fixed the regression, and while he picked some rather high 
> > percentages, I think we could certainly raise the rather aggressive 
> > default ones. 
> > 
> > After all, those default percentages were picked (a) with the old dirty 
> > logic and (b) largely at random and (c) designed to be aggressive. In 
> > particular, that (a) means that having fixed some of the dirty accounting, 
> > maybe the real bug is now that it was always too aggressive, just hidden 
> > by an accounting issue.
> > 
> > If we raised the default ratio from 5/10 to 10/20, what happens to the 
> > iozone regression?
> 
> echo 10 > /proc/sys/vm/dirty_background_ratio
> echo 20 > /proc/sys/vm/dirty_ratio
> 
> It fixed the regression of iozone (filesize 1200M) on 4P dual-core HT
> machine(8G mem).

A quick&coarse calculation: 8G * 15% = 1200M.
This means an iozone process dirtying 1200M data won't be write-blocked.

So the thresholds of 10/20 are just about enough for fixing this regression.

Thanks,
Fengguang

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

[-- Attachment #1: Type: text/plain, Size: 4430 bytes --]

On Mon, Mar 16, 2009 at 4:26 AM, Ingo Molnar <mingo@elte.hu> wrote:
> * Johannes Berg <johannes@sipsolutions.net> wrote:
>> that the commit he quotes doesn't even change the driver he's
>> working with.

Here's what I did, and it's repeatable.

Take the attached bisect log and replay it, and the last offending
commit is this ...
# git log
commit 71c11fb57b924c160297ccd9e1761db598d00ac2
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Tue Oct 28 18:29:48 2008 +0100

    b43/legacy: remove SSID code

Yes, this is not the real problem, but it's the last commit that cause
the problem, and I couldn't bisect further, typing the next "git
bisect bad" and the commit is

# git bisect bad
71c11fb57b924c160297ccd9e1761db598d00ac2 is first bad commit
commit 71c11fb57b924c160297ccd9e1761db598d00ac2
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Tue Oct 28 18:29:48 2008 +0100

    b43/legacy: remove SSID code


Johannes, Ok, this is not the commit causing the problem, but anything
after this commit doesn't associate with my hidden APs. I may not have
run over every single commits since, but 2.6.29-rc8 is definitely not
associating at all automatically -- only manually by specifying the
AP.

This bug is quite hard to trigger, and it doesn't shows easily in
2.6.28-rc3. May be once every 10 times you tried.



# git reset --hard 71c11fb57b924c160297ccd9e1761db598d00ac2

I've tried on two different Linksys's AP. Association with WAG354G  is
better than with WAG200G ... meaning it's harder to get association
failure on 2.6.28-rc3. 1/10 fail on WAG354G, and 9/10 fails on
WAG200G.

Here's how I associate with the AP.

# modprobe -r iwlagn
# modprobe iwlagn
# iwconfig wlan0 mode Managed
# ifconfig wlan0 up
# iwconfig wlan0 essid "myessid"
# iwconfig wlan0 key restricted "hex key"
# iwconfig wlan0 ap auto channel auto
# ... wait for association
# ping -c 3 <IP of the AP>
# shutdown the interface
# ifconfig wlan0 down
# modprobe -r iwlagn


Repeat these and it'll fail to associate. On WAG200G, can't associate
after 2nd attempt.


Next revert these two commits

commit 4607816f608b42a5379aca97ceed08378804c99f
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Tue Oct 28 18:25:43 2008 +0100

    iwlwifi: remove unused essid variable

commit a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Tue Oct 28 18:21:05 2008 +0100

    iwlwifi: remove implicit direct scan


With these patches reverted, associating with the APs are always
successful 10 out of 10 times with the same steps as above.

I've even used the bad modules and when it failed, I can associate
again with the patched module. Same 2.6.28-rc3 kernel.


Here's part of the dmesg
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
        (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:03:00.0: setting latency timer to 64
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels
iwlagn 0000:03:00.0: PCI INT A disabled
wmaster0 (iwlagn): not using net_device_ops yet
phy0: Selected rate control algorithm 'iwl-agn-rs'
wlan0 (iwlagn): not using net_device_ops yet
iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:03:00.0: restoring config space at offset 0x1 (was
0x100102, writing 0
x100106)
iwlagn 0000:03:00.0: irq 28 for MSI/MSI-X
iwlagn 0000:03:00.0: firmware: requesting iwlwifi-4965-2.ucode
iwlagn loaded firmware version 228.57.2.23
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
iwlagn: TX Power requested while scanning!

Anything I can help to debug further, just let me know.

Thanks,
Jeff.

[-- Attachment #2: bisect.log --]
[-- Type: application/octet-stream, Size: 2095 bytes --]

git bisect start
# bad: [0191b625ca5a46206d2fb862bb08f36f2fcb3b31] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6
git bisect bad 0191b625ca5a46206d2fb862bb08f36f2fcb3b31
# good: [1d248b2593e92db6c51ca07235985a95c625a93f] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband
git bisect good 1d248b2593e92db6c51ca07235985a95c625a93f
# bad: [7d359daafe12b36b6da7ec6247caddf534183aed] apne: convert to net_device_ops
git bisect bad 7d359daafe12b36b6da7ec6247caddf534183aed
# bad: [0a888fd1f6320d1d9318c58de9bca3cef41546d6] virtio_net: Recycle some more rx buffer pages
git bisect bad 0a888fd1f6320d1d9318c58de9bca3cef41546d6
# good: [c354e1246348e25c714e6b2973f3257183d06e2c] net: clean up net/ipv4/ipmr.c
git bisect good c354e1246348e25c714e6b2973f3257183d06e2c
# good: [f21f237cf55494c3a4209de323281a3b0528da10] Merge branch 'timers-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
git bisect good f21f237cf55494c3a4209de323281a3b0528da10
# bad: [05a1e2d111c98340fb17ec702cf09450eec3a947] ath9k: Enable interrupts at the proper place
git bisect bad 05a1e2d111c98340fb17ec702cf09450eec3a947
# good: [4bab0ea1d42dd1927af9df6fbf0003fc00617c50] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6
git bisect good 4bab0ea1d42dd1927af9df6fbf0003fc00617c50
# good: [0a95f56323ce93dac354c1b2d54bf959a985cf7d] sfc: Clean up non-volatile memory partitioning
git bisect good 0a95f56323ce93dac354c1b2d54bf959a985cf7d
# good: [1239cd58d237fa6ad501acaec8776262a5784ec8] wireless: move mesh config length constant
git bisect good 1239cd58d237fa6ad501acaec8776262a5784ec8
# bad: [17683c65c8a5f3f29f5408334992986b996d8205] ath5k: fix keytable type buglet in ath5k_hw_reset_key
git bisect bad 17683c65c8a5f3f29f5408334992986b996d8205
# bad: [71c11fb57b924c160297ccd9e1761db598d00ac2] b43/legacy: remove SSID code
git bisect bad 71c11fb57b924c160297ccd9e1761db598d00ac2
# good: [430cfe95a401baa0dc2022deaad02cb75d63c73c] iwl3945: remove dead code
git bisect good 430cfe95a401baa0dc2022deaad02cb75d63c73c

Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up

[Sitsofe Wheeler]

On Sat, Mar 14, 2009 at 08:05:32PM +0100, Rafael J. Wysocki wrote:
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
> Subject		: i915 VT switch with AIGLX causes X lock up
> Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
> Date		: 2009-02-21 15:38 (22 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
> References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4

Still here in 2.6.29-rc8.

-- 
Sitsofe | http://sucs.org/~sits/

Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up

[Sitsofe Wheeler]

On Sat, Mar 14, 2009 at 08:05:32PM +0100, Rafael J. Wysocki wrote:
> 
> The following bug entry is on the current list of known regressions
> from 2.6.28.  Please verify if it still should be listed and let me know
> (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
> Subject		: i915 VT switch with AIGLX causes X lock up
> Submitter	: Sitsofe Wheeler <sitsofe-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> Date		: 2009-02-21 15:38 (22 days old)
> First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
> References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4

Still here in 2.6.29-rc8.

-- 
Sitsofe | http://sucs.org/~sits/

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Linus Torvalds]

On Mon, 16 Mar 2009, Jeff Chua wrote:
> 
> Take the attached bisect log and replay it

Taking a bisect log is repeatable, but pointless.

If you made any mistakes in bisecting (marking a kernel that was good as 
being bad, or the other way around), the log will always replay to the 
same thing, but it will still be wrong.

In other words, "git bisect" is only as reliable as the data you feed it, 
and if the behavior isn't 100% repeatable and unambiguous (or if you 
simply made a mistake), you need to double-check things.

So after bisecting a commit, if there is any question what-so-ever whether 
the commit makes sense as a result, you need to double-check it. The best 
way to double-check it is to go back to a known-bad state (preferably the 
tip of the branch) and revert the presumed-bad commit, and verify that it 
really fixes the behavior.

But if that is impossible (for example, because the commit no longer 
reverts cleanly), at least make 100% sure that the state at the commit is 
bad, and then go to (all) parents of that commit and make 100% sure that 
the state at those points is _good_. 

IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as 
being bad, then you should go back and double-check that its parent 
(in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.

Because if it's parent is also bad, then that just means that you made 
some mistake in "git bisect".

The thing about bisecting is that it is _extremely_ efficient. It takes 
essentially the minimal number of answers to get to the end result. But 
that very efficiency also means that getting even just _one_ of those 
answers wrong will take you _way_ off base. There's no room for error, 
because bisect will take each bit and use it to maximally split the error 
space.

In this case, it really sounds like maybe you marked the parent good, even 
though you should have marked it bad.

			Linus

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Hugh Dickins]

On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> Subject		: 2.6.29-rc "TKIP: replay detected" regression
> Submitter	: Hugh Dickins <hugh@veritas.com>
> Date		: 2009-03-11 12:07 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> Handled-By	: John W. Linville <linville@tuxdriver.com>

Yes, it should still be listed, but could go into the "with patches"
section: there's a good patch from John in linux-next, which I expect
he'll get Linus to pull in due course.

Hugh

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Hugh Dickins]

On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> Subject		: 2.6.29-rc "TKIP: replay detected" regression
> Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
> Date		: 2009-03-11 12:07 (4 days old)
> References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> Handled-By	: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

Yes, it should still be listed, but could go into the "with patches"
section: there's a good patch from John in linux-next, which I expect
he'll get Linus to pull in due course.

Hugh

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Rafael J. Wysocki]

On Monday 16 March 2009, Hugh Dickins wrote:
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> > Subject		: 2.6.29-rc "TKIP: replay detected" regression
> > Submitter	: Hugh Dickins <hugh@veritas.com>
> > Date		: 2009-03-11 12:07 (4 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> > Handled-By	: John W. Linville <linville@tuxdriver.com>
> 
> Yes, it should still be listed, but could go into the "with patches"
> section: there's a good patch from John in linux-next, which I expect
> he'll get Linus to pull in due course.

Well, I need a pointer to the patch please.  John?

Rafael

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[Rafael J. Wysocki]

On Monday 16 March 2009, Hugh Dickins wrote:
> On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> > Subject		: 2.6.29-rc "TKIP: replay detected" regression
> > Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
> > Date		: 2009-03-11 12:07 (4 days old)
> > References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> > Handled-By	: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> 
> Yes, it should still be listed, but could go into the "with patches"
> section: there's a good patch from John in linux-next, which I expect
> he'll get Linus to pull in due course.

Well, I need a pointer to the patch please.  John?

Rafael

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:

> IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> being bad, then you should go back and double-check that its parent
> (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> Because if it's parent is also bad, then that just means that you made
> some mistake in "git bisect".
> In this case, it really sounds like maybe you marked the parent good, even
> though you should have marked it bad.

I should have been more careful, just got thrown off during the last
few steps of the bisect. But with the bad association to the AP after
a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
direct scan), can someone suggest where to go from here?

Meanwhile, I'll try bisecting again.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:

> IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> being bad, then you should go back and double-check that its parent
> (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> Because if it's parent is also bad, then that just means that you made
> some mistake in "git bisect".
> In this case, it really sounds like maybe you marked the parent good, even
> though you should have marked it bad.

I should have been more careful, just got thrown off during the last
few steps of the bisect. But with the bad association to the AP after
a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
direct scan), can someone suggest where to go from here?

Meanwhile, I'll try bisecting again.

Thanks,
Jeff.

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[John W. Linville]

On Mon, Mar 16, 2009 at 10:57:06PM +0100, Rafael J. Wysocki wrote:
> On Monday 16 March 2009, Hugh Dickins wrote:
> > On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> > > Subject		: 2.6.29-rc "TKIP: replay detected" regression
> > > Submitter	: Hugh Dickins <hugh@veritas.com>
> > > Date		: 2009-03-11 12:07 (4 days old)
> > > References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> > > Handled-By	: John W. Linville <linville@tuxdriver.com>
> > 
> > Yes, it should still be listed, but could go into the "with patches"
> > section: there's a good patch from John in linux-next, which I expect
> > he'll get Linus to pull in due course.
> 
> Well, I need a pointer to the patch please.  John?

http://marc.info/?l=linux-wireless&m=123678463704691&w=2

Just sent a pull request through Dave...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: [Bug #12870] 2.6.29-rc "TKIP: replay detected" regression

[John W. Linville]

On Mon, Mar 16, 2009 at 10:57:06PM +0100, Rafael J. Wysocki wrote:
> On Monday 16 March 2009, Hugh Dickins wrote:
> > On Sat, 14 Mar 2009, Rafael J. Wysocki wrote:
> > > 
> > > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
> > > Subject		: 2.6.29-rc "TKIP: replay detected" regression
> > > Submitter	: Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>
> > > Date		: 2009-03-11 12:07 (4 days old)
> > > References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
> > > Handled-By	: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> > 
> > Yes, it should still be listed, but could go into the "with patches"
> > section: there's a good patch from John in linux-next, which I expect
> > he'll get Linus to pull in due course.
> 
> Well, I need a pointer to the patch please.  John?

http://marc.info/?l=linux-wireless&m=123678463704691&w=2

Just sent a pull request through Dave...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]

On Tue, 2009-03-17 at 07:55 +0800, Jeff Chua wrote:

> > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > being bad, then you should go back and double-check that its parent
> > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > Because if it's parent is also bad, then that just means that you made
> > some mistake in "git bisect".
> > In this case, it really sounds like maybe you marked the parent good, even
> > though you should have marked it bad.
> 
> I should have been more careful, just got thrown off during the last
> few steps of the bisect. But with the bad association to the AP after
> a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> direct scan), can someone suggest where to go from here?

That actually makes some sense, though I'm convinced the code I removed
there is actually wrong that doesn't mean it couldn't have had positive
side effects too. I'll take a look at it, in the meantime your time
would be better spent trying to capture what's going on on the air
instead of bisecting again.

If you don't have a second device to monitor, you can also create a
monitor interface as such:
	iw dev wlan0 interface add moni0 type monitor flags none

and run tcpdump on the resulting 'moni0' interface while you try to
associate etc. Write the packets to files and send them to me.

Due to this implicit scan modification in the driver that I removed,
however, I won't see scans in that file, so it won't be all that useful,
a capture made on a second device would be much better.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]

On Tue, 2009-03-17 at 07:55 +0800, Jeff Chua wrote:

> > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > being bad, then you should go back and double-check that its parent
> > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > Because if it's parent is also bad, then that just means that you made
> > some mistake in "git bisect".
> > In this case, it really sounds like maybe you marked the parent good, even
> > though you should have marked it bad.
> 
> I should have been more careful, just got thrown off during the last
> few steps of the bisect. But with the bad association to the AP after
> a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> direct scan), can someone suggest where to go from here?

That actually makes some sense, though I'm convinced the code I removed
there is actually wrong that doesn't mean it couldn't have had positive
side effects too. I'll take a look at it, in the meantime your time
would be better spent trying to capture what's going on on the air
instead of bisecting again.

If you don't have a second device to monitor, you can also create a
monitor interface as such:
	iw dev wlan0 interface add moni0 type monitor flags none

and run tcpdump on the resulting 'moni0' interface while you try to
associate etc. Write the packets to files and send them to me.

Due to this implicit scan modification in the driver that I removed,
however, I won't see scans in that file, so it won't be all that useful,
a capture made on a second device would be much better.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> 
> > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > being bad, then you should go back and double-check that its parent
> > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > Because if it's parent is also bad, then that just means that you made
> > some mistake in "git bisect".
> > In this case, it really sounds like maybe you marked the parent good, even
> > though you should have marked it bad.
> 
> I should have been more careful, just got thrown off during the last
> few steps of the bisect. But with the bad association to the AP after
> a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> direct scan), can someone suggest where to go from here?

The obvious question for me is did you try this?

	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9

Does that restore operation for you?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:
> 
> > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > being bad, then you should go back and double-check that its parent
> > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > Because if it's parent is also bad, then that just means that you made
> > some mistake in "git bisect".
> > In this case, it really sounds like maybe you marked the parent good, even
> > though you should have marked it bad.
> 
> I should have been more careful, just got thrown off during the last
> few steps of the bisect. But with the bad association to the AP after
> a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> direct scan), can someone suggest where to go from here?

The obvious question for me is did you try this?

	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9

Does that restore operation for you?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Tue, Mar 17, 2009 at 10:48:02AM -0400, John W. Linville wrote:
> On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> > On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > 
> > > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > > being bad, then you should go back and double-check that its parent
> > > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > > Because if it's parent is also bad, then that just means that you made
> > > some mistake in "git bisect".
> > > In this case, it really sounds like maybe you marked the parent good, even
> > > though you should have marked it bad.
> > 
> > I should have been more careful, just got thrown off during the last
> > few steps of the bisect. But with the bad association to the AP after
> > a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> > direct scan), can someone suggest where to go from here?
> 
> The obvious question for me is did you try this?
> 
> 	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9

Hmmm...more like this:

git revert 41bb73eeac5ff5fb217257ba33b654747b3abf11
git revert b23f99bcfa12c7b452f7ad201ea5921534d4e9ff
git revert 71c11fb57b924c160297ccd9e1761db598d00ac2
git revert 4607816f608b42a5379aca97ceed08378804c99f
git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
 
This first one has a conflict -- just take the hunk.

> Does that restore operation for you?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Tue, Mar 17, 2009 at 10:48:02AM -0400, John W. Linville wrote:
> On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> > On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> > <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:
> > 
> > > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > > being bad, then you should go back and double-check that its parent
> > > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > > Because if it's parent is also bad, then that just means that you made
> > > some mistake in "git bisect".
> > > In this case, it really sounds like maybe you marked the parent good, even
> > > though you should have marked it bad.
> > 
> > I should have been more careful, just got thrown off during the last
> > few steps of the bisect. But with the bad association to the AP after
> > a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> > direct scan), can someone suggest where to go from here?
> 
> The obvious question for me is did you try this?
> 
> 	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9

Hmmm...more like this:

git revert 41bb73eeac5ff5fb217257ba33b654747b3abf11
git revert b23f99bcfa12c7b452f7ad201ea5921534d4e9ff
git revert 71c11fb57b924c160297ccd9e1761db598d00ac2
git revert 4607816f608b42a5379aca97ceed08378804c99f
git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
 
This first one has a conflict -- just take the hunk.

> Does that restore operation for you?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Ingo Molnar]

* John W. Linville <linville@tuxdriver.com> wrote:

> On Tue, Mar 17, 2009 at 10:48:02AM -0400, John W. Linville wrote:
> > On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> > > On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> > > <torvalds@linux-foundation.org> wrote:
> > > 
> > > > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > > > being bad, then you should go back and double-check that its parent
> > > > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > > > Because if it's parent is also bad, then that just means that you made
> > > > some mistake in "git bisect".
> > > > In this case, it really sounds like maybe you marked the parent good, even
> > > > though you should have marked it bad.
> > > 
> > > I should have been more careful, just got thrown off during the last
> > > few steps of the bisect. But with the bad association to the AP after
> > > a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> > > direct scan), can someone suggest where to go from here?
> > 
> > The obvious question for me is did you try this?
> > 
> > 	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
> 
> Hmmm...more like this:
> 
> git revert 41bb73eeac5ff5fb217257ba33b654747b3abf11
> git revert b23f99bcfa12c7b452f7ad201ea5921534d4e9ff
> git revert 71c11fb57b924c160297ccd9e1761db598d00ac2
> git revert 4607816f608b42a5379aca97ceed08378804c99f
> git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
>  
> This first one has a conflict -- just take the hunk.

Since you apparently have done this sequence and have
resolved the conflict (which is hard to do for testers
even in trivial cases) - would you mind to post the
resulting combo patch for Jeff to test?

	Ingo

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Tue, Mar 17, 2009 at 04:39:24PM +0100, Ingo Molnar wrote:
> 
> * John W. Linville <linville@tuxdriver.com> wrote:
> 
> > On Tue, Mar 17, 2009 at 10:48:02AM -0400, John W. Linville wrote:
> > > On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> > > > On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> > > > <torvalds@linux-foundation.org> wrote:
> > > > 
> > > > > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > > > > being bad, then you should go back and double-check that its parent
> > > > > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > > > > Because if it's parent is also bad, then that just means that you made
> > > > > some mistake in "git bisect".
> > > > > In this case, it really sounds like maybe you marked the parent good, even
> > > > > though you should have marked it bad.
> > > > 
> > > > I should have been more careful, just got thrown off during the last
> > > > few steps of the bisect. But with the bad association to the AP after
> > > > a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> > > > direct scan), can someone suggest where to go from here?
> > > 
> > > The obvious question for me is did you try this?
> > > 
> > > 	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
> > 
> > Hmmm...more like this:
> > 
> > git revert 41bb73eeac5ff5fb217257ba33b654747b3abf11
> > git revert b23f99bcfa12c7b452f7ad201ea5921534d4e9ff
> > git revert 71c11fb57b924c160297ccd9e1761db598d00ac2
> > git revert 4607816f608b42a5379aca97ceed08378804c99f
> > git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
> >  
> > This first one has a conflict -- just take the hunk.
> 
> Since you apparently have done this sequence and have
> resolved the conflict (which is hard to do for testers
> even in trivial cases) - would you mind to post the
> resulting combo patch for Jeff to test?

Since Jeff has been using git for bisect, I presumed he could handle
the reverts.  But if you think it is helpful:

	http://bugzilla.kernel.org/attachment.cgi?id=20567&action=view

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Tue, Mar 17, 2009 at 04:39:24PM +0100, Ingo Molnar wrote:
> 
> * John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org> wrote:
> 
> > On Tue, Mar 17, 2009 at 10:48:02AM -0400, John W. Linville wrote:
> > > On Tue, Mar 17, 2009 at 07:55:49AM +0800, Jeff Chua wrote:
> > > > On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
> > > > <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:
> > > > 
> > > > > IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> > > > > being bad, then you should go back and double-check that its parent
> > > > > (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> > > > > Because if it's parent is also bad, then that just means that you made
> > > > > some mistake in "git bisect".
> > > > > In this case, it really sounds like maybe you marked the parent good, even
> > > > > though you should have marked it bad.
> > > > 
> > > > I should have been more careful, just got thrown off during the last
> > > > few steps of the bisect. But with the bad association to the AP after
> > > > a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
> > > > direct scan), can someone suggest where to go from here?
> > > 
> > > The obvious question for me is did you try this?
> > > 
> > > 	git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
> > 
> > Hmmm...more like this:
> > 
> > git revert 41bb73eeac5ff5fb217257ba33b654747b3abf11
> > git revert b23f99bcfa12c7b452f7ad201ea5921534d4e9ff
> > git revert 71c11fb57b924c160297ccd9e1761db598d00ac2
> > git revert 4607816f608b42a5379aca97ceed08378804c99f
> > git revert a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9
> >  
> > This first one has a conflict -- just take the hunk.
> 
> Since you apparently have done this sequence and have
> resolved the conflict (which is hard to do for testers
> even in trivial cases) - would you mind to post the
> resulting combo patch for Jeff to test?

Since Jeff has been using git for bisect, I presumed he could handle
the reverts.  But if you think it is helpful:

	http://bugzilla.kernel.org/attachment.cgi?id=20567&action=view

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Wed, Mar 18, 2009 at 12:05 AM, John W. Linville <linville@tuxdriver.com>
> the reverts.  But if you think it is helpful:
>        http://bugzilla.kernel.org/attachment.cgi?id=20567&action=view

I tried applying the above patch against the latest linux git
(18439c39e826191c0ef08c3a3271ce7ece46a860), but got a lot of rejects.
Is this supposed to be?


patch -p1 </tar/v2.6/revert-remove-ssid-knowledge-from-driver-series.patch
1 out of 1 hunk FAILED -- saving rejects to file
drivers/net/wireless/adm8211.h.rej
1 out of 2 hunks FAILED -- saving rejects to file
drivers/net/wireless/b43/main.c.rej
1 out of 2 hunks FAILED -- saving rejects to file
drivers/net/wireless/b43legacy/main.c.rej
1 out of 1 hunk FAILED -- saving rejects to file
drivers/net/wireless/iwlwifi/iwl-3945.h.rej
3 out of 4 hunks FAILED -- saving rejects to file
drivers/net/wireless/iwlwifi/iwl-agn.c.rej
1 out of 1 hunk FAILED -- saving rejects to file
drivers/net/wireless/iwlwifi/iwl-dev.h.rej
3 out of 5 hunks FAILED -- saving rejects to file
drivers/net/wireless/iwlwifi/iwl3945-base.c.rej
1 out of 3 hunks FAILED -- saving rejects to file include/net/mac80211.h.rej

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Wed, Mar 18, 2009 at 12:24:33AM +0800, Jeff Chua wrote:
> On Wed, Mar 18, 2009 at 12:05 AM, John W. Linville <linville@tuxdriver.com>
> > the reverts.  But if you think it is helpful:
> >        http://bugzilla.kernel.org/attachment.cgi?id=20567&action=view
> 
> I tried applying the above patch against the latest linux git
> (18439c39e826191c0ef08c3a3271ce7ece46a860), but got a lot of rejects.
> Is this supposed to be?
> 
> 
> patch -p1 </tar/v2.6/revert-remove-ssid-knowledge-from-driver-series.patch
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/net/wireless/adm8211.h.rej
> 1 out of 2 hunks FAILED -- saving rejects to file
> drivers/net/wireless/b43/main.c.rej
> 1 out of 2 hunks FAILED -- saving rejects to file
> drivers/net/wireless/b43legacy/main.c.rej
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl-3945.h.rej
> 3 out of 4 hunks FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl-agn.c.rej
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl-dev.h.rej
> 3 out of 5 hunks FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl3945-base.c.rej
> 1 out of 3 hunks FAILED -- saving rejects to file include/net/mac80211.h.rej

Works for me...I even re-downloaded the patch from bugzilla.

/home/linville/git/linux-2.6
[linville-t400.local]:> git show
commit 18439c39e826191c0ef08c3a3271ce7ece46a860
Merge: 9e8912e... b35f8ca...
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 17 08:59:33 2009 -0700

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm:
      dm crypt: wait for endio to complete before destruction
      dm crypt: fix kcryptd_async_done parameter
      dm io: respect BIO_MAX_PAGES limit
      dm table: rework reference counting fix
      dm ioctl: validate name length when renaming


/home/linville/git/linux-2.6
[linville-t400.local]:> patch -p1 < revert-remove-ssid-knowledge-from-driver-series.patch 
patching file drivers/net/wireless/adm8211.c
patching file drivers/net/wireless/adm8211.h
patching file drivers/net/wireless/b43/main.c
patching file drivers/net/wireless/b43legacy/main.c
patching file drivers/net/wireless/iwlwifi/iwl-3945.h
patching file drivers/net/wireless/iwlwifi/iwl-agn.c
patching file drivers/net/wireless/iwlwifi/iwl-dev.h
patching file drivers/net/wireless/iwlwifi/iwl-scan.c
patching file drivers/net/wireless/iwlwifi/iwl3945-base.c
patching file include/net/mac80211.h
patching file net/mac80211/ieee80211_i.h
patching file net/mac80211/main.c
patching file net/mac80211/mlme.c
patching file net/mac80211/wext.c

Perhaps you have a dirty tree?

	git checkout -f

Does that help?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Wed, Mar 18, 2009 at 12:24:33AM +0800, Jeff Chua wrote:
> On Wed, Mar 18, 2009 at 12:05 AM, John W. Linville <linville@tuxdriver.com>
> > the reverts.  But if you think it is helpful:
> >        http://bugzilla.kernel.org/attachment.cgi?id=20567&action=view
> 
> I tried applying the above patch against the latest linux git
> (18439c39e826191c0ef08c3a3271ce7ece46a860), but got a lot of rejects.
> Is this supposed to be?
> 
> 
> patch -p1 </tar/v2.6/revert-remove-ssid-knowledge-from-driver-series.patch
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/net/wireless/adm8211.h.rej
> 1 out of 2 hunks FAILED -- saving rejects to file
> drivers/net/wireless/b43/main.c.rej
> 1 out of 2 hunks FAILED -- saving rejects to file
> drivers/net/wireless/b43legacy/main.c.rej
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl-3945.h.rej
> 3 out of 4 hunks FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl-agn.c.rej
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl-dev.h.rej
> 3 out of 5 hunks FAILED -- saving rejects to file
> drivers/net/wireless/iwlwifi/iwl3945-base.c.rej
> 1 out of 3 hunks FAILED -- saving rejects to file include/net/mac80211.h.rej

Works for me...I even re-downloaded the patch from bugzilla.

/home/linville/git/linux-2.6
[linville-t400.local]:> git show
commit 18439c39e826191c0ef08c3a3271ce7ece46a860
Merge: 9e8912e... b35f8ca...
Author: Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Date:   Tue Mar 17 08:59:33 2009 -0700

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm:
      dm crypt: wait for endio to complete before destruction
      dm crypt: fix kcryptd_async_done parameter
      dm io: respect BIO_MAX_PAGES limit
      dm table: rework reference counting fix
      dm ioctl: validate name length when renaming


/home/linville/git/linux-2.6
[linville-t400.local]:> patch -p1 < revert-remove-ssid-knowledge-from-driver-series.patch 
patching file drivers/net/wireless/adm8211.c
patching file drivers/net/wireless/adm8211.h
patching file drivers/net/wireless/b43/main.c
patching file drivers/net/wireless/b43legacy/main.c
patching file drivers/net/wireless/iwlwifi/iwl-3945.h
patching file drivers/net/wireless/iwlwifi/iwl-agn.c
patching file drivers/net/wireless/iwlwifi/iwl-dev.h
patching file drivers/net/wireless/iwlwifi/iwl-scan.c
patching file drivers/net/wireless/iwlwifi/iwl3945-base.c
patching file include/net/mac80211.h
patching file net/mac80211/ieee80211_i.h
patching file net/mac80211/main.c
patching file net/mac80211/mlme.c
patching file net/mac80211/wext.c

Perhaps you have a dirty tree?

	git checkout -f

Does that help?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Tue, Mar 17, 2009 at 3:50 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> If you don't have a second device to monitor, you can also create a
> monitor interface as such:
>        iw dev wlan0 interface add moni0 type monitor flags none
>
> and run tcpdump on the resulting 'moni0' interface while you try to
> associate etc. Write the packets to files and send them to me.
>
> Due to this implicit scan modification in the driver that I removed,
> however, I won't see scans in that file, so it won't be all that useful,
> a capture made on a second device would be much better.

Ok, I'll try this out later. Got good news to share. I've applied
John's patches and just need to modified net/mac80211/wext.c slightly
since len and ssid are not defined, and function arguments are
different. I'm checking my tree again ... my seems different from his.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Tue, Mar 17, 2009 at 3:50 PM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> If you don't have a second device to monitor, you can also create a
> monitor interface as such:
>        iw dev wlan0 interface add moni0 type monitor flags none
>
> and run tcpdump on the resulting 'moni0' interface while you try to
> associate etc. Write the packets to files and send them to me.
>
> Due to this implicit scan modification in the driver that I removed,
> however, I won't see scans in that file, so it won't be all that useful,
> a capture made on a second device would be much better.

Ok, I'll try this out later. Got good news to share. I've applied
John's patches and just need to modified net/mac80211/wext.c slightly
since len and ssid are not defined, and function arguments are
different. I'm checking my tree again ... my seems different from his.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Wed, Mar 18, 2009 at 1:10 AM, John W. Linville
> Works for me...I even re-downloaded the patch from bugzilla.
> commit 18439c39e826191c0ef08c3a3271ce7ece46a860
> Merge: 9e8912e... b35f8ca...
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Tue Mar 17 08:59:33 2009 -0700

Same.

> [linville-t400.local]:> patch -p1 < revert-remove-ssid-knowledge-from-driver-series.patch
> patching file drivers/net/wireless/adm8211.c
> patching file drivers/net/wireless/adm8211.h
> patching file drivers/net/wireless/b43/main.c
> patching file drivers/net/wireless/b43legacy/main.c
> patching file drivers/net/wireless/iwlwifi/iwl-3945.h
> patching file drivers/net/wireless/iwlwifi/iwl-agn.c
> patching file drivers/net/wireless/iwlwifi/iwl-dev.h
> patching file drivers/net/wireless/iwlwifi/iwl-scan.c
> patching file drivers/net/wireless/iwlwifi/iwl3945-base.c
> patching file include/net/mac80211.h
> patching file net/mac80211/ieee80211_i.h
> patching file net/mac80211/main.c
> patching file net/mac80211/mlme.c
> patching file net/mac80211/wext.c
>
> Perhaps you have a dirty tree?
>        git checkout -f

May be. Checking now.

> Does that help?

Definitely. Even with the failing chunks, and I copied back the old
wext.c from 2.6.28-rc3, and now my wireless is associating to the
hidden AP on 2.6.29-rc8. I tried just a few times, and it's ok so far.
I'll have to pit against the WAG200G that seems to have a worse
behavior tomorrow. ... anyway, this is all good. With the patch, it's
_impossible_ to "auto" associate to the AP.  Definitely on the right
track!

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Wed, Mar 18, 2009 at 1:10 AM, John W. Linville
> Works for me...I even re-downloaded the patch from bugzilla.
> commit 18439c39e826191c0ef08c3a3271ce7ece46a860
> Merge: 9e8912e... b35f8ca...
> Author: Linus Torvalds <torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> Date:   Tue Mar 17 08:59:33 2009 -0700

Same.

> [linville-t400.local]:> patch -p1 < revert-remove-ssid-knowledge-from-driver-series.patch
> patching file drivers/net/wireless/adm8211.c
> patching file drivers/net/wireless/adm8211.h
> patching file drivers/net/wireless/b43/main.c
> patching file drivers/net/wireless/b43legacy/main.c
> patching file drivers/net/wireless/iwlwifi/iwl-3945.h
> patching file drivers/net/wireless/iwlwifi/iwl-agn.c
> patching file drivers/net/wireless/iwlwifi/iwl-dev.h
> patching file drivers/net/wireless/iwlwifi/iwl-scan.c
> patching file drivers/net/wireless/iwlwifi/iwl3945-base.c
> patching file include/net/mac80211.h
> patching file net/mac80211/ieee80211_i.h
> patching file net/mac80211/main.c
> patching file net/mac80211/mlme.c
> patching file net/mac80211/wext.c
>
> Perhaps you have a dirty tree?
>        git checkout -f

May be. Checking now.

> Does that help?

Definitely. Even with the failing chunks, and I copied back the old
wext.c from 2.6.28-rc3, and now my wireless is associating to the
hidden AP on 2.6.29-rc8. I tried just a few times, and it's ok so far.
I'll have to pit against the WAG200G that seems to have a worse
behavior tomorrow. ... anyway, this is all good. With the patch, it's
_impossible_ to "auto" associate to the AP.  Definitely on the right
track!

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Wed, Mar 18, 2009 at 1:27 AM, Jeff Chua
>> Perhaps you have a dirty tree?
>>        git checkout -f
>
> May be. Checking now.

Oh, now I know why. I was "mucking" the SSID stuffs trying to revert
some of the wireless codes on 2.6.29-rc8, and just applied your
patches on top.

My downloaded tree is clean. I'm trying your patches now.

Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Wed, Mar 18, 2009 at 1:27 AM, Jeff Chua
>> Perhaps you have a dirty tree?
>>        git checkout -f
>
> May be. Checking now.

Oh, now I know why. I was "mucking" the SSID stuffs trying to revert
some of the wireless codes on 2.6.29-rc8, and just applied your
patches on top.

My downloaded tree is clean. I'm trying your patches now.

Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Wed, Mar 18, 2009 at 1:31 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> My downloaded tree is clean. I'm trying your patches now.

John,

Your patches applied cleanly this time. And associating to the hidden
AP on 2.6.29-rc8. I'll run it against the WAG200G tomorrow. But from
what I can see, it's working well with the WAG354G.

I'll try out this as well "iw dev wlan0 interface add moni0 type
monitor flags none"

Your guys are great!

Thank you.

Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]

On Mon, 2009-03-16 at 21:24 +0800, Jeff Chua wrote:

> Here's what I did, and it's repeatable.
> 
> Take the attached bisect log and replay it, and the last offending
> commit is this ...
> # git log
> commit 71c11fb57b924c160297ccd9e1761db598d00ac2
> Author: Johannes Berg <johannes@sipsolutions.net>
> Date:   Tue Oct 28 18:29:48 2008 +0100
> 
>     b43/legacy: remove SSID code
> 
> Yes, this is not the real problem, but it's the last commit that cause
> the problem, and I couldn't bisect further, typing the next "git
> bisect bad" and the commit is

I'm on 0191b62 now and cannot reproduce the problem with iwlwifi
hardware and a linksys (broadcom-based) AP with hidden SSID.

> Anything I can help to debug further, just let me know.

Compile iwlwifi with debugging please, and instead of plain modprobe
iwlagn, do this:
	modprobe iwlagn debug=0x800 debug50=0x800

Then send me the relevant dmesg output from a working and a failed
attempt. You should see something like this

[  318.420537] ieee80211 phy4: U iwl_bg_request_scan Start direct scan for 'myssid'

in the log. I can't see any reason why it would be missing. For me, the
association is instantaneous after saying "ap any". This is expected
too, because
	iwconfig wlan0 essid "myessid"
will have triggered a directed scan for the AP.

There are two possible failure scenarios that I can imagine:

1) You see no line like the one above in your log, but rather

[  736.047879] ieee80211 phy5: U iwl_bg_request_scan Start indirect scan.

This would indicate a bug in the driver.


2) You do see the line with the SSID, but you don't get any reply. In
this case, please try doing it manually:
	iwlist wlan0 scan essid 'myssid'
Wait about 15 seconds between each attempt of doing so, and report
whether your AP is listed in the results or not. If it isn't most of the
time, then your AP is broken.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]

On Wed, Mar 18, 2009 at 3:22 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:

> I'm on 0191b62 now and cannot reproduce the problem with
> iwlwifi hardware and a linksys (broadcom-based) AP wit
> hidden SSID.

I think I know why it works on your but not mind.

I've tracked down to the sequence of iwconfig that causes it to fail.

I can now get vanilla 2.6.28-rc8 to work (7/10 times) by changing the
sequence of iwconfig.


This loop does not work at all without John's patch , but will work
100% when patched.
        iwconfig wlan0 mode Managed essid xxx key restricted xxx
        for((i = 0; i < 5; i++))
        do
                iwconfig wlan0 ap auto channel auto  # auto inside loop
                iwconfig wlan0 | grep -q "Access Point: Not-Associated"
                [ $? -ne 0 ] && break
                echo ".\c"
                sleep 1
        done


This loop only works 8 of 10 times with/without the patch.
        iwconfig wlan0 mode Managed essid xxx key restricted xxx
        iwconfig wlan0 ap auto channel auto  # auto outside loop
        for((i = 0; i < 5; i++))
        do
                iwconfig wlan0 | grep -q "Access Point: Not-Associated"
                [ $? -ne 0 ] && break
                echo ".\c"
                sleep 1
        done


The only difference is having "iwconfig wlan0 ap auto channel auto"
inside the loop.


> Then send me the relevant dmesg output from a working and a
> failed attempt. You should see something like this
> [  318.420537] ieee80211 phy4: U iwl_bg_request_scan Start
> direct scan for 'myssid'

Yes, I see it.


> 2) You do see the line with the SSID, but you don't get any reply. In
> this case, please try doing it manually:
>        iwlist wlan0 scan essid 'myssid'
> Wait about 15 seconds between each attempt of doing so, and
> report whether your AP is listed in the results or not. If it isn't
> most of the time, then your AP is broken.

Can be broken if it works with the patch? Also, it works with WinXP,
Nokia phone, and everything else.

Attached are 4 logs (all runs with the "auto" outside loop).
  nopatch.fail
  nopatch.pass
  patched.fail
  patched.pass


Thanks,
Jeff.

[-- Attachment #2: nopatch.pass --]
[-- Type: application/octet-stream, Size: 12687 bytes --]

2009-03-19T10:20:02.572499+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:20:02.572535+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:20:03.147536+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.147553+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147561+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147567+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147572+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147589+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.148489+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001B47) - 1 (beacon timer 95417)
2009-03-19T10:20:03.148503+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:20:03.152533+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000026F8:00000000) - 2
2009-03-19T10:20:03.152547+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:20:03.152555+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.152563+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152571+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152585+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152600+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152608+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152629+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152637+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152644+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.156497+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:0000365B) - 1 (beacon timer 88484)
2009-03-19T10:20:03.172496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006D96) - 0 elapsed=14139 usec (20ms since last)
2009-03-19T10:20:03.172511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:00006F21) - 1 (beacon timer 73951)
2009-03-19T10:20:03.183500+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A568) - 0 elapsed=13895 usec (12ms since last)
2009-03-19T10:20:03.183514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A6F2) - 1 (beacon timer 59661)
2009-03-19T10:20:03.199514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0000DF15) - 1 elapsed=14371 usec (16ms since last)
2009-03-19T10:20:03.199527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0000E0A0) - 1 (beacon timer 44896)
2009-03-19T10:20:03.215498+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:0001188C) - 0 elapsed=14316 usec (16ms since last)
2009-03-19T10:20:03.215511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00011A17) - 1 (beacon timer 30185)
2009-03-19T10:20:03.252490+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T10:20:03.252512+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:20:03.256580+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.256594+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256603+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256618+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256625+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256632+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256639+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256666+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256673+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256680+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256686+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256693+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:20:03.256700+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015E5) - 1 (beacon timer 96795)
2009-03-19T10:20:03.371535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CE12) - 0 elapsed=112685 usec (156ms since last)
2009-03-19T10:20:03.371582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF9D) - 1 (beacon timer 4280419)
2009-03-19T10:20:03.483530+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000387CD) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.483565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038957) - 1 (beacon timer 8464041)
2009-03-19T10:20:03.595508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00054188) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.595522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054312) - 1 (beacon timer 12647662)
2009-03-19T10:20:03.707522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB43) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.707536+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FCCE) - 1 (beacon timer 16831282)
2009-03-19T10:20:03.823503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4FE) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:20:03.823523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B689) - 1 (beacon timer 21014903)
2009-03-19T10:20:03.935504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6EB9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.935518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7044) - 1 (beacon timer 25198524)
2009-03-19T10:20:04.047526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2874) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.047540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29FF) - 1 (beacon timer 29382145)
2009-03-19T10:20:04.163504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE230) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.163518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE3BD) - 1 (beacon timer 33565763)
2009-03-19T10:20:04.276496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BED) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.276510+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D7A) - 1 (beacon timer 37749382)
2009-03-19T10:20:04.387504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001155AB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.387519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115738) - 1 (beacon timer 46229704)
2009-03-19T10:20:04.499503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F69) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.499518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310F6) - 1 (beacon timer 50413322)
2009-03-19T10:20:04.615504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C927) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.615524+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CAB4) - 1 (beacon timer 54596940)
2009-03-19T10:20:04.728542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682E5) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.728556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168497:00000000) - 1
2009-03-19T10:20:04.728565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #3: nopatch.fail --]
[-- Type: application/octet-stream, Size: 11275 bytes --]

2009-03-19T10:18:23.588517+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:18:23.588532+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:18:24.188573+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:18:24.188667+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188706+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188736+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188745+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188770+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188778+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188802+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188811+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188835+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188860+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188869+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188892+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:18:24.188901+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001C9B) - 1 (beacon timer 95077)
2009-03-19T10:18:24.188925+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:18:24.192526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x0000255A:00000000) - 2
2009-03-19T10:18:24.192541+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:18:24.195528+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:18:24.195540+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195547+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195553+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195559+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195564+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195571+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195577+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195582+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195588+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195604+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:18:24.195621+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:000037B5) - 1 (beacon timer 88139)
2009-03-19T10:18:24.200574+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00000094:00000000) - 2
2009-03-19T10:18:24.200596+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:18:24.200603+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:18:24.200611+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200626+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200633+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200660+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200667+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200675+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200682+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200690+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200697+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200705+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200712+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:18:24.204518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000013EA) - 1 (beacon timer 97302)
2009-03-19T10:18:24.319505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CC17) - 0 elapsed=112685 usec (128ms since last)
2009-03-19T10:18:24.319563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CDA2) - 1 (beacon timer 4280926)
2009-03-19T10:18:24.432505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000385D2) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.432521+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:0003875C) - 1 (beacon timer 8464548)
2009-03-19T10:18:24.543862+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00053F8D) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:24.543876+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054118) - 1 (beacon timer 12648168)
2009-03-19T10:18:24.655504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006F948) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.655518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FAD3) - 1 (beacon timer 16831789)
2009-03-19T10:18:24.771529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B303) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:18:24.771543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B48E) - 1 (beacon timer 21015410)
2009-03-19T10:18:24.883504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6CBE) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.883518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A6E49) - 1 (beacon timer 25199031)
2009-03-19T10:18:24.995505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2679) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.995519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C2804) - 1 (beacon timer 29382652)
2009-03-19T10:18:25.107490+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE035) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:25.107504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE1C2) - 1 (beacon timer 33566270)
2009-03-19T10:18:25.224535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F99F2) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:18:25.224551+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9B7F) - 1 (beacon timer 37749889)
2009-03-19T10:18:25.335504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001153B0) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:25.335519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:0011553D) - 1 (beacon timer 46230211)
2009-03-19T10:18:25.447504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130D6E) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:25.447519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:00130EFB) - 1 (beacon timer 50413829)
2009-03-19T10:18:25.563849+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C72C) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:18:25.563863+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014C8BA) - 1 (beacon timer 54597446)
2009-03-19T10:18:25.676504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001680EA) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:25.676519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168289:00000000) - 1
2009-03-19T10:18:25.676527+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #4: nopatch.pass --]
[-- Type: application/octet-stream, Size: 12687 bytes --]

2009-03-19T10:20:02.572499+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:20:02.572535+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:20:03.147536+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.147553+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147561+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147567+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147572+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147589+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.148489+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001B47) - 1 (beacon timer 95417)
2009-03-19T10:20:03.148503+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:20:03.152533+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000026F8:00000000) - 2
2009-03-19T10:20:03.152547+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:20:03.152555+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.152563+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152571+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152585+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152600+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152608+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152629+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152637+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152644+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.156497+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:0000365B) - 1 (beacon timer 88484)
2009-03-19T10:20:03.172496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006D96) - 0 elapsed=14139 usec (20ms since last)
2009-03-19T10:20:03.172511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:00006F21) - 1 (beacon timer 73951)
2009-03-19T10:20:03.183500+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A568) - 0 elapsed=13895 usec (12ms since last)
2009-03-19T10:20:03.183514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A6F2) - 1 (beacon timer 59661)
2009-03-19T10:20:03.199514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0000DF15) - 1 elapsed=14371 usec (16ms since last)
2009-03-19T10:20:03.199527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0000E0A0) - 1 (beacon timer 44896)
2009-03-19T10:20:03.215498+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:0001188C) - 0 elapsed=14316 usec (16ms since last)
2009-03-19T10:20:03.215511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00011A17) - 1 (beacon timer 30185)
2009-03-19T10:20:03.252490+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T10:20:03.252512+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:20:03.256580+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.256594+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256603+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256618+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256625+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256632+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256639+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256666+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256673+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256680+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256686+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256693+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:20:03.256700+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015E5) - 1 (beacon timer 96795)
2009-03-19T10:20:03.371535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CE12) - 0 elapsed=112685 usec (156ms since last)
2009-03-19T10:20:03.371582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF9D) - 1 (beacon timer 4280419)
2009-03-19T10:20:03.483530+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000387CD) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.483565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038957) - 1 (beacon timer 8464041)
2009-03-19T10:20:03.595508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00054188) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.595522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054312) - 1 (beacon timer 12647662)
2009-03-19T10:20:03.707522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB43) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.707536+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FCCE) - 1 (beacon timer 16831282)
2009-03-19T10:20:03.823503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4FE) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:20:03.823523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B689) - 1 (beacon timer 21014903)
2009-03-19T10:20:03.935504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6EB9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.935518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7044) - 1 (beacon timer 25198524)
2009-03-19T10:20:04.047526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2874) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.047540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29FF) - 1 (beacon timer 29382145)
2009-03-19T10:20:04.163504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE230) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.163518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE3BD) - 1 (beacon timer 33565763)
2009-03-19T10:20:04.276496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BED) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.276510+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D7A) - 1 (beacon timer 37749382)
2009-03-19T10:20:04.387504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001155AB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.387519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115738) - 1 (beacon timer 46229704)
2009-03-19T10:20:04.499503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F69) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.499518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310F6) - 1 (beacon timer 50413322)
2009-03-19T10:20:04.615504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C927) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.615524+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CAB4) - 1 (beacon timer 54596940)
2009-03-19T10:20:04.728542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682E5) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.728556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168497:00000000) - 1
2009-03-19T10:20:04.728565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #5: patched.fail --]
[-- Type: application/octet-stream, Size: 11275 bytes --]

2009-03-19T10:23:02.031482+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:23:02.031496+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:23:02.603534+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:02.603592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603626+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603676+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603683+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603705+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603712+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603717+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603739+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603746+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603768+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603775+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:02.603780+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001BD3) - 1 (beacon timer 95277)
2009-03-19T10:23:02.603802+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:23:02.608536+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000027C0:00000000) - 2
2009-03-19T10:23:02.608551+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:23:02.612565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:02.612577+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612590+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612604+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612611+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612634+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612643+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612656+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612670+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:02.612678+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00003A93) - 1 (beacon timer 87405)
2009-03-19T10:23:02.616483+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00000094:00000000) - 2
2009-03-19T10:23:02.616500+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:23:02.619560+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:02.619574+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619583+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619591+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619599+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619606+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619631+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619638+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619654+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619662+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619669+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619682+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619689+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619696+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:23:02.619703+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:0000148B) - 1 (beacon timer 97141)
2009-03-19T10:23:02.735529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CCB8) - 0 elapsed=112685 usec (128ms since last)
2009-03-19T10:23:02.735552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CE43) - 1 (beacon timer 4280765)
2009-03-19T10:23:02.847520+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:00038673) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:02.847558+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:000387FD) - 1 (beacon timer 8464387)
2009-03-19T10:23:02.959508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:0005402E) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:02.959527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:000541B9) - 1 (beacon timer 12648007)
2009-03-19T10:23:03.071504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006F9E9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.071519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FB74) - 1 (beacon timer 16831628)
2009-03-19T10:23:03.187504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B3A4) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:23:03.187516+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B52F) - 1 (beacon timer 21015249)
2009-03-19T10:23:03.299503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6D5F) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.299515+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A6EEA) - 1 (beacon timer 25198870)
2009-03-19T10:23:03.411529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C271A) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.411543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C28A5) - 1 (beacon timer 29382491)
2009-03-19T10:23:03.527504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE0D6) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:03.527518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE263) - 1 (beacon timer 33566109)
2009-03-19T10:23:03.640494+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9A93) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.640508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9C20) - 1 (beacon timer 37749728)
2009-03-19T10:23:03.751521+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:00115451) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:03.751535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:001155DE) - 1 (beacon timer 46230050)
2009-03-19T10:23:03.863504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130E0F) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:03.863517+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:00130F9C) - 1 (beacon timer 50413668)
2009-03-19T10:23:03.979528+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C7CD) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:03.979540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014C95B) - 1 (beacon timer 54597285)
2009-03-19T10:23:04.092503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:0016818B) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:04.092520+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x0016832A:00000000) - 1
2009-03-19T10:23:04.092527+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #6: patched.pass --]
[-- Type: application/octet-stream, Size: 12686 bytes --]

2009-03-19T10:23:45.844526+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:23:45.844555+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:23:46.456557+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:46.456620+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456661+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456689+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456713+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456720+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456726+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456748+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456755+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456777+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456783+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456789+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456812+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:46.456822+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001BE7) - 1 (beacon timer 95257)
2009-03-19T10:23:46.456844+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:23:46.459540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00002770:00000000) - 2
2009-03-19T10:23:46.459553+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:23:46.459563+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:46.459569+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459574+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459581+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459586+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459604+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459628+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459633+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:46.464489+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:000030CF) - 1 (beacon timer 89905)
2009-03-19T10:23:46.476520+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006768) - 0 elapsed=13977 usec (16ms since last)
2009-03-19T10:23:46.476535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:000068F3) - 1 (beacon timer 75533)
2009-03-19T10:23:46.491512+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A013) - 0 elapsed=14112 usec (16ms since last)
2009-03-19T10:23:46.491525+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A19E) - 1 (beacon timer 61026)
2009-03-19T10:23:46.535527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:000149AD) - 1 elapsed=43023 usec (44ms since last)
2009-03-19T10:23:46.535540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:00014B39) - 1 (beacon timer 17607)
2009-03-19T10:23:46.551529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:000183DE) - 0 elapsed=14501 usec (16ms since last)
2009-03-19T10:23:46.551543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00018569) - 1 (beacon timer 2711)
2009-03-19T10:23:46.564484+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T10:23:46.564507+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:23:46.568554+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:46.568568+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568576+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568591+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568598+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568620+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568634+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568641+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568648+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568655+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568662+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:23:46.568670+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015E5) - 1 (beacon timer 96795)
2009-03-19T10:23:46.683505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CE12) - 0 elapsed=112685 usec (132ms since last)
2009-03-19T10:23:46.683565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF9D) - 1 (beacon timer 4280419)
2009-03-19T10:23:46.795504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000387CD) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:46.795542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038957) - 1 (beacon timer 8464041)
2009-03-19T10:23:46.907528+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00054188) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:46.907563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054312) - 1 (beacon timer 12647662)
2009-03-19T10:23:47.019504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB43) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:47.019523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FCCE) - 1 (beacon timer 16831282)
2009-03-19T10:23:47.135503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4FE) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:23:47.135523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B689) - 1 (beacon timer 21014903)
2009-03-19T10:23:47.247504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6EB9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:47.247524+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7044) - 1 (beacon timer 25198524)
2009-03-19T10:23:47.359504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2874) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:47.359518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29FF) - 1 (beacon timer 29382145)
2009-03-19T10:23:47.475504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE230) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:47.475519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE3BD) - 1 (beacon timer 33565763)
2009-03-19T10:23:47.588526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BED) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:47.588542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D7A) - 1 (beacon timer 37749382)
2009-03-19T10:23:47.699506+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001155AB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:47.699521+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115738) - 1 (beacon timer 46229704)
2009-03-19T10:23:47.811525+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F69) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:47.811539+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310F6) - 1 (beacon timer 50413322)
2009-03-19T10:23:47.927503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C927) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:47.927517+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CAB4) - 1 (beacon timer 54596940)
2009-03-19T10:23:48.039556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682E5) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:48.039572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168498:00000000) - 1
2009-03-19T10:23:48.039581+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

On Wed, Mar 18, 2009 at 3:22 AM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:

> I'm on 0191b62 now and cannot reproduce the problem with
> iwlwifi hardware and a linksys (broadcom-based) AP wit
> hidden SSID.

I think I know why it works on your but not mind.

I've tracked down to the sequence of iwconfig that causes it to fail.

I can now get vanilla 2.6.28-rc8 to work (7/10 times) by changing the
sequence of iwconfig.


This loop does not work at all without John's patch , but will work
100% when patched.
        iwconfig wlan0 mode Managed essid xxx key restricted xxx
        for((i = 0; i < 5; i++))
        do
                iwconfig wlan0 ap auto channel auto  # auto inside loop
                iwconfig wlan0 | grep -q "Access Point: Not-Associated"
                [ $? -ne 0 ] && break
                echo ".\c"
                sleep 1
        done


This loop only works 8 of 10 times with/without the patch.
        iwconfig wlan0 mode Managed essid xxx key restricted xxx
        iwconfig wlan0 ap auto channel auto  # auto outside loop
        for((i = 0; i < 5; i++))
        do
                iwconfig wlan0 | grep -q "Access Point: Not-Associated"
                [ $? -ne 0 ] && break
                echo ".\c"
                sleep 1
        done


The only difference is having "iwconfig wlan0 ap auto channel auto"
inside the loop.


> Then send me the relevant dmesg output from a working and a
> failed attempt. You should see something like this
> [  318.420537] ieee80211 phy4: U iwl_bg_request_scan Start
> direct scan for 'myssid'

Yes, I see it.


> 2) You do see the line with the SSID, but you don't get any reply. In
> this case, please try doing it manually:
>        iwlist wlan0 scan essid 'myssid'
> Wait about 15 seconds between each attempt of doing so, and
> report whether your AP is listed in the results or not. If it isn't
> most of the time, then your AP is broken.

Can be broken if it works with the patch? Also, it works with WinXP,
Nokia phone, and everything else.

Attached are 4 logs (all runs with the "auto" outside loop).
  nopatch.fail
  nopatch.pass
  patched.fail
  patched.pass


Thanks,
Jeff.

[-- Attachment #2: nopatch.pass --]
[-- Type: application/octet-stream, Size: 12687 bytes --]

2009-03-19T10:20:02.572499+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:20:02.572535+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:20:03.147536+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.147553+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147561+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147567+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147572+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147589+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.148489+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001B47) - 1 (beacon timer 95417)
2009-03-19T10:20:03.148503+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:20:03.152533+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000026F8:00000000) - 2
2009-03-19T10:20:03.152547+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:20:03.152555+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.152563+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152571+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152585+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152600+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152608+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152629+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152637+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152644+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.156497+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:0000365B) - 1 (beacon timer 88484)
2009-03-19T10:20:03.172496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006D96) - 0 elapsed=14139 usec (20ms since last)
2009-03-19T10:20:03.172511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:00006F21) - 1 (beacon timer 73951)
2009-03-19T10:20:03.183500+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A568) - 0 elapsed=13895 usec (12ms since last)
2009-03-19T10:20:03.183514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A6F2) - 1 (beacon timer 59661)
2009-03-19T10:20:03.199514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0000DF15) - 1 elapsed=14371 usec (16ms since last)
2009-03-19T10:20:03.199527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0000E0A0) - 1 (beacon timer 44896)
2009-03-19T10:20:03.215498+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:0001188C) - 0 elapsed=14316 usec (16ms since last)
2009-03-19T10:20:03.215511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00011A17) - 1 (beacon timer 30185)
2009-03-19T10:20:03.252490+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T10:20:03.252512+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:20:03.256580+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.256594+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256603+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256618+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256625+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256632+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256639+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256666+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256673+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256680+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256686+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256693+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:20:03.256700+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015E5) - 1 (beacon timer 96795)
2009-03-19T10:20:03.371535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CE12) - 0 elapsed=112685 usec (156ms since last)
2009-03-19T10:20:03.371582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF9D) - 1 (beacon timer 4280419)
2009-03-19T10:20:03.483530+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000387CD) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.483565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038957) - 1 (beacon timer 8464041)
2009-03-19T10:20:03.595508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00054188) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.595522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054312) - 1 (beacon timer 12647662)
2009-03-19T10:20:03.707522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB43) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.707536+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FCCE) - 1 (beacon timer 16831282)
2009-03-19T10:20:03.823503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4FE) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:20:03.823523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B689) - 1 (beacon timer 21014903)
2009-03-19T10:20:03.935504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6EB9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.935518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7044) - 1 (beacon timer 25198524)
2009-03-19T10:20:04.047526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2874) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.047540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29FF) - 1 (beacon timer 29382145)
2009-03-19T10:20:04.163504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE230) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.163518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE3BD) - 1 (beacon timer 33565763)
2009-03-19T10:20:04.276496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BED) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.276510+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D7A) - 1 (beacon timer 37749382)
2009-03-19T10:20:04.387504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001155AB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.387519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115738) - 1 (beacon timer 46229704)
2009-03-19T10:20:04.499503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F69) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.499518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310F6) - 1 (beacon timer 50413322)
2009-03-19T10:20:04.615504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C927) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.615524+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CAB4) - 1 (beacon timer 54596940)
2009-03-19T10:20:04.728542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682E5) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.728556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168497:00000000) - 1
2009-03-19T10:20:04.728565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #3: nopatch.fail --]
[-- Type: application/octet-stream, Size: 11275 bytes --]

2009-03-19T10:18:23.588517+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:18:23.588532+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:18:24.188573+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:18:24.188667+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188706+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188736+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188745+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188770+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188778+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188802+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188811+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188835+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188860+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188869+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.188892+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:18:24.188901+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001C9B) - 1 (beacon timer 95077)
2009-03-19T10:18:24.188925+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:18:24.192526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x0000255A:00000000) - 2
2009-03-19T10:18:24.192541+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:18:24.195528+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:18:24.195540+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195547+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195553+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195559+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195564+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195571+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195577+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195582+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195588+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195604+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:18:24.195615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:18:24.195621+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:000037B5) - 1 (beacon timer 88139)
2009-03-19T10:18:24.200574+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00000094:00000000) - 2
2009-03-19T10:18:24.200596+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:18:24.200603+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:18:24.200611+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200626+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200633+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200660+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200667+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200675+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200682+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200690+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200697+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200705+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:18:24.200712+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:18:24.204518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000013EA) - 1 (beacon timer 97302)
2009-03-19T10:18:24.319505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CC17) - 0 elapsed=112685 usec (128ms since last)
2009-03-19T10:18:24.319563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CDA2) - 1 (beacon timer 4280926)
2009-03-19T10:18:24.432505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000385D2) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.432521+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:0003875C) - 1 (beacon timer 8464548)
2009-03-19T10:18:24.543862+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00053F8D) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:24.543876+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054118) - 1 (beacon timer 12648168)
2009-03-19T10:18:24.655504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006F948) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.655518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FAD3) - 1 (beacon timer 16831789)
2009-03-19T10:18:24.771529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B303) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:18:24.771543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B48E) - 1 (beacon timer 21015410)
2009-03-19T10:18:24.883504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6CBE) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.883518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A6E49) - 1 (beacon timer 25199031)
2009-03-19T10:18:24.995505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2679) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:24.995519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C2804) - 1 (beacon timer 29382652)
2009-03-19T10:18:25.107490+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE035) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:25.107504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE1C2) - 1 (beacon timer 33566270)
2009-03-19T10:18:25.224535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F99F2) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:18:25.224551+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9B7F) - 1 (beacon timer 37749889)
2009-03-19T10:18:25.335504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001153B0) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:25.335519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:0011553D) - 1 (beacon timer 46230211)
2009-03-19T10:18:25.447504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130D6E) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:18:25.447519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:00130EFB) - 1 (beacon timer 50413829)
2009-03-19T10:18:25.563849+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C72C) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:18:25.563863+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014C8BA) - 1 (beacon timer 54597446)
2009-03-19T10:18:25.676504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001680EA) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:18:25.676519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168289:00000000) - 1
2009-03-19T10:18:25.676527+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #4: nopatch.pass --]
[-- Type: application/octet-stream, Size: 12687 bytes --]

2009-03-19T10:20:02.572499+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:20:02.572535+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:20:03.147536+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.147553+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147561+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147567+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147572+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147589+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.147627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.148489+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001B47) - 1 (beacon timer 95417)
2009-03-19T10:20:03.148503+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:20:03.152533+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000026F8:00000000) - 2
2009-03-19T10:20:03.152547+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:20:03.152555+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.152563+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152571+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152585+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152600+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152608+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152629+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152637+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:20:03.152644+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:20:03.156497+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:0000365B) - 1 (beacon timer 88484)
2009-03-19T10:20:03.172496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006D96) - 0 elapsed=14139 usec (20ms since last)
2009-03-19T10:20:03.172511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:00006F21) - 1 (beacon timer 73951)
2009-03-19T10:20:03.183500+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A568) - 0 elapsed=13895 usec (12ms since last)
2009-03-19T10:20:03.183514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A6F2) - 1 (beacon timer 59661)
2009-03-19T10:20:03.199514+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0000DF15) - 1 elapsed=14371 usec (16ms since last)
2009-03-19T10:20:03.199527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0000E0A0) - 1 (beacon timer 44896)
2009-03-19T10:20:03.215498+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:0001188C) - 0 elapsed=14316 usec (16ms since last)
2009-03-19T10:20:03.215511+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00011A17) - 1 (beacon timer 30185)
2009-03-19T10:20:03.252490+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T10:20:03.252512+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:20:03.256580+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:20:03.256594+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256603+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256618+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256625+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256632+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256639+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256666+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256673+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256680+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256686+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:20:03.256693+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:20:03.256700+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015E5) - 1 (beacon timer 96795)
2009-03-19T10:20:03.371535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CE12) - 0 elapsed=112685 usec (156ms since last)
2009-03-19T10:20:03.371582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF9D) - 1 (beacon timer 4280419)
2009-03-19T10:20:03.483530+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000387CD) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.483565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038957) - 1 (beacon timer 8464041)
2009-03-19T10:20:03.595508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00054188) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.595522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054312) - 1 (beacon timer 12647662)
2009-03-19T10:20:03.707522+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB43) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:03.707536+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FCCE) - 1 (beacon timer 16831282)
2009-03-19T10:20:03.823503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4FE) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:20:03.823523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B689) - 1 (beacon timer 21014903)
2009-03-19T10:20:03.935504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6EB9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:03.935518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7044) - 1 (beacon timer 25198524)
2009-03-19T10:20:04.047526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2874) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.047540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29FF) - 1 (beacon timer 29382145)
2009-03-19T10:20:04.163504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE230) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.163518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE3BD) - 1 (beacon timer 33565763)
2009-03-19T10:20:04.276496+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BED) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:20:04.276510+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D7A) - 1 (beacon timer 37749382)
2009-03-19T10:20:04.387504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001155AB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.387519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115738) - 1 (beacon timer 46229704)
2009-03-19T10:20:04.499503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F69) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.499518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310F6) - 1 (beacon timer 50413322)
2009-03-19T10:20:04.615504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C927) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:20:04.615524+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CAB4) - 1 (beacon timer 54596940)
2009-03-19T10:20:04.728542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682E5) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:20:04.728556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168497:00000000) - 1
2009-03-19T10:20:04.728565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #5: patched.fail --]
[-- Type: application/octet-stream, Size: 11275 bytes --]

2009-03-19T10:23:02.031482+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:23:02.031496+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:23:02.603534+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:02.603592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603626+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603676+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603683+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603705+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603712+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603717+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603739+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603746+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603768+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.603775+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:02.603780+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001BD3) - 1 (beacon timer 95277)
2009-03-19T10:23:02.603802+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:23:02.608536+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000027C0:00000000) - 2
2009-03-19T10:23:02.608551+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:23:02.612565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:02.612577+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612590+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612604+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612611+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612634+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612643+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612656+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:02.612670+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:02.612678+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00003A93) - 1 (beacon timer 87405)
2009-03-19T10:23:02.616483+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00000094:00000000) - 2
2009-03-19T10:23:02.616500+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:23:02.619560+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:02.619574+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619583+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619591+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619599+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619606+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619631+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619638+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619654+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619662+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619669+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619682+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619689+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:23:02.619696+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:23:02.619703+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:0000148B) - 1 (beacon timer 97141)
2009-03-19T10:23:02.735529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CCB8) - 0 elapsed=112685 usec (128ms since last)
2009-03-19T10:23:02.735552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CE43) - 1 (beacon timer 4280765)
2009-03-19T10:23:02.847520+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:00038673) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:02.847558+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:000387FD) - 1 (beacon timer 8464387)
2009-03-19T10:23:02.959508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:0005402E) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:02.959527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:000541B9) - 1 (beacon timer 12648007)
2009-03-19T10:23:03.071504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006F9E9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.071519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FB74) - 1 (beacon timer 16831628)
2009-03-19T10:23:03.187504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B3A4) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:23:03.187516+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B52F) - 1 (beacon timer 21015249)
2009-03-19T10:23:03.299503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6D5F) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.299515+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A6EEA) - 1 (beacon timer 25198870)
2009-03-19T10:23:03.411529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C271A) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.411543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C28A5) - 1 (beacon timer 29382491)
2009-03-19T10:23:03.527504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE0D6) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:03.527518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE263) - 1 (beacon timer 33566109)
2009-03-19T10:23:03.640494+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9A93) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:03.640508+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9C20) - 1 (beacon timer 37749728)
2009-03-19T10:23:03.751521+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:00115451) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:03.751535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:001155DE) - 1 (beacon timer 46230050)
2009-03-19T10:23:03.863504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130E0F) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:03.863517+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:00130F9C) - 1 (beacon timer 50413668)
2009-03-19T10:23:03.979528+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C7CD) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:03.979540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014C95B) - 1 (beacon timer 54597285)
2009-03-19T10:23:04.092503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:0016818B) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:04.092520+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x0016832A:00000000) - 1
2009-03-19T10:23:04.092527+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #6: patched.pass --]
[-- Type: application/octet-stream, Size: 12686 bytes --]

2009-03-19T10:23:45.844526+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T10:23:45.844555+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T10:23:46.456557+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:46.456620+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456661+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456689+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456713+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456720+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456726+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456748+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456755+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456777+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456783+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456789+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.456812+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:46.456822+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001BE7) - 1 (beacon timer 95257)
2009-03-19T10:23:46.456844+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T10:23:46.459540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00002770:00000000) - 2
2009-03-19T10:23:46.459553+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T10:23:46.459563+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:46.459569+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459574+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459581+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459586+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459604+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459628+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T10:23:46.459633+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T10:23:46.464489+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:000030CF) - 1 (beacon timer 89905)
2009-03-19T10:23:46.476520+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006768) - 0 elapsed=13977 usec (16ms since last)
2009-03-19T10:23:46.476535+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:000068F3) - 1 (beacon timer 75533)
2009-03-19T10:23:46.491512+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A013) - 0 elapsed=14112 usec (16ms since last)
2009-03-19T10:23:46.491525+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A19E) - 1 (beacon timer 61026)
2009-03-19T10:23:46.535527+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:000149AD) - 1 elapsed=43023 usec (44ms since last)
2009-03-19T10:23:46.535540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:00014B39) - 1 (beacon timer 17607)
2009-03-19T10:23:46.551529+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:000183DE) - 0 elapsed=14501 usec (16ms since last)
2009-03-19T10:23:46.551543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00018569) - 1 (beacon timer 2711)
2009-03-19T10:23:46.564484+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T10:23:46.564507+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T10:23:46.568554+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T10:23:46.568568+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568576+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568591+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568598+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568620+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568634+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568641+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568648+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568655+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T10:23:46.568662+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T10:23:46.568670+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015E5) - 1 (beacon timer 96795)
2009-03-19T10:23:46.683505+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CE12) - 0 elapsed=112685 usec (132ms since last)
2009-03-19T10:23:46.683565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF9D) - 1 (beacon timer 4280419)
2009-03-19T10:23:46.795504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000387CD) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:46.795542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038957) - 1 (beacon timer 8464041)
2009-03-19T10:23:46.907528+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00054188) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:46.907563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00054312) - 1 (beacon timer 12647662)
2009-03-19T10:23:47.019504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB43) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:47.019523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FCCE) - 1 (beacon timer 16831282)
2009-03-19T10:23:47.135503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4FE) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T10:23:47.135523+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B689) - 1 (beacon timer 21014903)
2009-03-19T10:23:47.247504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6EB9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:47.247524+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7044) - 1 (beacon timer 25198524)
2009-03-19T10:23:47.359504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2874) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:47.359518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29FF) - 1 (beacon timer 29382145)
2009-03-19T10:23:47.475504+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE230) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:47.475519+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE3BD) - 1 (beacon timer 33565763)
2009-03-19T10:23:47.588526+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BED) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T10:23:47.588542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D7A) - 1 (beacon timer 37749382)
2009-03-19T10:23:47.699506+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001155AB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:47.699521+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115738) - 1 (beacon timer 46229704)
2009-03-19T10:23:47.811525+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F69) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:47.811539+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310F6) - 1 (beacon timer 50413322)
2009-03-19T10:23:47.927503+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C927) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T10:23:47.927517+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CAB4) - 1 (beacon timer 54596940)
2009-03-19T10:23:48.039556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682E5) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T10:23:48.039572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168498:00000000) - 1
2009-03-19T10:23:48.039581+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Thu, Mar 19, 2009 at 10:58 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> I've tracked down to the sequence of iwconfig that causes it to fail.

> This loop only works 8 of 10 times with/without the patch.
>        iwconfig wlan0 mode Managed essid xxx key restricted xxx
>        iwconfig wlan0 ap auto channel auto  # auto outside loop
>        for((i = 0; i < 5; i++))
>        do
>                iwconfig wlan0 | grep -q "Not-Associated"
>                [ $? -ne 0 ] && break
>                echo ".\c"
>                sleep 1
>        done


I've modified it a little, and now it works 100% without patch, by
using "iwlist scan" instead of "sleep 1" ...
        iwconfig wlan0 mode Managed essid xxx key restricted xxx
        iwconfig wlan0 ap auto channel auto  # auto outside loop
        for((i = 0; i < 5; i++))
        do
                iwlist wlan0 scan >/dev/null  #use scan instead of sleep
                iwconfig $DEV | grep -q "Access Point: Not-Associated"
                [ $? -ne 0 ] && break
                echo ".\c"
        done


So, this will work for older kernel and well as 2.6.29-rc8.

Rafael, can we close the case? It's the iwconfig sequence that used to
work on 2.6.28-rc3 but now needs to be updated for 2.6.29-rc8.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

On Thu, Mar 19, 2009 at 11:25 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> Rafael, can we close the case?

Not yet. I reran a few more times, and without patch, it'll fail sometimes.

Here's the 3 files. With patch, pass every time (so far).

nopatch.fail
nopatch.pass
passed.pass


> 1) You see no line like the one above in your log, but rather
> [  736.047879] ieee80211 phy5: U iwl_bg_request_scan
> Start indirect scan.
> This would indicate a bug in the driver.

*** this is in nopatch.fail ***

2009-03-19T12:07:22.437578+08:00 boston kernel: ieee80211 phy0: U
iwl_bg_request_scan Start direct scan for 'sdg2088a88'

2009-03-19T12:07:24.337644+08:00 boston kernel: ieee80211 phy0: U
iwl_bg_request_scan Start indirect scan.


For the passing run, it's always "direct scan".


Thanks,
Jeff.

[-- Attachment #2: nopatch.fail --]
[-- Type: application/octet-stream, Size: 61509 bytes --]

2009-03-19T12:07:21.845534+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T12:07:21.845546+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T12:07:22.437578+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T12:07:22.437591+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437598+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437611+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437617+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437623+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437631+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437637+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437643+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437650+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437657+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437663+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.437670+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:22.437678+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001B5B) - 1 (beacon timer 95397)
2009-03-19T12:07:22.437685+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T12:07:22.441537+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000026BB:00000000) - 2
2009-03-19T12:07:22.441553+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:22.445594+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T12:07:22.445606+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445622+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445628+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445635+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445643+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445651+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445658+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445666+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445671+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445677+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445684+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T12:07:22.445692+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:22.445700+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:0000397A) - 1 (beacon timer 87686)
2009-03-19T12:07:22.450558+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00000094:00000000) - 2
2009-03-19T12:07:22.450577+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T12:07:22.450582+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T12:07:22.450592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450599+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450607+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450614+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450623+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450630+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450639+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450647+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450654+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450662+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450670+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450677+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450684+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T12:07:22.450692+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T12:07:22.454547+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000013FE) - 1 (beacon timer 97282)
2009-03-19T12:07:22.569551+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CC2B) - 0 elapsed=112685 usec (128ms since last)
2009-03-19T12:07:22.569572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CDB6) - 1 (beacon timer 4280906)
2009-03-19T12:07:22.682560+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000385E6) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:22.682575+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038770) - 1 (beacon timer 8464528)
2009-03-19T12:07:22.793898+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:00053FA1) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:22.793913+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:0005412B) - 1 (beacon timer 12648149)
2009-03-19T12:07:22.905564+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006F95C) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:22.905582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FAE7) - 1 (beacon timer 16831769)
2009-03-19T12:07:23.021568+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B317) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:23.021583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B4A2) - 1 (beacon timer 21015390)
2009-03-19T12:07:23.133568+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6CD2) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:23.133583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A6E5D) - 1 (beacon timer 25199011)
2009-03-19T12:07:23.245563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C268D) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:23.245575+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C2818) - 1 (beacon timer 29382632)
2009-03-19T12:07:23.357561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE049) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:23.357578+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE1D6) - 1 (beacon timer 33566250)
2009-03-19T12:07:23.473570+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9A06) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:23.473584+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9B93) - 1 (beacon timer 37749869)
2009-03-19T12:07:23.585569+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001153C4) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:23.585583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115551) - 1 (beacon timer 46230191)
2009-03-19T12:07:23.697569+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130D82) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:23.697580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:00130F0F) - 1 (beacon timer 50413809)
2009-03-19T12:07:23.813555+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C740) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:23.813566+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014C8CD) - 1 (beacon timer 54597427)
2009-03-19T12:07:23.925545+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001680FE) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:23.925556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x0016829D:00000000) - 1
2009-03-19T12:07:23.925565+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:24.021578+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:24.021587+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021600+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021621+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021633+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021638+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021644+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021649+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021655+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:24.021661+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:24.026547+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00180BE0) - 1 (beacon timer 62977056)
2009-03-19T12:07:24.038553+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00184026) - 0 elapsed=13382 usec (112ms since last)
2009-03-19T12:07:24.038595+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:001841B1) - 1 (beacon timer 62963279)
2009-03-19T12:07:24.053554+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:00187477) - 0 elapsed=12998 usec (16ms since last)
2009-03-19T12:07:24.053599+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:00187601) - 1 (beacon timer 62949886)
2009-03-19T12:07:24.065565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0018A952) - 1 elapsed=13137 usec (12ms since last)
2009-03-19T12:07:24.065577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0018AADD) - 1 (beacon timer 62936355)
2009-03-19T12:07:24.081553+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:0018DF0C) - 0 elapsed=13359 usec (16ms since last)
2009-03-19T12:07:24.081563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:0018E097) - 1 (beacon timer 62922601)
2009-03-19T12:07:24.121590+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 5 [802.11bg] (TSF: 0x00000000:00197FCD) - 10 elapsed=40758 usec (40ms since last)
2009-03-19T12:07:24.121650+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 6 [802.11bg] (TSF: 0x00000000:00198158) - 1 (beacon timer 67178151)
2009-03-19T12:07:24.161565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 6 [802.11bg] (TSF: 0x00000000:001A1D5D) - 11 elapsed=39941 usec (40ms since last)
2009-03-19T12:07:24.161607+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 7 [802.11bg] (TSF: 0x00000000:001A1EE9) - 1 (beacon timer 67137815)
2009-03-19T12:07:24.201548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 7 [802.11bg] (TSF: 0x00000000:001ABAFB) - 13 elapsed=39954 usec (40ms since last)
2009-03-19T12:07:24.201558+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 8 [802.11bg] (TSF: 0x00000000:001ABC87) - 1 (beacon timer 71394169)
2009-03-19T12:07:24.241552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 8 [802.11bg] (TSF: 0x00000000:001B589E) - 4 elapsed=39959 usec (40ms since last)
2009-03-19T12:07:24.241563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 9 [802.11bg] (TSF: 0x00000000:001B5A2A) - 1 (beacon timer 71353814)
2009-03-19T12:07:24.281551+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 9 [802.11bg] (TSF: 0x00000000:001BF631) - 3 elapsed=39943 usec (40ms since last)
2009-03-19T12:07:24.281561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 10 [802.11bg] (TSF: 0x00000000:001BF7BD) - 1 (beacon timer 71313474)
2009-03-19T12:07:24.321563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 10 [802.11bg] (TSF: 0x00000000:001C93CD) - 3 elapsed=39952 usec (40ms since last)
2009-03-19T12:07:24.321575+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 11 [802.11bg] (TSF: 0x00000000:001C955A) - 1 (beacon timer 75569830)
2009-03-19T12:07:24.337624+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 11 [802.11bg] (TSF: 0x00000000:001CC82C) - 0 elapsed=13010 usec (16ms since last)
2009-03-19T12:07:24.337636+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 11 channels (TSF 0x001CC9CB:00000000) - 1
2009-03-19T12:07:24.337644+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:24.337650+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337657+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337662+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337669+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337677+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337684+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337692+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337700+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337708+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337716+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337723+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337736+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337749+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:24.337757+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T12:07:24.337765+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:001CD343) - 1 (beacon timer 75553981)
2009-03-19T12:07:24.453575+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:001E8B71) - 0 elapsed=112686 usec (116ms since last)
2009-03-19T12:07:24.453589+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:001E8CFB) - 1 (beacon timer 79737605)
2009-03-19T12:07:24.565568+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:0020452C) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:24.565579+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:002046B6) - 1 (beacon timer 83921226)
2009-03-19T12:07:24.677570+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:0021FEE7) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:24.677609+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:00220071) - 1 (beacon timer 88104847)
2009-03-19T12:07:24.789563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0023B8A2) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:24.789580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0023BA2D) - 1 (beacon timer 92288467)
2009-03-19T12:07:24.905560+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0025725D) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:24.905572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:002573E8) - 1 (beacon timer 96472088)
2009-03-19T12:07:25.017583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:00272C18) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:25.017595+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:00272DA3) - 1 (beacon timer 104952413)
2009-03-19T12:07:25.129548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:0028E5D3) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:25.129591+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:0028E75E) - 1 (beacon timer 109136034)
2009-03-19T12:07:25.241559+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:002A9F8F) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:25.241577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:002AA11C) - 1 (beacon timer 113319652)
2009-03-19T12:07:25.357560+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:002C594C) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:25.357577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:002C5AD9) - 1 (beacon timer 117503271)
2009-03-19T12:07:25.469568+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:002E130A) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:25.469580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:002E1497) - 1 (beacon timer 121686889)
2009-03-19T12:07:25.581580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:002FCCC8) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:25.581619+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:002FCE55) - 1 (beacon timer 125870507)
2009-03-19T12:07:25.697565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:00318686) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:25.697577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:00318813) - 1 (beacon timer 130054125)
2009-03-19T12:07:25.810579+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:00334044) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:25.810591+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x003341E3:00000000) - 1
2009-03-19T12:07:25.810599+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:25.877567+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:25.877578+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877590+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877596+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877602+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877608+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877614+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877624+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877636+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877642+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877647+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:25.877653+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:25.881559+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00345D76) - 1 (beacon timer 138461833)
2009-03-19T12:07:25.894553+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:0034911C) - 0 elapsed=13222 usec (84ms since last)
2009-03-19T12:07:25.894567+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:003492A7) - 1 (beacon timer 138448217)
2009-03-19T12:07:25.909549+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0034C56D) - 1 elapsed=12998 usec (16ms since last)
2009-03-19T12:07:25.909561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0034C6F7) - 1 (beacon timer 138434824)
2009-03-19T12:07:25.949564+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:00356300) - 2 elapsed=39945 usec (40ms since last)
2009-03-19T12:07:25.949576+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0035648C) - 1 (beacon timer 142691188)
2009-03-19T12:07:25.961566+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:00359957) - 0 elapsed=13515 usec (12ms since last)
2009-03-19T12:07:25.961577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00359AE2) - 1 (beacon timer 142677278)
2009-03-19T12:07:25.977552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 5 [802.11bg] (TSF: 0x00000000:0035CD5C) - 1 elapsed=12922 usec (16ms since last)
2009-03-19T12:07:25.977567+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 6 [802.11bg] (TSF: 0x00000000:0035CEE7) - 1 (beacon timer 142663961)
2009-03-19T12:07:26.017543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 6 [802.11bg] (TSF: 0x00000000:00366AF2) - 13 elapsed=39947 usec (40ms since last)
2009-03-19T12:07:26.017556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 7 [802.11bg] (TSF: 0x00000000:00366C7E) - 1 (beacon timer 142623618)
2009-03-19T12:07:26.057576+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 7 [802.11bg] (TSF: 0x00000000:00370893) - 6 elapsed=39957 usec (40ms since last)
2009-03-19T12:07:26.057590+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 8 [802.11bg] (TSF: 0x00000000:00370A1F) - 1 (beacon timer 146879969)
2009-03-19T12:07:26.069552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 8 [802.11bg] (TSF: 0x00000000:00374048) - 0 elapsed=13865 usec (12ms since last)
2009-03-19T12:07:26.069563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 9 [802.11bg] (TSF: 0x00000000:003741D3) - 1 (beacon timer 146865709)
2009-03-19T12:07:26.109552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 9 [802.11bg] (TSF: 0x00000000:0037DDDE) - 3 elapsed=39947 usec (40ms since last)
2009-03-19T12:07:26.109563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 10 [802.11bg] (TSF: 0x00000000:0037DF6A) - 1 (beacon timer 146825365)
2009-03-19T12:07:26.149578+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 10 [802.11bg] (TSF: 0x00000000:00387B72) - 4 elapsed=39944 usec (40ms since last)
2009-03-19T12:07:26.149588+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 11 [802.11bg] (TSF: 0x00000000:00387CFF) - 1 (beacon timer 151081729)
2009-03-19T12:07:26.193613+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 11 [802.11bg] (TSF: 0x00000000:00391903) - 1 elapsed=39940 usec (44ms since last)
2009-03-19T12:07:26.193625+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 11 channels (TSF 0x00391AA3:00000000) - 1
2009-03-19T12:07:26.193631+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:26.193635+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193641+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193652+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193664+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193672+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193680+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193694+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193703+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193710+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193719+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193727+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193735+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193742+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:26.193750+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T12:07:26.193757+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:00392443) - 1 (beacon timer 151038909)
2009-03-19T12:07:26.305580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:003ADC71) - 0 elapsed=112686 usec (112ms since last)
2009-03-19T12:07:26.305592+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:003ADDFB) - 1 (beacon timer 155222533)
2009-03-19T12:07:26.418565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:003C962C) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:26.418580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:003C97B6) - 1 (beacon timer 159406154)
2009-03-19T12:07:26.533570+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:003E4FE7) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:26.533584+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:003E5172) - 1 (beacon timer 163589774)
2009-03-19T12:07:26.645566+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:004009A2) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:26.645580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:00400B2D) - 1 (beacon timer 167773395)
2009-03-19T12:07:26.761544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0041C35D) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:26.761559+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0041C4E8) - 1 (beacon timer 176253720)
2009-03-19T12:07:26.873545+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:00437D18) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:26.873559+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:00437EA3) - 1 (beacon timer 180437341)
2009-03-19T12:07:26.985563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:004536D3) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:26.985581+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:0045385E) - 1 (beacon timer 184620962)
2009-03-19T12:07:27.097548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:0046F08F) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:27.097562+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:0046F21C) - 1 (beacon timer 188804580)
2009-03-19T12:07:27.213565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:0048AA4C) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:27.213577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:0048ABD9) - 1 (beacon timer 192988199)
2009-03-19T12:07:27.325545+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:004A640A) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:27.325565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:004A6597) - 1 (beacon timer 197171817)
2009-03-19T12:07:27.437566+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:004C1DC8) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:27.437580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:004C1F55) - 1 (beacon timer 201355435)
2009-03-19T12:07:27.549544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:004DD786) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:27.549558+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:004DD914) - 1 (beacon timer 205539052)
2009-03-19T12:07:27.665544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:004F9144) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:27.665556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x004F92E3:00000000) - 1
2009-03-19T12:07:27.665564+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:27.733573+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:27.733584+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733597+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733605+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733616+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733629+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733637+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733645+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733652+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733659+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733666+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:27.733671+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:27.738555+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:0050B07E) - 1 (beacon timer 213946242)
2009-03-19T12:07:27.749554+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:0050E410) - 0 elapsed=13202 usec (84ms since last)
2009-03-19T12:07:27.749564+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:0050E59B) - 1 (beacon timer 213932645)
2009-03-19T12:07:27.765549+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:00511901) - 0 elapsed=13158 usec (16ms since last)
2009-03-19T12:07:27.765561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:00511A8B) - 1 (beacon timer 213919092)
2009-03-19T12:07:27.805547+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0051B69C) - 2 elapsed=39953 usec (40ms since last)
2009-03-19T12:07:27.805588+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0051B828) - 1 (beacon timer 218175448)
2009-03-19T12:07:27.817548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:0051EC5A) - 0 elapsed=13362 usec (12ms since last)
2009-03-19T12:07:27.817580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:0051EDE5) - 1 (beacon timer 218161691)
2009-03-19T12:07:27.833551+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 5 [802.11bg] (TSF: 0x00000000:00522618) - 1 elapsed=14387 usec (16ms since last)
2009-03-19T12:07:27.833561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 6 [802.11bg] (TSF: 0x00000000:005227A3) - 1 (beacon timer 218146909)
2009-03-19T12:07:27.873572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 6 [802.11bg] (TSF: 0x00000000:0052C3AF) - 11 elapsed=39948 usec (40ms since last)
2009-03-19T12:07:27.873612+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 7 [802.11bg] (TSF: 0x00000000:0052C53B) - 1 (beacon timer 218106565)
2009-03-19T12:07:27.913541+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 7 [802.11bg] (TSF: 0x00000000:00536144) - 8 elapsed=39945 usec (40ms since last)
2009-03-19T12:07:27.913580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 8 [802.11bg] (TSF: 0x00000000:005362D0) - 1 (beacon timer 222362928)
2009-03-19T12:07:27.953543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 8 [802.11bg] (TSF: 0x00000000:0053FEDB) - 4 elapsed=39947 usec (40ms since last)
2009-03-19T12:07:27.953583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 9 [802.11bg] (TSF: 0x00000000:00540067) - 1 (beacon timer 222322584)
2009-03-19T12:07:27.993540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 9 [802.11bg] (TSF: 0x00000000:00549C7D) - 7 elapsed=39958 usec (40ms since last)
2009-03-19T12:07:27.993579+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 10 [802.11bg] (TSF: 0x00000000:00549E09) - 1 (beacon timer 226578934)
2009-03-19T12:07:28.033553+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 10 [802.11bg] (TSF: 0x00000000:00553A16) - 3 elapsed=39949 usec (40ms since last)
2009-03-19T12:07:28.033589+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 11 [802.11bg] (TSF: 0x00000000:00553BA3) - 1 (beacon timer 226538589)
2009-03-19T12:07:28.049619+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 11 [802.11bg] (TSF: 0x00000000:00556E6F) - 0 elapsed=13004 usec (16ms since last)
2009-03-19T12:07:28.049632+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 11 channels (TSF 0x0055700E:00000000) - 1
2009-03-19T12:07:28.049639+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:28.049645+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049661+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049672+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049687+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049695+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049702+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049710+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049717+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049725+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049733+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049747+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049755+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049762+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:28.049769+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T12:07:28.049777+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:005579C2) - 1 (beacon timer 226522686)
2009-03-19T12:07:28.165571+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:005731F0) - 0 elapsed=112686 usec (116ms since last)
2009-03-19T12:07:28.165583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0057337A) - 1 (beacon timer 230706310)
2009-03-19T12:07:28.277548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:0058EBAB) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:28.277590+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:0058ED35) - 1 (beacon timer 234889931)
2009-03-19T12:07:28.389546+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:005AA566) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:28.389558+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:005AA6F0) - 1 (beacon timer 243370256)
2009-03-19T12:07:28.502582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:005C5F21) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:28.502594+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:005C60AC) - 1 (beacon timer 247553876)
2009-03-19T12:07:28.617569+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:005E18DC) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:28.617609+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:005E1A67) - 1 (beacon timer 251737497)
2009-03-19T12:07:28.729564+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:005FD297) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:28.729576+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:005FD422) - 1 (beacon timer 255921118)
2009-03-19T12:07:28.841563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:00618C52) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:28.841580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:00618DDD) - 1 (beacon timer 260104739)
2009-03-19T12:07:28.957540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:0063460E) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:28.957552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:0063479B) - 1 (beacon timer 264288357)
2009-03-19T12:07:29.069544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:0064FFCB) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:29.069588+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:00650158) - 1 (beacon timer 268471976)
2009-03-19T12:07:29.181544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:0066B989) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:29.181586+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:0066BB16) - 1 (beacon timer 272655594)
2009-03-19T12:07:29.293560+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00687347) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:29.293578+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:006874D4) - 1 (beacon timer 276839212)
2009-03-19T12:07:29.409557+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:006A2D05) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:29.409575+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:006A2E93) - 1 (beacon timer 281022829)
2009-03-19T12:07:29.522545+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:006BE6C3) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:29.522584+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x006BE862:00000000) - 1
2009-03-19T12:07:29.522618+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:29.589574+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:29.589586+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589592+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589598+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589603+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589608+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589614+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589619+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589625+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589630+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589636+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589641+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0x7 [ACTIVE 39]
2009-03-19T12:07:29.589646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:29.594548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:006D0139) - 1 (beacon timer 289431239)
2009-03-19T12:07:29.609542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:006D3BA7) - 1 elapsed=14958 usec (88ms since last)
2009-03-19T12:07:29.609554+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:006D3D32) - 1 (beacon timer 289415886)
2009-03-19T12:07:29.621561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:006D6FF9) - 0 elapsed=12999 usec (12ms since last)
2009-03-19T12:07:29.621576+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:006D7184) - 1 (beacon timer 293699196)
2009-03-19T12:07:29.633540+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:006DA4D6) - 0 elapsed=13138 usec (12ms since last)
2009-03-19T12:07:29.633552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:006DA661) - 1 (beacon timer 293685663)
2009-03-19T12:07:29.649556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:006DD9BC) - 0 elapsed=13147 usec (16ms since last)
2009-03-19T12:07:29.649570+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:006DDB47) - 1 (beacon timer 293672121)
2009-03-19T12:07:29.689568+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 5 [802.11bg] (TSF: 0x00000000:006E775A) - 5 elapsed=39955 usec (40ms since last)
2009-03-19T12:07:29.689580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 6 [802.11bg] (TSF: 0x00000000:006E78E6) - 1 (beacon timer 293631770)
2009-03-19T12:07:29.729547+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 6 [802.11bg] (TSF: 0x00000000:006F14F2) - 10 elapsed=39948 usec (40ms since last)
2009-03-19T12:07:29.729557+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 7 [802.11bg] (TSF: 0x00000000:006F167E) - 1 (beacon timer 297888130)
2009-03-19T12:07:29.769563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 7 [802.11bg] (TSF: 0x00000000:006FB284) - 7 elapsed=39942 usec (40ms since last)
2009-03-19T12:07:29.769572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 8 [802.11bg] (TSF: 0x00000000:006FB410) - 1 (beacon timer 297847792)
2009-03-19T12:07:29.809553+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 8 [802.11bg] (TSF: 0x00000000:00705022) - 6 elapsed=39954 usec (40ms since last)
2009-03-19T12:07:29.809563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 9 [802.11bg] (TSF: 0x00000000:007051AE) - 1 (beacon timer 297807441)
2009-03-19T12:07:29.849551+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 9 [802.11bg] (TSF: 0x00000000:0070EDB8) - 5 elapsed=39946 usec (40ms since last)
2009-03-19T12:07:29.849562+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 10 [802.11bg] (TSF: 0x00000000:0070EF44) - 1 (beacon timer 302063803)
2009-03-19T12:07:29.889555+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 10 [802.11bg] (TSF: 0x00000000:00718B4D) - 3 elapsed=39945 usec (40ms since last)
2009-03-19T12:07:29.889570+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 11 [802.11bg] (TSF: 0x00000000:00718CDA) - 1 (beacon timer 302023462)
2009-03-19T12:07:29.905636+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 11 [802.11bg] (TSF: 0x00000000:0071C587) - 1 elapsed=14509 usec (16ms since last)
2009-03-19T12:07:29.905650+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 11 channels (TSF 0x0071C725:00000000) - 1
2009-03-19T12:07:29.905658+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start indirect scan.
2009-03-19T12:07:29.905665+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905672+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905680+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905685+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905692+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905699+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905728+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905737+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905758+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905767+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905787+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905796+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905817+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0x6 [PASSIVE 110]
2009-03-19T12:07:29.905839+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T12:07:29.909555+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:0071D09E) - 1 (beacon timer 302006114)
2009-03-19T12:07:30.021543+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:007388CC) - 0 elapsed=112686 usec (116ms since last)
2009-03-19T12:07:30.021556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:00738A56) - 1 (beacon timer 306189738)
2009-03-19T12:07:30.133544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:00754287) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:30.133559+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00754411) - 1 (beacon timer 314670063)
2009-03-19T12:07:30.246557+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:0076FC42) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:30.246571+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:0076FDCC) - 1 (beacon timer 318853684)
2009-03-19T12:07:30.361569+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0078B5FD) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:30.361583+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0078B788) - 1 (beacon timer 323037304)
2009-03-19T12:07:30.473564+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:007A6FB8) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:30.473582+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:007A7143) - 1 (beacon timer 327220925)
2009-03-19T12:07:30.585561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:007C2973) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:30.585579+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:007C2AFE) - 1 (beacon timer 331404546)
2009-03-19T12:07:30.701542+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:007DE32E) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T12:07:30.701554+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:007DE4B9) - 1 (beacon timer 335588167)
2009-03-19T12:07:30.813545+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:007F9CEA) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:30.813559+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:007F9E77) - 1 (beacon timer 339771785)
2009-03-19T12:07:30.925561+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:008156A7) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:30.925578+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:00815834) - 1 (beacon timer 343955404)
2009-03-19T12:07:31.037541+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:00831065) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:31.037554+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:008311F2) - 1 (beacon timer 348139022)
2009-03-19T12:07:31.153566+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:0084CA23) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:31.153580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:0084CBB1) - 1 (beacon timer 352322639)
2009-03-19T12:07:31.265562+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:008683E1) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:31.265581+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0086856E) - 1 (beacon timer 360802962)
2009-03-19T12:07:31.378548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:00883D9F) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:31.378563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00883F3E:00000000) - 1
2009-03-19T12:07:31.378571+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan

[-- Attachment #3: nopatch.pass --]
[-- Type: application/octet-stream, Size: 13006 bytes --]

2009-03-19T12:07:08.017530+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T12:07:08.017616+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T12:07:08.622582+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T12:07:08.622596+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622603+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622610+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622615+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622621+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622628+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622639+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622645+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622652+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622658+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622664+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.622670+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:08.622677+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001CFF) - 1 (beacon timer 94977)
2009-03-19T12:07:08.622683+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T12:07:08.625518+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x000027E7:00000000) - 2
2009-03-19T12:07:08.625539+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:08.630577+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T12:07:08.630587+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630593+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630606+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630612+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630617+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630623+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630629+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630634+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630640+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630646+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630651+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T12:07:08.630663+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T12:07:08.630669+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00003ABA) - 1 (beacon timer 87366)
2009-03-19T12:07:08.645546+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00007245) - 0 elapsed=14219 usec (20ms since last)
2009-03-19T12:07:08.645562+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:000073D0) - 1 (beacon timer 72752)
2009-03-19T12:07:08.661567+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000ABF4) - 0 elapsed=14372 usec (16ms since last)
2009-03-19T12:07:08.661581+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000AD7F) - 1 (beacon timer 57985)
2009-03-19T12:07:08.677548+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:0000E4AF) - 1 elapsed=14128 usec (16ms since last)
2009-03-19T12:07:08.677563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:0000E63A) - 1 (beacon timer 43462)
2009-03-19T12:07:08.689541+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:00011EF4) - 1 elapsed=14522 usec (12ms since last)
2009-03-19T12:07:08.689552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:0001207F) - 1 (beacon timer 28545)
2009-03-19T12:07:08.725562+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T12:07:08.729605+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T12:07:08.729613+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T12:07:08.729620+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729627+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729634+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729641+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729649+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729656+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729663+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729670+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729677+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729685+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729692+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729699+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729707+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T12:07:08.729714+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T12:07:08.729722+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:00001711) - 1 (beacon timer 96495)
2009-03-19T12:07:08.845544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CF3E) - 0 elapsed=112685 usec (156ms since last)
2009-03-19T12:07:08.845565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001D0C9) - 1 (beacon timer 4280119)
2009-03-19T12:07:08.957552+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:000388F9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:08.957567+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:00038A83) - 1 (beacon timer 8463741)
2009-03-19T12:07:09.069565+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:000542B4) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:09.069585+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:0005443E) - 1 (beacon timer 12647362)
2009-03-19T12:07:09.185571+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FC6F) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:09.185584+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FDFA) - 1 (beacon timer 16830982)
2009-03-19T12:07:09.297572+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B62A) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:09.297586+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B7B5) - 1 (beacon timer 21014603)
2009-03-19T12:07:09.409544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6FE5) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:09.409557+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7170) - 1 (beacon timer 25198224)
2009-03-19T12:07:09.521563+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C29A0) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:09.521579+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C2B2B) - 1 (beacon timer 29381845)
2009-03-19T12:07:09.637544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE35C) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:09.637557+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE4E9) - 1 (beacon timer 33565463)
2009-03-19T12:07:09.749544+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9D19) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:09.749556+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9EA6) - 1 (beacon timer 37749082)
2009-03-19T12:07:09.861569+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:001156D7) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:09.861584+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:00115864) - 1 (beacon timer 46229404)
2009-03-19T12:07:09.973566+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00131095) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T12:07:09.973580+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:00131222) - 1 (beacon timer 50413022)
2009-03-19T12:07:10.089562+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014CA53) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T12:07:10.089577+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CBE1) - 1 (beacon timer 54596639)
2009-03-19T12:07:10.201578+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:00168411) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T12:07:10.201592+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x001685B0:00000000) - 1
2009-03-19T12:07:10.201601+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:10.549556+08:00 boston kernel: ieee80211 phy0: U iwl_mac_hw_scan scan rejected: within next scan period
2009-03-19T12:07:10.549570+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T12:07:10.576024+08:00 boston named[1666]: the working directory is not writable

[-- Attachment #4: patched.pass --]
[-- Type: application/octet-stream, Size: 13004 bytes --]

2009-03-19T11:58:10.183807+08:00 boston kernel: iwlagn: index 0 not used in uCode key table.
2009-03-19T11:58:10.183820+08:00 boston kernel: mac80211-phy0: failed to remove key (0, ff:ff:ff:ff:ff:ff) from hardware (-16)
2009-03-19T11:58:10.759843+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T11:58:10.759859+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759875+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759881+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759889+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759899+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759907+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759914+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759919+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759926+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759934+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759941+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.759949+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T11:58:10.759957+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00001B47) - 1 (beacon timer 95417)
2009-03-19T11:58:10.759965+08:00 boston kernel: ieee80211 phy0: U iwl_scan_cancel Queuing scan abort.
2009-03-19T11:58:10.763835+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 0 channels (TSF 0x00002643:00000000) - 2
2009-03-19T11:58:10.763847+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T11:58:10.763863+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T11:58:10.763868+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=1 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763874+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=2 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763881+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=3 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763888+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=4 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763896+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=5 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763908+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=6 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763916+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=7 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763923+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=8 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763930+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=9 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763937+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=10 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763943+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=11 prob=0xF [ACTIVE 42]
2009-03-19T11:58:10.763948+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 11 
2009-03-19T11:58:10.764783+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 1 [802.11bg] (TSF: 0x00000000:00002FA2) - 1 (beacon timer 90206)
2009-03-19T11:58:10.779806+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 1 [802.11bg] (TSF: 0x00000000:00006CD1) - 1 elapsed=15663 usec (16ms since last)
2009-03-19T11:58:10.783784+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 2 [802.11bg] (TSF: 0x00000000:00006E5C) - 1 (beacon timer 74148)
2009-03-19T11:58:10.795804+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 2 [802.11bg] (TSF: 0x00000000:0000A70E) - 0 elapsed=14514 usec (16ms since last)
2009-03-19T11:58:10.795815+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 3 [802.11bg] (TSF: 0x00000000:0000A899) - 1 (beacon timer 59239)
2009-03-19T11:58:10.839802+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 3 [802.11bg] (TSF: 0x00000000:000150A7) - 3 elapsed=43022 usec (44ms since last)
2009-03-19T11:58:10.839812+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 4 [802.11bg] (TSF: 0x00000000:00015233) - 1 (beacon timer 15821)
2009-03-19T11:58:10.856828+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 4 [802.11bg] (TSF: 0x00000000:00018D1F) - 1 elapsed=15084 usec (16ms since last)
2009-03-19T11:58:10.856841+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 5 [802.11bg] (TSF: 0x00000000:00018EAA) - 1 (beacon timer 342)
2009-03-19T11:58:10.863804+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 4 channels (TSF 0x000001EE:00000000) - 2
2009-03-19T11:58:10.867888+08:00 boston kernel: iwlagn: Error sending TX power (-11)
2009-03-19T11:58:10.867896+08:00 boston kernel: ieee80211 phy0: U iwl_bg_request_scan Start direct scan for 'sdg2088a88'
2009-03-19T11:58:10.867901+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=36 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867908+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=40 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867914+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=44 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867923+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=48 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867930+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=52 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867937+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=56 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867945+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=60 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867957+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=64 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867970+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=149 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867978+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=153 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867985+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=157 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867992+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=161 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.867999+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan Scanning ch=165 prob=0xE [PASSIVE 110]
2009-03-19T11:58:10.868006+08:00 boston kernel: ieee80211 phy0: U iwl_get_channels_for_scan total channels to scan 13 
2009-03-19T11:58:10.868014+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 36 [802.11a] (TSF: 0x00000000:000015A9) - 1 (beacon timer 96855)
2009-03-19T11:58:10.983807+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 36 [802.11a] (TSF: 0x00000000:0001CDD6) - 0 elapsed=112685 usec (128ms since last)
2009-03-19T11:58:10.983821+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 40 [802.11a] (TSF: 0x00000000:0001CF61) - 1 (beacon timer 4280479)
2009-03-19T11:58:11.095794+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 40 [802.11a] (TSF: 0x00000000:00038791) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T11:58:11.095843+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 44 [802.11a] (TSF: 0x00000000:0003891B) - 1 (beacon timer 8464101)
2009-03-19T11:58:11.207816+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 44 [802.11a] (TSF: 0x00000000:0005414C) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T11:58:11.207835+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 48 [802.11a] (TSF: 0x00000000:000542D6) - 1 (beacon timer 12647722)
2009-03-19T11:58:11.319813+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 48 [802.11a] (TSF: 0x00000000:0006FB07) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T11:58:11.319830+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 52 [802.11a] (TSF: 0x00000000:0006FC92) - 1 (beacon timer 16831342)
2009-03-19T11:58:11.435834+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 52 [802.11a] (TSF: 0x00000000:0008B4C2) - 0 elapsed=112688 usec (116ms since last)
2009-03-19T11:58:11.435846+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 56 [802.11a] (TSF: 0x00000000:0008B64D) - 1 (beacon timer 21014963)
2009-03-19T11:58:11.547816+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 56 [802.11a] (TSF: 0x00000000:000A6E7D) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T11:58:11.547859+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 60 [802.11a] (TSF: 0x00000000:000A7008) - 1 (beacon timer 25198584)
2009-03-19T11:58:11.659812+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 60 [802.11a] (TSF: 0x00000000:000C2838) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T11:58:11.659824+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 64 [802.11a] (TSF: 0x00000000:000C29C3) - 1 (beacon timer 29382205)
2009-03-19T11:58:11.775812+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 64 [802.11a] (TSF: 0x00000000:000DE1F4) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T11:58:11.775824+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 149 [802.11a] (TSF: 0x00000000:000DE381) - 1 (beacon timer 33565823)
2009-03-19T11:58:11.887791+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 149 [802.11a] (TSF: 0x00000000:000F9BB1) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T11:58:11.887803+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 153 [802.11a] (TSF: 0x00000000:000F9D3E) - 1 (beacon timer 37749442)
2009-03-19T11:58:11.999801+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 153 [802.11a] (TSF: 0x00000000:0011556F) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T11:58:11.999813+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 157 [802.11a] (TSF: 0x00000000:001156FC) - 1 (beacon timer 46229764)
2009-03-19T11:58:12.111792+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 157 [802.11a] (TSF: 0x00000000:00130F2D) - 0 elapsed=112689 usec (112ms since last)
2009-03-19T11:58:12.111805+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 161 [802.11a] (TSF: 0x00000000:001310BA) - 1 (beacon timer 50413382)
2009-03-19T11:58:12.227818+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 161 [802.11a] (TSF: 0x00000000:0014C8EB) - 0 elapsed=112689 usec (116ms since last)
2009-03-19T11:58:12.227830+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_start_notif Scan start: 165 [802.11a] (TSF: 0x00000000:0014CA79) - 1 (beacon timer 54596999)
2009-03-19T11:58:12.339767+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_results_notif Scan ch.res: 165 [802.11a] (TSF: 0x00000000:001682A9) - 0 elapsed=112688 usec (112ms since last)
2009-03-19T11:58:12.339779+08:00 boston kernel: ieee80211 phy0: I iwl_rx_scan_complete_notif Scan complete: 13 channels (TSF 0x00168448:00000000) - 1
2009-03-19T11:58:12.339787+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T11:58:12.687732+08:00 boston kernel: ieee80211 phy0: U iwl_mac_hw_scan scan rejected: within next scan period
2009-03-19T11:58:12.687744+08:00 boston kernel: ieee80211 phy0: U iwl_bg_scan_completed SCAN complete scan
2009-03-19T11:58:12.713724+08:00 boston named[1666]: the working directory is not writable

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Thu, Mar 19, 2009 at 10:58 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> I've tracked down to the sequence of iwconfig that causes it to fail.
> This loop does not work at all without John's patch , but will work
> 100% when patched.
> This loop only works 8 of 10 times with/without the patch.

Ignore the above loop thing. The cause seems to be this one instead.


# this needs patch to work ...
iwconfig wlan0 mode Managed
ifconfig wlan0 up
iwconfig wlan0 essid xxx
iwconfig wlan0 key restricted xxx
iwconfig wlan0 ap auto channel auto


# this works with patch ...
iwconfig wlan0 mode Managed essid xxx key restricted xxx
ifconfig wlan0 up
iwconfig wlan0 ap auto channel auto

It looks the placement of "ifconfig" matters. But works on 2.6.28-rc3.


Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Thu, Mar 19, 2009 at 10:58 AM, Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I've tracked down to the sequence of iwconfig that causes it to fail.
> This loop does not work at all without John's patch , but will work
> 100% when patched.
> This loop only works 8 of 10 times with/without the patch.

Ignore the above loop thing. The cause seems to be this one instead.


# this needs patch to work ...
iwconfig wlan0 mode Managed
ifconfig wlan0 up
iwconfig wlan0 essid xxx
iwconfig wlan0 key restricted xxx
iwconfig wlan0 ap auto channel auto


# this works with patch ...
iwconfig wlan0 mode Managed essid xxx key restricted xxx
ifconfig wlan0 up
iwconfig wlan0 ap auto channel auto

It looks the placement of "ifconfig" matters. But works on 2.6.28-rc3.


Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:

> Ignore the above loop thing. The cause seems to be this one instead.
> 
> 
> # this needs patch to work ...
> iwconfig wlan0 mode Managed
> ifconfig wlan0 up
> iwconfig wlan0 essid xxx
> iwconfig wlan0 key restricted xxx
> iwconfig wlan0 ap auto channel auto

If you swap the key and essid lines, it will probably always work. But
I've yet to analyse your data to see why it doesn't in the other case.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [Bug #12765] i915 VT switch with AIGLX causes X lock up

[Rafael J. Wysocki]

On Monday 16 March 2009, Sitsofe Wheeler wrote:
> On Sat, Mar 14, 2009 at 08:05:32PM +0100, Rafael J. Wysocki wrote:
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
> > Subject		: i915 VT switch with AIGLX causes X lock up
> > Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
> > Date		: 2009-02-21 15:38 (22 days old)
> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
> > References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4
> 
> Still here in 2.6.29-rc8.

Thanks for the update.

Rafael

Re: [Bug #12574] possible circular locking dependency detected

[Rafael J. Wysocki]

On Monday 16 March 2009, Michael S. Tsirkin wrote:
> On Sat, Mar 14, 2009 at 08:05:29PM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.28.  Please verify if it still should be listed and let me know
> > (either way).
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
> > Subject		: possible circular locking dependency detected
> > Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
> > Date		: 2009-01-29 11:35 (45 days old)
> > References	: http://lkml.org/lkml/2009/2/9/205
> > 
> 
> It's still there in rc8.

Thanks for the update.

Rafael

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[John W. Linville]

On Thu, Mar 19, 2009 at 10:38:54AM +0100, Johannes Berg wrote:
> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
> 
> > Ignore the above loop thing. The cause seems to be this one instead.
> > 
> > 
> > # this needs patch to work ...
> > iwconfig wlan0 mode Managed
> > ifconfig wlan0 up
> > iwconfig wlan0 essid xxx
> > iwconfig wlan0 key restricted xxx
> > iwconfig wlan0 ap auto channel auto
> 
> If you swap the key and essid lines, it will probably always work. But
> I've yet to analyse your data to see why it doesn't in the other case.

That is what I was going to suggest.  I go so far as to say that you
should set everything else before doing the "iwconfig wlan0 essid
xxx" bit.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28)

[Frans Pop]

John W. Linville wrote:
> On Thu, Mar 19, 2009 at 10:38:54AM +0100, Johannes Berg wrote:
>> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>> > # this needs patch to work ...
>> > iwconfig wlan0 mode Managed
>> > ifconfig wlan0 up
>> > iwconfig wlan0 essid xxx
>> > iwconfig wlan0 key restricted xxx
>> > iwconfig wlan0 ap auto channel auto
>> 
>> If you swap the key and essid lines, it will probably always work. But
>> I've yet to analyse your data to see why it doesn't in the other case.
> 
> That is what I was going to suggest.  I go so far as to say that you
> should set everything else before doing the "iwconfig wlan0 essid
> xxx" bit.

Mostly just curious, but is that actually required by some wireless 
standard? If not, is it really reasonable to ask userland to do things in 
that particular order?

Reason I ask is that for example when writing wireless support for e.g. a 
distro installation system, it seems most logical to *first* ask the user 
what network (ESSID) he wants to connect to. Next to check if we can 
connect to that network without additional authentication and only then, 
if needed, ask for keys etc.
If it's not possible to set that info in that logical order that seems 
rather restrictive to me and would probably mean that you'd have to reset 
AP, ESSID and possibly other settings before each incremental attempt.

Cheers,
FJP

Re: Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28)

[John W. Linville]

On Thu, Mar 19, 2009 at 04:02:56PM +0100, Frans Pop wrote:
> John W. Linville wrote:
> > On Thu, Mar 19, 2009 at 10:38:54AM +0100, Johannes Berg wrote:
> >> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
> >> > # this needs patch to work ...
> >> > iwconfig wlan0 mode Managed
> >> > ifconfig wlan0 up
> >> > iwconfig wlan0 essid xxx
> >> > iwconfig wlan0 key restricted xxx
> >> > iwconfig wlan0 ap auto channel auto
> >> 
> >> If you swap the key and essid lines, it will probably always work. But
> >> I've yet to analyse your data to see why it doesn't in the other case.
> > 
> > That is what I was going to suggest.  I go so far as to say that you
> > should set everything else before doing the "iwconfig wlan0 essid
> > xxx" bit.
> 
> Mostly just curious, but is that actually required by some wireless 
> standard? If not, is it really reasonable to ask userland to do things in 
> that particular order?
> 
> Reason I ask is that for example when writing wireless support for e.g. a 
> distro installation system, it seems most logical to *first* ask the user 
> what network (ESSID) he wants to connect to. Next to check if we can 
> connect to that network without additional authentication and only then, 
> if needed, ask for keys etc.
> If it's not possible to set that info in that logical order that seems 
> rather restrictive to me and would probably mean that you'd have to reset 
> AP, ESSID and possibly other settings before each incremental attempt.

You can ask the user for the data in whatever order you like, but
when you are done collecting it you should issue the "iwconfig wlan0
essid xxx" command (or execute the SIOCSIWESSID ioctl) last.  IMHO,
it is silly to even bother setting the SSID before you have set any
required key or (if you so choose) selecting an AP or channel.

This is a limitation of the wireless extensions API -- nothing in
the API really defines when an association should be triggered.
The mac80211 component uses the setting of the SSID as the trigger
for association.  AFAIK, this ordering should work with all other
drivers as well.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

Re: Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28)

[Jeff Chua]

On Thu, Mar 19, 2009 at 11:24 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Thu, Mar 19, 2009 at 04:02:56PM +0100, Frans Pop wrote:
>> John W. Linville wrote:
>> > On Thu, Mar 19, 2009 at 10:38:54AM +0100, Johannes Berg wrote:
>> >> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>> >> > # this needs patch to work ...
>> >> > iwconfig wlan0 mode Managed
>> >> > ifconfig wlan0 up
>> >> > iwconfig wlan0 essid xxx
>> >> > iwconfig wlan0 key restricted xxx
>> >> > iwconfig wlan0 ap auto channel auto
>> >>
>> >> If you swap the key and essid lines, it will probably always work.

I just discovered that  "iwconfig wlan0 ap auto channel auto" is the
one causing the problem on 2.6.29-rc8. Remove the line and it'll
associate to the AP. Just tried on two different APs a few times, and
it seems to behave that way. If I execute the "auto" command, it'll
fail to associate, but works fine with the patch.

Jeff.

Re: Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28)

[Jeff Chua]

On Thu, Mar 19, 2009 at 11:24 PM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Thu, Mar 19, 2009 at 04:02:56PM +0100, Frans Pop wrote:
>> John W. Linville wrote:
>> > On Thu, Mar 19, 2009 at 10:38:54AM +0100, Johannes Berg wrote:
>> >> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>> >> > # this needs patch to work ...
>> >> > iwconfig wlan0 mode Managed
>> >> > ifconfig wlan0 up
>> >> > iwconfig wlan0 essid xxx
>> >> > iwconfig wlan0 key restricted xxx
>> >> > iwconfig wlan0 ap auto channel auto
>> >>
>> >> If you swap the key and essid lines, it will probably always work.

I just discovered that  "iwconfig wlan0 ap auto channel auto" is the
one causing the problem on 2.6.29-rc8. Remove the line and it'll
associate to the AP. Just tried on two different APs a few times, and
it seems to behave that way. If I execute the "auto" command, it'll
fail to associate, but works fine with the patch.

Jeff.

Re: Required sequence to set wireless parameters? (was: 2.6.29-rc8: Reported regressions from 2.6.28)

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

On Thu, 2009-03-19 at 16:02 +0100, Frans Pop wrote:

> Mostly just curious, but is that actually required by some wireless 
> standard? If not, is it really reasonable to ask userland to do things in 
> that particular order?

Wext is a mess, and we've known that for a long time... But no, the
sequence should _not_ be required, it's just _easier_ for the kernel,
and as such has a better probability of succeeding if there are
problems, it should still work though.

However, one thing that will _not_ work is this:

iwconfig wlan0 essid xyz
iwconfig wlan0 key s:xyz

you still need

iwconfig wlan0 ap any

or anything similar after setting the key to trigger the kernel to do
something.

> Reason I ask is that for example when writing wireless support for e.g. a 
> distro installation system, it seems most logical to *first* ask the user 
> what network (ESSID) he wants to connect to. Next to check if we can 
> connect to that network without additional authentication and only then, 
> if needed, ask for keys etc.
> If it's not possible to set that info in that logical order that seems 
> rather restrictive to me and would probably mean that you'd have to reset 
> AP, ESSID and possibly other settings before each incremental attempt.

That's a pretty wrong argument, nothing says your software cannot
collect all the information and then give it to the kernel at once
later, I think... In fact, this is required anyway when you use RSN or
WPA (wpa_supplicant needs all information at once), for example.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

On Thu, 2009-03-19 at 12:23 +0800, Jeff Chua wrote:

> *** this is in nopatch.fail ***
> 
> 2009-03-19T12:07:22.437578+08:00 boston kernel: ieee80211 phy0: U
> iwl_bg_request_scan Start direct scan for 'sdg2088a88'
> 
> 2009-03-19T12:07:24.337644+08:00 boston kernel: ieee80211 phy0: U
> iwl_bg_request_scan Start indirect scan.
> 
> 
> For the passing run, it's always "direct scan".

That's because of your 'iwlist wlan0 scan' command, it triggers an
indirect scan, if you did 'iwlist wlan0 scan essid sdg2088a88' you would
get a direct scan there. It's always 'direct' for when it passes because
then you don't get to the point where you scan again, I think.

All in all, I don't see much in the logs, it seems to be behaving
properly and asking for a direct scan when you set the essid. The kernel
will not try to connect to an encrypted network before you give it a
key, but "iwconfig wlan0 ap any" should trigger the association
process...

Can you do something else for me?

Get iw (some distros ship it, or see wireless.kernel.org) and enter this
command:
	iw dev wlan0 interface add moni0 type monitor flags none

Then,
	ip link set moni0 up

Start a capture:
	iwevent > /tmp/event.txt

Now do, in a separate shell:
	iwconfig wlan0 essid ...
	iwconfig wlan0 key ...

_Now_ start tcpdump:
	tcpdump -i moni0 -s 10000 -w /tmp/dump.pkt

and in a separate shell do:
	iwlist wlan0 scan last > /tmp/scan.txt ; iwconfig wlan0 ap any

(this is important in one command so it's timed closed together)

Send me the contents of all the files from a failed run please.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: Required sequence to set wireless parameters?

[Frans Pop]

On Thursday 19 March 2009, Johannes Berg wrote:
> Wext is a mess, and we've known that for a long time... But no, the
> sequence should _not_ be required, it's just _easier_ for the kernel,
> and as such has a better probability of succeeding if there are
> problems, it should still work though.
>
> However, one thing that will _not_ work is this:
> iwconfig wlan0 essid xyz
> iwconfig wlan0 key s:xyz
>
> you still need:
> iwconfig wlan0 ap any
>
> or anything similar after setting the key to trigger the kernel to do
> something.

OK. Thanks for the info.

> > Reason I ask is that for example when writing wireless support for
> > e.g. a distro installation system, it seems most logical to *first*
> > ask the user what network (ESSID) he wants to connect to. Next to
> > check if we can connect to that network without additional
> > authentication and only then, if needed, ask for keys etc.
> > If it's not possible to set that info in that logical order that
> > seems rather restrictive to me and would probably mean that you'd
> > have to reset AP, ESSID and possibly other settings before each
> > incremental attempt.
>
> That's a pretty wrong argument, nothing says your software cannot
> collect all the information and then give it to the kernel at once
> later, I think... In fact, this is required anyway when you use RSN or
> WPA (wpa_supplicant needs all information at once), for example.

Well, the thing is that we'll already have tried just setting essid to 
check if it's an open network. However, I can see the point of needing to 
set the essid _again_ after asking the key info and setting that.

I can also see how you might have to unset some settings in some cases, 
for example if the NIC has already associated with the wrong network 
(e.g. because there's a totally open network in range).

Our current logic (in Debian Installer) definitely needs improving and 
these pointers will help. Thanks.

Re: Required sequence to set wireless parameters?

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]

On Thu, 2009-03-19 at 20:24 +0100, Frans Pop wrote:

> > > Reason I ask is that for example when writing wireless support for
> > > e.g. a distro installation system, it seems most logical to *first*
> > > ask the user what network (ESSID) he wants to connect to. Next to
> > > check if we can connect to that network without additional
> > > authentication and only then, if needed, ask for keys etc.
> > > If it's not possible to set that info in that logical order that
> > > seems rather restrictive to me and would probably mean that you'd
> > > have to reset AP, ESSID and possibly other settings before each
> > > incremental attempt.
> >
> > That's a pretty wrong argument, nothing says your software cannot
> > collect all the information and then give it to the kernel at once
> > later, I think... In fact, this is required anyway when you use RSN or
> > WPA (wpa_supplicant needs all information at once), for example.
> 
> Well, the thing is that we'll already have tried just setting essid to 
> check if it's an open network. However, I can see the point of needing to 
> set the essid _again_ after asking the key info and setting that.

Ah.

> I can also see how you might have to unset some settings in some cases, 
> for example if the NIC has already associated with the wrong network 
> (e.g. because there's a totally open network in range).

No, there should be no need for that really, an
	iwconfig wlan0 ap any
should always make it associate with the current settings.

Now, this thread is about why it doesn't for Jeff :)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: Required sequence to set wireless parameters?

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]

On Thu, 2009-03-19 at 20:24 +0100, Frans Pop wrote:

> > > Reason I ask is that for example when writing wireless support for
> > > e.g. a distro installation system, it seems most logical to *first*
> > > ask the user what network (ESSID) he wants to connect to. Next to
> > > check if we can connect to that network without additional
> > > authentication and only then, if needed, ask for keys etc.
> > > If it's not possible to set that info in that logical order that
> > > seems rather restrictive to me and would probably mean that you'd
> > > have to reset AP, ESSID and possibly other settings before each
> > > incremental attempt.
> >
> > That's a pretty wrong argument, nothing says your software cannot
> > collect all the information and then give it to the kernel at once
> > later, I think... In fact, this is required anyway when you use RSN or
> > WPA (wpa_supplicant needs all information at once), for example.
> 
> Well, the thing is that we'll already have tried just setting essid to 
> check if it's an open network. However, I can see the point of needing to 
> set the essid _again_ after asking the key info and setting that.

Ah.

> I can also see how you might have to unset some settings in some cases, 
> for example if the NIC has already associated with the wrong network 
> (e.g. because there's a totally open network in range).

No, there should be no need for that really, an
	iwconfig wlan0 ap any
should always make it associate with the current settings.

Now, this thread is about why it doesn't for Jeff :)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Thu, Mar 19, 2009 at 5:38 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>
>> Ignore the above loop thing. The cause seems to be this one instead.
>>
>>
>> # this needs patch to work ...
>> iwconfig wlan0 mode Managed
>> ifconfig wlan0 up
>> iwconfig wlan0 essid xxx
>> iwconfig wlan0 key restricted xxx
>> iwconfig wlan0 ap auto channel auto
>
> If you swap the key and essid lines, it will probably always work. But
> I've yet to analyse your data to see why it doesn't in the other case.

Doesn't. Taking away "hiwconfig wlan0 ap auto channel auto" makes it works.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Thu, Mar 19, 2009 at 5:38 PM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>
>> Ignore the above loop thing. The cause seems to be this one instead.
>>
>>
>> # this needs patch to work ...
>> iwconfig wlan0 mode Managed
>> ifconfig wlan0 up
>> iwconfig wlan0 essid xxx
>> iwconfig wlan0 key restricted xxx
>> iwconfig wlan0 ap auto channel auto
>
> If you swap the key and essid lines, it will probably always work. But
> I've yet to analyse your data to see why it doesn't in the other case.

Doesn't. Taking away "hiwconfig wlan0 ap auto channel auto" makes it works.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Fri, Mar 20, 2009 at 12:55 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Thu, Mar 19, 2009 at 5:38 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> On Thu, 2009-03-19 at 12:49 +0800, Jeff Chua wrote:
>>
>>> Ignore the above loop thing. The cause seems to be this one instead.
>>>
>>>
>>> # this needs patch to work ...
>>> iwconfig wlan0 mode Managed
>>> ifconfig wlan0 up
>>> iwconfig wlan0 essid xxx
>>> iwconfig wlan0 key restricted xxx
>>> iwconfig wlan0 ap auto channel auto
>>
>> If you swap the key and essid lines, it will probably always work. But
>> I've yet to analyse your data to see why it doesn't in the other case.
>
> Doesn't. Taking away "hiwconfig wlan0 ap auto channel auto" makes it works.

More discoveries...

It seems position of "ifconfig wlan0 up" matters

1) It can't be before iwconfig which will result in "SET failed on
device wlan0 ; Device or resource busy".

2) _Before_ "essid" and "key" settings. "ap auto channel auto" MUST NOT BE SET.

3) _After_ "essid" and "key". Ensure all iwconfig settings comes
before "ifconfig".


So, it seems "ifconfig" must be done as the last stage.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]

On Fri, 2009-03-20 at 12:55 +0800, Jeff Chua wrote:

> >> # this needs patch to work ...
> >> iwconfig wlan0 mode Managed
> >> ifconfig wlan0 up
> >> iwconfig wlan0 essid xxx
> >> iwconfig wlan0 key restricted xxx
> >> iwconfig wlan0 ap auto channel auto
> >
> > If you swap the key and essid lines, it will probably always work. But
> > I've yet to analyse your data to see why it doesn't in the other case.
> 
> Doesn't. Taking away "hiwconfig wlan0 ap auto channel auto" makes it works.

That's a little weird, but not entirely, you probably manage to cut it
short in the middle of the assoc process when issuing the auto command.

> It seems position of "ifconfig wlan0 up" matters
> 
> 1) It can't be before iwconfig which will result in "SET failed on
> device wlan0 ; Device or resource busy".
> 
> 2) _Before_ "essid" and "key" settings. "ap auto channel auto" MUST
> NOT BE SET.
> 
> 3) _After_ "essid" and "key". Ensure all iwconfig settings comes
> before "ifconfig".
> 
> 
> So, it seems "ifconfig" must be done as the last stage.

This, however, is completely strange. You should always set the
interface up before doing anything with it. wext allows you to do it the
other way around, but that's not quite natural since without it being up
you cannot even scan.

However, -EBUSY isn't returned anywhere in mac80211, and I don't see the
driver passing it out either. So your point 1) confuses me. Can you
explain that a little more?

As for 2), that is very very strange since ap auto channel auto is the
default, so saying that before you do anything else should do anything
at all.

I suspect something is going on in the driver because the ifconfig order
matters and for mac80211, it shouldn't make a difference when the state
machine is really started. I'll probably need to try to reproduce this,
but to be honest between the varying failure modes, undefined wireless
extensions semantics, etc. I'm not very confident I can.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Fri, Mar 20, 2009 at 4:32 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> 1) It can't be before iwconfig which will result in "SET failed on
> device wlan0 ; Device or resource busy".
>  So your point 1) confuses me. Can you
> explain that a little more?

This is what happened ...

# modprobe -r iwlagn
# modprobe iwlagn
# ifconfig wlan0 up
# iwconfig wlan0 mode Managed
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Device or resource busy.


> As for 2), that is very very strange since ap auto channel auto is the
> default, so saying that before you do anything else should do anything
> at all.
>
> I suspect something is going on in the driver because the ifconfig order
> matters and for mac80211, it shouldn't make a difference when the state
> machine is really started. I'll probably need to try to reproduce this,
> but to be honest between the varying failure modes, undefined wireless
> extensions semantics, etc. I'm not very confident I can.

I'll try all the different combination again for 2.6.28, and see if
it's the same, and on the other AP that seems harder to associate (but
works well in 2.6.28, and other OSs include Nokia phones ... so I
don't think it's the AP problem ... because it's been around a while
and gone thru many 2.6.xx).

It worked so well before that I didn't even bother to think twice, and
I may have made silly mistakes along the way, so pardon me if I
confused you.

Thanks for your help.

Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Fri, Mar 20, 2009 at 4:32 PM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> 1) It can't be before iwconfig which will result in "SET failed on
> device wlan0 ; Device or resource busy".
>  So your point 1) confuses me. Can you
> explain that a little more?

This is what happened ...

# modprobe -r iwlagn
# modprobe iwlagn
# ifconfig wlan0 up
# iwconfig wlan0 mode Managed
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Device or resource busy.


> As for 2), that is very very strange since ap auto channel auto is the
> default, so saying that before you do anything else should do anything
> at all.
>
> I suspect something is going on in the driver because the ifconfig order
> matters and for mac80211, it shouldn't make a difference when the state
> machine is really started. I'll probably need to try to reproduce this,
> but to be honest between the varying failure modes, undefined wireless
> extensions semantics, etc. I'm not very confident I can.

I'll try all the different combination again for 2.6.28, and see if
it's the same, and on the other AP that seems harder to associate (but
works well in 2.6.28, and other OSs include Nokia phones ... so I
don't think it's the AP problem ... because it's been around a while
and gone thru many 2.6.xx).

It worked so well before that I didn't even bother to think twice, and
I may have made silly mistakes along the way, so pardon me if I
confused you.

Thanks for your help.

Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]

On Fri, 2009-03-20 at 18:04 +0800, Jeff Chua wrote:
> On Fri, Mar 20, 2009 at 4:32 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > 1) It can't be before iwconfig which will result in "SET failed on
> > device wlan0 ; Device or resource busy".
> >  So your point 1) confuses me. Can you
> > explain that a little more?
> 
> This is what happened ...
> 
> # modprobe -r iwlagn
> # modprobe iwlagn
> # ifconfig wlan0 up
> # iwconfig wlan0 mode Managed
> Error for wireless request "Set Mode" (8B06) :
>     SET failed on device wlan0 ; Device or resource busy.

Oh, ok, yes, you cannot change the mode while the interface is up.
Though I guess setting it to the same mode should be accepted. Not that
it matters, the default mode is "managed" anyway.

> > As for 2), that is very very strange since ap auto channel auto is the
> > default, so saying that before you do anything else should do anything
> > at all.
> >
> > I suspect something is going on in the driver because the ifconfig order
> > matters and for mac80211, it shouldn't make a difference when the state
> > machine is really started. I'll probably need to try to reproduce this,
> > but to be honest between the varying failure modes, undefined wireless
> > extensions semantics, etc. I'm not very confident I can.
> 
> I'll try all the different combination again for 2.6.28, and see if
> it's the same, and on the other AP that seems harder to associate (but
> works well in 2.6.28, and other OSs include Nokia phones ... so I
> don't think it's the AP problem ... because it's been around a while
> and gone thru many 2.6.xx).

Yeah, I have to admit that an AP problem doesn't make much sense -- but
the entire failure mode doesn't make much sense to me so far.

> It worked so well before that I didn't even bother to think twice, and
> I may have made silly mistakes along the way, so pardon me if I
> confused you.

No worries. It really should still work well. Can I convince you to try
getting the packet dump I asked for in another mail?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Fri, Mar 20, 2009 at 6:13 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> Can I convince you to try getting the packet dump I asked for in
> another mail?

Was digging around for the "iw" package and got distracted. I'll test it soon.

I went back to 2.6.28 and found out that I could associate as follows
(but this would not work in 2.6.29-rc8 ... should work with the
patch).

modprobe -r iwlagn
modprobe iwlagn
iwconfig wlan0 mode Managed
ifconfig wlan0 up
iwconfig wlan0 essid "xxx"
iwconfig wlan0 key restricted xxx
iwconfig wlan0 ap auto channel auto
iwlist wlan0 scan >/dev/null


Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

[-- Attachment #1: Type: text/plain, Size: 183 bytes --]

On Fri, Mar 20, 2009 at 12:59 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> Send me the contents of all the files from a failed run please.

Attached. 2 runs.

Thanks,
Jeff.

[-- Attachment #2: dump.fail --]
[-- Type: application/octet-stream, Size: 58642 bytes --]

[-- Attachment #3: dump.pass --]
[-- Type: application/octet-stream, Size: 75764 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Sat, 2009-03-21 at 00:14 +0800, Jeff Chua wrote:

> I went back to 2.6.28 and found out that I could associate as follows
> (but this would not work in 2.6.29-rc8 ... should work with the
> patch).
> 
> modprobe -r iwlagn
> modprobe iwlagn
> iwconfig wlan0 mode Managed
> ifconfig wlan0 up
> iwconfig wlan0 essid "xxx"
> iwconfig wlan0 key restricted xxx
> iwconfig wlan0 ap auto channel auto
> iwlist wlan0 scan >/dev/null

Thing is that this works perfectly fine for me, on very similar
hardware.

OTOH, maybe it got _fixed_ again. Would you check wireless-testing
(http://wireless.kernel.org/en/developers/Documentation#wireless-testing.git) for me? Or compat-wireless (http://wireless.kernel.org/en/users/Download)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Sat, 2009-03-21 at 00:14 +0800, Jeff Chua wrote:

> I went back to 2.6.28 and found out that I could associate as follows
> (but this would not work in 2.6.29-rc8 ... should work with the
> patch).
> 
> modprobe -r iwlagn
> modprobe iwlagn
> iwconfig wlan0 mode Managed
> ifconfig wlan0 up
> iwconfig wlan0 essid "xxx"
> iwconfig wlan0 key restricted xxx
> iwconfig wlan0 ap auto channel auto
> iwlist wlan0 scan >/dev/null

Thing is that this works perfectly fine for me, on very similar
hardware.

OTOH, maybe it got _fixed_ again. Would you check wireless-testing
(http://wireless.kernel.org/en/developers/Documentation#wireless-testing.git) for me? Or compat-wireless (http://wireless.kernel.org/en/users/Download)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Sat, Mar 21, 2009 at 8:09 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> Thing is that this works perfectly fine for me, on very similar
> hardware.

I've set hidden SSID + mac address filtering (only allow my notebook
MAC address) as well as 128 WEP. And no problem to associate with
non-hidden AP.

> OTOH, maybe it got _fixed_ again. Would you check wireless-testing
> (http://wireless.kernel.org/en/developers/Documentation#wireless-testing.git) for me? Or compat-wireless (http://wireless.kernel.org/en/users/Download)

I'll try that tomorrow. Seems a lot to pull from git.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Jeff Chua]

On Sat, Mar 21, 2009 at 8:09 PM, Johannes Berg
<johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> Thing is that this works perfectly fine for me, on very similar
> hardware.

I've set hidden SSID + mac address filtering (only allow my notebook
MAC address) as well as 128 WEP. And no problem to associate with
non-hidden AP.

> OTOH, maybe it got _fixed_ again. Would you check wireless-testing
> (http://wireless.kernel.org/en/developers/Documentation#wireless-testing.git) for me? Or compat-wireless (http://wireless.kernel.org/en/users/Download)

I'll try that tomorrow. Seems a lot to pull from git.

Thanks,
Jeff.

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

On Sat, 2009-03-21 at 23:08 +0800, Jeff Chua wrote:
> On Sat, Mar 21, 2009 at 8:09 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > Thing is that this works perfectly fine for me, on very similar
> > hardware.
> 
> I've set hidden SSID + mac address filtering (only allow my notebook
> MAC address) as well as 128 WEP. And no problem to associate with
> non-hidden AP.

Ok, I haven't tried WEP or MAC address filtering, but I don't see how
those would make a significant difference. I can try again, but not
before mid next week since I'm away from my test machine.

> > OTOH, maybe it got _fixed_ again. Would you check wireless-testing
> >
> (http://wireless.kernel.org/en/developers/Documentation#wireless-testing.git) for me? Or compat-wireless (http://wireless.kernel.org/en/users/Download)
> 
> I'll try that tomorrow. Seems a lot to pull from git.

Thanks, I appreciate it. You should be able to cut it down by using
--reference /path/to/local/linux-git-tree or just compat (though I would
recommend using the git tree). I've also tried to go back to the
versions you were testing before and had no problem.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: 2.6.29-rc8: Reported regressions from 2.6.28

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

On Sat, 2009-03-21 at 23:08 +0800, Jeff Chua wrote:
> On Sat, Mar 21, 2009 at 8:09 PM, Johannes Berg
> <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org> wrote:
> > Thing is that this works perfectly fine for me, on very similar
> > hardware.
> 
> I've set hidden SSID + mac address filtering (only allow my notebook
> MAC address) as well as 128 WEP. And no problem to associate with
> non-hidden AP.

Ok, I haven't tried WEP or MAC address filtering, but I don't see how
those would make a significant difference. I can try again, but not
before mid next week since I'm away from my test machine.

> > OTOH, maybe it got _fixed_ again. Would you check wireless-testing
> >
> (http://wireless.kernel.org/en/developers/Documentation#wireless-testing.git) for me? Or compat-wireless (http://wireless.kernel.org/en/users/Download)
> 
> I'll try that tomorrow. Seems a lot to pull from git.

Thanks, I appreciate it. You should be able to cut it down by using
--reference /path/to/local/linux-git-tree or just compat (though I would
recommend using the git tree). I've also tried to go back to the
versions you were testing before and had no problem.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

2.6.29-rc8: Reported regressions from 2.6.28

[Rafael J. Wysocki]

This message contains a list of some regressions from 2.6.28, for which there
are no fixes in the mainline I know of.  If any of them have been fixed already,
please let me know.

If you know of any other unresolved regressions from 2.6.28, please let me know
either and I'll add them to the list.  Also, please let me know if any of the
entries below are invalid.

Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2009-03-14      124       36          32
  2009-03-03      108       33          28
  2009-02-24       95       32          24
  2009-02-14       85       33          27
  2009-02-08       82       45          36
  2009-02-04       66       51          39
  2009-01-20       38       35          27
  2009-01-11       13       13          10


Unresolved regressions
----------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12872
Subject		: pwc mmap always fails with EAGAIN
Submitter	: Markus <M4rkusXXL@web.de>
Date		: 2009-03-14 16:42 (1 days old)
References	: http://marc.info/?l=linux-kernel&m=123704902201378&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12871
Subject		: usb bluetooth crashes system
Submitter	: Pavel Machek <pavel@ucw.cz>
Date		: 2009-03-10 11:23 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123668450400940&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12870
Subject		: 2.6.29-rc "TKIP: replay detected" regression
Submitter	: Hugh Dickins <hugh@veritas.com>
Date		: 2009-03-11 12:07 (4 days old)
References	: http://marc.info/?l=linux-kernel&m=123677337219148&w=4
Handled-By	: John W. Linville <linville@tuxdriver.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12867
Subject		: 2.6.29-rc7 broke r8169 MAC on Thecus n2100 ARM board
Submitter	: Mikael Pettersson <mikpe@it.uu.se>
Date		: 2009-03-09 20:29 (6 days old)
References	: http://marc.info/?l=linux-kernel&m=123663065403760&w=4
Handled-By	: Francois Romieu <romieu@fr.zoreil.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12861
Subject		: Xorg fails to start "Failed to allocate space for kernel memory manager"
Submitter	: Emil Karlson <jkarlson@cc.hut.fi>
Date		: 2009-03-12 12:06 (3 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12856
Subject		: Thinkpad freezes with X.org and acpi=rsdt
Submitter	: Maciej Piechotka <uzytkownik2@gmail.com>
Date		: 2009-03-11 16:46 (4 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12846
Subject		: Regression issue with kernel 2.6.29-rc6-git1: high power consumption during sleep
Submitter	: Raymond Wooninck <tittiatcoke@gmail.com>
Date		: 2009-03-09 08:18 (6 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12842
Subject		: CCMP: replay detected
Submitter	: Peter Teoh <htmldeveloper@gmail.com>
Date		: 2009-03-08 07:42 (7 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12836
Subject		: 2.6.29-rc breaks STD using Intel 945
Submitter	: Rolf Eike Beer <eike-kernel@sf-tec.de>
Date		: 2009-03-04 19:20 (11 days old)
References	: http://marc.info/?l=linux-kernel&m=123619451406192&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12831
Subject		: Hot/Fn Keys do not work EEEPC 1000HE (eeepc_laptop)
Submitter	: Matthew <pyther@pyther.net>
Date		: 2009-03-07 10:05 (8 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12809
Subject		: iozone regression with 2.6.29-rc6
Submitter	: Lin Ming <ming.m.lin@intel.com>
Date		: 2009-02-27 9:13 (16 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cf6e7d83bf334cc5916137862c920a97aabc018
References	: http://marc.info/?l=linux-kernel&m=123572630504360&w=4
Handled-By	: Wu Fengguang <fengguang.wu@intel.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12808
Subject		: Suspend regression with 2.6.29-rc
Submitter	: Tino Keitel <tino.keitel@gmx.de>
Date		: 2009-02-24 19:08 (19 days old)
References	: http://marc.info/?l=linux-kernel&m=123550257312112&w=4
Handled-By	: Rafael J. Wysocki <rjw@sisk.pl>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12806
Subject		: i915 broken STR
Submitter	: Harvey Harrison <harvey.harrison@gmail.com>
Date		: 2009-02-28 4:20 (15 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5669fcacc58bf3a7386057addffd280d75380858
References	: http://marc.info/?l=linux-kernel&m=123579487801064&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12805
Subject		: QinQ vlan trunking regression
Submitter	: Bart Trojanowski <bart@jukie.net>
Date		: 2009-02-28 18:05 (15 days old)
References	: http://marc.info/?l=linux-kernel&m=123584439115868&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12800
Subject		: x86 PAT invalid vm_insert_pfn assumptions
Submitter	: Thomas Hellstrom <thellstrom@vmware.com>
Date		: 2009-03-02 01:40 (13 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12792
Subject		: 2.6.29-rc6-git4 boot failure
Submitter	: Sachin P. Sant <sachinp@in.ibm.com>
Date		: 2009-02-27 23:19 (16 days old)
References	: http://ozlabs.org/pipermail/linuxppc-dev/2009-February/068771.html


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12778
Subject		: suspend regression from 29rc5 to 29rc6
Submitter	: yury <urykhy@gmail.com>
Date		: 2009-02-25 09:25 (18 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12771
Subject		: Oops in i915_gem_flush
Submitter	: Kalev Lember <kalev@colleduc.ee>
Date		: 2009-02-24 08:35 (19 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject		: i915 VT switch with AIGLX causes X lock up
Submitter	: Sitsofe Wheeler <sitsofe@yahoo.com>
Date		: 2009-02-21 15:38 (22 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References	: http://marc.info/?l=linux-kernel&m=123523074304955&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12763
Subject		: Different cpu MHz values for processor0 and processor1
Submitter	: Matthew A. Bockol <mbockol@carleton.edu>
Date		: 2009-02-21 5:42 (22 days old)
References	: http://marc.info/?l=linux-kernel&m=123519687807246&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12705
Subject		: X200: Brightness broken since 2.6.29-rc4-58-g4c098bc
Submitter	: Nico Schottelius <nico-linux-20090213@schottelius.org>
Date		: 2009-02-13 9:33 (30 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e806b4957412bf472d826bd8cc571da041248799
References	: http://marc.info/?l=linux-kernel&m=123451768406825&w=4
		  http://marc.info/?l=linux-kernel&m=123479975503827&w=2
Handled-By	: Len Brown <lenb@kernel.org>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12681
Subject		: s2ram: fails to wake up on Acer Extensa 4220 (SMP disabled)
Submitter	: Orivej Desh <smpuj@bk.ru>
Date		: 2009-02-09 13:01 (34 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1cfe62c8010ac56e1bd3827e30386a87cc2f3594


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12680
Subject		: Entropy pool problem
Submitter	: Valentin QUEQUET <v.quequet-techniques@orange.fr>
Date		: 2009-02-09 09:12 (34 days old)


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12670
Subject		: BUG: unable to handle kernel paging request at pin_to_kill+0x21
Submitter	: Alessandro Bono <alessandro.bono@gmail.com>
Date		: 2009-02-08 11:04 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123409113223833&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12668
Subject		: USB flash disk surprise disconnect
Submitter	: Vegard Nossum <vegard.nossum@gmail.com>
Date		: 2009-02-08 10:21 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123408851821292&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12574
Subject		: possible circular locking dependency detected
Submitter	: Michael S. Tsirkin <m.s.tsirkin@gmail.com>
Date		: 2009-01-29 11:35 (45 days old)
References	: http://lkml.org/lkml/2009/2/9/205


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12499
Subject		: Problem with using bluetooth adaper connected to usb port
Submitter	: Maciej Rutecki <maciej.rutecki@gmail.com>
Date		: 2009-01-13 18:34 (61 days old)
References	: http://marc.info/?l=linux-kernel&m=123187185426236&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12490
Subject		: ath5k related kernel panic in 2.6.29-rc1
Submitter	: Sergey S. Kostyliov <rathamahata@gmail.com>
Date		: 2009-01-12 7:38 (62 days old)
References	: http://marc.info/?l=linux-kernel&m=123174591509586&w=4
Handled-By	: Bob Copeland <me@bobcopeland.com>


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12444
Subject		: X hangs following switch from radeonfb console - Bisected
Submitter	: Graham Murray <graham@gmurray.org.uk>
Date		: 2009-01-13 14:03 (61 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12419
Subject		: possible circular locking dependency on i915 dma
Submitter	: Wang Chen <wangchen@cn.fujitsu.com>
Date		: 2009-01-08 14:11 (66 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=546b0974c39657017407c86fe79811100b60700d
References	: http://marc.info/?l=linux-kernel&m=123142399720125&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12418
Subject		: Repeated ioctl(4, 0x40046445, ..) loop in glxgears
Submitter	: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
Date		: 2009-01-07 22:43 (67 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c1c2871a6a3a114853ec6836e9035ac1c0c7f7a
References	: http://marc.info/?l=linux-kernel&m=123136836213319&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12414
Subject		: iwl4965 cannot use "ap auto" on latest 2.6.28/29?
Submitter	: Jeff Chua <jeff.chua.linux@gmail.com>
Date		: 2009-01-05 4:13 (69 days old)
References	: http://marc.info/?l=linux-kernel&m=123112882127823&w=4


Regressions with patches
------------------------

Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12869
Subject		: BUG when disabled ipv6 module is unloaded
Submitter	: Thomas Backlund <tmb@mandriva.org>
Date		: 2009-03-10 20:15 (5 days old)
References	: http://marc.info/?l=linux-kernel&m=123671614621097&w=4
Handled-By	: John Dykstra <john.dykstra1@gmail.com>
Patch		: http://marc.info/?l=linux-kernel&m=123672746905127&w=4


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12758
Subject		: ACPI exception with 2.6.29-rc6
Submitter	: Heinz Diehl <htd@fancy-poultry.org>
Date		: 2009-02-23 16:46 (20 days old)
References	: http://marc.info/?l=linux-kernel&m=123540758700861&w=4
Handled-By	: Len Brown <lenb@kernel.org>
Patch		: http://bugzilla.kernel.org/attachment.cgi?id=20368&action=view


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12671
Subject		: uvc_status_cleanup(): undefined reference to `input_unregister_device'
Submitter	: Ingo Molnar <mingo@elte.hu>
Date		: 2009-02-08 14:58 (35 days old)
References	: http://marc.info/?l=linux-kernel&m=123410529909318&w=4
Handled-By	: Randy Dunlap <randy.dunlap@oracle.com>
Patch		: http://lkml.org/lkml/2009/2/15/172


Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=12667
Subject		: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended)
Submitter	: Paul Collins <paul@burly.ondioline.org>
Date		: 2009-01-21 7:15 (53 days old)
First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1c5745aa380efb6417b5681104b007c8612fb496
References	: http://marc.info/?l=linux-kernel&m=123252215315106&w=4
Handled-By	: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Patch		: http://lkml.org/lkml/2009/2/16/78


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 2.6.28,
unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=12398

Please let me know if there are any Bugzilla entries that should be added to
the list in there.

Thanks,
Rafael