[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Keeping it short: I've followed all the instructions on

http://wireless.kernel.org/en/users/Drivers/ath9k_htc

in order to get the TL-WN721N USB WiFi device to work. I tried with 

2.6.37
2.6.37.1
2.6.38-rc6 mainline last stable

in all permutations with

linux-next compat-wireless
linux-2.6-allstable compat-wireless

in turn in all permutations with the firmware for the Ar9271

from the Kernel GIT
from wireless.kernel.org:
http://wireless.kernel.org/en/users/Drivers/ath9k_htc?action=AttachFile&do=view&target=ar9271.fw

Nothing helped. The best results I got, and where I am currently stuck
is with

2.6.38-rc6, linux-next compat-wireless, firmware from GIT

When I boot (Gentoo), everything starts okay, but I get constant

"try 1"
"try 2"
"try 3"
"authentication timed out"

in dmesg. When I restart /etc/init.d/net.wlan1 I get, after
wpa_supplicant is said to start

SIOCSIFFLAGS: Unknown error 132
SIOCSIFFLAGS: Unknown error 132

wpa_cli can subsequently not connect to wpa_supplicant. I'm clueless,
what else can I do? Why is it not working? on wireless.kernel.org the
chipset and the device I own are said to work!

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Cedric Sodhi wrote:
> When I boot (Gentoo), everything starts okay, but I get constant
> 
> "try 1"
> "try 2"
> "try 3"
> "authentication timed out"
> 
> in dmesg.

Basically one of the issues I've had with ath9k since 2009.


> When I restart /etc/init.d/net.wlan1 I get, after wpa_supplicant is
> said to start
> 
> SIOCSIFFLAGS: Unknown error 132
> SIOCSIFFLAGS: Unknown error 132

Yes, I've also gotten this. Sometimes even for ath5k, but more
reliably for ath9k. The only thing that has helped is power cycle.
(The machine, not just the card.)


> I'm clueless, what else can I do? Why is it not working?

Yes, quite.


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Wed, 2011-02-23 at 12:46 -0800, Cedric Sodhi wrote:

> in dmesg. When I restart /etc/init.d/net.wlan1 I get, after
> wpa_supplicant is said to start
> 
> SIOCSIFFLAGS: Unknown error 132
> SIOCSIFFLAGS: Unknown error 132

Error 132 is ERFKILL, i.e., something in the system disabled the
wireless device. Does you laptop have a physical switch or some key
combination that may have been hit to disable wireless? The rfkill state
can also be changed using software calls. You could use rfkill tool to
monitor rfkill events to see when that state changes.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Jouni Malinen wrote:
> > SIOCSIFFLAGS: Unknown error 132
> 
> Error 132 is ERFKILL

Thanks for this clue!


> Does you laptop have a physical switch or some key combination that
> may have been hit to disable wireless?

In my case no. I have gotten both minipci ath9k card and cardbus
ath5k "stuck" in reporting 132 on ip l s dev .. up IIRC both after
using wpa_supplicant and only using iw manually.


> The rfkill state can also be changed using software calls. You
> could use rfkill tool to monitor rfkill events to see when that
> state changes.

I will remember this next time I see the 132.


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Wed, 2011-02-23 at 13:49 -0800, Peter Stuge wrote:
> In my case no. I have gotten both minipci ath9k card and cardbus
> ath5k "stuck" in reporting 132 on ip l s dev .. up IIRC both after
> using wpa_supplicant and only using iw manually.

I'm not sure what could trigger this apart from the most common case of
a real RF kill button (which can be very inconvenient in some laptops...
I hit mine accidentally commonly). In case of ath9k and ath5k, I would
expect this to be a GPIO interrupt if that blocking is indeed coming
from the driver (rfkill event / list could help to figure out whether
that is the case). I'm not familiar with that area of the code, so I'm
not sure how likely it would be for the GPIO setup to be incorrect for
any particular card/laptop.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Jouni Malinen wrote:
> > In my case no. I have gotten both minipci ath9k card and cardbus
> > ath5k "stuck" in reporting 132 on ip l s dev .. up IIRC both after
> > using wpa_supplicant and only using iw manually.
> 
> I'm not sure what could trigger this apart from the most common case of
> a real RF kill button (which can be very inconvenient in some laptops...
> I hit mine accidentally commonly).

ThinkPad X40 has no rfkill button. Fn+F5 is used to enable/disable
wifi but in Linux that goes through the H8 EC into acpid where I just
load/unload the module.


> In case of ath9k and ath5k, I would expect this to be a GPIO
> interrupt if that blocking is indeed coming from the driver (rfkill
> event / list could help to figure out whether that is the case).

Will keep an eye there next time!


> I'm not familiar with that area of the code, so I'm not sure how
> likely it would be for the GPIO setup to be incorrect for any
> particular card/laptop.

Nod. The ath5k card is cardbus also, and once it starts reporting
ERFKILL it does not help to unplug the card, unload ath and ath5k
modules, and then replug card. Only power cycle makes it work again.
The ath5k card+driver is otherwise very reliable for me.


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Sujith]

Cedric Sodhi wrote:
> Keeping it short: I've followed all the instructions on
> 
> http://wireless.kernel.org/en/users/Drivers/ath9k_htc
> 
> in order to get the TL-WN721N USB WiFi device to work. I tried with 
> 
> 2.6.37
> 2.6.37.1
> 2.6.38-rc6 mainline last stable
> 
> in all permutations with
> 
> linux-next compat-wireless
> linux-2.6-allstable compat-wireless
> 

The best thing would be to stick to your distribution's kernel,
and use the latest compat-wireless package.

Run "./scripts/driver-select ath9k_htc" in the compat-wireless directory
and then do a standard "make && sudo make install", and then reboot.
If the FW is present in the right location (check Gentoo's policies),
things should work.

Sujith

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Sujith wrote:
> The best thing would be to stick to your distribution's kernel,
> and use the latest compat-wireless package.

Unlike many binary distributions, Gentoo does not push a particular
kernel down their users' throat. It's very easy to use any kernel
whatsoever and many Gentoo users do just that.

Why a developer team working with wireless-testing.git consistently
recommends using some other code is very difficult to comprehend at
least for this fellow developer.


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Sujith]

Peter Stuge wrote:
> Sujith wrote:
> > The best thing would be to stick to your distribution's kernel,
> > and use the latest compat-wireless package.
> 
> Unlike many binary distributions, Gentoo does not push a particular
> kernel down their users' throat. It's very easy to use any kernel
> whatsoever and many Gentoo users do just that.
> 
> Why a developer team working with wireless-testing.git consistently
> recommends using some other code is very difficult to comprehend at
> least for this fellow developer.

You really need to lighten up.

Compiling a kernel and installing it is not a simple process
for the vast majority of end users. Each distribution has its
own idiosyncrasies and demanding kernel compilation knowledge in
a user who just wants his card to work is absurd.

In contrast, all it takes to install compat-wireless is the usual
make, make install. Some distributions like Ubuntu have binary
compat-wireless packages too.

The reported issue shows signs of basic configuration/setup deficiencies,
which is why compat-wireless was recommended.

Sujith

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Sujith wrote:
> > > The best thing would be to stick to your distribution's kernel,
> > > and use the latest compat-wireless package.
..
> > Why a developer team working with wireless-testing.git consistently
> > recommends using some other code is very difficult to comprehend at
> > least for this fellow developer.
> 
> You really need to lighten up.

In that case you need to pay more attention.


> Compiling a kernel and installing it is not a simple process
> for the vast majority of end users. Each distribution has its
> own idiosyncrasies and demanding kernel compilation knowledge in
> a user who just wants his card to work is absurd.

Your user classification filter is terribly flawed. The poster
described trying several different kernels with several different
wireless driver setups, some even -rc, as well as different variants
of compat-wireless, and reported the best results attained from that
testing. In every other project and community this is interpreted for
what it is; good thorough testing done by the reporter, before asking
for help. It is also a sign of competency.


> The reported issue shows signs of basic configuration/setup
> deficiencies,

Do you seriously believe that is the problem?

The report contains *exactly* the same problem that I have tried to
communicate to anyone and everyone involved with ath9k on and off for
more than a year, as well as a second problem which I confirmed that
I have also experienced with both ath5k and ath9k.

And you have the nerve to dismiss it as configuration/setup
deficiency. That looks incredibly bad!


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Sujith]

Peter Stuge wrote:
> In that case you need to pay more attention.

You go to hell.

Sujith

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Sujith]

Sujith wrote:
> Peter Stuge wrote:
> > In that case you need to pay more attention.
> 
> You go to hell.

To elaborate a bit more, everyone is incredibly tired
of your trollish verbiage and jumping on every random thread
spouting nonsense. It isn't as if the developers are involved
in a conspiracy to make the end users' lives difficult.
Sure, you have an issue that has gone unresolved for an obscenely
long amount of time, but how does that affect this particular thread/issue ?

Sujith

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Sujith wrote:
> > In that case you need to pay more attention.
> 
> You go to hell.

I'm sorry to see that we interpret the reported issue so differently. :\

(I love your hostname though! Noticed it just now. :)


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

I will not quote all the replies. I will just reply:

Peter:

Thanks for your reply. I tried rebooting, AC-off etc a dozen times by
now. Basically, every time when I tried a new kernel. The problem did
not change.

Jouni:

Thanks for the clue, it's good to know what's going on. No, the computer
(which is a desktop station) does not have any controls to trigger
Wireless. Besides, it is an external USB card

TL-WN721N (PS: This device is said to be supported according to
wireless.kernel.org)

