Linux wireless drivers development
 help / color / mirror / Atom feed
* Re: [ath5k-devel] [PATCH v2] ath5k: disable ASPM
From: Luis R. Rodriguez @ 2010-06-22 16:48 UTC (permalink / raw)
  To: Matthew Garrett
  Cc: Jussi Kivilinna, Maxim Levitsky, David Quan, Bob Copeland,
	Luis R. Rodriguez, ath5k-devel, linux-wireless, linux-kernel
In-Reply-To: <20100622163138.GD20668@srcf.ucam.org>

On Tue, Jun 22, 2010 at 9:31 AM, Matthew Garrett <mjg@redhat.com> wrote:
> On Mon, Jun 21, 2010 at 01:39:07PM -0700, Luis R. Rodriguez wrote:
>> Last I reviewed CONFIG_PCIEASPM won't buy you *anything* other than
>> debugging knobs. With it you can force all devices to enable ASPM
>> completely on or disable it. Both of which I think are not really
>> useful and instead should be done in userspace given that if you are
>> testing ASPM you likely want to test only one one device and its
>> respective root complex, not all at the same time.
>
> It buys you enabling of ASPM on devices that the BIOS hasn't configured,
> which is legitimate and useful.

Sure, I agree with that, but it also will enable ASPM for *all*
devices which have the capability which IMHO is a terrible idea for
users when all they want to do is enable ASPM for one device. Instead
I recommend users to enable ASPM for their devices selectively and
from userspace.

  Luis

^ permalink raw reply

* Re: intel 5100/iwlagn bug in 2.6.35-rc2 during large file transfer
From: reinette chatre @ 2010-06-22 16:48 UTC (permalink / raw)
  To: Richard Farina; +Cc: linux-wireless@vger.kernel.org
In-Reply-To: <4C198EF0.5080807@gmail.com>

On Wed, 2010-06-16 at 19:56 -0700, Richard Farina wrote:
> The repeated line appears ad infinitum filling my dmesg buffer.  This of 
> hangcheck timer seem to trigger with every large file transfer on my 
> intel 5100.  What would you like me to do to provide a more useful 
> output as this is currently extremely easy to reproduce.  Kernel 2.6.34 
> using compat-wireless stable 2.6.35-rc2
> 
> Thanks,
> Rick Farina
> 
> phy0: failed to reallocate TX buffer
> phy0: failed to reallocate TX buffer
> phy0: failed to reallocate TX buffer
> phy0: failed to reallocate TX buffer
> phy0: failed to reallocate TX buffer
> phy0: failed to reallocate TX buffer
> phy0: failed to reallocate TX buffer

First mac80211 runs out of memory ... it cannot even allocate enough
memory for a skb header.

> net_ratelimit: 22 callbacks suppressed
> __alloc_pages_slowpath: 3799 callbacks suppressed
> swapper: page allocation failure. order:1, mode:0x4020
> Pid: 0, comm: swapper Not tainted 2.6.34-pentoo #5
> Call Trace:
>  <IRQ>  [<ffffffff8109cb74>] __alloc_pages_nodemask+0x571/0x5b9
>  [<ffffffff816732e9>] ? skb_release_data+0xc4/0xc9
>  [<ffffffffa04701e4>] iwlagn_rx_allocate+0x98/0x25a [iwlagn]

Next driver runs out of memory.

Note that the above are all atomic allocations that fail and should be
able to recover. 

Is your system low on memory? Are you running applications that take a
lot of memory? Does your wifi connection drop or otherwise suffer at the
time you see these messages?

Reinette




^ permalink raw reply

* Re: [ath5k-devel] [PATCH v2] ath5k: disable ASPM
From: Matthew Garrett @ 2010-06-22 16:31 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: Jussi Kivilinna, Maxim Levitsky, David Quan, Bob Copeland,
	Luis R. Rodriguez, ath5k-devel, linux-wireless, linux-kernel
In-Reply-To: <AANLkTikkt4dqYWrwtTCJ8tJZLB1kZXgF1KvaPsIOO3Dl@mail.gmail.com>

On Mon, Jun 21, 2010 at 01:39:07PM -0700, Luis R. Rodriguez wrote:
> Last I reviewed CONFIG_PCIEASPM won't buy you *anything* other than
> debugging knobs. With it you can force all devices to enable ASPM
> completely on or disable it. Both of which I think are not really
> useful and instead should be done in userspace given that if you are
> testing ASPM you likely want to test only one one device and its
> respective root complex, not all at the same time.

It buys you enabling of ASPM on devices that the BIOS hasn't configured, 
which is legitimate and useful.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

^ permalink raw reply

* Re: Recent results with BCM4312 on Netbook
From: Michael Büsch @ 2010-06-22 16:31 UTC (permalink / raw)
  To: Larry Finger; +Cc: b43-dev, wireless, John Linville
In-Reply-To: <4C20D884.3010501@lwfinger.net>

On 06/22/2010 05:36 PM, Larry Finger wrote:
> My first discovery is that if PIO mode is to be used, it is not sufficient
> to load the module with the "pio=1" option, but that both "qos=0" and
> "nohwcrypt=1" options must also be used, at least for WPA/WPA2 networks.

That is known. I posted it once or twice. It is b43 making bad
assumptions about mac80211 behavior. And mac80211 behavior changed...
b43 does modify the number of queues in the data structure after it
registered things to mac80211. That used to work properly in the past.
But it breaks now. The init does have to be re-ordered and implementation
of async firmware loading is required to fix that.

> No other combination works. In addition, the automatic failover to PIO
> mode does not work unless those two options were used when the module was
> loaded. Thus both of the following work:

It only works by accident anyway. But I already said that several times.

-- 
Greetings Michael.

^ permalink raw reply

* Re: ASPM status for iwlwifi and power-management (in general)
From: Luis R. Rodriguez @ 2010-06-22 15:54 UTC (permalink / raw)
  To: sedat.dilek; +Cc: wireless, Reinette Chatre, Johannes Berg, John Linville
In-Reply-To: <AANLkTilpqUnWG2CnMNZR7a45rY9cbqks3W-gkjsMbYOQ@mail.gmail.com>

On Tue, Jun 22, 2010 at 3:44 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi,
>
> yesterday, I was playing with PowerTop and my iwl3945 still is in the
> TOP 3 of energy user.
>
> Inspired by the recently published ASPM doc from Luis [2] I played a
> bit with ASPM.
>
> Currently, I am using a 2.6.35-rc3 Linux-kernel with latest
> acpi-2.6/release fixes.
>
> # dmesg | grep -i aspm
> [    0.226963] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe
> device.  You can enable it with 'pcie_aspm=force'
> [    0.227629] pci 0000:08:00.0: disabling ASPM on pre-1.1 PCIe
> device.  You can enable it with 'pcie_aspm=force'
> [    0.228205] pci 0000:10:00.0: disabling ASPM on pre-1.1 PCIe
> device.  You can enable it with 'pcie_aspm=force'
>
> # for i in 01:00.0 08:00.0 10:00.0 ; do lspci -v | grep $i ; done
> 01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility
> Radeon X1300] (prog-if 00 [VGA controller])
> 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5753M
> Gigabit Ethernet PCI Express (rev 21)
> 10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
> [Golan] Network Connection (rev 02)
>
> # lspci -vvvv -s 10:00.0 | grep -i aspm
>                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
> <128ns, L1 <64us
>                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
>
> Before I will try 'pcie_aspm=force' cheat-code

I should note I discourage the usage of pcie_aspm=force, it will try
to enable ASPM for all devices which do have the capability, and this
means when you are enabling it you are not only testing ASPM on the
device you had in mind but *all* devices capable of it.

> I wanted to ask about
> the status of iwlwifi and ASPM.
> Is there code available. yet?

Driver code for ASPM only exists to help tweak it if for whatever
reason it does need tweaking. An example is ath9k which disables the
PLL when it uses ASPM to save power. iwlagn or iwl3945 might have
similar stuff, but not sure. Technically drivers should not need any
code for ASPM unless its driver specific tweaks.

> Which kernel has it - linux-next,
> wireless-testing GIT, iwlwifi GIT?

ASPM can be used so long as you just have a PCIE bus. If the driver
has ASPM tweaks that's a different thing.

> Which user-space apps are required?

None.

> IIRC iw [3] from GIT has already "iw: add set/get power_save commands" [4].

That's different. Read:

http://wireless.kernel.org/en/users/Documentation/Power-consumption

  Luis

> Anyone tested ASPM with iwlwifi hardware? Experiences?
>
> Beyond ASPM code, what is the actual status on power-mangement for
> wifi-hardware in general?
> IIRC it was turned off by default (with 2.6.33?)?
>
> Thanks for any help in advance.
>
>
> Kind Regards,
> - Sedat -
>
>
> [1] http://wireless.kernel.org/en/users/Documentation/ASPM
> [2] http://marc.info/?l=linux-wireless&m=127716115227206&w=2
> [3] http://git.sipsolutions.net/?p=iw.git
> [4] http://git.sipsolutions.net/?p=iw.git;a=commit;h=cf40ef379fd6c74a01092d1dfdd936385ea402b0
>

^ permalink raw reply

* Recent results with BCM4312 on Netbook
From: Larry Finger @ 2010-06-22 15:36 UTC (permalink / raw)
  To: Michael Buesch; +Cc: b43-dev, wireless, John Linville

Michael,

I have some good news. The Netbook that came from John is suddenly
developing DMA errors for the BCM4312, even though it does not have a
Phoenix BIOS. I have no idea why it did not fail this way earlier, but at
least I have a machine to debug that failure.

My first discovery is that if PIO mode is to be used, it is not sufficient
to load the module with the "pio=1" option, but that both "qos=0" and
"nohwcrypt=1" options must also be used, at least for WPA/WPA2 networks.
No other combination works. In addition, the automatic failover to PIO
mode does not work unless those two options were used when the module was
loaded. Thus both of the following work:

modprobe b43 pio=1 qos=0 nohwcrypt=1
modprobe b43 qos=0 hwcrypt=1

The second example gets a fatal DMA error and resets the controller before
the network comes up. I tried setting the latter two options before the
controller reset call in the failover, but that did not work.

If you have suggestions on changes in the switch from DMA to PIO mode,
please send them to me. In the meantime, I will be looking at differences
in the MMIO traces between wl and b43 to try to fix the DMA problem at the
source of the trouble.

Larry

^ permalink raw reply

* [PATCH 2/2] at76c50x-usb: Extract bssid from authentication frame
From: Sebastian Smolorz @ 2010-06-22 14:55 UTC (permalink / raw)
  To: kalle.valo; +Cc: linux-wireless
In-Reply-To: <201006221651.24853.Sebastian.Smolorz@gmx.de>

The driver at76c50x-usb is unable to authenticate with an AP since
kernel 2.6.31 for the following reason: The join command of the firmware
needs to be sent with the right bssid before any transmission can start.
Before kernel 2.6.31 mac80211 informed its drivers about the changing
bssid early enough for at76c50x-usb but during the development of 2.6.31
mac80211's behaviour changed. Now a new bssid is set after the
association.

This patch changes the tx routine of the driver at76c50x-usb in such a
way that a new bssid is extracted from an authentication frame and the
join command with that bssid is processed.

Signed-off-by: Sebastian Smolorz <sesmo@gmx.net>
---
 drivers/net/wireless/at76c50x-usb.c |   36 +++++++++++++++++++++++++++++++++++
 drivers/net/wireless/at76c50x-usb.h |    1 +
 2 files changed, 37 insertions(+), 0 deletions(-)

diff --git a/drivers/net/wireless/at76c50x-usb.c b/drivers/net/wireless/at76c50x-usb.c
index cb3d4b7..98328b7 100644
--- a/drivers/net/wireless/at76c50x-usb.c
+++ b/drivers/net/wireless/at76c50x-usb.c
@@ -7,6 +7,7 @@
  * Copyright (c) 2004 Balint Seeber <n0_5p4m_p13453@hotmail.com>
  * Copyright (c) 2007 Guido Guenther <agx@sigxcpu.org>
  * Copyright (c) 2007 Kalle Valo <kalle.valo@iki.fi>
+ * Copyright (c) 2010 Sebastian Smolorz <sesmo@gmx.net>
  *
  * This program is free software; you can redistribute it and/or
  * modify it under the terms of the GNU General Public License as
@@ -1685,6 +1686,22 @@ static int at76_join(struct at76_priv *priv)
 	return 0;
 }
 
+static void at76_work_join_bssid(struct work_struct *work)
+{
+	struct at76_priv *priv = container_of(work, struct at76_priv,
+					      work_join_bssid);
+
+	if (priv->device_unplugged)
+		return;
+
+	mutex_lock(&priv->mtx);
+
+	if (is_valid_ether_addr(priv->bssid))
+		at76_join(priv);
+
+	mutex_unlock(&priv->mtx);
+}
+
 static void at76_mac80211_tx_callback(struct urb *urb)
 {
 	struct at76_priv *priv = urb->context;
@@ -1722,6 +1739,7 @@ static int at76_mac80211_tx(struct ieee80211_hw *hw, struct sk_buff *skb)
 	struct at76_priv *priv = hw->priv;
 	struct at76_tx_buffer *tx_buffer = priv->bulk_out_buffer;
 	struct ieee80211_tx_info *info = IEEE80211_SKB_CB(skb);
+	struct ieee80211_mgmt *mgmt = (struct ieee80211_mgmt *)skb->data;
 	int padding, submit_len, ret;
 
 	at76_dbg(DBG_MAC80211, "%s()", __func__);
@@ -1732,6 +1750,21 @@ static int at76_mac80211_tx(struct ieee80211_hw *hw, struct sk_buff *skb)
 		return NETDEV_TX_BUSY;
 	}
 
+	/* The following code lines are important when the device is going to
+	 * authenticate with a new bssid. The driver must send CMD_JOIN before
+	 * an authentication frame is transmitted. For this to succeed, the
+	 * correct bssid of the AP must be known. As mac80211 does not inform
+	 * drivers about the bssid prior to the authentication process the
+	 * following workaround is necessary. If the TX frame is an
+	 * authentication frame extract the bssid and send the CMD_JOIN. */
+	if (mgmt->frame_control & cpu_to_le16(IEEE80211_STYPE_AUTH)) {
+		if (compare_ether_addr(priv->bssid, mgmt->bssid)) {
+			memcpy(priv->bssid, mgmt->bssid, ETH_ALEN);
+			ieee80211_queue_work(hw, &priv->work_join_bssid);
+			return NETDEV_TX_BUSY;
+		}
+	}
+
 	ieee80211_stop_queues(hw);
 
 	at76_ledtrig_tx_activity();	/* tell ledtrigger we send a packet */
@@ -1806,6 +1839,7 @@ static void at76_mac80211_stop(struct ieee80211_hw *hw)
 	at76_dbg(DBG_MAC80211, "%s()", __func__);
 
 	cancel_delayed_work(&priv->dwork_hw_scan);
+	cancel_work_sync(&priv->work_join_bssid);
 	cancel_work_sync(&priv->work_set_promisc);
 
 	mutex_lock(&priv->mtx);
@@ -2107,6 +2141,7 @@ static struct at76_priv *at76_alloc_new_device(struct usb_device *udev)
 	mutex_init(&priv->mtx);
 	INIT_WORK(&priv->work_set_promisc, at76_work_set_promisc);
 	INIT_WORK(&priv->work_submit_rx, at76_work_submit_rx);
+	INIT_WORK(&priv->work_join_bssid, at76_work_join_bssid);
 	INIT_DELAYED_WORK(&priv->dwork_hw_scan, at76_dwork_hw_scan);
 
 	tasklet_init(&priv->rx_tasklet, at76_rx_tasklet, 0);