which would not be affected by such a "hard-off" button. It does have a
little button on the side of it which is called QSS (some security
feature I don't know anything about). I pressed it repeatedly, also
worrying that it could be the cause, but it did not have any effects.

I installed rfkill and when I run "rfkill list", the tool returns that
"Soft blocked: no; Hard blocked: no".

Jouni:

So far I had GPIO disabled in the kernel. I enabled it with the
suboptions

CONFIG_GPIO_BASIC_MNIO
CONFIG_GPIO_SCM

(buest guess) but it had no effect.

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Sujith wrote:
> Sujith wrote:
> > Peter Stuge wrote:
> > > In that case you need to pay more attention.
> > 
> > You go to hell.
> 
> To elaborate a bit more,

Thanks for the clarification!


> everyone is incredibly tired of your trollish verbiage and jumping
> on every random thread spouting nonsense.

Again, I try not to rant without also providing something useful in
the reply. If my impression is that a new person arrive and posts an
issue then I might be more likely to reply, and while I understand
that hearing over and over how I think things could work better gets
old quickly I think it can help those new to the list to e.g. point
them to l-w or suggest what they might expect or not on this
particular list. It would have helped me.


> It isn't as if the developers are involved in a conspiracy to make
> the end users' lives difficult.

I hope not, then I would really be in for problems. :) I don't expect
this to be the case. But I react strongly to how things work because
it is so different from what I expected when approaching the primary
Linux supporting wifi vendor.


> Sure, you have an issue that has gone unresolved for an obscenely
> long amount of time, but how does that affect this particular
> thread/issue ?

Symptoms are identical to what I have experienced, so there's a
chance that it's actually the same issue if some amount of code or
design is shared between ath9k and ath9k_htc. Although not much might
be, maybe some lines were copypasted over, or maybe some design
pattern was reused, and there lies the elusive problem.

The PCI thing is actually way more annoying right now, because it's
blocking the other debugging and I'm not sure what to throw at it
short of a logic analyzer, which is so not what I want to do..


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

PS, if that matters: When I observe the ERFKILL status with rfkill I get
a

idx 0 type 1 op 2 soft 0 hard 0
idx 0 type 1 op 2 soft 0 hard 0

every time I restart /etc/init.d/net.wlan1.