@@ -2508,5 +2543,6 @@ MODULE_AUTHOR("Balint Seeber <n0_5p4m_p13453@hotmail.com>");
 MODULE_AUTHOR("Pavel Roskin <proski@gnu.org>");
 MODULE_AUTHOR("Guido Guenther <agx@sigxcpu.org>");
 MODULE_AUTHOR("Kalle Valo <kalle.valo@iki.fi>");
+MODULE_AUTHOR("Sebastian Smolorz <sesmo@gmx.net>");
 MODULE_DESCRIPTION(DRIVER_DESC);
 MODULE_LICENSE("GPL");
diff --git a/drivers/net/wireless/at76c50x-usb.h b/drivers/net/wireless/at76c50x-usb.h
index 1ec5ccf..db89d72 100644
--- a/drivers/net/wireless/at76c50x-usb.h
+++ b/drivers/net/wireless/at76c50x-usb.h
@@ -387,6 +387,7 @@ struct at76_priv {
 	/* work queues */
 	struct work_struct work_set_promisc;
 	struct work_struct work_submit_rx;
+	struct work_struct work_join_bssid;
 	struct delayed_work dwork_hw_scan;
 
 	struct tasklet_struct rx_tasklet;
-- 
1.6.4.4


^ permalink raw reply related

* [PATCH 1/2] at76c50x-usb: Move function at76_join() several lines up
From: Sebastian Smolorz @ 2010-06-22 14:53 UTC (permalink / raw)
  To: kalle.valo; +Cc: linux-wireless
In-Reply-To: <201006221651.24853.Sebastian.Smolorz@gmx.de>

This patch does a simple code move of at76_join() so that
at76_mac80211_tx() follows at76_join() in the driver's source file.

This is a preparatory patch for the following patch where we need
to call at76_join() from at76_mac80211_tx() in order to
authenticate successfully with a bssid.

Signed-off-by: Sebastian Smolorz <sesmo@gmx.net>
---
 drivers/net/wireless/at76c50x-usb.c |   72 +++++++++++++++++-----------------
 1 files changed, 36 insertions(+), 36 deletions(-)

diff --git a/drivers/net/wireless/at76c50x-usb.c b/drivers/net/wireless/at76c50x-usb.c
index 8a2d4af..cb3d4b7 100644
--- a/drivers/net/wireless/at76c50x-usb.c
+++ b/drivers/net/wireless/at76c50x-usb.c
@@ -1649,6 +1649,42 @@ exit:
 		return NULL;
 }
 