Attached is a log of dmesg. If you want me to enable certain DEBUG
options and grab another one, please say so. I've just read that certain
DEBUG options might cause problems so I disabled them all, to be
careful.
-------------- next part --------------
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Linux version 2.6.38-rc6 (root at engine) (gcc version 4.4.4 (Gentoo 4.4.4-r2 p1.2, pie-0.4.5) ) #2 SMP Thu Feb 24 10:36:24 CET 2011
[    0.000000] Command line: root=/dev/sda3 vide=vesafb:mtrr:3,ywrap vga=0x317
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 00000000dfee0000 (usable)
[    0.000000]  BIOS-e820: 00000000dfee0000 - 00000000dfee3000 (ACPI NVS)
[    0.000000]  BIOS-e820: 00000000dfee3000 - 00000000dfef0000 (ACPI data)
[    0.000000]  BIOS-e820: 00000000dfef0000 - 00000000dff00000 (reserved)
[    0.000000]  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[    0.000000]  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[    0.000000]  BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI 2.4 present.
[    0.000000] DMI: Gigabyte Technology Co., Ltd. P35-DS4/P35-DS4, BIOS F6 08/20/2007
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[    0.000000] No AGP bridge found
[    0.000000] last_pfn = 0x120000 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-CBFFF write-protect
[    0.000000]   CC000-EFFFF uncachable
[    0.000000]   F0000-FFFFF write-through
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 000000000 mask F00000000 write-back
[    0.000000]   1 base 0E0000000 mask FE0000000 uncachable
[    0.000000]   2 base 100000000 mask FE0000000 write-back
[    0.000000]   3 base 0DFF00000 mask FFFF00000 write-through
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] last_pfn = 0xdfee0 max_arch_pfn = 0x400000000
[    0.000000] Scanning 0 areas for low memory corruption
[    0.000000] initial memory mapped : 0 - 20000000
[    0.000000] init_memory_mapping: 0000000000000000-00000000dfee0000
[    0.000000]  0000000000 - 00dfe00000 page 2M
[    0.000000]  00dfe00000 - 00dfee0000 page 4k
[    0.000000] kernel direct mapping tables up to dfee0000 @ 1fffa000-20000000
[    0.000000] init_memory_mapping: 0000000100000000-0000000120000000
[    0.000000]  0100000000 - 0120000000 page 2M
[    0.000000] kernel direct mapping tables up to 120000000 @ dfeda000-dfee0000
[    0.000000] ACPI: RSDP 00000000000f6d90 00014 (v00 GBT   )
[    0.000000] ACPI: RSDT 00000000dfee3040 00034 (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)
[    0.000000] ACPI: FACP 00000000dfee30c0 00074 (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)
[    0.000000] ACPI: DSDT 00000000dfee3180 04A88 (v01 GBT    GBTUACPI 00001000 MSFT 0100000C)
[    0.000000] ACPI: FACS 00000000dfee0000 00040
[    0.000000] ACPI: HPET 00000000dfee7d80 00038 (v01 GBT    GBTUACPI 42302E31 GBTU 00000098)
[    0.000000] ACPI: MCFG 00000000dfee7e00 0003C (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)
[    0.000000] ACPI: APIC 00000000dfee7c80 00084 (v01 GBT    GBTUACPI 42302E31 GBTU 01010101)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-0000000120000000
[    0.000000] Initmem setup node 0 0000000000000000-0000000120000000
[    0.000000]   NODE_DATA [000000011fffb000 - 000000011fffffff]
[    0.000000]  [ffffea0000000000-ffffea0003ffffff] PMD -> [ffff88011be00000-ffff88011f7fffff] on node 0
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x00120000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[3] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009f
[    0.000000]     0: 0x00000100 -> 0x000dfee0
[    0.000000]     0: 0x00100000 -> 0x00120000
[    0.000000] On node 0 totalpages: 1048175
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 6 pages reserved
[    0.000000]   DMA zone: 3921 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 14280 pages used for memmap
[    0.000000]   DMA32 zone: 898840 pages, LIFO batch:31
[    0.000000]   Normal zone: 1792 pages used for memmap
[    0.000000]   Normal zone: 129280 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0x408
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 40
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[    0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[    0.000000] PM: Registered nosave memory: 00000000dfee0000 - 00000000dfee3000
[    0.000000] PM: Registered nosave memory: 00000000dfee3000 - 00000000dfef0000
[    0.000000] PM: Registered nosave memory: 00000000dfef0000 - 00000000dff00000
[    0.000000] PM: Registered nosave memory: 00000000dff00000 - 00000000f0000000
[    0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000f4000000
[    0.000000] PM: Registered nosave memory: 00000000f4000000 - 00000000fec00000
[    0.000000] PM: Registered nosave memory: 00000000fec00000 - 0000000100000000
[    0.000000] Allocating PCI resources starting at dff00000 (gap: dff00000:10100000)
[    0.000000] setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
[    0.000000] PERCPU: Embedded 25 pages/cpu @ffff8800dfc00000 s73216 r8192 d20992 u524288
[    0.000000] pcpu-alloc: s73216 r8192 d20992 u524288 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 2 3 
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 1032041
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: root=/dev/sda3 vide=vesafb:mtrr:3,ywrap vga=0x317
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Memory: 4059076k/4718592k available (4075k kernel code, 525892k absent, 133624k reserved, 2224k data, 520k init)
[    0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU-based detection of stalled CPUs is disabled.
[    0.000000] NR_IRQS:4352 nr_irqs:72 16
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] hpet clockevent registered
[    0.000000] Fast TSC calibration using PIT
[    0.000000] Detected 2399.636 MHz processor.
[    0.001004] Calibrating delay loop (skipped), value calculated using timer frequency.. 4799.27 BogoMIPS (lpj=2399636)
[    0.001015] pid_max: default: 32768 minimum: 301
[    0.001047] Security Framework initialized
[    0.001575] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.004070] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.005095] Mount-cache hash table entries: 256
[    0.005275] Initializing cgroup subsys ns
[    0.005282] ns_cgroup deprecated: consider using the 'clone_children' flag without the ns_cgroup.
[    0.005289] Initializing cgroup subsys cpuacct
[    0.005298] Initializing cgroup subsys freezer
[    0.005325] CPU: Physical Processor ID: 0
[    0.005329] CPU: Processor Core ID: 0
[    0.005334] mce: CPU supports 6 MCE banks
[    0.005344] CPU0: Thermal monitoring enabled (TM2)
[    0.005351] using mwait in idle threads.
[    0.005405] ACPI: Core revision 20110112
[    0.008076] Setting APIC routing to flat
[    0.008389] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.018828] CPU0: Intel(R) Core(TM)2 Quad CPU           @ 2.40GHz stepping 07
[    0.018998] Performance Events: PEBS fmt0-, Core2 events, Intel PMU driver.
[    0.018998] PEBS disabled due to CPU errata.
[    0.018998] ... version:                2
[    0.018998] ... bit width:              40
[    0.018998] ... generic registers:      2
[    0.018998] ... value mask:             000000ffffffffff
[    0.018998] ... max period:             000000007fffffff
[    0.018998] ... fixed-purpose events:   3
[    0.018998] ... event mask:             0000000700000003
[    0.018998] Booting Node   0, Processors  #1 #2 #3 Ok.
[    0.233991] Brought up 4 CPUs
[    0.233998] Total of 4 processors activated (19198.98 BogoMIPS).
[    0.236096] NET: Registered protocol family 16
[    0.236998] ACPI: bus type pci registered
[    0.237016] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[    0.237016] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
[    0.245762] PCI: Using configuration type 1 for base access
[    0.253120] bio: create slab <bio-0> at 0
[    0.254513] ACPI: EC: Look up EC in DSDT
[    0.259300] ACPI: Interpreter enabled
[    0.259310] ACPI: (supports S0 S3 S4 S5)
[    0.259338] ACPI: Using IOAPIC for interrupt routing
[    0.268091] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
[    0.268091] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[    0.268116] pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
[    0.268116] pci_root PNP0A03:00: host bridge window [io  0x0d00-0xffff] (ignored)
[    0.268116] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
[    0.268116] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
[    0.268116] pci_root PNP0A03:00: host bridge window [mem 0xdff00000-0xfebfffff] (ignored)
[    0.268116] pci 0000:00:00.0: [8086:29c0] type 0 class 0x000600
[    0.268151] pci 0000:00:01.0: [8086:29c1] type 1 class 0x000604
[    0.268190] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    0.268194] pci 0000:00:01.0: PME# disabled
[    0.268237] pci 0000:00:1a.0: [8086:2937] type 0 class 0x000c03
[    0.268284] pci 0000:00:1a.0: reg 20: [io  0xe200-0xe21f]
[    0.268332] pci 0000:00:1a.1: [8086:2938] type 0 class 0x000c03
[    0.268378] pci 0000:00:1a.1: reg 20: [io  0xe000-0xe01f]
[    0.268425] pci 0000:00:1a.2: [8086:2939] type 0 class 0x000c03
[    0.268471] pci 0000:00:1a.2: reg 20: [io  0xe100-0xe11f]
[    0.268992] pci 0000:00:1a.7: [8086:293c] type 0 class 0x000c03
[    0.269011] pci 0000:00:1a.7: reg 10: [mem 0xfa105000-0xfa1053ff]
[    0.269098] pci 0000:00:1b.0: [8086:293e] type 0 class 0x000403
[    0.269115] pci 0000:00:1b.0: reg 10: [mem 0xfa100000-0xfa103fff 64bit]
[    0.269173] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.269178] pci 0000:00:1b.0: PME# disabled
[    0.269198] pci 0000:00:1c.0: [8086:2940] type 1 class 0x000604
[    0.269258] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.269262] pci 0000:00:1c.0: PME# disabled
[    0.269287] pci 0000:00:1c.4: [8086:2948] type 1 class 0x000604
[    0.269347] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[    0.269351] pci 0000:00:1c.4: PME# disabled
[    0.269373] pci 0000:00:1c.5: [8086:294a] type 1 class 0x000604
[    0.269432] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[    0.269437] pci 0000:00:1c.5: PME# disabled
[    0.269461] pci 0000:00:1d.0: [8086:2934] type 0 class 0x000c03
[    0.269507] pci 0000:00:1d.0: reg 20: [io  0xe300-0xe31f]
[    0.269554] pci 0000:00:1d.1: [8086:2935] type 0 class 0x000c03
[    0.269601] pci 0000:00:1d.1: reg 20: [io  0xe400-0xe41f]
[    0.269652] pci 0000:00:1d.2: [8086:2936] type 0 class 0x000c03
[    0.269698] pci 0000:00:1d.2: reg 20: [io  0xe500-0xe51f]
[    0.269751] pci 0000:00:1d.7: [8086:293a] type 0 class 0x000c03
[    0.269769] pci 0000:00:1d.7: reg 10: [mem 0xfa104000-0xfa1043ff]
[    0.269852] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
[    0.269913] pci 0000:00:1f.0: [8086:2916] type 0 class 0x000601
[    0.270000] pci 0000:00:1f.0: quirk: [io  0x0400-0x047f] claimed by ICH6 ACPI/GPIO/TCO
[    0.270010] pci 0000:00:1f.0: quirk: [io  0x0480-0x04bf] claimed by ICH6 GPIO
[    0.270019] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0800 (mask 000f)
[    0.270027] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0290 (mask 000f)
[    0.270071] pci 0000:00:1f.2: [8086:2920] type 0 class 0x000101
[    0.270088] pci 0000:00:1f.2: reg 10: [io  0x0000-0x0007]
[    0.270098] pci 0000:00:1f.2: reg 14: [io  0x0000-0x0003]
[    0.270107] pci 0000:00:1f.2: reg 18: [io  0x0000-0x0007]
[    0.270117] pci 0000:00:1f.2: reg 1c: [io  0x0000-0x0003]
[    0.270126] pci 0000:00:1f.2: reg 20: [io  0xf000-0xf00f]
[    0.270136] pci 0000:00:1f.2: reg 24: [io  0xfc00-0xfc0f]
[    0.270176] pci 0000:00:1f.3: [8086:2930] type 0 class 0x000c05
[    0.270193] pci 0000:00:1f.3: reg 10: [mem 0xfa106000-0xfa1060ff 64bit]
[    0.270217] pci 0000:00:1f.3: reg 20: [io  0x0500-0x051f]
[    0.270252] pci 0000:00:1f.5: [8086:2926] type 0 class 0x000101
[    0.270269] pci 0000:00:1f.5: reg 10: [io  0xe700-0xe707]
[    0.270279] pci 0000:00:1f.5: reg 14: [io  0xe800-0xe803]
[    0.270288] pci 0000:00:1f.5: reg 18: [io  0xe900-0xe907]
[    0.270298] pci 0000:00:1f.5: reg 1c: [io  0xea00-0xea03]
[    0.270307] pci 0000:00:1f.5: reg 20: [io  0xeb00-0xeb0f]
[    0.270316] pci 0000:00:1f.5: reg 24: [io  0xec00-0xec0f]
[    0.270393] pci 0000:01:00.0: [10de:0191] type 0 class 0x000300
[    0.270405] pci 0000:01:00.0: reg 10: [mem 0xf6000000-0xf6ffffff]
[    0.270417] pci 0000:01:00.0: reg 14: [mem 0xe0000000-0xefffffff 64bit pref]
[    0.270430] pci 0000:01:00.0: reg 1c: [mem 0xf4000000-0xf5ffffff 64bit]
[    0.270439] pci 0000:01:00.0: reg 24: [io  0xc000-0xc07f]
[    0.270448] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
[    0.270478] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
[    0.270492] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    0.270499] pci 0000:00:01.0:   bridge window [io  0xc000-0xcfff]
[    0.270504] pci 0000:00:01.0:   bridge window [mem 0xf4000000-0xf7ffffff]
[    0.270510] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xefffffff 64bit pref]
[    0.270553] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
[    0.270561] pci 0000:00:1c.0:   bridge window [io  0xa000-0xafff]
[    0.270566] pci 0000:00:1c.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
[    0.270574] pci 0000:00:1c.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.270618] pci 0000:00:1c.4: PCI bridge to [bus 03-03]
[    0.270625] pci 0000:00:1c.4:   bridge window [io  0xb000-0xbfff]
[    0.270630] pci 0000:00:1c.4:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
[    0.270637] pci 0000:00:1c.4:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.270704] pci 0000:04:00.0: [10ec:8168] type 0 class 0x000200
[    0.270724] pci 0000:04:00.0: reg 10: [io  0xd000-0xd0ff]
[    0.270758] pci 0000:04:00.0: reg 18: [mem 0xf9000000-0xf9000fff 64bit]
[    0.270797] pci 0000:04:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
[    0.270847] pci 0000:04:00.0: supports D1 D2
[    0.270850] pci 0000:04:00.0: PME# supported from D1 D2 D3hot D3cold
[    0.270856] pci 0000:04:00.0: PME# disabled
[    0.270875] pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
[    0.270891] pci 0000:00:1c.5: PCI bridge to [bus 04-04]
[    0.270898] pci 0000:00:1c.5:   bridge window [io  0xd000-0xdfff]
[    0.270903] pci 0000:00:1c.5:   bridge window [mem 0xf8000000-0xf9ffffff]
[    0.270910] pci 0000:00:1c.5:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.270954] pci 0000:05:06.0: [104c:8024] type 0 class 0x000c00
[    0.270978] pci 0000:05:06.0: reg 10: [mem 0xfa004000-0xfa0047ff]
[    0.270990] pci 0000:05:06.0: reg 14: [mem 0xfa000000-0xfa003fff]
[    0.271055] pci 0000:05:06.0: supports D1 D2
[    0.271058] pci 0000:05:06.0: PME# supported from D0 D1 D2 D3hot
[    0.271064] pci 0000:05:06.0: PME# disabled
[    0.271106] pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
[    0.271115] pci 0000:00:1e.0:   bridge window [io  0xf000-0x0000] (disabled)
[    0.271120] pci 0000:00:1e.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    0.271127] pci 0000:00:1e.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.271131] pci 0000:00:1e.0:   bridge window [io  0x0000-0xffff] (subtractive decode)
[    0.271135] pci 0000:00:1e.0:   bridge window [mem 0x00000000-0xfffffffff] (subtractive decode)
[    0.271159] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.271339] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
[    0.271396] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
[    0.271454] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX5._PRT]
[    0.271501] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[    0.286238] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[    0.286238] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[    0.286985] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[    0.287055] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    0.287123] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[    0.287194] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[    0.287262] ACPI: PCI Interrupt Link [LNK0] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
[    0.287331] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 *6 7 9 10 11 12 14 15)
[    0.287377] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[    0.287377] vgaarb: loaded
[    0.287377] SCSI subsystem initialized
[    0.287377] libata version 3.00 loaded.
[    0.287998] usbcore: registered new interface driver usbfs
[    0.288000] usbcore: registered new interface driver hub
[    0.288000] usbcore: registered new device driver usb
[    0.288000] Advanced Linux Sound Architecture Driver Version 1.0.23.
[    0.288000] PCI: Using ACPI for IRQ routing
[    0.288000] PCI: pci_cache_line_size set to 64 bytes
[    0.288091] reserve RAM buffer: 000000000009f800 - 000000000009ffff 
[    0.288095] reserve RAM buffer: 00000000dfee0000 - 00000000dfffffff 
[    0.288974] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[    0.288985] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[    0.291003] Switching to clocksource hpet
[    0.291025] Switched to NOHz mode on CPU #0
[    0.291052] Switched to NOHz mode on CPU #2
[    0.291092] Switched to NOHz mode on CPU #3
[    0.291117] Switched to NOHz mode on CPU #1
[    0.292693] pnp: PnP ACPI init
[    0.292715] ACPI: bus type pnp registered
[    0.292826] pnp 00:00: [bus 00-3f]
[    0.292829] pnp 00:00: [io  0x0cf8-0x0cff]
[    0.292833] pnp 00:00: [io  0x0000-0x0cf7 window]
[    0.292836] pnp 00:00: [io  0x0d00-0xffff window]
[    0.292839] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[    0.292842] pnp 00:00: [mem 0x000c0000-0x000dffff window]
[    0.292845] pnp 00:00: [mem 0xdff00000-0xfebfffff window]
[    0.292961] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
[    0.293081] pnp 00:01: [io  0x0010-0x001f]
[    0.293084] pnp 00:01: [io  0x0022-0x003f]
[    0.293087] pnp 00:01: [io  0x0044-0x005f]
[    0.293090] pnp 00:01: [io  0x0062-0x0063]
[    0.293092] pnp 00:01: [io  0x0065-0x006f]
[    0.293095] pnp 00:01: [io  0x0074-0x007f]
[    0.293098] pnp 00:01: [io  0x0091-0x0093]
[    0.293100] pnp 00:01: [io  0x00a2-0x00bf]
[    0.293103] pnp 00:01: [io  0x00e0-0x00ef]
[    0.293106] pnp 00:01: [io  0x04d0-0x04d1]
[    0.293108] pnp 00:01: [io  0x0290-0x029f]
[    0.293111] pnp 00:01: [io  0x0800-0x087f]
[    0.293113] pnp 00:01: [io  0x0290-0x0294]
[    0.293116] pnp 00:01: [io  0x0880-0x088f]
[    0.293250] system 00:01: [io  0x04d0-0x04d1] has been reserved
[    0.293257] system 00:01: [io  0x0290-0x029f] has been reserved
[    0.293264] system 00:01: [io  0x0800-0x087f] has been reserved
[    0.293271] system 00:01: [io  0x0290-0x0294] has been reserved
[    0.293277] system 00:01: [io  0x0880-0x088f] has been reserved
[    0.293284] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.293304] pnp 00:02: [dma 4]
[    0.293307] pnp 00:02: [io  0x0000-0x000f]
[    0.293310] pnp 00:02: [io  0x0080-0x0090]
[    0.293312] pnp 00:02: [io  0x0094-0x009f]
[    0.293315] pnp 00:02: [io  0x00c0-0x00df]
[    0.293394] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
[    0.293410] pnp 00:03: [io  0x0070-0x0073]
[    0.293420] pnp 00:03: [irq 8]
[    0.293499] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.293512] pnp 00:04: [io  0x0061]
[    0.293595] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
[    0.293608] pnp 00:05: [io  0x00f0-0x00ff]
[    0.293618] pnp 00:05: [irq 13]
[    0.293698] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[    0.293975] pnp 00:06: [io  0x03f8-0x03ff]
[    0.293982] pnp 00:06: [irq 4]
[    0.294118] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.294347] pnp 00:07: [io  0x0378-0x037f]
[    0.294354] pnp 00:07: [irq 7]
[    0.294470] pnp 00:07: Plug and Play ACPI device, IDs PNP0400 (active)
[    0.294586] pnp 00:08: [io  0x0060]
[    0.294589] pnp 00:08: [io  0x0064]
[    0.294595] pnp 00:08: [irq 1]
[    0.294677] pnp 00:08: Plug and Play ACPI device, IDs PNP0303 (active)
[    0.294722] pnp 00:09: [io  0x0400-0x04bf]
[    0.294831] system 00:09: [io  0x0400-0x04bf] could not be reserved
[    0.294839] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.295105] pnp 00:0a: [mem 0xf0000000-0xf3ffffff]
[    0.295235] system 00:0a: [mem 0xf0000000-0xf3ffffff] has been reserved
[    0.295243] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.295457] pnp 00:0b: [mem 0x000cc400-0x000cffff]
[    0.295461] pnp 00:0b: [mem 0x000f0000-0x000f7fff]
[    0.295464] pnp 00:0b: [mem 0x000f8000-0x000fbfff]
[    0.295467] pnp 00:0b: [mem 0x000fc000-0x000fffff]
[    0.295470] pnp 00:0b: [mem 0xdfee0000-0xdfefffff]
[    0.295473] pnp 00:0b: [mem 0x00000000-0x0009ffff]
[    0.295476] pnp 00:0b: [mem 0x00100000-0xdfedffff]
[    0.295479] pnp 00:0b: [mem 0xfec00000-0xfec00fff]
[    0.295481] pnp 00:0b: [mem 0xfed10000-0xfed1dfff]
[    0.295484] pnp 00:0b: [mem 0xfed20000-0xfed8ffff]
[    0.295487] pnp 00:0b: [mem 0xfee00000-0xfee00fff]
[    0.295490] pnp 00:0b: [mem 0xffb00000-0xffb7ffff]
[    0.295493] pnp 00:0b: [mem 0xfff00000-0xffffffff]
[    0.295496] pnp 00:0b: [mem 0x000e0000-0x000effff]
[    0.295632] system 00:0b: [mem 0x000cc400-0x000cffff] has been reserved
[    0.295640] system 00:0b: [mem 0x000f0000-0x000f7fff] could not be reserved
[    0.295647] system 00:0b: [mem 0x000f8000-0x000fbfff] could not be reserved
[    0.295655] system 00:0b: [mem 0x000fc000-0x000fffff] could not be reserved
[    0.295662] system 00:0b: [mem 0xdfee0000-0xdfefffff] could not be reserved
[    0.295669] system 00:0b: [mem 0x00000000-0x0009ffff] could not be reserved
[    0.295676] system 00:0b: [mem 0x00100000-0xdfedffff] could not be reserved
[    0.295683] system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
[    0.295690] system 00:0b: [mem 0xfed10000-0xfed1dfff] has been reserved
[    0.295697] system 00:0b: [mem 0xfed20000-0xfed8ffff] has been reserved
[    0.295704] system 00:0b: [mem 0xfee00000-0xfee00fff] has been reserved
[    0.295711] system 00:0b: [mem 0xffb00000-0xffb7ffff] has been reserved
[    0.295718] system 00:0b: [mem 0xfff00000-0xffffffff] has been reserved
[    0.295725] system 00:0b: [mem 0x000e0000-0x000effff] has been reserved
[    0.295732] system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.295760] pnp 00:0c: [mem 0xffb80000-0xffbfffff]
[    0.295865] pnp 00:0c: Plug and Play ACPI device, IDs INT0800 (active)
[    0.295873] pnp: PnP ACPI: found 13 devices
[    0.295878] ACPI: ACPI bus type pnp unregistered
[    0.305695] pci 0000:00:1c.0: BAR 8: assigned [mem 0xfa200000-0xfa3fffff]
[    0.305707] pci 0000:00:1c.0: BAR 9: assigned [mem 0xfa400000-0xfa5fffff 64bit pref]
[    0.305717] pci 0000:00:1c.4: BAR 8: assigned [mem 0xfa600000-0xfa7fffff]
[    0.305727] pci 0000:00:1c.4: BAR 9: assigned [mem 0xfa800000-0xfa9fffff 64bit pref]
[    0.305738] pci 0000:00:1c.5: BAR 9: assigned [mem 0xfaa00000-0xfabfffff pref]
[    0.305747] pci 0000:01:00.0: BAR 6: assigned [mem 0xf7000000-0xf701ffff pref]
[    0.305754] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    0.305760] pci 0000:00:01.0:   bridge window [io  0xc000-0xcfff]
[    0.305768] pci 0000:00:01.0:   bridge window [mem 0xf4000000-0xf7ffffff]
[    0.305776] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xefffffff 64bit pref]
[    0.305786] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
[    0.305792] pci 0000:00:1c.0:   bridge window [io  0xa000-0xafff]
[    0.305801] pci 0000:00:1c.0:   bridge window [mem 0xfa200000-0xfa3fffff]
[    0.305809] pci 0000:00:1c.0:   bridge window [mem 0xfa400000-0xfa5fffff 64bit pref]
[    0.305820] pci 0000:00:1c.4: PCI bridge to [bus 03-03]
[    0.305826] pci 0000:00:1c.4:   bridge window [io  0xb000-0xbfff]
[    0.305835] pci 0000:00:1c.4:   bridge window [mem 0xfa600000-0xfa7fffff]
[    0.305843] pci 0000:00:1c.4:   bridge window [mem 0xfa800000-0xfa9fffff 64bit pref]
[    0.305855] pci 0000:04:00.0: BAR 6: assigned [mem 0xfaa00000-0xfaa0ffff pref]
[    0.305862] pci 0000:00:1c.5: PCI bridge to [bus 04-04]
[    0.305868] pci 0000:00:1c.5:   bridge window [io  0xd000-0xdfff]
[    0.305877] pci 0000:00:1c.5:   bridge window [mem 0xf8000000-0xf9ffffff]
[    0.305885] pci 0000:00:1c.5:   bridge window [mem 0xfaa00000-0xfabfffff pref]
[    0.305896] pci 0000:00:1e.0: PCI bridge to [bus 05-05]
[    0.305901] pci 0000:00:1e.0:   bridge window [io  disabled]
[    0.305910] pci 0000:00:1e.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    0.305918] pci 0000:00:1e.0:   bridge window [mem pref disabled]
[    0.305940] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.305948] pci 0000:00:01.0: setting latency timer to 64
[    0.305956] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.305964] pci 0000:00:1c.0: setting latency timer to 64
[    0.305971] pci 0000:00:1c.4: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.305979] pci 0000:00:1c.4: setting latency timer to 64
[    0.305990] pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[    0.305998] pci 0000:00:1c.5: setting latency timer to 64
[    0.306016] pci 0000:00:1e.0: setting latency timer to 64
[    0.306021] pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
[    0.306025] pci_bus 0000:00: resource 1 [mem 0x00000000-0xfffffffff]
[    0.306028] pci_bus 0000:01: resource 0 [io  0xc000-0xcfff]
[    0.306032] pci_bus 0000:01: resource 1 [mem 0xf4000000-0xf7ffffff]
[    0.306035] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
[    0.306039] pci_bus 0000:02: resource 0 [io  0xa000-0xafff]
[    0.306042] pci_bus 0000:02: resource 1 [mem 0xfa200000-0xfa3fffff]
[    0.306046] pci_bus 0000:02: resource 2 [mem 0xfa400000-0xfa5fffff 64bit pref]
[    0.306049] pci_bus 0000:03: resource 0 [io  0xb000-0xbfff]
[    0.306052] pci_bus 0000:03: resource 1 [mem 0xfa600000-0xfa7fffff]
[    0.306056] pci_bus 0000:03: resource 2 [mem 0xfa800000-0xfa9fffff 64bit pref]
[    0.306059] pci_bus 0000:04: resource 0 [io  0xd000-0xdfff]
[    0.306063] pci_bus 0000:04: resource 1 [mem 0xf8000000-0xf9ffffff]
[    0.306066] pci_bus 0000:04: resource 2 [mem 0xfaa00000-0xfabfffff pref]
[    0.306070] pci_bus 0000:05: resource 1 [mem 0xfa000000-0xfa0fffff]
[    0.306073] pci_bus 0000:05: resource 4 [io  0x0000-0xffff]
[    0.306076] pci_bus 0000:05: resource 5 [mem 0x00000000-0xfffffffff]
[    0.306116] NET: Registered protocol family 2
[    0.306308] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.307734] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[    0.311317] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.311840] TCP: Hash tables configured (established 524288 bind 65536)
[    0.311847] TCP reno registered
[    0.311863] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[    0.311906] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[    0.312082] NET: Registered protocol family 1
[    0.312220] RPC: Registered udp transport module.
[    0.312225] RPC: Registered tcp transport module.
[    0.312230] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.312421] pci 0000:01:00.0: Boot video device
[    0.312432] PCI: CLS 32 bytes, default 64
[    0.312456] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.312463] Placing 64MB software IO TLB between ffff8800dbc00000 - ffff8800dfc00000
[    0.312470] software IO TLB at phys 0xdbc00000 - 0xdfc00000
[    0.314618] Scanning for low memory corruption every 60 seconds
[    0.329576] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.335605] Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
[    0.336182] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.336190] io scheduler noop registered
[    0.336194] io scheduler deadline registered
[    0.336284] io scheduler cfq registered (default)
[    0.336511] pcieport 0000:00:01.0: setting latency timer to 64
[    0.336606] pcieport 0000:00:1c.0: setting latency timer to 64
[    0.336704] pcieport 0000:00:1c.4: setting latency timer to 64
[    0.336805] pcieport 0000:00:1c.5: setting latency timer to 64
[    0.337000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    0.337808] vesafb: framebuffer at 0xf5000000, mapped to 0xffffc90005100000, using 3072k, total 14336k
[    0.337817] vesafb: mode is 1024x768x16, linelength=2048, pages=1
[    0.337822] vesafb: scrolling: redraw
[    0.337827] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[    0.351680] Console: switching to colour frame buffer device 128x48
[    0.365519] fb0: VESA VGA frame buffer device
[    0.365683] intel_idle: MWAIT substates: 0x20
[    0.365686] intel_idle: does not run on family 6 model 15
[    0.365954] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
[    0.366188] ACPI: Power Button [PWRB]
[    0.366405] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    0.366601] ACPI: Power Button [PWRF]
[    0.366866] ACPI: acpi_idle registered with cpuidle
[    0.369331] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.634116] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    0.715720] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    0.733424] Non-volatile memory driver v1.3
[    0.733636] Linux agpgart interface v0.103
[    0.733814] [drm] Initialized drm 1.1.0 20060810
[    0.736636] brd: module loaded
[    0.738083] loop: module loaded
[    0.738608] ata_piix 0000:00:1f.2: version 2.13
[    0.738631] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    0.738821] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[    0.739038] ata_piix 0000:00:1f.2: setting latency timer to 64
[    0.739724] scsi0 : ata_piix
[    0.739971] scsi1 : ata_piix
[    0.740853] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[    0.741057] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[    0.741261] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    0.741472] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[    0.741674] ata_piix 0000:00:1f.5: setting latency timer to 64
[    0.742259] scsi2 : ata_piix
[    0.742490] scsi3 : ata_piix
[    0.748393] ata3: SATA max UDMA/133 cmd 0xe700 ctl 0xe800 bmdma 0xeb00 irq 19
[    0.753798] ata4: SATA max UDMA/133 cmd 0xe900 ctl 0xea00 bmdma 0xeb08 irq 19
[    0.759352] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.764751] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    0.770276] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[    0.770280] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[    0.775825] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[    0.789924] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[    0.789942] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfa105000
[    0.805017] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[    0.810325] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.815663] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.820997] usb usb1: Product: EHCI Host Controller
[    0.826274] usb usb1: Manufacturer: Linux 2.6.38-rc6 ehci_hcd
[    0.831529] usb usb1: SerialNumber: 0000:00:1a.7
[    0.836881] hub 1-0:1.0: USB hub found
[    0.841977] hub 1-0:1.0: 6 ports detected
[    0.847129] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    0.852366] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[    0.852370] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    0.857668] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[    0.870917] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[    0.870933] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfa104000
[    0.885015] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[    0.890118] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    0.895209] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.900299] usb usb2: Product: EHCI Host Controller
[    0.905376] usb usb2: Manufacturer: Linux 2.6.38-rc6 ehci_hcd
[    0.910438] usb usb2: SerialNumber: 0000:00:1d.7
[    0.915604] hub 2-0:1.0: USB hub found
[    0.920508] hub 2-0:1.0: 6 ports detected
[    0.925407] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.930256] uhci_hcd: USB Universal Host Controller Interface driver
[    0.935113] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.939906] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[    0.939911] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[    0.944694] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[    0.954041] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000e200
[    0.958769] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    0.963564] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.968378] usb usb3: Product: UHCI Host Controller
[    0.973172] usb usb3: Manufacturer: Linux 2.6.38-rc6 uhci_hcd
[    0.978036] usb usb3: SerialNumber: 0000:00:1a.0
[    0.982991] hub 3-0:1.0: USB hub found
[    0.987769] hub 3-0:1.0: 2 ports detected
[    0.992584] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[    0.997524] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[    0.997528] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[    1.002460] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[    1.013040] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000e000
[    1.017974] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    1.022957] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.027957] usb usb4: Product: UHCI Host Controller
[    1.033020] usb usb4: Manufacturer: Linux 2.6.38-rc6 uhci_hcd
[    1.038062] usb usb4: SerialNumber: 0000:00:1a.1
[    1.043330] hub 4-0:1.0: USB hub found
[    1.048355] hub 4-0:1.0: 2 ports detected
[    1.053733] uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    1.058770] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[    1.058774] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[    1.063826] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[    1.074771] ata3: SATA link down (SStatus 0 SControl 300)
[    1.090610] ata4: SATA link down (SStatus 0 SControl 300)
[    1.090627] uhci_hcd 0000:00:1a.2: irq 18, io base 0x0000e100
[    1.090668] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[    1.090671] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.090673] usb usb5: Product: UHCI Host Controller
[    1.090676] usb usb5: Manufacturer: Linux 2.6.38-rc6 uhci_hcd
[    1.090678] usb usb5: SerialNumber: 0000:00:1a.2
[    1.090846] hub 5-0:1.0: USB hub found
[    1.090851] hub 5-0:1.0: 2 ports detected
[    1.090937] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    1.090944] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[    1.090947] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    1.091035] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[    1.158032] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000e300
[    1.163012] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    1.168011] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.172982] usb usb6: Product: UHCI Host Controller
[    1.177936] usb usb6: Manufacturer: Linux 2.6.38-rc6 uhci_hcd
[    1.182915] usb usb6: SerialNumber: 0000:00:1d.0
[    1.188047] hub 6-0:1.0: USB hub found
[    1.193038] hub 6-0:1.0: 2 ports detected
[    1.198028] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    1.203134] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[    1.203138] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    1.208168] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[    1.218031] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000e400
[    1.223000] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[    1.228008] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.232972] usb usb7: Product: UHCI Host Controller
[    1.237909] usb usb7: Manufacturer: Linux 2.6.38-rc6 uhci_hcd
[    1.242830] usb usb7: SerialNumber: 0000:00:1d.1
[    1.247882] hub 7-0:1.0: USB hub found
[    1.252761] hub 7-0:1.0: 2 ports detected
[    1.253016] usb 2-1: new high speed USB device using ehci_hcd and address 2
[    1.262703] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    1.267742] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[    1.267746] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    1.272803] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[    1.285035] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000e500
[    1.290050] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[    1.295059] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.300073] usb usb8: Product: UHCI Host Controller
[    1.305034] usb usb8: Manufacturer: Linux 2.6.38-rc6 uhci_hcd
[    1.310011] usb usb8: SerialNumber: 0000:00:1d.2
[    1.315080] Refined TSC clocksource calibration: 2399.999 MHz.
[    1.315240] hub 8-0:1.0: USB hub found
[    1.315245] hub 8-0:1.0: 2 ports detected
[    1.315422] usbcore: registered new interface driver cdc_wdm
[    1.315425] Initializing USB Mass Storage driver...
[    1.315508] usbcore: registered new interface driver usb-storage
[    1.315510] USB Mass Storage support registered.
[    1.315648] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[    1.315651] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    1.315820] serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.315938] mousedev: PS/2 mouse device common for all mice
[    1.318929] usbcore: registered new interface driver wacom
[    1.318932] wacom: v1.52:USB Wacom tablet driver
[    1.318954] rtc_cmos 00:03: RTC can wake from S4
[    1.386725] Switching to clocksource tsc
[    1.392644] usb 2-1: New USB device found, idVendor=0cf3, idProduct=9271
[    1.395106] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    1.395131] rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
[    1.395203] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    1.395367] cpuidle: using governor ladder
[    1.395370] cpuidle: using governor menu
[    1.396141] usbcore: registered new interface driver usbhid
[    1.396143] usbhid: USB HID core driver
[    1.396564] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[    1.396572] hda_intel: position_fix set to 1 for device 1458:a022
[    1.396606] HDA Intel 0000:00:1b.0: setting latency timer to 64
[    1.397934] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[    1.451751] usb 2-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[    1.457416] usb 2-1: Product: USB2.0 WLAN
[    1.463009] usb 2-1: Manufacturer: ATHEROS
[    1.468565] usb 2-1: SerialNumber: 12345
[    1.476366] hda_codec: ALC889A: BIOS auto-probing.
[    1.488388] ALSA device list:
[    1.493814]   #0: HDA Intel at 0xfa100000 irq 22
[    1.499475] TCP cubic registered
[    1.502066] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.502080] ata1.01: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.502203] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.502214] ata2.01: SATA link down (SStatus 0 SControl 300)
[    1.524235] ata1.00: HPA detected: current 234490943, native 234493056
[    1.524240] ata1.00: ATA-7: SAMSUNG SP1213C, SV100-34, max UDMA7
[    1.524243] ata1.00: 234490943 sectors, multi 16: LBA48 
[    1.524251] ata1.01: ATAPI: TSSTcorp CDDVDW SH-S203B, SB00, max UDMA/100
[    1.524314] ata2.00: HPA detected: current 976771055, native 976773168
[    1.524319] ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
[    1.524322] ata2.00: 976771055 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    1.527303] ata2.00: configured for UDMA/133
[    1.527343] ata1.00: configured for UDMA/133
[    1.533118] ata1.01: configured for UDMA/100
[    1.576020] usb 2-2: new high speed USB device using ehci_hcd and address 3
[    1.585317] Initializing XFRM netlink socket
[    1.585437] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG SP1213C  SV10 PQ: 0 ANSI: 5
[    1.585716] sd 0:0:0:0: [sda] 234490943 512-byte logical blocks: (120 GB/111 GiB)
[    1.585786] sd 0:0:0:0: [sda] Write Protect is off
[    1.585789] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.585819] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.585870] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.618035] NET: Registered protocol family 10
[    1.618083] scsi 0:0:1:0: CD-ROM            TSSTcorp CDDVDW SH-S203B  SB00 PQ: 0 ANSI: 5
[    1.629509] NET: Registered protocol family 17
[    1.634852] Registering the dns_resolver key type
[    1.645058] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.650462] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.656075] sr 0:0:1:0: Attached scsi CD-ROM sr0
[    1.656228] sr 0:0:1:0: Attached scsi generic sg1 type 5
[    1.657535]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[    1.667231] scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
[    1.672928] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.675083] sd 1:0:0:0: [sdb] 976771055 512-byte logical blocks: (500 GB/465 GiB)
[    1.675146] sd 1:0:0:0: [sdb] Write Protect is off
[    1.675150] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.675178] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.675615] sd 1:0:0:0: Attached scsi generic sg2 type 0
[    1.712895] usb 2-2: New USB device found, idVendor=1e3d, idProduct=2092
[    1.718528] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.724119] usb 2-2: Product: Flash Disk      
[    1.729637] usb 2-2: Manufacturer: CBM     
[    1.734653]  sdb: sdb1 sdb2 sdb3
[    1.740236] usb 2-2: SerialNumber: 2113310111C56300
[    1.740620] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.751167] scsi4 : usb-storage 2-2:1.0
[    1.760360] EXT3-fs: barriers not enabled
[    1.772389] kjournald starting.  Commit interval 5 seconds
[    1.772409] EXT3-fs (sda3): mounted filesystem with writeback data mode
[    1.772423] VFS: Mounted root (ext3 filesystem) readonly on device 8:3.
[    1.790178] Freeing unused kernel memory: 520k freed
[    1.858013] usb 3-1: new low speed USB device using uhci_hcd and address 2
[    2.025773] usb 3-1: New USB device found, idVendor=046d, idProduct=c626
[    2.031435] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[    2.037113] usb 3-1: Product: SpaceNavigator
[    2.042713] usb 3-1: Manufacturer: 3Dconnexion
[    2.165773] logitech 0003:046D:C626.0001: fixing up rel/abs in Logitech report descriptor
[    2.246903] input: 3Dconnexion SpaceNavigator as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input3
[    2.253049] logitech 0003:046D:C626.0001: input,hidraw0: USB HID v1.10 Multi-Axis Controller [3Dconnexion SpaceNavigator] on usb-0000:00:1a.0-1/input0
[    2.471014] usb 3-2: new low speed USB device using uhci_hcd and address 3
[    2.716778] usb 3-2: New USB device found, idVendor=1020, idProduct=030a
[    2.716782] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.716786] usb 3-2: Product: USB HID Device        
[    2.716789] usb 3-2: Manufacturer: PATEN
[    2.756555] scsi 4:0:0:0: Direct-Access     CBM      Flash Disk       5.00 PQ: 0 ANSI: 2
[    2.756927] sd 4:0:0:0: Attached scsi generic sg3 type 0
[    2.757405] sd 4:0:0:0: [sdc] 4057088 512-byte logical blocks: (2.07 GB/1.93 GiB)
[    2.757903] sd 4:0:0:0: [sdc] Write Protect is off
[    2.757907] sd 4:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[    2.758652] sd 4:0:0:0: [sdc] No Caching mode page present
[    2.758655] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[    2.760900] sd 4:0:0:0: [sdc] No Caching mode page present
[    2.760904] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[    2.761902]  sdc: sdc1
[    2.764403] sd 4:0:0:0: [sdc] No Caching mode page present
[    2.764406] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[    2.764410] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[    2.772085] input: PATEN USB HID Device         as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/input/input4
[    2.772305] generic-usb 0003:1020:030A.0002: input,hidraw1: USB HID v1.10 Mouse [PATEN USB HID Device        ] on usb-0000:00:1a.0-2/input0
[    3.185800] udev: starting version 151
[    3.185872] udevd (1000): /proc/1000/oom_adj is deprecated, please use /proc/1000/oom_score_adj instead.
[    3.412527] cfg80211: Calling CRDA to update world regulatory domain
[    3.943772] usb 2-1: ath9k_htc: Transferred FW: ar9271.fw, size: 51280
[    4.209021] usb 2-1: ath9k_htc: HTC initialized with 33 credits
[    4.607898] ath: EEPROM regdomain: 0x809c
[    4.607901] ath: EEPROM indicates we should expect a country code
[    4.607904] ath: doing EEPROM country->regdmn map search
[    4.607906] ath: country maps to regdmn code: 0x52
[    4.607909] ath: Country alpha2 being used: CN
[    4.607911] ath: Regpair used: 0x52
[    4.612228] Registered led device: ath9k-phy0::radio
[    4.612299] Registered led device: ath9k-phy0::assoc
[    4.612328] Registered led device: ath9k-phy0::tx
[    4.612353] Registered led device: ath9k-phy0::rx
[    4.612357] usb 2-1: ath9k_htc: USB layer initialized
[    4.612389] usbcore: registered new interface driver ath9k_hif_usb
[    4.632439] udev: renamed network interface wlan0 to wlan1
[    4.901157] EXT3-fs (sda3): using internal journal
[    5.167477] EXT3-fs: barriers not enabled
[    5.181992] kjournald starting.  Commit interval 5 seconds
[    5.182033] EXT3-fs (sda6): warning: maximal mount count reached, running e2fsck is recommended
[    5.182188] EXT3-fs (sda6): using internal journal
[    5.182193] EXT3-fs (sda6): mounted filesystem with writeback data mode
[    5.231312] EXT2-fs (sda5): warning: mounting unchecked fs, running e2fsck is recommended
[    5.246836] EXT3-fs: barriers not enabled
[    5.253317] kjournald starting.  Commit interval 5 seconds
[    5.253330] EXT3-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
[    5.253470] EXT3-fs (sdb1): using internal journal
[    5.253474] EXT3-fs (sdb1): mounted filesystem with writeback data mode
[    5.266960] EXT3-fs: barriers not enabled
[    5.271120] kjournald starting.  Commit interval 5 seconds
[    5.271138] EXT3-fs (sdb2): warning: maximal mount count reached, running e2fsck is recommended
[    5.271284] EXT3-fs (sdb2): using internal journal
[    5.271288] EXT3-fs (sdb2): mounted filesystem with writeback data mode
[    5.285053] EXT3-fs: barriers not enabled
[    5.297998] kjournald starting.  Commit interval 5 seconds
[    5.298131] EXT3-fs (sdb3): warning: maximal mount count reached, running e2fsck is recommended
[    5.298358] EXT3-fs (sdb3): using internal journal
[    5.298362] EXT3-fs (sdb3): mounted filesystem with writeback data mode
[    5.411436] Adding 2000088k swap on /dev/sda2.  Priority:-1 extents:1 across:2000088k 
[   13.178752] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   14.781156] wlan1: authenticate with 00:1c:4a:07:7f:76 (try 1)
[   14.981025] wlan1: authenticate with 00:1c:4a:07:7f:76 (try 2)
[   15.181038] wlan1: authenticate with 00:1c:4a:07:7f:76 (try 3)
[   15.381033] wlan1: authentication with 00:1c:4a:07:7f:76 timed out
[   26.029037] wlan1: authenticate with 00:1c:4a:07:7f:76 (try 1)
[   26.229012] wlan1: authenticate with 00:1c:4a:07:7f:76 (try 2)
[   26.429020] wlan1: authenticate with 00:1c:4a:07:7f:76 (try 3)
[   26.629019] wlan1: authentication with 00:1c:4a:07:7f:76 timed out

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Cedric Sodhi wrote:
> Jouni:
> 
> So far I had GPIO disabled in the kernel. I enabled it with the
> suboptions
> 
> CONFIG_GPIO_BASIC_MNIO
> CONFIG_GPIO_SCM
> 
> (buest guess) but it had no effect.

I think Jouni was refering to GPIO in the AR9271 chipset, and that
maybe something within the USB adapter was causing the 9271 to
believe that it received an rfkill signal via a GPIO from somewhere.

I'm afraid I also know little about both chipset and driver though. :\


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Thu, 2011-02-24 at 01:15 -0800, Cedric Sodhi wrote:
> PS, if that matters: When I observe the ERFKILL status with rfkill I get
> a
> 
> idx 0 type 1 op 2 soft 0 hard 0
> idx 0 type 1 op 2 soft 0 hard 0
> 
> every time I restart /etc/init.d/net.wlan1.

Those lines are saying that WLAN (type 1) was changes (op 2) to having
both soft and hard block off. There would need to be a case where either
the soft or the hard block value would change to 1 for ERFKILL to be
indicated.

Could you please run "rfkill event" while injected the card and keep it
running until you see the first ERFKILL? I would like to see at which
point soft/hard block is enabled and what may have happened just before
that..

> Attached is a log of dmesg. If you want me to enable certain DEBUG
> options and grab another one, please say so. I've just read that certain
> DEBUG options might cause problems so I disabled them all, to be
> careful.

This looks like a separate issue. For some reason, the card is either
not transmitting or receiving frames when trying to authenticate. If you
can reproduce this easily, it would be interesting to see a wireless
capture log (if you have another device that could run in monitor mode)
to confirm whether the authentication frames are indeed transmitted.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Sujith]