+static int at76_join(struct at76_priv *priv)
+{
+	struct at76_req_join join;
+	int ret;
+
+	memset(&join, 0, sizeof(struct at76_req_join));
+	memcpy(join.essid, priv->essid, priv->essid_size);
+	join.essid_size = priv->essid_size;
+	memcpy(join.bssid, priv->bssid, ETH_ALEN);
+	join.bss_type = INFRASTRUCTURE_MODE;
+	join.channel = priv->channel;
+	join.timeout = cpu_to_le16(2000);
+
+	at76_dbg(DBG_MAC80211, "%s: sending CMD_JOIN", __func__);
+	ret = at76_set_card_command(priv->udev, CMD_JOIN, &join,
+				    sizeof(struct at76_req_join));
+
+	if (ret < 0) {
+		printk(KERN_ERR "%s: at76_set_card_command failed: %d\n",
+		       wiphy_name(priv->hw->wiphy), ret);
+		return 0;
+	}
+
+	ret = at76_wait_completion(priv, CMD_JOIN);
+	at76_dbg(DBG_MAC80211, "%s: CMD_JOIN returned: 0x%02x", __func__, ret);
+	if (ret != CMD_STATUS_COMPLETE) {
+		printk(KERN_ERR "%s: at76_wait_completion failed: %d\n",
+		       wiphy_name(priv->hw->wiphy), ret);
+		return 0;
+	}
+
+	at76_set_pm_mode(priv);
+
+	return 0;
+}
+
 static void at76_mac80211_tx_callback(struct urb *urb)
 {
 	struct at76_priv *priv = urb->context;
@@ -1818,42 +1854,6 @@ static void at76_remove_interface(struct ieee80211_hw *hw,
 	at76_dbg(DBG_MAC80211, "%s()", __func__);
 }
 
-static int at76_join(struct at76_priv *priv)
-{
-	struct at76_req_join join;
-	int ret;
-
-	memset(&join, 0, sizeof(struct at76_req_join));
-	memcpy(join.essid, priv->essid, priv->essid_size);
-	join.essid_size = priv->essid_size;
-	memcpy(join.bssid, priv->bssid, ETH_ALEN);
-	join.bss_type = INFRASTRUCTURE_MODE;
-	join.channel = priv->channel;
-	join.timeout = cpu_to_le16(2000);
-
-	at76_dbg(DBG_MAC80211, "%s: sending CMD_JOIN", __func__);
-	ret = at76_set_card_command(priv->udev, CMD_JOIN, &join,
-				    sizeof(struct at76_req_join));
-
-	if (ret < 0) {
-		printk(KERN_ERR "%s: at76_set_card_command failed: %d\n",
-		       wiphy_name(priv->hw->wiphy), ret);
-		return 0;
-	}
-
-	ret = at76_wait_completion(priv, CMD_JOIN);
-	at76_dbg(DBG_MAC80211, "%s: CMD_JOIN returned: 0x%02x", __func__, ret);
-	if (ret != CMD_STATUS_COMPLETE) {
-		printk(KERN_ERR "%s: at76_wait_completion failed: %d\n",
-		       wiphy_name(priv->hw->wiphy), ret);
-		return 0;
-	}
-
-	at76_set_pm_mode(priv);
-
-	return 0;
-}
-
 static void at76_dwork_hw_scan(struct work_struct *work)
 {
 	struct at76_priv *priv = container_of(work, struct at76_priv,
-- 
1.6.4.4


^ permalink raw reply related

* [PATCH 0/2] at76c50x-usb.c: Fix broken authentication process
From: Sebastian Smolorz @ 2010-06-22 14:51 UTC (permalink / raw)
  To: kalle.valo; +Cc: linux-wireless

Fix authentication process of wireless driver at76c50x-usb.c which was broken
since kernel 2.6.31

Sebastian Smolorz (2):
  at76c50x-usb: Move function at76_join() several lines up
  at76c50x-usb: Extract bssid from authentication frame

 drivers/net/wireless/at76c50x-usb.c |  108 +++++++++++++++++++++++------------
 drivers/net/wireless/at76c50x-usb.h |    1 +
 2 files changed, 73 insertions(+), 36 deletions(-)


^ permalink raw reply

* Disable post-backoff
From: Dennis Borgmann @ 2010-06-22 12:09 UTC (permalink / raw)
  To: ath5k-devel, linux-wireless

Hello ath5k-list and linux-wireless-list!

I am sorry, if this is a double-post. I sent this message to the wrong
address before. I apologize.

For testing reasons I would like to disable backoff times in ath5k.

In the code of ath5k we have the macro AR5K_TXQ_FLAG_BACKOFF_DISABLE in
file linux-2.6.34/drivers/net/wireless/ath/ath5k/ath5k.h. It is issued
in the file linux-2.6.34/drivers/net/wireless/ath/ath5k/qcu.c in line 384.

How can this option be activated?

Kind regards, Dennis

^ permalink raw reply

* Re: ASPM status for iwlwifi and power-management (in general)
From: Sedat Dilek @ 2010-06-22 11:11 UTC (permalink / raw)
  To: wireless; +Cc: Luis R. Rodriguez, Reinette Chatre, Johannes Berg, John Linville
In-Reply-To: <AANLkTilr1jzS2-q3Je_QEKE-eZyHSwIIbbd07tZFJgJQ@mail.gmail.com>

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

Attached iwl3945_ASPM-enabled_full.txt

- Sedat -

On Tue, Jun 22, 2010 at 1:09 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> I booted now with 'pcie_aspm=force':
>
> # dmesg | grep -i aspm
> [    0.000000] Kernel command line:
> BOOT_IMAGE=/boot/vmlinuz-2.6.35-rc3-iniza-686-kms
> root=UUID=b1333729-42ce-4a1b-9669-41c14c42bb81 ro nomodeset 3
> pcie_aspm=force
> [    0.000000] PCIe ASPM is forcedly enabled
>
> # lspci -vvvv -s 10:00.0 | grep -i aspm
>                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
> <128ns, L1 <64us
>                LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
>
> Full dmesg and lspci for iwl3945 outputs are attached.
>
> - Sedat -
>
> On Tue, Jun 22, 2010 at 12:44 PM, Sedat Dilek
> <sedat.dilek@googlemail.com> wrote:
>> Hi,
>>
>> yesterday, I was playing with PowerTop and my iwl3945 still is in the
>> TOP 3 of energy user.
>>
>> Inspired by the recently published ASPM doc from Luis [2] I played a
>> bit with ASPM.
>>
>> Currently, I am using a 2.6.35-rc3 Linux-kernel with latest
>> acpi-2.6/release fixes.
>>
>> # dmesg | grep -i aspm
>> [    0.226963] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe
>> device.  You can enable it with 'pcie_aspm=force'
>> [    0.227629] pci 0000:08:00.0: disabling ASPM on pre-1.1 PCIe
>> device.  You can enable it with 'pcie_aspm=force'
>> [    0.228205] pci 0000:10:00.0: disabling ASPM on pre-1.1 PCIe
>> device.  You can enable it with 'pcie_aspm=force'
>>
>> # for i in 01:00.0 08:00.0 10:00.0 ; do lspci -v | grep $i ; done
>> 01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility
>> Radeon X1300] (prog-if 00 [VGA controller])
>> 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5753M
>> Gigabit Ethernet PCI Express (rev 21)
>> 10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
>> [Golan] Network Connection (rev 02)
>>
>> # lspci -vvvv -s 10:00.0 | grep -i aspm
>>                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
>> <128ns, L1 <64us
>>                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
>>
>> Before I will try 'pcie_aspm=force' cheat-code I wanted to ask about
>> the status of iwlwifi and ASPM.
>> Is there code available. yet? Which kernel has it - linux-next,
>> wireless-testing GIT, iwlwifi GIT?
>> Which user-space apps are required?
>> IIRC iw [3] from GIT has already "iw: add set/get power_save commands" [4].
>> Anyone tested ASPM with iwlwifi hardware? Experiences?
>>
>> Beyond ASPM code, what is the actual status on power-mangement for
>> wifi-hardware in general?
>> IIRC it was turned off by default (with 2.6.33?)?
>>
>> Thanks for any help in advance.
>>
>>
>> Kind Regards,
>> - Sedat -
>>
>>
>> [1] http://wireless.kernel.org/en/users/Documentation/ASPM
>> [2] http://marc.info/?l=linux-wireless&m=127716115227206&w=2
>> [3] http://git.sipsolutions.net/?p=iw.git
>> [4] http://git.sipsolutions.net/?p=iw.git;a=commit;h=cf40ef379fd6c74a01092d1dfdd936385ea402b0
>>
>

[-- Attachment #2: iwl3945_ASPM-enabled_full.txt --]
[-- Type: text/plain, Size: 2191 bytes --]

10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
	Subsystem: Hewlett-Packard Company Compaq 6710b or nx9420 Notebook
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 45
	Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0300c  Data: 41a1
	Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP+ BadDLLP+ Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [140 v1] Device Serial Number 00-19-d2-ff-ff-62-e4-bb
	Kernel driver in use: iwl3945


^ permalink raw reply

* Re: ASPM status for iwlwifi and power-management (in general)
From: Sedat Dilek @ 2010-06-22 11:09 UTC (permalink / raw)
  To: wireless; +Cc: Luis R. Rodriguez, Reinette Chatre, Johannes Berg, John Linville
In-Reply-To: <AANLkTilpqUnWG2CnMNZR7a45rY9cbqks3W-gkjsMbYOQ@mail.gmail.com>

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

I booted now with 'pcie_aspm=force':

# dmesg | grep -i aspm
[    0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.35-rc3-iniza-686-kms
root=UUID=b1333729-42ce-4a1b-9669-41c14c42bb81 ro nomodeset 3
pcie_aspm=force
[    0.000000] PCIe ASPM is forcedly enabled

# lspci -vvvv -s 10:00.0 | grep -i aspm
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
<128ns, L1 <64us
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+

Full dmesg and lspci for iwl3945 outputs are attached.

- Sedat -

On Tue, Jun 22, 2010 at 12:44 PM, Sedat Dilek
<sedat.dilek@googlemail.com> wrote:
> Hi,
>
> yesterday, I was playing with PowerTop and my iwl3945 still is in the
> TOP 3 of energy user.
>
> Inspired by the recently published ASPM doc from Luis [2] I played a
> bit with ASPM.
>
> Currently, I am using a 2.6.35-rc3 Linux-kernel with latest
> acpi-2.6/release fixes.
>
> # dmesg | grep -i aspm
> [    0.226963] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe
> device.  You can enable it with 'pcie_aspm=force'
> [    0.227629] pci 0000:08:00.0: disabling ASPM on pre-1.1 PCIe
> device.  You can enable it with 'pcie_aspm=force'
> [    0.228205] pci 0000:10:00.0: disabling ASPM on pre-1.1 PCIe
> device.  You can enable it with 'pcie_aspm=force'
>
> # for i in 01:00.0 08:00.0 10:00.0 ; do lspci -v | grep $i ; done
> 01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility
> Radeon X1300] (prog-if 00 [VGA controller])
> 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5753M
> Gigabit Ethernet PCI Express (rev 21)
> 10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
> [Golan] Network Connection (rev 02)
>
> # lspci -vvvv -s 10:00.0 | grep -i aspm
>                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
> <128ns, L1 <64us
>                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
>
> Before I will try 'pcie_aspm=force' cheat-code I wanted to ask about
> the status of iwlwifi and ASPM.
> Is there code available. yet? Which kernel has it - linux-next,
> wireless-testing GIT, iwlwifi GIT?
> Which user-space apps are required?
> IIRC iw [3] from GIT has already "iw: add set/get power_save commands" [4].
> Anyone tested ASPM with iwlwifi hardware? Experiences?
>
> Beyond ASPM code, what is the actual status on power-mangement for
> wifi-hardware in general?
> IIRC it was turned off by default (with 2.6.33?)?
>
> Thanks for any help in advance.
>
>
> Kind Regards,
> - Sedat -
>
>
> [1] http://wireless.kernel.org/en/users/Documentation/ASPM
> [2] http://marc.info/?l=linux-wireless&m=127716115227206&w=2
> [3] http://git.sipsolutions.net/?p=iw.git
> [4] http://git.sipsolutions.net/?p=iw.git;a=commit;h=cf40ef379fd6c74a01092d1dfdd936385ea402b0
>

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 62581 bytes --]

00000] ACPI: RSDP 000f7870 00024 (v02 HP    )
[    0.000000] ACPI: XSDT 7ffe57c8 0007C (v01 HPQOEM SLIC-MPC 00000001 HP   00000001)
[    0.000000] ACPI: FACP 7ffe5684 000F4 (v04 HP     30AC     00000003 HP   00000001)
[    0.000000] ACPI: DSDT 7ffe5acc 104BB (v01 HP       nc6400 00010000 MSFT 0100000E)
[    0.000000] ACPI: FACS 7fff7e80 00040
[    0.000000] ACPI: SLIC 7ffe5844 00176 (v01 HPQOEM SLIC-MPC 00000001 HP   00000001)
[    0.000000] ACPI: HPET 7ffe59bc 00038 (v01 HP     30AC     00000001 HP   00000001)
[    0.000000] ACPI: APIC 7ffe59f4 00068 (v01 HP     30AC     00000001 HP   00000001)
[    0.000000] ACPI: MCFG 7ffe5a5c 0003C (v01 HP     30AC     00000001 HP   00000001)
[    0.000000] ACPI: TCPA 7ffe5a98 00032 (v02 HP     30AC     00000001 HP   00000001)
[    0.000000] ACPI: SSDT 7fff5f87 00059 (v01 HP       HPQNLP 00000001 MSFT 0100000E)
[    0.000000] ACPI: SSDT 7fff5fe0 0032D (v01 HP       HPQSAT 00000001 MSFT 0100000E)
[    0.000000] ACPI: SSDT 7fff6b62 0025F (v01 HP      Cpu0Tst 00003000 INTL 20060317)
[    0.000000] ACPI: SSDT 7fff6dc1 000A6 (v01 HP      Cpu1Tst 00003000 INTL 20060317)
[    0.000000] ACPI: SSDT 7fff6e67 004D7 (v01 HP        CpuPm 00003000 INTL 20060317)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] 1159MB HIGHMEM available.
[    0.000000] 887MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 377fe000
[    0.000000]   low ram: 0 - 377fe000
[    0.000000] early_res array is doubled to 64 at [8000 - 87ff]
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000001 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x000377fe
[    0.000000]   HighMem  0x000377fe -> 0x0007ffd0
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000001 -> 0x0000009f
[    0.000000]     0: 0x00000100 -> 0x0007ffd0
[    0.000000] On node 0 totalpages: 524142
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 3966 pages, LIFO batch:0
[    0.000000]   Normal zone: 1744 pages used for memmap
[    0.000000]   Normal zone: 221486 pages, LIFO batch:31
[    0.000000]   HighMem zone: 2320 pages used for memmap
[    0.000000]   HighMem zone: 294594 pages, LIFO batch:31
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0x1008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 1, 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 2 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 40
[    0.000000] early_res array is doubled to 128 at [8800 - 97ff]
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
[    0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 80000000 (gap: 80000000:7ec00000)
[    0.000000] Booting paravirtualized kernel on bare hardware
[    0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:2 nr_node_ids:1
[    0.000000] PERCPU: Embedded 13 pages/cpu @c2400000 s29696 r0 d23552 u2097152
[    0.000000] pcpu-alloc: s29696 r0 d23552 u2097152 alloc=1*4194304
[    0.000000] pcpu-alloc: [0] 0 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 520046
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-rc3-iniza-686-kms root=UUID=b1333729-42ce-4a1b-9669-41c14c42bb81 ro nomodeset 3 pcie_aspm=force
[    0.000000] PCIe ASPM is forcedly enabled
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] Subtract (76 early reservations)
[    0.000000]   #1 [0000001000 - 0000002000]   EX TRAMPOLINE
[    0.000000]   #2 [0001000000 - 00013e60d4]   TEXT DATA BSS
[    0.000000]   #3 [000009fc00 - 0000100000]   BIOS reserved
[    0.000000]   #4 [00013e7000 - 00013ed140]             BRK
[    0.000000]   #5 [0000002000 - 0000003000]      TRAMPOLINE
[    0.000000]   #6 [0000003000 - 0000007000]     ACPI WAKEUP
[    0.000000]   #7 [0000007000 - 0000008000]         PGTABLE
[    0.000000]   #8 [0000100000 - 0000a6a000]     NEW RAMDISK
[    0.000000]   #9 [00013ee000 - 00013ef000]         BOOTMEM
[    0.000000]   #10 [00013e6200 - 00013e6300]         BOOTMEM
[    0.000000]   #11 [00013ef000 - 000146f000]         BOOTMEM
[    0.000000]   #12 [000146f000 - 00014ef000]         BOOTMEM
[    0.000000]   #13 [00014ef000 - 000156f000]         BOOTMEM
[    0.000000]   #14 [000156f000 - 00015ef000]         BOOTMEM
[    0.000000]   #15 [00015ef000 - 000166f000]         BOOTMEM
[    0.000000]   #16 [000166f000 - 00016ef000]         BOOTMEM
[    0.000000]   #17 [00016ef000 - 000176f000]         BOOTMEM
[    0.000000]   #18 [000176f000 - 00017ef000]         BOOTMEM
[    0.000000]   #19 [00017ef000 - 000186f000]         BOOTMEM
[    0.000000]   #20 [000186f000 - 00018ef000]         BOOTMEM
[    0.000000]   #21 [00018ef000 - 000196f000]         BOOTMEM
[    0.000000]   #22 [000196f000 - 00019ef000]         BOOTMEM
[    0.000000]   #23 [00019ef000 - 0001a6f000]         BOOTMEM
[    0.000000]   #24 [0001a6f000 - 0001aef000]         BOOTMEM
[    0.000000]   #25 [0001aef000 - 0001b6f000]         BOOTMEM
[    0.000000]   #26 [0001b6f000 - 0001bef000]         BOOTMEM
[    0.000000]   #27 [0001bef000 - 0001c6f000]         BOOTMEM
[    0.000000]   #28 [0001c6f000 - 0001cef000]         BOOTMEM
[    0.000000]   #29 [0001cef000 - 0001d6f000]         BOOTMEM
[    0.000000]   #30 [0001d6f000 - 0001def000]         BOOTMEM
[    0.000000]   #31 [0001def000 - 0001e6f000]         BOOTMEM
[    0.000000]   #32 [0001e6f000 - 0001eef000]         BOOTMEM
[    0.000000]   #33 [0001eef000 - 0001f6f000]         BOOTMEM
[    0.000000]   #34 [0001f6f000 - 0001fef000]         BOOTMEM
[    0.000000]   #35 [0001fef000 - 000206f000]         BOOTMEM
[    0.000000]   #36 [000206f000 - 00020ef000]         BOOTMEM
[    0.000000]   #37 [00020ef000 - 000216f000]         BOOTMEM
[    0.000000]   #38 [000216f000 - 00021ef000]         BOOTMEM
[    0.000000]   #39 [00021ef000 - 000226f000]         BOOTMEM
[    0.000000]   #40 [000226f000 - 00022ef000]         BOOTMEM
[    0.000000]   #41 [00022ef000 - 000236f000]         BOOTMEM
[    0.000000]   #42 [000236f000 - 00023ef000]         BOOTMEM
[    0.000000]   #43 [00013e6100 - 00013e61c0]         BOOTMEM
[    0.000000]   #44 [00023ef000 - 00023f2000]         BOOTMEM
[    0.000000]   #45 [00023f2000 - 00023f8000]         BOOTMEM
[    0.000000]   #46 [00013e61c0 - 00013e61e5]         BOOTMEM
[    0.000000]   #47 [00013e6300 - 00013e6327]         BOOTMEM
[    0.000000]   #48 [00013e6340 - 00013e64c8]         BOOTMEM
[    0.000000]   #49 [00013e6500 - 00013e6540]         BOOTMEM
[    0.000000]   #50 [00013e6540 - 00013e6580]         BOOTMEM
[    0.000000]   #51 [00013e6580 - 00013e65c0]         BOOTMEM
[    0.000000]   #52 [00013e65c0 - 00013e6600]         BOOTMEM
[    0.000000]   #53 [00013e6600 - 00013e6640]         BOOTMEM
[    0.000000]   #54 [00013e6640 - 00013e6680]         BOOTMEM
[    0.000000]   #55 [00013e6680 - 00013e66c0]         BOOTMEM
[    0.000000]   #56 [00013e66c0 - 00013e6700]         BOOTMEM
[    0.000000]   #57 [00013e6700 - 00013e6740]         BOOTMEM
[    0.000000]   #58 [00013e6740 - 00013e6780]         BOOTMEM
[    0.000000]   #59 [00013e6780 - 00013e67c0]         BOOTMEM
[    0.000000]   #60 [00013e67c0 - 00013e6800]         BOOTMEM
[    0.000000]   #61 [00013e6800 - 00013e6840]         BOOTMEM
[    0.000000]   #62 [00013e6840 - 00013e6850]         BOOTMEM
[    0.000000]   #63 [00013e6880 - 00013e6900]         BOOTMEM
[    0.000000]   #64 [00013e6900 - 00013e6980]         BOOTMEM
[    0.000000]   #65 [0002400000 - 000240d000]         BOOTMEM
[    0.000000]   #66 [0002600000 - 000260d000]         BOOTMEM
[    0.000000]   #67 [00013e6980 - 00013e6984]         BOOTMEM
[    0.000000]   #68 [00013e69c0 - 00013e69c4]         BOOTMEM
[    0.000000]   #69 [00013e6a00 - 00013e6a08]         BOOTMEM
[    0.000000]   #70 [00013e6a40 - 00013e6a48]         BOOTMEM
[    0.000000]   #71 [00013e6a80 - 00013e6b28]         BOOTMEM
[    0.000000]   #72 [00013e6b40 - 00013e6ba8]         BOOTMEM
[    0.000000]   #73 [00023f8000 - 00023fc000]         BOOTMEM
[    0.000000]   #74 [000240d000 - 000248d000]         BOOTMEM
[    0.000000]   #75 [000248d000 - 00024cd000]         BOOTMEM
[    0.000000] Initializing HighMem for node 0 (000377fe:0007ffd0)
[    0.000000] Memory: 2065564k/2096960k available (2205k kernel code, 31004k reserved, 1056k data, 368k init, 1187656k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xffd35000 - 0xfffff000   (2856 kB)
[    0.000000]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    0.000000]     vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
[    0.000000]       .init : 0xc1330000 - 0xc138c000   ( 368 kB)
[    0.000000]       .data : 0xc122741b - 0xc132f598   (1056 kB)
[    0.000000]       .text : 0xc1000000 - 0xc122741b   (2205 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	Verbose stalled-CPUs detection is disabled.
[    0.000000] NR_IRQS:2304 nr_irqs:512
[    0.000000] Extended CMOS year: 2000
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] hpet clockevent registered
[    0.000000] Fast TSC calibration using PIT
[    0.000000] Detected 1995.329 MHz processor.
[    0.001004] Calibrating delay loop (skipped), value calculated using timer frequency.. 3990.65 BogoMIPS (lpj=1995329)
[    0.002004] pid_max: default: 32768 minimum: 301
[    0.002324] Security Framework initialized
[    0.002631] SELinux:  Disabled at boot.
[    0.003009] Mount-cache hash table entries: 512
[    0.003446] Initializing cgroup subsys ns
[    0.003749] Initializing cgroup subsys cpuacct
[    0.004006] Initializing cgroup subsys devices
[    0.004310] Initializing cgroup subsys freezer
[    0.004612] Initializing cgroup subsys net_cls
[    0.005029] CPU: Physical Processor ID: 0
[    0.005331] CPU: Processor Core ID: 0
[    0.005635] mce: CPU supports 6 MCE banks
[    0.006009] CPU0: Thermal monitoring handled by SMI
[    0.006013] using mwait in idle threads.
[    0.006322] Performance Events: PEBS fmt0-, Core2 events, Intel PMU driver.
[    0.007003] PEBS disabled due to CPU errata.
[    0.007309] ... version:                2
[    0.007612] ... bit width:              40
[    0.008003] ... generic registers:      2
[    0.008304] ... value mask:             000000ffffffffff
[    0.008608] ... max period:             000000007fffffff
[    0.008912] ... fixed-purpose events:   3
[    0.009003] ... event mask:             0000000700000003
[    0.010502] ACPI: Core revision 20100428
[    0.028050] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.028733] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.039138] CPU0: Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz stepping 06
[    0.044020] Booting Node   0, Processors  #1 Ok.
[    0.001999] Initializing CPU#1
[    0.001999] CPU1: Thermal monitoring handled by SMI
[    0.116024] Brought up 2 CPUs
[    0.116629] Total of 2 processors activated (7980.48 BogoMIPS).
[    0.118102] HP Compaq Laptop series board detected. Selecting BIOS-method for reboots.
[    0.118554] regulator: core version 0.5
[    0.119053] NET: Registered protocol family 16
[    0.119375] ACPI: bus type pci registered
[    0.120053] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[    0.120560] PCI: not using MMCONFIG
[    0.122485] PCI: PCI BIOS revision 2.10 entry at 0xf0322, last bus=32
[    0.122790] PCI: Using configuration type 1 for base access
[    0.124035] bio: create slab <bio-0> at 0
[    0.127365] ACPI: EC: Look up EC in DSDT
[    0.188922] ACPI: SSDT 7fff63d5 0023D (v01 HP      Cpu0Ist 00003000 INTL 20060317)
[    0.190215] ACPI: Dynamic OEM Table Load:
[    0.190584] ACPI: SSDT (null) 0023D (v01 HP      Cpu0Ist 00003000 INTL 20060317)
[    0.191586] ACPI: SSDT 7fff6697 004CB (v01 HP      Cpu0Cst 00003001 INTL 20060317)
[    0.193086] ACPI: Dynamic OEM Table Load:
[    0.193590] ACPI: SSDT (null) 004CB (v01 HP      Cpu0Cst 00003001 INTL 20060317)
[    0.194421] ACPI: SSDT 7fff630d 000C8 (v01 HP      Cpu1Ist 00003000 INTL 20060317)
[    0.195865] ACPI: Dynamic OEM Table Load:
[    0.196402] ACPI: SSDT (null) 000C8 (v01 HP      Cpu1Ist 00003000 INTL 20060317)
[    0.197139] ACPI: SSDT 7fff6612 00085 (v01 HP      Cpu1Cst 00003000 INTL 20060317)
[    0.198558] ACPI: Dynamic OEM Table Load:
[    0.199001] ACPI: SSDT (null) 00085 (v01 HP      Cpu1Cst 00003000 INTL 20060317)
[    0.214142] ACPI: Interpreter enabled
[    0.214450] ACPI: (supports S0 S3 S4 S5)
[    0.215003] ACPI: Using IOAPIC for interrupt routing
[    0.215362] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[    0.217294] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in ACPI motherboard resources
[    0.217799] PCI: Using MMCONFIG for extended config space
[    0.218150] [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function
[    0.234083] ACPI: EC: GPE = 0x16, I/O: command/status = 0x66, data = 0x62
[    0.235207] ACPI: Power Resource [C1F5] (on)
[    0.235667] ACPI: Power Resource [C1FC] (on)
[    0.236050] ACPI: Power Resource [C219] (on)
[    0.236399] ACPI: Power Resource [C221] (on)
[    0.236799] ACPI: Power Resource [C32A] (off)
[    0.237092] ACPI: Power Resource [C32B] (off)
[    0.237487] ACPI: Power Resource [C32C] (off)
[    0.237882] ACPI: Power Resource [C32D] (off)
[    0.238092] ACPI: Power Resource [C32E] (off)
[    0.238484] ACPI: Power Resource [C32F] (off)
[    0.239115] ACPI: Power Resource [C330] (off)
[    0.239508] ACPI: Power Resource [C331] (off)
[    0.239899] ACPI: Power Resource [C332] (off)
[    0.240091] ACPI: Power Resource [C333] (off)
[    0.240435] ACPI: Power Resource [C334] (off)
[    0.241381] ACPI: No dock devices found.
[    0.241686] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
[    0.246741] ACPI: PCI Root Bridge [C003] (domain 0000 [bus 00-ff])
[    0.256052] pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7] (ignored)
[    0.256056] pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff] (ignored)
[    0.256059] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
[    0.256063] pci_root PNP0A08:00: host bridge window [mem 0x80000000-0xfedfffff] (ignored)
[    0.256066] pci_root PNP0A08:00: host bridge window [mem 0xfee01000-0xffffffff] (ignored)
[    0.256069] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff] (ignored)
[    0.256158] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    0.256161] pci 0000:00:01.0: PME# disabled
[    0.256244] pci 0000:00:1b.0: reg 10: [mem 0xe0700000-0xe0703fff 64bit]
[    0.256307] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.256312] pci 0000:00:1b.0: PME# disabled
[    0.256413] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.256418] pci 0000:00:1c.0: PME# disabled
[    0.256522] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[    0.256527] pci 0000:00:1c.1: PME# disabled
[    0.256632] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[    0.256637] pci 0000:00:1c.3: PME# disabled
[    0.256704] pci 0000:00:1d.0: reg 20: [io  0x5000-0x501f]
[    0.256770] pci 0000:00:1d.1: reg 20: [io  0x5020-0x503f]
[    0.256836] pci 0000:00:1d.2: reg 20: [io  0x5040-0x505f]
[    0.256902] pci 0000:00:1d.3: reg 20: [io  0x5060-0x507f]
[    0.256964] pci 0000:00:1d.7: reg 10: [mem 0xe0704000-0xe07043ff]
[    0.257033] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[    0.257039] pci 0000:00:1d.7: PME# disabled
[    0.257206] pci 0000:00:1f.0: quirk: [io  0x1000-0x107f] claimed by ICH6 ACPI/GPIO/TCO
[    0.257713] pci 0000:00:1f.0: quirk: [io  0x1100-0x113f] claimed by ICH6 GPIO
[    0.258004] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0500 (mask 007f)
[    0.258509] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0100 (mask 000f)
[    0.259005] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 4 PIO at 0238 (mask 0007)
[    0.259558] pci 0000:00:1f.1: reg 10: [io  0x0000-0x0007]
[    0.259566] pci 0000:00:1f.1: reg 14: [io  0x0000-0x0003]
[    0.259574] pci 0000:00:1f.1: reg 18: [io  0x0000-0x0007]
[    0.259583] pci 0000:00:1f.1: reg 1c: [io  0x0000-0x0003]
[    0.259591] pci 0000:00:1f.1: reg 20: [io  0x5080-0x508f]
[    0.259651] pci 0000:00:1f.2: reg 10: [io  0x13f0-0x13f7]
[    0.259660] pci 0000:00:1f.2: reg 14: [io  0x15f4-0x15f7]
[    0.259668] pci 0000:00:1f.2: reg 18: [io  0x1370-0x1377]
[    0.259676] pci 0000:00:1f.2: reg 1c: [io  0x1574-0x1577]
[    0.259684] pci 0000:00:1f.2: reg 20: [io  0x50b0-0x50bf]
[    0.259693] pci 0000:00:1f.2: reg 24: [mem 0xe0705000-0xe07053ff]
[    0.259731] pci 0000:00:1f.2: PME# supported from D3hot
[    0.259736] pci 0000:00:1f.2: PME# disabled
[    0.259825] pci 0000:01:00.0: reg 10: [mem 0xd8000000-0xdbffffff pref]
[    0.259836] pci 0000:01:00.0: reg 14: [io  0x4000-0x40ff]
[    0.259847] pci 0000:01:00.0: reg 18: [mem 0xe0600000-0xe060ffff]
[    0.259878] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
[    0.259920] pci 0000:01:00.0: supports D1 D2
[    0.261022] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    0.261328] pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
[    0.261332] pci 0000:00:01.0:   bridge window [mem 0xe0600000-0xe06fffff]
[    0.261338] pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xdbffffff 64bit pref]
[    0.261593] pci 0000:08:00.0: reg 10: [mem 0xe0100000-0xe010ffff 64bit]
[    0.261883] pci 0000:08:00.0: PME# supported from D3hot D3cold
[    0.261897] pci 0000:08:00.0: PME# disabled
[    0.264077] pci 0000:00:1c.0: PCI bridge to [bus 08-08]
[    0.264386] pci 0000:00:1c.0:   bridge window [io  0xf000-0x0000] (disabled)
[    0.264392] pci 0000:00:1c.0:   bridge window [mem 0xe0100000-0xe01fffff]
[    0.264400] pci 0000:00:1c.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.264600] pci 0000:10:00.0: reg 10: [mem 0xe0000000-0xe0000fff]
[    0.264845] pci 0000:10:00.0: PME# supported from D0 D3hot D3cold
[    0.264858] pci 0000:10:00.0: PME# disabled
[    0.266075] pci 0000:00:1c.1: PCI bridge to [bus 10-10]
[    0.266383] pci 0000:00:1c.1:   bridge window [io  0xf000-0x0000] (disabled)
[    0.266388] pci 0000:00:1c.1:   bridge window [mem 0xe0000000-0xe00fffff]
[    0.266397] pci 0000:00:1c.1:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.266459] pci 0000:00:1c.3: PCI bridge to [bus 20-20]
[    0.266767] pci 0000:00:1c.3:   bridge window [io  0x2000-0x3fff]
[    0.266773] pci 0000:00:1c.3:   bridge window [mem 0xdc000000-0xdfffffff]
[    0.266781] pci 0000:00:1c.3:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.266863] pci 0000:02:06.0: reg 10: [mem 0xe0200000-0xe0200fff]
[    0.266894] pci 0000:02:06.0: supports D1 D2
[    0.266896] pci 0000:02:06.0: PME# supported from D0 D1 D2 D3hot
[    0.266903] pci 0000:02:06.0: PME# disabled
[    0.266950] pci 0000:02:06.2: reg 10: [mem 0xe0208000-0xe0208fff]
[    0.267030] pci 0000:02:06.2: supports D1 D2
[    0.267032] pci 0000:02:06.2: PME# supported from D0 D1 D2 D3hot
[    0.267038] pci 0000:02:06.2: PME# disabled
[    0.267083] pci 0000:02:06.3: reg 10: [mem 0xe0209000-0xe02090ff]
[    0.267160] pci 0000:02:06.3: supports D1 D2
[    0.267162] pci 0000:02:06.3: PME# supported from D0 D1 D2 D3hot
[    0.267168] pci 0000:02:06.3: PME# disabled
[    0.267213] pci 0000:02:06.4: reg 10: [mem 0xe020a000-0xe020afff]
[    0.267223] pci 0000:02:06.4: reg 14: [mem 0xe020b000-0xe020bfff]
[    0.267292] pci 0000:02:06.4: supports D1 D2
[    0.267295] pci 0000:02:06.4: PME# supported from D0 D1 D2 D3hot
[    0.267301] pci 0000:02:06.4: PME# disabled
[    0.267368] pci 0000:00:1e.0: PCI bridge to [bus 02-03] (subtractive decode)
[    0.267678] pci 0000:00:1e.0:   bridge window [io  0xf000-0x0000] (disabled)
[    0.267683] pci 0000:00:1e.0:   bridge window [mem 0xe0200000-0xe05fffff]
[    0.267692] pci 0000:00:1e.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[    0.267695] pci 0000:00:1e.0:   bridge window [io  0x0000-0xffff] (subtractive decode)
[    0.267698] pci 0000:00:1e.0:   bridge window [mem 0x00000000-0xffffffff] (subtractive decode)
[    0.267756] pci_bus 0000:03: [bus 03-06] partially hidden behind transparent bridge 0000:02 [bus 02-03]
[    0.268032] pci_bus 0000:00: on NUMA node 0
[    0.268037] ACPI: PCI Interrupt Routing Table [\_SB_.C003._PRT]
[    0.268252] ACPI: PCI Interrupt Routing Table [\_SB_.C003.C084._PRT]
[    0.268317] ACPI: PCI Interrupt Routing Table [\_SB_.C003.C099._PRT]
[    0.268453] ACPI: PCI Interrupt Routing Table [\_SB_.C003.C102._PRT]
[    0.268547] ACPI: PCI Interrupt Routing Table [\_SB_.C003.C112._PRT]
[    0.268639] ACPI: PCI Interrupt Routing Table [\_SB_.C003.C118._PRT]
[    0.297166] ACPI: PCI Interrupt Link [C10E] (IRQs *10 11)
[    0.298212] ACPI: PCI Interrupt Link [C10F] (IRQs *10 11)
[    0.299201] ACPI: PCI Interrupt Link [C110] (IRQs 10 *11)
[    0.300200] ACPI: PCI Interrupt Link [C111] (IRQs 10 11) *5
[    0.301201] ACPI: PCI Interrupt Link [C124] (IRQs *10 11)
[    0.302231] ACPI: PCI Interrupt Link [C125] (IRQs *10 11)
[    0.303153] ACPI: PCI Interrupt Link [C126] (IRQs 10 *11)
[    0.303953] ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20100428/pci_link-185)
[    0.304704] HEST: Table is not found!
[    0.305038] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[    0.305542] vgaarb: loaded
[    0.306034] PCI: Using ACPI for IRQ routing
[    0.307692] PCI: pci_cache_line_size set to 64 bytes
[    0.307984] reserve RAM buffer: 000000000009fc00 - 000000000009ffff 
[    0.307987] reserve RAM buffer: 000000007ffd0000 - 000000007fffffff 
[    0.308072] NetLabel: Initializing
[    0.308343] NetLabel:  domain hash size = 128
[    0.308647] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.309020] NetLabel:  unlabeled traffic allowed by default
[    0.309329] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[    0.309640] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    0.310401] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[    0.313019] Switching to clocksource tsc
[    0.313326] pnp: PnP ACPI init
[    0.313337] ACPI: bus type pnp registered
[    0.323609]   alloc irq_desc for 23 on node -1
[    0.323612]   alloc kstat_irqs on node -1
[    0.325451] pnp: PnP ACPI: found 16 devices
[    0.325759] ACPI: ACPI bus type pnp unregistered
[    0.326064] PnPBIOS: Disabled by ACPI PNP
[    0.326374] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
[    0.326689] system 00:00: [mem 0x000e0000-0x000fffff] could not be reserved
[    0.326995] system 00:00: [mem 0x00100000-0x7fffffff] could not be reserved
[    0.327308] system 00:0c: [io  0x0500-0x055f] has been reserved
[    0.327614] system 00:0c: [io  0x0800-0x080f] has been reserved
[    0.327923] system 00:0c: [mem 0xffb00000-0xffbfffff] has been reserved
[    0.328227] system 00:0c: [mem 0xfff00000-0xffffffff] has been reserved
[    0.328537] system 00:0e: [io  0x04d0-0x04d1] has been reserved
[    0.328846] system 00:0e: [io  0x1000-0x107f] has been reserved
[    0.329151] system 00:0e: [io  0x1100-0x113f] has been reserved
[    0.329456] system 00:0e: [io  0x1200-0x121f] has been reserved
[    0.329763] system 00:0e: [mem 0xf8000000-0xfbffffff] has been reserved
[    0.330071] system 00:0e: [mem 0xfec00000-0xfec000ff] could not be reserved
[    0.330378] system 00:0e: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.330686] system 00:0e: [mem 0xfed45000-0xfed8ffff] has been reserved
[    0.330992] system 00:0e: [mem 0xfed90000-0xfed9afff] has been reserved
[    0.331302] system 00:0f: [mem 0x000cfc00-0x000cffff] has been reserved
[    0.331607] system 00:0f: [mem 0xfeda0000-0xfedbffff] has been reserved
[    0.331917] system 00:0f: [mem 0xfee00000-0xfee00fff] has been reserved
[    0.367292] pci 0000:00:1e.0: BAR 15: assigned [mem 0x80000000-0x83ffffff pref]
[    0.367802] pci 0000:00:1c.0: BAR 15: assigned [mem 0x84000000-0x841fffff 64bit pref]
[    0.368309] pci 0000:00:1c.1: BAR 15: assigned [mem 0x84200000-0x843fffff 64bit pref]
[    0.368820] pci 0000:00:1c.3: BAR 15: assigned [mem 0x84400000-0x845fffff 64bit pref]
[    0.369329] pci 0000:00:1c.0: BAR 13: assigned [io  0x6000-0x6fff]
[    0.369637] pci 0000:00:1c.1: BAR 13: assigned [io  0x7000-0x7fff]
[    0.369945] pci 0000:00:1e.0: BAR 13: assigned [io  0x8000-0x8fff]
[    0.370252] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0620000-0xe063ffff pref]
[    0.370759] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    0.371063] pci 0000:00:01.0:   bridge window [io  0x4000-0x4fff]
[    0.371370] pci 0000:00:01.0:   bridge window [mem 0xe0600000-0xe06fffff]
[    0.371679] pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xdbffffff 64bit pref]
[    0.372186] pci 0000:00:1c.0: PCI bridge to [bus 08-08]
[    0.372490] pci 0000:00:1c.0:   bridge window [io  0x6000-0x6fff]
[    0.372803] pci 0000:00:1c.0:   bridge window [mem 0xe0100000-0xe01fffff]
[    0.373113] pci 0000:00:1c.0:   bridge window [mem 0x84000000-0x841fffff 64bit pref]
[    0.378184] pci 0000:00:1c.1: PCI bridge to [bus 10-10]
[    0.378490] pci 0000:00:1c.1:   bridge window [io  0x7000-0x7fff]
[    0.378802] pci 0000:00:1c.1:   bridge window [mem 0xe0000000-0xe00fffff]
[    0.379111] pci 0000:00:1c.1:   bridge window [mem 0x84200000-0x843fffff 64bit pref]
[    0.379620] pci 0000:00:1c.3: PCI bridge to [bus 20-20]
[    0.379929] pci 0000:00:1c.3:   bridge window [io  0x2000-0x3fff]
[    0.380239] pci 0000:00:1c.3:   bridge window [mem 0xdc000000-0xdfffffff]
[    0.380548] pci 0000:00:1c.3:   bridge window [mem 0x84400000-0x845fffff 64bit pref]
[    0.381060] pci 0000:02:06.0: BAR 15: assigned [mem 0x80000000-0x83ffffff pref]
[    0.381564] pci 0000:02:06.0: BAR 16: assigned [mem 0x88000000-0x8bffffff]
[    0.381872] pci 0000:02:06.0: BAR 13: assigned [io  0x8000-0x80ff]
[    0.382178] pci 0000:02:06.0: BAR 14: assigned [io  0x8400-0x84ff]
[    0.382483] pci 0000:02:06.0: CardBus bridge to [bus 03-06]
[    0.382790] pci 0000:02:06.0:   bridge window [io  0x8000-0x80ff]
[    0.383098] pci 0000:02:06.0:   bridge window [io  0x8400-0x84ff]
[    0.383408] pci 0000:02:06.0:   bridge window [mem 0x80000000-0x83ffffff pref]
[    0.383916] pci 0000:02:06.0:   bridge window [mem 0x88000000-0x8bffffff]
[    0.384226] pci 0000:00:1e.0: PCI bridge to [bus 02-03]
[    0.384536] pci 0000:00:1e.0:   bridge window [io  0x8000-0x8fff]
[    0.384849] pci 0000:00:1e.0:   bridge window [mem 0xe0200000-0xe05fffff]
[    0.385162] pci 0000:00:1e.0:   bridge window [mem 0x80000000-0x83ffffff pref]
[    0.385681]   alloc irq_desc for 16 on node -1
[    0.385683]   alloc kstat_irqs on node -1
[    0.385688] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.385999] pci 0000:00:01.0: setting latency timer to 64
[    0.386009] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    0.386322] pci 0000:00:1c.0: setting latency timer to 64
[    0.386332]   alloc irq_desc for 17 on node -1
[    0.386334]   alloc kstat_irqs on node -1
[    0.386338] pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[    0.386650] pci 0000:00:1c.1: setting latency timer to 64
[    0.386661]   alloc irq_desc for 19 on node -1
[    0.386663]   alloc kstat_irqs on node -1
[    0.386667] pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[    0.386975] pci 0000:00:1c.3: setting latency timer to 64
[    0.386984] pci 0000:00:1e.0: setting latency timer to 64
[    0.386997]   alloc irq_desc for 18 on node -1
[    0.386999]   alloc kstat_irqs on node -1
[    0.387003] pci 0000:02:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    0.387314] pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
[    0.387316] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
[    0.387319] pci_bus 0000:01: resource 0 [io  0x4000-0x4fff]
[    0.387321] pci_bus 0000:01: resource 1 [mem 0xe0600000-0xe06fffff]
[    0.387324] pci_bus 0000:01: resource 2 [mem 0xd8000000-0xdbffffff 64bit pref]
[    0.387327] pci_bus 0000:08: resource 0 [io  0x6000-0x6fff]
[    0.387329] pci_bus 0000:08: resource 1 [mem 0xe0100000-0xe01fffff]
[    0.387332] pci_bus 0000:08: resource 2 [mem 0x84000000-0x841fffff 64bit pref]
[    0.387335] pci_bus 0000:10: resource 0 [io  0x7000-0x7fff]
[    0.387337] pci_bus 0000:10: resource 1 [mem 0xe0000000-0xe00fffff]
[    0.387340] pci_bus 0000:10: resource 2 [mem 0x84200000-0x843fffff 64bit pref]
[    0.387342] pci_bus 0000:20: resource 0 [io  0x2000-0x3fff]
[    0.387345] pci_bus 0000:20: resource 1 [mem 0xdc000000-0xdfffffff]
[    0.387348] pci_bus 0000:20: resource 2 [mem 0x84400000-0x845fffff 64bit pref]
[    0.387350] pci_bus 0000:02: resource 0 [io  0x8000-0x8fff]
[    0.387353] pci_bus 0000:02: resource 1 [mem 0xe0200000-0xe05fffff]
[    0.387355] pci_bus 0000:02: resource 2 [mem 0x80000000-0x83ffffff pref]
[    0.387358] pci_bus 0000:02: resource 4 [io  0x0000-0xffff]
[    0.387360] pci_bus 0000:02: resource 5 [mem 0x00000000-0xffffffff]
[    0.387363] pci_bus 0000:03: resource 0 [io  0x8000-0x80ff]
[    0.387365] pci_bus 0000:03: resource 1 [io  0x8400-0x84ff]
[    0.387368] pci_bus 0000:03: resource 2 [mem 0x80000000-0x83ffffff pref]
[    0.387370] pci_bus 0000:03: resource 3 [mem 0x88000000-0x8bffffff]
[    0.387399] NET: Registered protocol family 2
[    0.387758] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.388294] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.389183] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.389679] TCP: Hash tables configured (established 131072 bind 65536)
[    0.389984] TCP reno registered
[    0.390286] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.390598] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.390974] NET: Registered protocol family 1
[    0.391412] pci 0000:01:00.0: Boot video device
[    0.391528] PCI: CLS 64 bytes, default 64
[    0.391572] Unpacking initramfs...
[    0.676574] Freeing initrd memory: 9640k freed
[    0.683460] audit: initializing netlink socket (disabled)
[    0.683787] type=2000 audit(1277211503.682:1): initialized
[    0.684282] highmem bounce pool size: 64 pages
[    0.684618] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[    0.687920] VFS: Disk quotas dquot_6.5.2
[    0.688321] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.688821] msgmni has been set to 1733
[    0.689360] alg: No test for stdrng (krng)
[    0.690091] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[    0.690600] io scheduler noop registered
[    0.690903] io scheduler deadline registered
[    0.691215] io scheduler cfq registered (default)
[    0.691645] pcieport 0000:00:01.0: setting latency timer to 64
[    0.691674]   alloc irq_desc for 40 on node -1
[    0.691676]   alloc kstat_irqs on node -1
[    0.691687] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
[    0.691814] pcieport 0000:00:1c.0: setting latency timer to 64
[    0.691861]   alloc irq_desc for 41 on node -1
[    0.691863]   alloc kstat_irqs on node -1
[    0.691872] pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
[    0.692068] pcieport 0000:00:1c.1: setting latency timer to 64
[    0.692115]   alloc irq_desc for 42 on node -1
[    0.692117]   alloc kstat_irqs on node -1
[    0.692126] pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
[    0.692319] pcieport 0000:00:1c.3: setting latency timer to 64
[    0.692366]   alloc irq_desc for 43 on node -1
[    0.692368]   alloc kstat_irqs on node -1
[    0.692377] pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X
[    0.692978] ERST: Table is not found!
[    0.693282] EINJ: Table is not found!
[    0.693620] isapnp: Scanning for PnP cards...
[    1.051508] isapnp: No Plug & Play device found
[    1.055576] Linux agpgart interface v0.103
[    1.055935] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.056569] serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
[    1.057535] Fixed MDIO Bus: probed
[    1.057970] PNP: PS/2 Controller [PNP0303:C216,PNP0f13:C217] at 0x60,0x64 irq 1,12
[    1.060126] i8042.c: Detected active multiplexing controller, rev 1.1.
[    1.061151] serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.061464] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[    1.061772] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[    1.062079] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[    1.062390] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[    1.062841] mice: PS/2 mouse device common for all mice
[    1.063205] cpuidle: using governor ladder
[    1.063544] cpuidle: using governor menu
[    1.064132] TCP cubic registered
[    1.064499] Using IPI No-Shortcut mode
[    1.064953] registered taskstats version 1
[    1.065863] Freeing unused kernel memory: 368k freed
[    1.066379] Write protecting the kernel text: 2208k
[    1.066714] Write protecting the kernel read-only data: 856k
[    1.084749] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[    1.273028] usbcore: registered new interface driver usbfs
[    1.273611] usbcore: registered new interface driver hub
[    1.274951] SCSI subsystem initialized
[    1.276048] tg3.c:v3.110 (April 9, 2010)
[    1.276528] tg3 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.276903] tg3 0000:08:00.0: setting latency timer to 64
[    1.296170] usbcore: registered new device driver usb
[    1.326360] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.326933]   alloc irq_desc for 20 on node -1
[    1.326936]   alloc kstat_irqs on node -1
[    1.326944] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[    1.327538] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[    1.327542] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    1.327867] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[    1.327923] tg3 0000:08:00.0: eth0: Tigon3 [partno(BCM95751M) rev 4201] (PCI Express) MAC address 00:16:d4:be:36:66
[    1.327927] tg3 0000:08:00.0: eth0: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1])
[    1.327930] tg3 0000:08:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[    1.327933] tg3 0000:08:00.0: eth0: dma_rwctrl[76180000] dma_mask[64-bit]
[    1.329382] sdhci: Secure Digital Host Controller Interface driver
[    1.329384] sdhci: Copyright(c) Pierre Ossman
[    1.330675] sdhci-pci 0000:02:06.3: SDHCI controller found [104c:803c] (rev 0)
[    1.330731]   alloc irq_desc for 22 on node -1
[    1.330733]   alloc kstat_irqs on node -1
[    1.330742] sdhci-pci 0000:02:06.3: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[    1.330868] Registered led device: mmc0::
[    1.330948] mmc0: SDHCI controller on PCI [0000:02:06.3] using PIO
[    1.332119] thermal LNXTHERM:01: registered as thermal_zone0
[    1.332129] ACPI: Thermal Zone [TZ0] (80 C)
[    1.332924] ehci_hcd 0000:00:1d.7: using broken periodic workaround
[    1.333258] ehci_hcd 0000:00:1d.7: debug port 1
[    1.337466] ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
[    1.337482] ehci_hcd 0000:00:1d.7: irq 20, io mem 0xe0704000
[    1.344018] libata version 3.00 loaded.
[    1.347010] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[    1.347376] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.347522] thermal LNXTHERM:02: registered as thermal_zone1
[    1.347531] ACPI: Thermal Zone [TZ1] (81 C)
[    1.348343] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.348860] usb usb1: Product: EHCI Host Controller
[    1.349176] usb usb1: Manufacturer: Linux 2.6.35-rc3-iniza-686-kms ehci_hcd
[    1.349494] usb usb1: SerialNumber: 0000:00:1d.7
[    1.349973] hub 1-0:1.0: USB hub found
[    1.350295] hub 1-0:1.0: 8 ports detected
[    1.352503] ata_piix 0000:00:1f.1: version 2.13
[    1.352517] ata_piix 0000:00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.352868] ata_piix 0000:00:1f.1: setting latency timer to 64
[    1.353166] uhci_hcd: USB Universal Host Controller Interface driver
[    1.353531] scsi0 : ata_piix
[    1.353958] scsi1 : ata_piix
[    1.359907] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x5080 irq 14
[    1.360220] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x5088 irq 15
[    1.360562] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[    1.360875] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[    1.360879] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    1.361213] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    1.361766] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00005000
[    1.362116] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    1.362432] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.362959] usb usb2: Product: UHCI Host Controller
[    1.363394] usb usb2: Manufacturer: Linux 2.6.35-rc3-iniza-686-kms uhci_hcd
[    1.363710] usb usb2: SerialNumber: 0000:00:1d.0
[    1.364178] hub 2-0:1.0: USB hub found
[    1.364495] hub 2-0:1.0: 2 ports detected
[    1.364863] thermal LNXTHERM:03: registered as thermal_zone2
[    1.364953] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22
[    1.365084] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[    1.365090] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    1.365103] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[    1.365188] uhci_hcd 0000:00:1d.1: irq 22, io base 0x00005020
[    1.365239] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    1.365242] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.365244] usb usb3: Product: UHCI Host Controller
[    1.365246] usb usb3: Manufacturer: Linux 2.6.35-rc3-iniza-686-kms uhci_hcd
[    1.365247] usb usb3: SerialNumber: 0000:00:1d.1
[    1.365392] hub 3-0:1.0: USB hub found
[    1.365397] hub 3-0:1.0: 2 ports detected
[    1.365537] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    1.365554] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[    1.365560] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    1.365567] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[    1.365647] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00005040
[    1.365706] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    1.365709] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.365711] usb usb4: Product: UHCI Host Controller
[    1.365713] usb usb4: Manufacturer: Linux 2.6.35-rc3-iniza-686-kms uhci_hcd
[    1.365714] usb usb4: SerialNumber: 0000:00:1d.2
[    1.365859] hub 4-0:1.0: USB hub found
[    1.365863] hub 4-0:1.0: 2 ports detected
[    1.366011] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[    1.366033] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[    1.366039] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[    1.366047] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[    1.366169] uhci_hcd 0000:00:1d.3: irq 19, io base 0x00005060
[    1.366225] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[    1.366228] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.366230] usb usb5: Product: UHCI Host Controller
[    1.366232] usb usb5: Manufacturer: Linux 2.6.35-rc3-iniza-686-kms uhci_hcd
[    1.366234] usb usb5: SerialNumber: 0000:00:1d.3
[    1.366380] hub 5-0:1.0: USB hub found
[    1.366384] hub 5-0:1.0: 2 ports detected
[    1.381326] ACPI: Thermal Zone [TZ2] (79 C)
[    1.381808] ata2: port disabled. ignoring.
[    1.396403] thermal LNXTHERM:04: registered as thermal_zone3
[    1.396718] ACPI: Thermal Zone [TZ3] (59 C)
[    1.405736] thermal LNXTHERM:05: registered as thermal_zone4
[    1.406054] ACPI: Thermal Zone [TZ4] (31 C)
[    1.410410] thermal LNXTHERM:06: registered as thermal_zone5
[    1.410726] ACPI: Thermal Zone [TZ5] (64 C)
[    1.535506] ata1.00: ATAPI: MATSHITADVD-RAM UJ-842S, 1.01, max MWDMA2
[    1.541423] ata1.00: configured for MWDMA2
[    1.543968] scsi 0:0:0:0: CD-ROM            MATSHITA DVD-RAM UJ-842S  1.01 PQ: 0 ANSI: 5
[    1.547261] ahci 0000:00:1f.2: version 3.0
[    1.547279]   alloc irq_desc for 21 on node -1
[    1.547281]   alloc kstat_irqs on node -1
[    1.547288] ahci 0000:00:1f.2: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[    1.547635]   alloc irq_desc for 44 on node -1
[    1.547637]   alloc kstat_irqs on node -1
[    1.547647] ahci 0000:00:1f.2: irq 44 for MSI/MSI-X
[    1.547701] ahci: SSS flag set, parallel bus scan disabled
[    1.548032] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x1 impl SATA mode
[    1.548544] ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pmp pio slum part 
[    1.549053] ahci 0000:00:1f.2: setting latency timer to 64
[    1.549789] scsi2 : ahci
[    1.550236] scsi3 : ahci
[    1.550642] scsi4 : ahci
[    1.551165] scsi5 : ahci
[    1.551577] ata3: SATA max UDMA/133 abar m1024@0xe0705000 port 0xe0705100 irq 44
[    1.552086] ata4: DUMMY
[    1.552392] ata5: DUMMY
[    1.552696] ata6: DUMMY
[    1.559984] ACPI: Fan [C335] (off)
[    1.560500] ACPI: Fan [C336] (off)
[    1.561001] ACPI: Fan [C337] (off)
[    1.568527] ACPI: Fan [C338] (off)
[    1.569034] ACPI: Fan [C339] (off)
[    1.569550] ACPI: Fan [C33A] (off)
[    1.570047] ACPI: Fan [C33B] (off)
[    1.570547] ACPI: Fan [C33C] (off)
[    1.571044] ACPI: Fan [C33D] (off)
[    1.571545] ACPI: Fan [C33E] (off)
[    1.571945] ACPI: Fan [C33F] (off)
[    1.908261] usb 1-5: new high speed USB device using ehci_hcd and address 5
[    2.038845] usb 1-5: New USB device found, idVendor=152d, idProduct=2329
[    2.039158] usb 1-5: New USB device strings: Mfr=10, Product=11, SerialNumber=3
[    2.039666] usb 1-5: Product: Storagebird 35EV821
[    2.039973] usb 1-5: Manufacturer: 0123456
[    2.040283] usb 1-5: SerialNumber: 000000000340
[    2.047993] Initializing USB Mass Storage driver...
[    2.048389] scsi6 : usb-storage 1-5:1.0
[    2.048766] usbcore: registered new interface driver usb-storage
[    2.049080] USB Mass Storage support registered.
[    2.247010] usb 2-2: new full speed USB device using uhci_hcd and address 2
[    2.318018] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.320790] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    2.321305] ata3.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[    2.321963] ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[    2.321967] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    2.323194] ata3.00: ATA-7: Hitachi HTS541680J9SA00, SB2OC7BP, max UDMA/100
[    2.323502] ata3.00: 156301488 sectors, multi 16: LBA48 
[    2.326426] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    2.326931] ata3.00: ACPI cmd b1/c1:00:00:00:00:a0 (DEVICE CONFIGURATION OVERLAY) filtered out
[    2.327591] ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[    2.327595] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    2.328840] ata3.00: configured for UDMA/100
[    2.341682] ata3.00: configured for UDMA/100
[    2.341986] ata3: EH complete
[    2.353111] scsi 2:0:0:0: Direct-Access     ATA      Hitachi HTS54168 SB2O PQ: 0 ANSI: 5
[    2.361195] sd 2:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
[    2.361772] sd 2:0:0:0: [sda] Write Protect is off
[    2.362079] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.362105] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.362869]  sda:
[    2.396944] usb 2-2: New USB device found, idVendor=03f0, idProduct=1e1d
[    2.397555] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.397862] usb 2-2: Product: HP hs2300 HSDPA Broadband Wireless Module
[    2.398170] usb 2-2: Manufacturer: HP
[    2.661009] usb 3-1: new full speed USB device using uhci_hcd and address 2
[    2.748602]  sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
[    2.795175] sd 2:0:0:0: [sda] Attached SCSI disk
[    2.803342] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    2.803844] Uniform CD-ROM driver Revision: 3.20
[    2.804243] sr 0:0:0:0: Attached scsi CD-ROM sr0
[    2.808621] sr 0:0:0:0: Attached scsi generic sg0 type 5
[    2.809334] sd 2:0:0:0: Attached scsi generic sg1 type 0
[    2.815001] usb 3-1: New USB device found, idVendor=08ff, idProduct=2580
[    2.815348] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.815678] usb 3-1: Product: Fingerprint Sensor
[    3.025012] usb 3-2: new low speed USB device using uhci_hcd and address 3
[    3.091322] scsi 6:0:0:0: Direct-Access     WDC WD10 EAVS-00D7B0           PQ: 0 ANSI: 2 CCS
[    3.092393] sd 6:0:0:0: Attached scsi generic sg2 type 0
[    3.093062] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.094306] sd 6:0:0:0: [sdb] Write Protect is off
[    3.094613] sd 6:0:0:0: [sdb] Mode Sense: 34 00 00 00
[    3.094616] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[    3.096745] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[    3.097063]  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 >
[    3.188040] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[    3.188359] sd 6:0:0:0: [sdb] Attached SCSI disk
[    3.188937] usb 3-2: New USB device found, idVendor=046d, idProduct=c00e
[    3.189248] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.189559] usb 3-2: Product: USB-PS/2 Optical Mouse
[    3.189865] usb 3-2: Manufacturer: Logitech
[    3.202533] usbcore: registered new interface driver hiddev
[    3.214166] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input1
[    3.214728] generic-usb 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-2/input0
[    3.215267] usbcore: registered new interface driver usbhid
[    3.215577] usbhid: USB HID core driver
[    4.186807] device-mapper: uevent: version 1.0.3
[    4.187464] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com
[    4.193246] PM: Starting manual resume from disk
[    4.274501] EXT3-fs: barriers not enabled
[    4.288789] kjournald starting.  Commit interval 5 seconds
[    4.288810] EXT3-fs (sda2): mounted filesystem with writeback data mode
[    7.009454] udev: starting version 157
[    7.532988] ACPI: acpi_idle registered with cpuidle
[    7.539611] Monitor-Mwait will be used to enter C-1 state
[    7.539641] Monitor-Mwait will be used to enter C-2 state
[    7.539648] Marking TSC unstable due to TSC halts in idle
[    7.540684] Switching to clocksource hpet
[    7.722477] ACPI: Battery Slot [C1BA] (battery present)
[    7.723071] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[    7.723621] ACPI: Sleep Button [C242]
[    7.723979] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
[    7.724598] ACPI: Lid Switch [C23A]
[    7.724967] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[    7.725764] ACPI: AC Adapter [C1B8] (on-line)
[    7.726110] ACPI: Power Button [PWRF]
[    7.726633] ACPI: Battery Slot [C1B9] (battery absent)
[    7.957801] NET: Registered protocol family 23
[    8.207527] ACPI: WMI: Mapper loaded
[    8.401630] tpm_tis 00:04: 1.2 TPM (device-id 0xB, rev-id 16)
[    8.535155] input: PC Speaker as /devices/platform/pcspkr/input/input5
[    8.619343] [Firmware Bug]: ACPI: ACPI brightness control misses _BQC function
[    8.619978] [Firmware Bug]: _BCQ is used instead of _BQC
[    8.621492] acpi device:02: registered as cooling_device13
[    8.622180] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input6
[    8.622696] ACPI: Video Device [C12F] (multi-head: yes  rom: no  post: no)
[    8.764824] found SMC SuperIO Chip (devid=0x7a rev=01 base=0x004e): LPC47N227
[    8.765195] smsc_superio_flat(): fir: 0x100, sir: 0x3e8, dma: 03, irq: 7, mode: 0x0e
[    8.765708] smsc_ircc_present: can't get sir_base of 0x3e8
[    8.863984] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x2580b1, caps: 0xa04793/0x300000/0x0
[    8.864549] serio: Synaptics pass-through port at isa0060/serio4/input0
[    8.868920] input: HP WMI hotkeys as /devices/virtual/input/input7
[    8.907953] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8
[    8.966249] found SMC SuperIO Chip (devid=0x7a rev=01 base=0x004e): LPC47N227
[    8.971555] smsc_superio_flat(): fir: 0x100, sir: 0x3e8, dma: 03, irq: 7, mode: 0x0e
[    8.972213] smsc_ircc_present: can't get sir_base of 0x3e8
[    9.346961] usbcore: registered new interface driver usbserial
[    9.347426] USB Serial support registered for generic
[    9.347783] usbcore: registered new interface driver usbserial_generic
[    9.348129] usbserial: USB Serial Driver core
[    9.446567] rtc_cmos 00:08: RTC can wake from S4
[    9.446929] rtc_cmos 00:08: rtc core: registered rtc_cmos as rtc0
[    9.447300] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[    9.448788] parport_pc 00:03: reported by Plug and Play ACPI
[    9.449186] parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
[    9.455164] cfg80211: Calling CRDA to update world regulatory domain
[    9.594548] iTCO_vendor_support: vendor-support=0
[    9.919108] USB Serial support registered for Sierra USB modem
[    9.919489] sierra 2-2:1.0: Sierra USB modem converter detected
[    9.921245] usb 2-2: Sierra USB modem converter now attached to ttyUSB0
[    9.921622] usb 2-2: Sierra USB modem converter now attached to ttyUSB1
[    9.921970] usb 2-2: Sierra USB modem converter now attached to ttyUSB2
[    9.922315] usbcore: registered new interface driver sierra
[    9.922653] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems
[   10.187671] tifm_7xx1 0000:02:06.2: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   10.241568] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
[   10.241967] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x1060)
[   10.242596] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   10.323781] lis3lv02d: hardware type NC64x0 found.
[   10.328011] lis3lv02d: 12 bits sensor found
[   10.503271] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input9
[   10.504473] Registered led device: hp::hddprotect
[   10.504674] lis3lv02d driver loaded.
[   10.736435] intel_rng: FWH not detected
[   10.767884] yenta_cardbus 0000:02:06.0: CardBus bridge found [103c:30ac]
[   10.768239] yenta_cardbus 0000:02:06.0: Enabling burst memory read transactions
[   10.768756] yenta_cardbus 0000:02:06.0: Using INTVAL to route CSC interrupts to PCI
[   10.769286] yenta_cardbus 0000:02:06.0: Routing CardBus interrupts to PCI
[   10.769619] yenta_cardbus 0000:02:06.0: TI: mfunc 0x01aa1b22, devctl 0x64
[   10.992721] yenta_cardbus 0000:02:06.0: ISA IRQ mask 0x0c78, PCI irq 18
[   10.993042] yenta_cardbus 0000:02:06.0: Socket status: 30000006
[   10.993369] pci_bus 0000:02: Raising subordinate bus# of parent bus (#02) from #03 to #06
[   10.993893] yenta_cardbus 0000:02:06.0: pcmcia: parent PCI bridge window: [io  0x8000-0x8fff]
[   10.994409] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x8000-0x8fff: excluding 0x8000-0x80ff 0x8400-0x84ff
[   11.002976] yenta_cardbus 0000:02:06.0: pcmcia: parent PCI bridge window: [mem 0xe0200000-0xe05fffff]
[   11.003520] pcmcia_socket pcmcia_socket0: cs: memory probe 0xe0200000-0xe05fffff: excluding 0xe0200000-0xe023ffff
[   11.004367] yenta_cardbus 0000:02:06.0: pcmcia: parent PCI bridge window: [mem 0x80000000-0x83ffffff pref]
[   11.004887] pcmcia_socket pcmcia_socket0: cs: memory probe 0x80000000-0x83ffffff: excluding 0x80000000-0x83ffffff
[   11.040706] [drm] Initialized drm 1.1.0 20060810
[   11.451788] psmouse serio5: ID: 10 00 64
[   11.544905] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x100-0x107 0x170-0x177 0x1f0-0x1f7 0x370-0x37f
[   11.548311] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3e8-0x3f7 0x4d0-0x4d7
[   11.550177] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
[   11.551579] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
[   11.553087] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff 0xe0000-0xfffff
[   11.554084] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[   11.554768] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: excluding 0x60000000-0x60ffffff
[   11.555689] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
[   11.641622] [drm] VGACON disable radeon kernel modesetting.
[   11.642567] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   11.642890] pci 0000:01:00.0: setting latency timer to 64
[   11.643134] [drm] Initialized radeon 1.33.0 20080528 for 0000:01:00.0 on minor 0
[   11.901191] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:ds
[   11.901734] iwl3945: Copyright(c) 2003-2010 Intel Corporation
[   11.902154] iwl3945 0000:10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   11.902527] iwl3945 0000:10:00.0: setting latency timer to 64
[   11.957102] iwl3945 0000:10:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
[   11.957609] iwl3945 0000:10:00.0: Detected Intel Wireless WiFi Link 3945ABG
[   11.958052]   alloc irq_desc for 45 on node -1
[   11.958054]   alloc kstat_irqs on node -1
[   11.958088] iwl3945 0000:10:00.0: irq 45 for MSI/MSI-X
[   12.075517] phy0: Selected rate control algorithm 'iwl-3945-rs'
[   12.866876] cfg80211: World regulatory domain updated:
[   12.867196]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   12.867714]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   12.868042]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   12.868350]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   12.868671]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   12.868979]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   13.103663] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
[   13.104025] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
[   13.104347] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   13.104927]   alloc irq_desc for 46 on node -1
[   13.104930]   alloc kstat_irqs on node -1
[   13.104943] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[   13.104981] HDA Intel 0000:00:1b.0: setting latency timer to 64
[   13.104986] hda-intel: chipset global capabilities = 0x4401
[   13.114034] hda-intel: codec_mask = 0x3
[   13.114498] hda-intel: codec #0 probed OK
[   13.114889] hda-intel: codec #1 probed OK
[   13.145611] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
[   13.146175] hda_codec: model 'hp' is selected for config 103c:0 (HP nx)
[   14.150801] input: PS/2 Generic Mouse as /devices/platform/i8042/serio4/serio5/input/input11
[   17.088742] EXT3-fs (sda2): using internal journal
[   20.327044] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   20.437288] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   20.637894] fuse init (API version 7.14)
[   23.379176] iwl3945 0000:10:00.0: loaded firmware version 15.32.2.9
[   23.540589] NET: Registered protocol family 17
[   24.178740] NET: Registered protocol family 10
[   24.179605] lo: Disabled Privacy Extensions
[   24.180686] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   28.032024] lp0: using parport0 (interrupt-driven).
[   28.032586] lp0: console ready
[   28.164594] ppdev: user-space parallel port driver
[   31.828263] wlan0: direct probe to 00:04:0e:e4:00:3d (try 1)
[   31.831083] wlan0: direct probe responded
[   31.835036] wlan0: authenticate with 00:04:0e:e4:00:3d (try 1)
[   31.836746] wlan0: authenticated
[   31.837393] wlan0: associate with 00:04:0e:e4:00:3d (try 1)
[   31.840997] wlan0: RX AssocResp from 00:04:0e:e4:00:3d (capab=0x411 status=0 aid=1)
[   31.841018] wlan0: associated
[   31.844164] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   31.923996] padlock: VIA PadLock not detected.
[   33.229107] Bluetooth: Core ver 2.15
[   33.229482] NET: Registered protocol family 31
[   33.229814] Bluetooth: HCI device and connection manager initialized
[   33.230133] Bluetooth: HCI socket layer initialized
[   33.279299] Bluetooth: L2CAP ver 2.14
[   33.279617] Bluetooth: L2CAP socket layer initialized
[   33.289400] Bluetooth: RFCOMM TTY layer initialized
[   33.289728] Bluetooth: RFCOMM socket layer initialized
[   33.290047] Bluetooth: RFCOMM ver 1.11
[   33.379614] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   33.379940] Bluetooth: BNEP filters: protocol multicast
[   33.503660] Bridge firewalling registered
[   33.602425] Bluetooth: SCO (Voice Link) ver 0.6
[   33.602953] Bluetooth: SCO socket layer initialized
[   36.692556] CPUFREQ: Per core ondemand sysfs interface is deprecated - up_threshold
[   36.694288] CPUFREQ: Per core ondemand sysfs interface is deprecated - ignore_nice_load
[   42.546040] wlan0: no IPv6 routers present
[   48.166198] [drm] Module unloaded
[   51.258984] [drm] Initialized drm 1.1.0 20060810
[   51.302362] [drm] radeon kernel modesetting enabled.
[   51.302758] radeon 0000:01:00.0: setting latency timer to 64
[   51.304327] [drm] initializing kernel modesetting (RV515 0x1002:0x714A).
[   51.306121] [drm] register mmio base: 0xE0600000
[   51.306436] [drm] register mmio size: 65536
[   51.307070] ATOM BIOS: M52T
[   51.307487] [drm] Generation 2 PCI interface, using max accessible memory
[   51.307803] radeon 0000:01:00.0: VRAM: 64M 0x00000000 - 0x03FFFFFF (64M used)
[   51.308126] radeon 0000:01:00.0: GTT: 512M 0x04000000 - 0x23FFFFFF
[   51.308645]   alloc irq_desc for 47 on node -1
[   51.308649]   alloc kstat_irqs on node -1
[   51.308673] radeon 0000:01:00.0: irq 47 for MSI/MSI-X
[   51.308692] [drm] radeon: using MSI.
[   51.309093] [drm] radeon: irq initialized.
[   51.310690] [drm] Detected VRAM RAM=64M, BAR=64M
[   51.311057] [drm] RAM width 64bits DDR
[   51.311472] [TTM] Zone  kernel: Available graphics memory: 443958 kiB.
[   51.311783] [TTM] Zone highmem: Available graphics memory: 1037786 kiB.
[   51.312145] [TTM] Initializing pool allocator.
[   51.312488] [drm] radeon: 64M of VRAM memory ready
[   51.312797] [drm] radeon: 512M of GTT memory ready.
[   51.313191] [drm] GART: num cpu pages 131072, num gpu pages 131072
[   51.315081] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[   51.316900] [drm] PCIE GART of 512M enabled (table at 0x00040000).
[   51.317508] [drm] Loading R500 Microcode
[   51.361451] [drm] radeon: ring at 0x0000000004000000
[   51.361832] [drm] ring test succeeded in 4 usecs
[   51.362428] [drm] radeon: ib pool ready.
[   51.362904] [drm] ib test succeeded in 0 usecs
[   51.363264] [drm] Default TV standard: NTSC
[   51.363608] [drm] Default TV standard: NTSC
[   51.364410] [drm] Default TV standard: NTSC
[   51.364798] [drm] Radeon Display Connectors
[   51.365574] [drm] Connector 0:
[   51.365991] [drm]   VGA
[   51.367817] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[   51.368550] [drm]   Encoders:
[   51.368857] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[   51.369175] [drm] Connector 1:
[   51.369530] [drm]   LVDS
[   51.369832] [drm]   DDC: 0x7e30 0x7e30 0x7e34 0x7e34 0x7e38 0x7e38 0x7e3c 0x7e3c
[   51.370355] [drm]   Encoders:
[   51.370694] [drm]     LCD1: INTERNAL_LVTM1
[   51.370998] [drm] Connector 2:
[   51.371315] [drm]   S-video
[   51.371661] [drm]   Encoders:
[   51.371963] [drm]     TV1: INTERNAL_KLDSCP_DAC2
[   51.372280] [drm] Connector 3:
[   51.372636] [drm]   DVI-I
[   51.372938] [drm]   HPD1
[   51.373252] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[   51.373793] [drm]   Encoders:
[   51.374106] [drm]     DFP1: INTERNAL_KLDSCP_TMDS1
[   51.443368] [drm] radeon: power management initialized
[   51.796427] [drm] fb mappable at 0xD80C0000
[   51.796733] [drm] vram apper at 0xD8000000
[   51.797049] [drm] size 4096000
[   51.797378] [drm] fb depth is 24
[   51.797692] [drm]    pitch is 5120
[   51.798224] fbcon: radeondrmfb (fb0) is primary device
[   51.944520] Console: switching to colour frame buffer device 160x50
[   51.949476] fb0: radeondrmfb frame buffer device
[   51.949520] drm: registered panic notifier
[   51.949562] Slow work thread pool: Starting up
[   51.949703] Slow work thread pool: Ready
[   51.949750] [drm] Initialized radeon 2.6.0 20080528 for 0000:01:00.0 on minor 0
[   67.890005] CE: hpet increased min_delta_ns to 7500 nsec