Cedric Sodhi wrote:
> PS, if that matters: When I observe the ERFKILL status with rfkill I get
> a
> 
> idx 0 type 1 op 2 soft 0 hard 0
> idx 0 type 1 op 2 soft 0 hard 0
> 
> every time I restart /etc/init.d/net.wlan1.
> 
> Attached is a log of dmesg. If you want me to enable certain DEBUG
> options and grab another one, please say so. I've just read that certain
> DEBUG options might cause problems so I disabled them all, to be
> careful.

What is the AP configuration ?
And you are using wpa_supplicant, right ?
Can you post the supplicant configuration here ?

And yes, enabling debug options would help, please load
the driver with modparam debug=0x201 and post the kernel log.

Sujith

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Oh I'm a fool, I made a typo, the two lines that I get with rfkill event
are

idx 0 type 1 op 2 soft 1 hard 0
idx 0 type 1 op 2 soft 0 hard 0

I'll do what you requested. I just wanted to clear this out


On Thu, Feb 24, 2011 at 10:15:10AM +0100, Cedric Sodhi wrote:
> PS, if that matters: When I observe the ERFKILL status with rfkill I get
> a
> 
> idx 0 type 1 op 2 soft 0 hard 0
> idx 0 type 1 op 2 soft 0 hard 0
> 
> every time I restart /etc/init.d/net.wlan1.
> 
> Attached is a log of dmesg. If you want me to enable certain DEBUG
> options and grab another one, please say so. I've just read that certain
> DEBUG options might cause problems so I disabled them all, to be
> careful.

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Thu, 2011-02-24 at 01:39 -0800, Cedric Sodhi wrote:
> Oh I'm a fool, I made a typo, the two lines that I get with rfkill event
> are
> 
> idx 0 type 1 op 2 soft 1 hard 0
> idx 0 type 1 op 2 soft 0 hard 0

The interesting part about that is the block being soft, not hard.. In
other words, this looks like some software application in the system
disabling the wireless, not the WLAN driver.

> I'll do what you requested. I just wanted to clear this out

Please also run "rfkill list" at the point when ERFKILL is being
reported. It shows a bit more helpful names for the interfaces than the
idx value from the events.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Sujith:

The AP runs on 802.11g/b/n

Yes I'm using wpa_supplicant

You need to tell me which module you suggest I should set this modparm
for. Can you give me the exact kernel parameter that I should pass?

Jouni:

You mean "capture log" as in a log with wireshark? I'm really
unexperienced in that field. If you could tell me what program I need I
can do my best.

As for rfkill event:

---BOOT---
---Start rfkill event---
idx 0 type 1 op 0 soft 0 hard 0
---Unplug device---
idx 0 type 1 op 1 soft 0 hard 0
---Replug device---
idx 1 type 1 op 0 soft 0 hard 0
idx 1 type 1 op 2 soft 0 hard 0
---/etc/init.d/net.wlan1 restart---
idx 1 type 1 op 2 soft 1 hard 0
idx 1 type 1 op 2 soft 0 hard 0
---Unplug device---
idx 1 type 1 op 1 soft 0 hard 0
---Replug device---
idx 2 type 1 op 0 soft 0 hard 0
idx 2 type 1 op 2 soft 0 hard 0