[-- Attachment #3: iwl3945_ASPM-enabled.txt --]
[-- Type: text/plain, Size: 153 bytes --]

		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <64us
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+

^ permalink raw reply

* ASPM status for iwlwifi and power-management (in general)
From: Sedat Dilek @ 2010-06-22 10:44 UTC (permalink / raw)
  To: wireless; +Cc: Luis R. Rodriguez, Reinette Chatre, Johannes Berg, John Linville

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

Hi,

yesterday, I was playing with PowerTop and my iwl3945 still is in the
TOP 3 of energy user.

Inspired by the recently published ASPM doc from Luis [2] I played a
bit with ASPM.

Currently, I am using a 2.6.35-rc3 Linux-kernel with latest
acpi-2.6/release fixes.

# dmesg | grep -i aspm
[    0.226963] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe
device.  You can enable it with 'pcie_aspm=force'
[    0.227629] pci 0000:08:00.0: disabling ASPM on pre-1.1 PCIe
device.  You can enable it with 'pcie_aspm=force'
[    0.228205] pci 0000:10:00.0: disabling ASPM on pre-1.1 PCIe
device.  You can enable it with 'pcie_aspm=force'

# for i in 01:00.0 08:00.0 10:00.0 ; do lspci -v | grep $i ; done
01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility
Radeon X1300] (prog-if 00 [VGA controller])
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5753M
Gigabit Ethernet PCI Express (rev 21)
10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
[Golan] Network Connection (rev 02)

# lspci -vvvv -s 10:00.0 | grep -i aspm
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0
<128ns, L1 <64us
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+

Before I will try 'pcie_aspm=force' cheat-code I wanted to ask about
the status of iwlwifi and ASPM.
Is there code available. yet? Which kernel has it - linux-next,
wireless-testing GIT, iwlwifi GIT?
Which user-space apps are required?
IIRC iw [3] from GIT has already "iw: add set/get power_save commands" [4].
Anyone tested ASPM with iwlwifi hardware? Experiences?

Beyond ASPM code, what is the actual status on power-mangement for
wifi-hardware in general?
IIRC it was turned off by default (with 2.6.33?)?

Thanks for any help in advance.


Kind Regards,
- Sedat -


[1] http://wireless.kernel.org/en/users/Documentation/ASPM
[2] http://marc.info/?l=linux-wireless&m=127716115227206&w=2
[3] http://git.sipsolutions.net/?p=iw.git
[4] http://git.sipsolutions.net/?p=iw.git;a=commit;h=cf40ef379fd6c74a01092d1dfdd936385ea402b0

[-- Attachment #2: iwl3945_ASPM.txt --]
[-- Type: text/plain, Size: 2189 bytes --]

10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
	Subsystem: Hewlett-Packard Company Compaq 6710b or nx9420 Notebook
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 45
	Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0300c  Data: 41a1
	Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP+ Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [140 v1] Device Serial Number 00-19-d2-ff-ff-62-e4-bb
	Kernel driver in use: iwl3945


^ permalink raw reply

* rt2500usb: WPA2 TKIP+AES does not work with HW encryption
From: Ondrej Zary @ 2010-06-22 10:38 UTC (permalink / raw)
  To: Ivo Van Doorn; +Cc: rt2x00 Users List, linux-wireless

Hello,
I'm (again) trying to solve (debug) a weird problem with Asus WL-167G:
0b05:1706 ASUSTek Computer, Inc. WL-167G v1 802.11g Adapter [Ralink RT2500USB]

The problem only appears when HW encryption is enabled and connecting to an AP
configured as WPA2 TKIP+AES.

HW encryption works when the AP is configured as TKIP-only or AES-only. It
also works when AP is configured as TKIP+AES but wpa_supplicant is forced to
use TKIP as pairwise cipher (pairwise=TKIP)

SW encryption works always.

The problem is that no packets are transmitted. I can't see DHCP broadcasts on
other machine using tcpdump. But when I run tcpdump on the rt2500usb, I see
broadcasts from the other machine, so receive seems to work fine.

Added some printk()s to the driver, 6 packets from unsuccessful DHCP:
[  371.760073] rt2500usb_write_tx_desc: key_idx=0
[  371.852062] rt2500usb_write_tx_desc: key_idx=0
[  371.944054] rt2500usb_write_tx_desc: key_idx=0
[  372.036068] rt2500usb_write_tx_desc: key_idx=0
[  372.128056] rt2500usb_write_tx_desc: key_idx=0
[  372.220053] rt2500usb_write_tx_desc: key_idx=0
[  372.312053] rt2500usb_write_tx_desc: key_idx=0
[  372.404055] rt2500usb_write_tx_desc: key_idx=0
[  372.496101] rt2500usb_write_tx_desc: key_idx=0
[  372.588077] rt2500usb_write_tx_desc: key_idx=0
[  372.688073] rt2500usb_write_tx_desc: key_idx=0
[  373.272513] wlan1: authenticate with 00:13:d4:0f:f3:19 (try 1)
[  373.272552] rt2500usb_write_tx_desc: key_idx=0
[  373.274533] wlan1: authenticated
[  373.274564] wlan1: associate with 00:13:d4:0f:f3:19 (try 1)
[  373.274581] rt2500usb_write_tx_desc: key_idx=0
[  373.277696] wlan1: RX AssocResp from 00:13:d4:0f:f3:19 (capab=0x411 status=0 aid=1)
[  373.277704] wlan1: associated
[  373.308247] rt2500usb_write_tx_desc: key_idx=0
[  373.308392] rt2500usb_write_tx_desc: key_idx=0
[  373.315999] rt2500usb_write_tx_desc: key_idx=0
[  373.340306] rt2x00crypto_key_to_cipher: ALG_CCMP
[  373.340318] rt2500usb_config_key key->hw_key_idx=0 SET_KEY hw_key_idx = 0 OK
[  373.344521] rt2x00crypto_key_to_cipher: ALG_TKIP
[  373.344527] rt2500usb_config_key key->hw_key_idx=0 SET_KEY hw_key_idx = 1 OK
[  373.412083] rt2500usb_write_tx_desc: key_idx=0
[  375.160233] rt2x00crypto_key_to_cipher: ALG_CCMP
[  375.160246] rt2x00crypto_tx_overhead=8
[  375.160254] rt2500usb_write_tx_desc: key_idx=0
[  375.240078] rt2500usb_write_tx_desc: key_idx=0
[  381.163494] rt2x00crypto_key_to_cipher: ALG_CCMP
[  381.163507] rt2x00crypto_tx_overhead=8
[  381.163515] rt2500usb_write_tx_desc: key_idx=0
[  381.244066] rt2500usb_write_tx_desc: key_idx=0
[  388.165180] rt2x00crypto_key_to_cipher: ALG_CCMP
[  388.165194] rt2x00crypto_tx_overhead=8
[  388.165201] rt2500usb_write_tx_desc: key_idx=0
[  388.244069] rt2500usb_write_tx_desc: key_idx=0
[  399.169468] rt2x00crypto_key_to_cipher: ALG_CCMP
[  399.169481] rt2x00crypto_tx_overhead=8
[  399.169489] rt2500usb_write_tx_desc: key_idx=0
[  399.248067] rt2500usb_write_tx_desc: key_idx=0
[  404.080428] rt2500usb_write_tx_desc: key_idx=0
[  404.180066] rt2500usb_write_tx_desc: key_idx=0
[  410.168836] rt2x00crypto_key_to_cipher: ALG_CCMP
[  410.168850] rt2x00crypto_tx_overhead=8
[  410.168858] rt2500usb_write_tx_desc: key_idx=0
[  410.248068] rt2500usb_write_tx_desc: key_idx=0
[  414.374545] rt2500usb_write_tx_desc: key_idx=0
[  414.472061] rt2500usb_write_tx_desc: key_idx=0
[  422.169686] rt2x00crypto_key_to_cipher: ALG_CCMP
[  422.169699] rt2x00crypto_tx_overhead=8
[  422.169706] rt2500usb_write_tx_desc: key_idx=0
[  422.252069] rt2500usb_write_tx_desc: key_idx=0

Seems that it's trying to use CCMP, which is good. I wonder if the keys are 
properly handled in rt2500usb_config_key. They seem to be uploaded to the HW
correctly (one at index 0, one at 1) - but can't tell without any HW docs.

I did some framedumps before but don't know what to do with them (what to
look for):
http://www.rainbow-software.org/linux_files/rt2500usb/dump-wpa2-bad.txt
http://www.rainbow-software.org/linux_files/rt2500usb/dump-wpa2-good.txt