I think I made no typos this time

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Cedric Sodhi wrote:
> You need to tell me which module you suggest I should set this modparm
> for. Can you give me the exact kernel parameter that I should pass?

modprobe ath9k debug=0x201

(If I remember the value correctly)


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Jouni:

I hope I understood you correctly. If you want me to run "rfkill list"
at the very moment between those two 132 errors, that could be difficult
as they appear very quickly after eachother

# rfkill list
Soft: no
Hard: no
# /etc/init.d/net.wlan1 restart
SIOCSIFFLAGS: Unknown error 132
SIOCSIFFLAGS: Unknown error 132
# rfkill list
Soft: no
Hard: no

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Jouni:

I've run tcpdump, without any arguments, if that's correct. There
appears to be no communication between the AP and the computer with the
problematic device.

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Thu, 2011-02-24 at 01:58 -0800, Cedric Sodhi wrote:
> I hope I understood you correctly. If you want me to run "rfkill list"
> at the very moment between those two 132 errors, that could be difficult
> as they appear very quickly after eachother

Yes, I think you understood correctly. However, it looks like this is
something specific to what Gentoo is doing in its network configuration
scripts. It looks like /etc/init.d/net.wlan? script ends up soft
blocking all wifi for some reason and that result in the 132 error. If
this causes you any problems in getting wpa_supplicant running, I would
suggest targeting this question to whoever is maintaining the Gentoo
scripts. You can also try to manually unblock the soft block with
"rfkill unblock wifi" before starting wpa_supplicant.

I was able to reproduce the part of WLAN getting soft blocked, but the
script did manage to get wpa_supplicant running. Please make sure you
are running an up-to-date version of wpa_supplicant to get better
support for dynamically changing rfkill state.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Thu, 2011-02-24 at 01:55 -0800, Cedric Sodhi wrote:
> You mean "capture log" as in a log with wireshark? I'm really
> unexperienced in that field. If you could tell me what program I need I
> can do my best.

I meant running another wireless LAN card in monitor mode (e.g.,:
ifconfig wlan0 down; iw wlan0 set type monitor; iw wlan0 set channel 6
HT20; ifconfig wlan0 up) and using a program like wireshark to capture
the frames.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

On Thu, Feb 24, 2011 at 01:08:06PM +0200, Jouni Malinen wrote:
> On Thu, 2011-02-24 at 01:58 -0800, Cedric Sodhi wrote:
> > I hope I understood you correctly. If you want me to run "rfkill list"
> > at the very moment between those two 132 errors, that could be difficult
> > as they appear very quickly after eachother
> 
> Yes, I think you understood correctly. However, it looks like this is
> something specific to what Gentoo is doing in its network configuration
> scripts. It looks like /etc/init.d/net.wlan? script ends up soft
> blocking all wifi for some reason and that result in the 132 error.

Why would it do that? To be frank I doubt your diagnosis at this point,
how did you come to conclude that?

> If this causes you any problems in getting wpa_supplicant running, I would
> suggest targeting this question to whoever is maintaining the Gentoo
> scripts. You can also try to manually unblock the soft block with
> "rfkill unblock wifi" before starting wpa_supplicant.

I might have misunderstood, but as I said the device is unlocked before
and after the (attempted) start of wpa_supplicant:

# rfkill list
Soft lock: no
Hard lock: no
# /etc/init.d/net.wlan1 restart
... SIOCSIFFLAGS: Unknown error 132
SIOCSIFFLAGS: Unknown error 132 ...
# rfkill list
Soft lock: no
Hard lock: no

Trying to unlock wouldn't make any sense, correct?

> I was able to reproduce the part of WLAN getting soft blocked, but the
> script did manage to get wpa_supplicant running. Please make sure you
> are running an up-to-date version of wpa_supplicant to get better
> support for dynamically changing rfkill state.

I'll try a bleeding-edge wpa_supplicant and will report back. Do you
have any ideas left? I'm quite certain that Gentoo Devs will not be able
to help me with that but rather point me at you, saying the driver has a
problem.