Anything else I can try?

-- 
Ondrej Zary

^ permalink raw reply

* Re: [PATCH] ath9k: Modify LED blinking pattern during wifi activity.
From: Vasanthakumar Thiagarajan @ 2010-06-22  9:30 UTC (permalink / raw)
  To: Johannes Berg
  Cc: Vasanth Thiagarajan, Vivek Natarajan, linville@tuxdriver.com,
	linux-wireless@vger.kernel.org
In-Reply-To: <1277190087.3637.7.camel@jlt3.sipsolutions.net>

On Tue, Jun 22, 2010 at 12:31:27PM +0530, Johannes Berg wrote:
> On Tue, 2010-06-22 at 12:08 +0530, Vasanthakumar Thiagarajan wrote:
> 
> > > http://thread.gmane.org/gmane.linux.kernel.wireless.general/51218/focus=51520
> > 
> > Sorry for a late reply. LED implementation with ath9k is completely
> > manual, fully controlled by driver (We have to set/clear a particular
> > gpio pin to turn on/off the LED every time). on/off period during blink
> > is based on the number of brightness_set() on tx/rx led trigger. Do
> > you think your suggested implementation would help in this case too? 
> 
> I'm not sure. I was mostly describing the use in iwlwifi, and since I
> don't know how ath9k works I can't really comment much.

With ath9k hw itself does not blink LED based on the traffic, it is
the driver which turns on/off LED based on tx/rx.

> It just seemed 
> to me that the driver was also hard-coding the behaviour of the LEDs,
> which the user in that thread didn't like for iwlwifi.

Yeah, before Vivek's patch the driver was hard-coding the LED
behaviour. After this patch, the behaviour would be based on
a modparam.

> so integrating
> with the LED trigger stuff could be worthwhile for ath9k? Or maybe it
> does and I'm reading the patches incorrectly.

The existing LED implementation looks simple. As the blink rate is
determined in driver dynamically, I'm not quite sure integrating LED
trigger, would review this in detail later.

Vasanth

^ permalink raw reply

* Re: wireless-regdb: Add A band in IL - And general point regarding tx power limits in the dbase
From: Holger Schurig @ 2010-06-22  8:52 UTC (permalink / raw)
  To: Emmanuel Grumbach, linux-wireless@vger.kernel.org
In-Reply-To: <AANLkTinGczUb2xTX5RUtnrRnc2BitOjZnpkDeHPV9Hwf@mail.gmail.com>

> Can you please help me translation from mW to db ?

You cannot.

"dB" is without a reference. Is only a relative measurement. You can, however, 
convert "dB" into some factor.

What we were talking about was "dBm". Here we use a reference point of one 
milliwatt. Now you can convert dBm to milliwatt.

Another example of a "made absolute by using a reference" logarithmic scale is 
the gain of antennas. It's usually described in dBi or dBd. The first takes 
the (hypothetical) isotropical antenna, the second an dipol as reference.



For more info, search for "dBm" in http://en.wikipedia.org/wiki/Decibel

-- 
DH3HS, http://www.holgerschurig.de

^ permalink raw reply

* Re: [PATCH] ath9k: Modify LED blinking pattern during wifi activity.
From: Johannes Berg @ 2010-06-22  7:01 UTC (permalink / raw)
  To: Vasanthakumar Thiagarajan
  Cc: Vivek Natarajan, linville@tuxdriver.com,
	linux-wireless@vger.kernel.org
In-Reply-To: <20100622063800.GC9292@vasanth-laptop>

On Tue, 2010-06-22 at 12:08 +0530, Vasanthakumar Thiagarajan wrote:

> > http://thread.gmane.org/gmane.linux.kernel.wireless.general/51218/focus=51520
> 
> Sorry for a late reply. LED implementation with ath9k is completely
> manual, fully controlled by driver (We have to set/clear a particular
> gpio pin to turn on/off the LED every time). on/off period during blink
> is based on the number of brightness_set() on tx/rx led trigger. Do
> you think your suggested implementation would help in this case too? 

I'm not sure. I was mostly describing the use in iwlwifi, and since I
don't know how ath9k works I can't really comment much. It just seemed
to me that the driver was also hard-coding the behaviour of the LEDs,
which the user in that thread didn't like for iwlwifi, so integrating
with the LED trigger stuff could be worthwhile for ath9k? Or maybe it
does and I'm reading the patches incorrectly.

johannes


^ permalink raw reply

* Re: [PATCH] ath9k: Modify LED blinking pattern during wifi activity.
From: Vasanthakumar Thiagarajan @ 2010-06-22  6:38 UTC (permalink / raw)
  To: Johannes Berg
  Cc: Vivek Natarajan, linville@tuxdriver.com,
	linux-wireless@vger.kernel.org
In-Reply-To: <1276587140.3648.6.camel@jlt3.sipsolutions.net>

On Tue, Jun 15, 2010 at 01:02:20PM +0530, Johannes Berg wrote:
> On Tue, 2010-06-15 at 10:50 +0530, Vivek Natarajan wrote:
> 
> >  	case LED_FULL:
> 
> I wonder if you can just use different triggers which may be easier?
> Look at what I suggested earlier for integrating the LEDs with iwlwifi:
> 
> http://thread.gmane.org/gmane.linux.kernel.wireless.general/51218/focus=51520

Sorry for a late reply. LED implementation with ath9k is completely
manual, fully controlled by driver (We have to set/clear a particular
gpio pin to turn on/off the LED every time). on/off period during blink
is based on the number of brightness_set() on tx/rx led trigger. Do
you think your suggested implementation would help in this case too? 

thanks,

Vasanth

^ permalink raw reply

* [PATCH] ath9k: Add a module parameter to disable led blinking.
From: Vivek Natarajan @ 2010-06-22  6:22 UTC (permalink / raw)
  To: linville; +Cc: linux-wireless

Some vendors require the LED to be ON always irrespective of any
radio activity. Introducing a module parameter to disable blinking,
so that one can choose between always on or led blink during
activity.

Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
---
 drivers/net/wireless/ath/ath9k/ath9k.h |    1 +
 drivers/net/wireless/ath/ath9k/gpio.c  |    9 ++++++---
 drivers/net/wireless/ath/ath9k/init.c  |    4 ++++
 drivers/net/wireless/ath/ath9k/main.c  |    4 +++-
 4 files changed, 14 insertions(+), 4 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/ath9k.h b/drivers/net/wireless/ath/ath9k/ath9k.h
index 8d163ae..3a14630 100644
--- a/drivers/net/wireless/ath/ath9k/ath9k.h
+++ b/drivers/net/wireless/ath/ath9k/ath9k.h
@@ -628,6 +628,7 @@ static inline void ath_read_cachesize(struct ath_common *common, int *csz)
 
 extern struct ieee80211_ops ath9k_ops;
 extern int modparam_nohwcrypt;