PS: Would it perhaps be possible that you configure your MUA so that it
respects mailing lists? It appears to reply like to an ordinary message
which coerces me (and others) to manually copy over the correct address
when we want to reply to you.

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Thu, 2011-02-24 at 03:21 -0800, Cedric Sodhi wrote:
> Why would it do that? To be frank I doubt your diagnosis at this point,
> how did you come to conclude that?

I have no idea why it would do that; you would need to ask Gentoo
developers that. I concluded this by checking what my test laptop with
Gentoo was doing..

> I might have misunderstood, but as I said the device is unlocked before
> and after the (attempted) start of wpa_supplicant:
> 
> # rfkill list
> Soft lock: no
> Hard lock: no
> # /etc/init.d/net.wlan1 restart
> ... SIOCSIFFLAGS: Unknown error 132
> SIOCSIFFLAGS: Unknown error 132 ...

That SIOCSIFFFLAGS error is likely from wpa_supplicant which would
indicate that the unblocking was not done before wpa_supplicant was
started. The current wpa_supplicant handles the change during run time,
but older versions may not.

> # rfkill list
> Soft lock: no
> Hard lock: no
> 
> Trying to unlock wouldn't make any sense, correct?

In this state, correct. Before running net.wlan1 restart (or more likely
start), it may be enough to workaround some issues if your
wpa_supplicant is not new enough.

> I'll try a bleeding-edge wpa_supplicant and will report back. Do you
> have any ideas left? I'm quite certain that Gentoo Devs will not be able
> to help me with that but rather point me at you, saying the driver has a
> problem.

I doubt that. If that rfkill soft block is causing problems, it is not
because of the driver (it would use hard block). I see nothing here that
would point to the driver as far as this rfkill part is concerned (the
authentication timeout is different issue).

> PS: Would it perhaps be possible that you configure your MUA so that it
> respects mailing lists? It appears to reply like to an ordinary message
> which coerces me (and others) to manually copy over the correct address
> when we want to reply to you.

What do you mean? The common behavior on most Linux wireless development
lists, including this one, is to reply to the sender of the message and
include the mailing list (and possible other addresses) in the cc
line... I'm just following that policy here.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Jouni Malinen wrote:
> I have no idea why it would do that; you would need to ask Gentoo
> developers that. I concluded this by checking what my test laptop with
> Gentoo was doing..

Quick grep rfkill -r /lib/rc* /etc/init.d comes up empty.

But ifplugd is used, might it be twiddling rfkill knobs?


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

I'm as clueless. I inserted the "rfkill list" command at different
stages in the the init-script and it turns out the Lock occurs BEFORE
start( ) is called - outside of /etc/init.d/net.lo.

But where?

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Cedric Sodhi wrote:
> I'm as clueless. I inserted the "rfkill list" command at different
> stages in the the init-script and it turns out the Lock occurs BEFORE
> start( ) is called - outside of /etc/init.d/net.lo.
> 
> But where?

strace -fFs 1024 -o /tmp/out /etc/init.d/net.eth1 restart; grep -B 512 rfkill /tmp/out | wgetpaste -X

Another thing to try would be to see if simple ip l s dev eth1 down or
.. up triggers the lock?


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Peter Stuge]

Cedric Sodhi wrote:
> Wait a second, this can't possibly caused by calling rfkill. I only
> installed rfkill to examine why that happens in the first place!

Yes, but there might be a syscall. On second thought I guess that
would be an ioctl, so grep -i instead.


//Peter

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Wait a second, this can't possibly caused by calling rfkill. I only
installed rfkill to examine why that happens in the first place!

On Thu, Feb 24, 2011 at 01:27:59PM +0100, Peter Stuge wrote:
> Cedric Sodhi wrote:
> > I'm as clueless. I inserted the "rfkill list" command at different
> > stages in the the init-script and it turns out the Lock occurs BEFORE
> > start( ) is called - outside of /etc/init.d/net.lo.
> > 
> > But where?
> 
> strace -fFs 1024 -o /tmp/out /etc/init.d/net.eth1 restart; grep -B 512 rfkill /tmp/out | wgetpaste -X
> 
> Another thing to try would be to see if simple ip l s dev eth1 down or
> .. up triggers the lock?
> 
> 
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Jouni Malinen]

On Thu, 2011-02-24 at 03:52 -0800, Peter Stuge wrote:
> Quick grep rfkill -r /lib/rc* /etc/init.d comes up empty.

It is done with iwconfig. iwconfig_post_stop and failure in
iwconfig_pre_start results in "iwconfig wlan# txpower off" getting
executed. This results in soft blocking the interface.

iwconfig_pre_starts removes the soft block with iwconfig_defaults that
runs "iwconfig wlan# txpower auto", but this happens only after
wpa_supplicant has been started (I would do that in different order..)
and as such, depends on wpa_supplicant being able to handle a dynamic
rfkill blocking change.

Anyway, this is getting way off-topic for this mailing list. Like I
mentioned before, if this soft blocking causes issues, the question
should be directed to Gentoo maintainers. Though, it should be noted
that this works fine on my laptop with Gentoo as long as the network
settings are correct to avoid hitting the soft block on failure and as
long as wpa_supplicant is recent enough to handle the rfkill events
properly. In addition, it should be noted that any manual operation
after "net.wlan# stop" will need to take care of unblocking the soft
block before actually trying to use the radio.

- Jouni

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

I'm not sure whether I understand every bit of your reply. For practical
reasons, I would like to skip directly to...

On Thu, Feb 24, 2011 at 04:08:15PM +0200, Jouni Malinen wrote:
> On Thu, 2011-02-24 at 03:52 -0800, Peter Stuge wrote:
> > Quick grep rfkill -r /lib/rc* /etc/init.d comes up empty.
> 
> It is done with iwconfig. iwconfig_post_stop and failure in
> iwconfig_pre_start results in "iwconfig wlan# txpower off" getting
> executed. This results in soft blocking the interface.
> 
> iwconfig_pre_starts removes the soft block with iwconfig_defaults that
> runs "iwconfig wlan# txpower auto", but this happens only after
> wpa_supplicant has been started (I would do that in different order..)
> and as such, depends on wpa_supplicant being able to handle a dynamic
> rfkill blocking change.
> 
> Anyway, this is getting way off-topic for this mailing list. Like I
> mentioned before, if this soft blocking causes issues, the question
> should be directed to Gentoo maintainers. Though, it should be noted
> that this works fine on my laptop with Gentoo as long as the network
> settings are correct to avoid hitting the soft block on failure and as
> long as wpa_supplicant is recent enough to handle the rfkill events
> properly.

So you are implying that it's actually an issue of my network settings
and/or wpa_supplicant version? Is this the quintessence?

If so, what networksettings do I require and what version of
wpa_supplicant do you use?

Thanks, it sounded like it's already solved

> In addition, it should be noted that any manual operation
> after "net.wlan# stop" will need to take care of unblocking the soft
> block before actually trying to use the radio.
> 
> - Jouni

There, I lost you again. After the stop, there is no soft lock in place,
why are you saying this then?

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

I've just inserted a makeshift "rfkill unblock 0" in the init script
which got me rid of the two SIOCSIFFLAGS errors. But I still get an
authentication timed out, and apart from that nothing changed. I guess
there has to be something deeper than just a flawed init script.

I can't rule out that I have made a kernel misconfig apart from the
explicit settings which are stated to be required for compat-wireless.


On Thu, Feb 24, 2011 at 05:21:34PM +0100, Cedric Sodhi wrote:
> I'm not sure whether I understand every bit of your reply. For practical
> reasons, I would like to skip directly to...
> 
> On Thu, Feb 24, 2011 at 04:08:15PM +0200, Jouni Malinen wrote:
> > On Thu, 2011-02-24 at 03:52 -0800, Peter Stuge wrote:
> > > Quick grep rfkill -r /lib/rc* /etc/init.d comes up empty.
> > 
> > It is done with iwconfig. iwconfig_post_stop and failure in
> > iwconfig_pre_start results in "iwconfig wlan# txpower off" getting
> > executed. This results in soft blocking the interface.
> > 
> > iwconfig_pre_starts removes the soft block with iwconfig_defaults that
> > runs "iwconfig wlan# txpower auto", but this happens only after
> > wpa_supplicant has been started (I would do that in different order..)
> > and as such, depends on wpa_supplicant being able to handle a dynamic
> > rfkill blocking change.
> > 
> > Anyway, this is getting way off-topic for this mailing list. Like I
> > mentioned before, if this soft blocking causes issues, the question
> > should be directed to Gentoo maintainers. Though, it should be noted
> > that this works fine on my laptop with Gentoo as long as the network
> > settings are correct to avoid hitting the soft block on failure and as
> > long as wpa_supplicant is recent enough to handle the rfkill events
> > properly.
> 
> So you are implying that it's actually an issue of my network settings
> and/or wpa_supplicant version? Is this the quintessence?
> 
> If so, what networksettings do I require and what version of
> wpa_supplicant do you use?
> 
> Thanks, it sounded like it's already solved
> 
> > In addition, it should be noted that any manual operation
> > after "net.wlan# stop" will need to take care of unblocking the soft
> > block before actually trying to use the radio.
> > 
> > - Jouni
> 
> There, I lost you again. After the stop, there is no soft lock in place,
> why are you saying this then?
> 
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] ar9271 SIOCSIFFLAGS error and authentication timeout

[Cedric Sodhi]

Oh dear, this is so embarassing. It turned out that I neglected to
authenticate the device at my router.

I'm _so_ sorry for wasting your time!

It's not quite working, but I guess the rest is a matter of
configuration.

Again, I'm very sorry, I got lost in the errors and did not think of the
obvious. So turns out 132 wasn't responsible, my own stupidity was :-(

I'll handle from here on, please take my apologies, I'm embarassed.