+extern int led_blink;
 
 irqreturn_t ath_isr(int irq, void *dev);
 int ath9k_init_device(u16 devid, struct ath_softc *sc, u16 subsysid,
diff --git a/drivers/net/wireless/ath/ath9k/gpio.c b/drivers/net/wireless/ath/ath9k/gpio.c
index 0ee75e7..3a8ee99 100644
--- a/drivers/net/wireless/ath/ath9k/gpio.c
+++ b/drivers/net/wireless/ath/ath9k/gpio.c
@@ -76,7 +76,8 @@ static void ath_led_brightness(struct led_classdev *led_cdev,
 	case LED_FULL:
 		if (led->led_type == ATH_LED_ASSOC) {
 			sc->sc_flags |= SC_OP_LED_ASSOCIATED;
-			ieee80211_queue_delayed_work(sc->hw,
+			if (led_blink)
+				ieee80211_queue_delayed_work(sc->hw,
 						     &sc->ath_led_blink_work, 0);
 		} else if (led->led_type == ATH_LED_RADIO) {
 			ath9k_hw_set_gpio(sc->sc_ah, sc->sc_ah->led_pin, 0);
@@ -143,7 +144,8 @@ void ath_init_leds(struct ath_softc *sc)
 	/* LED off, active low */
 	ath9k_hw_set_gpio(sc->sc_ah, sc->sc_ah->led_pin, 1);
 
-	INIT_DELAYED_WORK(&sc->ath_led_blink_work, ath_led_blink_work);
+	if (led_blink)
+		INIT_DELAYED_WORK(&sc->ath_led_blink_work, ath_led_blink_work);
 
 	trigger = ieee80211_get_radio_led_name(sc->hw);
 	snprintf(sc->radio_led.name, sizeof(sc->radio_led.name),
@@ -180,7 +182,8 @@ void ath_init_leds(struct ath_softc *sc)
 	return;
 
 fail:
-	cancel_delayed_work_sync(&sc->ath_led_blink_work);
+	if (led_blink)
+		cancel_delayed_work_sync(&sc->ath_led_blink_work);
 	ath_deinit_leds(sc);
 }
 
diff --git a/drivers/net/wireless/ath/ath9k/init.c b/drivers/net/wireless/ath/ath9k/init.c
index 514a401..8700e3d 100644
--- a/drivers/net/wireless/ath/ath9k/init.c
+++ b/drivers/net/wireless/ath/ath9k/init.c
@@ -33,6 +33,10 @@ int modparam_nohwcrypt;
 module_param_named(nohwcrypt, modparam_nohwcrypt, int, 0444);
 MODULE_PARM_DESC(nohwcrypt, "Disable hardware encryption");
 
+int led_blink = 1;
+module_param_named(blink, led_blink, int, 0444);
+MODULE_PARM_DESC(blink, "Enable LED blink on activity");
+
 /* We use the hw_value as an index into our private channel structure */
 
 #define CHAN2G(_freq, _idx)  { \
diff --git a/drivers/net/wireless/ath/ath9k/main.c b/drivers/net/wireless/ath/ath9k/main.c
index c8de50f..5af2596 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -1241,7 +1241,9 @@ static void ath9k_stop(struct ieee80211_hw *hw)
 
 	aphy->state = ATH_WIPHY_INACTIVE;
 
-	cancel_delayed_work_sync(&sc->ath_led_blink_work);
+	if (led_blink)
+		cancel_delayed_work_sync(&sc->ath_led_blink_work);
+
 	cancel_delayed_work_sync(&sc->tx_complete_work);
 	cancel_work_sync(&sc->paprd_work);
 
-- 
1.7.1


^ permalink raw reply related

* Re: [PATCH] ath9k: Modify LED blinking pattern during wifi activity.
From: Senthil Balasubramanian @ 2010-06-22  5:45 UTC (permalink / raw)
  To: John W. Linville; +Cc: Vivek Natarajan, linux-wireless@vger.kernel.org
In-Reply-To: <20100616133824.GA2404@tuxdriver.com>

On Wed, Jun 16, 2010 at 07:08:24PM +0530, John W. Linville wrote:
> On Wed, Jun 16, 2010 at 11:21:27AM +0530, Vivek Natarajan wrote:
> > On Wed, Jun 16, 2010 at 1:21 AM, John W. Linville
> > <linville@tuxdriver.com> wrote:
> > > On Tue, Jun 15, 2010 at 10:50:17AM +0530, Vivek Natarajan wrote:
> > >> Some vendors require the LED to be ON always irrespective of any
> > >> radio activity. Introducing a module parameter to enable this,
> > >> so that one can choose between always on or led blink during
> > >> activity.
> > >>
> > >> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
> > >
> > > Any particular reason the always-on behaviour is the default?
> > 
> > There is no specific reason for setting it as default. It is only that
> > some customers preferred the led to be always on instead of blinking.
> 
> Well it is just that as I read the patch, you are changing the
> behaviour for everyone rather than simply giving a new option for
> those that don't like it that way it already is.
> 
> Look, I don't particular care about the behaviour.  Blinking w/
> activity makes sense to me.  But I also get to read the seemingly
> endless, whining complaints about how the blinking is distracting for
> laptop users.  I just would rather not add another endless stream of
> complaints that say "my wifi LED used to blink w/ activity, now it
> doesn't -- fix it!"
I agree with John. Let's not change the existing default pattern
(blinking during activity) and use this option to disable blinking
if someone wants it.
> 
> Perhaps we could standardize this somehow?  Anyone care to make
> a proposal?
> 
> John
> -- 
> John W. Linville		Someday the world will need a hero, and you
> linville@tuxdriver.com			might be all we have.  Be ready.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply

* Re: ATH5k - Signal measurement reports wrong values
From: Bruno Randolf @ 2010-06-22  4:01 UTC (permalink / raw)
  To: Jaroslav Fojtik; +Cc: linux-wireless
In-Reply-To: <4C1FBD42.20217.106AB2@jafojtik.seznam.cz>

On Tue June 22 2010 04:28:02 Jaroslav Fojtik wrote:
> root@dvouramenna:~# dmesg |grep "ath5.*chip"
> [    6.632843] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)
> [    7.101528] ath5k phy1: Atheros AR5213A chip found (MAC: 0x59, PHY:
> 0x43)
> 
> Both chipsets suffer with a same problem.

hi jara!

thanks, i was able to reproduce the problem here. can you try this patch, it 
should fix it. it's just one line, so you could also change that 1 to a 4 in 
the code directly. please let me know if it helps...

bruno

commit 36c597b80813988f6a9c47ca4a5cb5306bbc67fa
Author: Bruno Randolf <br1@einfach.org>
Date:   Tue Jun 22 12:37:34 2010 +0900

    ath5k: fix antenna div gc for <= AR5K_SREV_PHY_2413
    
    Commit 39d5b2c83ca8904b6826a0713263a4e5a9c0730a "ath5k: update
    AR5K_PHY_RESTART_DIV_GC values to match masks" introduced a regression on 
PHY
    chips older than AR5K_SREV_PHY_5413, which caused signal values to be 
about
    10dB less that before. This patch reverts the AR5K_PHY_RESTART_DIV_GC 
values to
    the same values which were effectively used before (without the bitmask
    mistake). This brings signal levels back to normal on these PHY chips.
    
    Signed-off-by: Bruno Randolf <br1@einfach.org>

diff --git a/drivers/net/wireless/ath/ath5k/phy.c 
b/drivers/net/wireless/ath/ath5k/phy.c
index 82720fc..2254cd1 100644
--- a/drivers/net/wireless/ath/ath5k/phy.c
+++ b/drivers/net/wireless/ath/ath5k/phy.c
@@ -1768,7 +1768,7 @@ ath5k_hw_set_fast_div(struct ath5k_hw *ah, u8 ee_mode, 
bool enable)
 
 	if (enable) {
 		AR5K_REG_WRITE_BITS(ah, AR5K_PHY_RESTART,
-				AR5K_PHY_RESTART_DIV_GC, 1);
+				AR5K_PHY_RESTART_DIV_GC, 4);
 
 		AR5K_REG_ENABLE_BITS(ah, AR5K_PHY_FAST_ANT_DIV,
 					AR5K_PHY_FAST_ANT_DIV_EN);

^ permalink raw reply related

* Re: 2.6.35-rc3: Reported regressions 2.6.33 -> 2.6.34
From: Luis R. Rodriguez @ 2010-06-22  0:26 UTC (permalink / raw)
  To: tim.gardner; +Cc: Pavel Roskin, linux-wireless, Rafael J. Wysocki, j
In-Reply-To: <4C200059.1090100@canonical.com>

On Mon, Jun 21, 2010 at 5:14 PM, Tim Gardner <tim.gardner@canonical.com> wrote:
> On 06/21/2010 04:18 PM, Luis R. Rodriguez wrote:
>>
>> On Mon, Jun 21, 2010 at 3:01 PM, Pavel Roskin<proski@gnu.org>  wrote:
>>>
>>> On Mon, 2010-06-21 at 11:32 -0700, Luis R. Rodriguez wrote:
>>>
>>>>> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=16111
>>>>> Subject         : hostap_pci: infinite registered netdevice wifi0
>>>>> Submitter       : Petr Pisar<petr.pisar@atlas.cz>
>>>>> Date            : 2010-06-02 20:55 (19 days old)
>>>>
>>>> The last entry on this one says we are not sure how to fix this...
>>>
>>> That was a patch posted for that by Tim Gardner:
>>> https://patchwork.kernel.org/patch/105008/
>>>
>>> The patch is applied to wireless-testing
>>> (d6a574ff6bfb842bdb98065da053881ff527be46)
>>>
>>> $ git describe d6a574ff6bfb842bdb98065da053881ff527be46
>>> v2.6.34-4694-gd6a574f
>>>
>>> I understand it was applied after 2.6.34, so it should be backported to
>>> 2.6.34 and whatever older kernels are affected.
>>
>> Tim can this be sent for stable?
>>
>>   Luis, a stable whore
>>
>
> Luis,
>
> The patch that I sent John is already Cc stable@kernel.org, though it may
> not now apply after 56bf882230d2266a2e07b7f404dc96d157a65daa 'Revert
> "wireless: hostap, fix oops due to early probing interrupt"'. I'll check in
> the morning and craft a backported patch if necessary.

Sweet thanks for the heads up!

  Luis

^ permalink raw reply

* Re: 2.6.35-rc3: Reported regressions 2.6.33 -> 2.6.34
From: Tim Gardner @ 2010-06-22  0:14 UTC (permalink / raw)
  To: Luis R. Rodriguez; +Cc: Pavel Roskin, linux-wireless, Rafael J. Wysocki, j
In-Reply-To: <AANLkTinRqbLH1NOx0o8GNfMaCa1N9NxlsqNzWZWzEyQt@mail.gmail.com>

On 06/21/2010 04:18 PM, Luis R. Rodriguez wrote:
> On Mon, Jun 21, 2010 at 3:01 PM, Pavel Roskin<proski@gnu.org>  wrote:
>> On Mon, 2010-06-21 at 11:32 -0700, Luis R. Rodriguez wrote:
>>
>>>> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=16111
>>>> Subject         : hostap_pci: infinite registered netdevice wifi0
>>>> Submitter       : Petr Pisar<petr.pisar@atlas.cz>
>>>> Date            : 2010-06-02 20:55 (19 days old)
>>>
>>> The last entry on this one says we are not sure how to fix this...
>>
>> That was a patch posted for that by Tim Gardner:
>> https://patchwork.kernel.org/patch/105008/
>>
>> The patch is applied to wireless-testing
>> (d6a574ff6bfb842bdb98065da053881ff527be46)
>>
>> $ git describe d6a574ff6bfb842bdb98065da053881ff527be46
>> v2.6.34-4694-gd6a574f
>>
>> I understand it was applied after 2.6.34, so it should be backported to
>> 2.6.34 and whatever older kernels are affected.
>
> Tim can this be sent for stable?
>
>    Luis, a stable whore
>

Luis,

The patch that I sent John is already Cc stable@kernel.org, though it 
may not now apply after 56bf882230d2266a2e07b7f404dc96d157a65daa 'Revert 
"wireless: hostap, fix oops due to early probing interrupt"'. I'll check 
in the morning and craft a backported patch if necessary.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

^ permalink raw reply

* Re: [ath5k-devel] [PATCH v2] ath5k: disable ASPM
From: Maxim Levitsky @ 2010-06-21 23:55 UTC (permalink / raw)
  To: Luis R. Rodriguez
  Cc: David Quan, Bob Copeland, Luis R. Rodriguez, Jussi Kivilinna,
	ath5k-devel, linux-wireless, linux-kernel, Jonathan May
In-Reply-To: <AANLkTin3fKn0_4mrhmPOlTeN--1EZbKECGF3NVdh9h1t@mail.gmail.com>

On Mon, 2010-06-21 at 13:37 -0700, Luis R. Rodriguez wrote: 
> On Mon, Jun 21, 2010 at 1:16 PM, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> > Luis, let me explain again, exactly the situation:
> >
> > First of all AR5001 and AR5001X devices (former was usualy listed as
> > AR2425, and I have it, later I don't know about much), don't work well
> > with ASPM L0s enabled.
> 
> Thanks for the clarification. David, do you see this as well on your end?
> 
> > I told that many times, but I tell again.
> > As soon as card it put on medium to high transmit load
> > (for example even if transmission consists mostly of TCP ACK packets),
> > it dies.
> >
> > Usualy it will stop transmitting, and then after few seconds it will
> > send RXORN intrrupt to the host, even though the channel was idle.
> > (Tested by sending a stream of UDP packets on channel that is neighbor
> > free).
> >
> > I didn't see it, but some users reported seeing jumbo frames at this
> > time as well.
> > Overall it doesn't matter because card just goes south.
> >
> > A reset sometimes brings card to life, sometimes causes another storm of
> > RXORN and sometimes just results in quiet dead card.
> > A next reset might bring it to life, or not.
> >
> > Card (at least mine) advertises its as a 'pre pci 1.1 device'.
> > Therefore if I enable CONFIG_PCIEASPM, the pci core will automaticly
> > disable ASPM (both L0s and L1) on this card.
> > I won't be surprised that windows does the same.
> 
> I am not sure when L0s was enabled as per the spec as mandatory, I
> thought it was optional. Interesting to hear this behavior on Linux
> with CONFIG_PCIEASPM. That Kconfig description and code really need
> some spit shining.
> 
> > Therefore the patch I sent it useless because it only works when
> > CONFIG_PCIEASPM is enabled.
> 
> How so ? Your patch disables L0s, I can use ASPM with L0s and L1 with
> or without CONFIG_PCIEASPM. If I added your calls to ath9k I would
> disable L0s.
Because due to card advertisement, CONFIG_PCIEASPM already disables L0s
and L1 on the card, therefore my patch does nothing.



Best regards,
Maxim Levitsky


^ permalink raw reply

* Re: Linux script to enable ASPM / Documentation for ASPM
From: Luis R. Rodriguez @ 2010-06-21 23:02 UTC (permalink / raw)
  To: linux-kernel; +Cc: linux-wireless, Martin Mares
In-Reply-To: <AANLkTikmFJAHEBwAZ_lPosAZH3JO2zA5KetXuHvfe4WT@mail.gmail.com>

On Mon, Jun 21, 2010 at 3:58 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> ASPM was a dark magic when I first started looking at it. Some of it
> is still dark but what I was able to understand with the help of
> colleagues at work I've managed to stash here for now:
>
> http://wireless.kernel.org/en/users/Documentation/ASPM
>
> Then enabling ASPM was also quite a challenge and I always had to go
> back and revisit the procedures, so to help with that instead I wrote
> a script to do this for you correctly:
>
> http://kernel.org/pub/linux/kernel/people/mcgrof/aspm/enable-aspm
>
> Its sha1sum is: f5804fdab512065f219e55addf78c6654f1fc045
>
> If any of that looks confusing refer to the documentation above.
>
> There's a TODO there, so I'll get to the different items when I can
> but if you like feel free to send me patches as well:
>
>  TODO: patches are welcomed to me until we submit to to
>       PCI Utilities upstream.
>
>  This can be improved by in this order:
>
>        * Accept arguments for endpoint and root complex address, and
>          desired ASPM settings
>        * Look for your ASPM capabilities by quering your
>          LnkCap register first. Use these values to let you
>          select whether you want to enable only L1 or L1 & L0s
>        * Searching for your root complex for you
>        * Search for your PCI device by using the driver
>        * Disable your driver and ask to reboot ?
>        * Rewrite in C
>        * Write ncurses interface [ wishlist ]
>        * Write GTK/QT interface [ wishlist ]
>        * Submit upstream as aspm.c to the PCI Utilities, which are
>          maintained by Martin Mares <mj@ucw.cz>

Come to think of it, would this be welcomed upstream in the PCI utils
as is for now?

  Luis

^ permalink raw reply


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox