* Compat-wireless release for 2010-07-09 is baked
From: Compat-wireless cronjob account @ 2010-07-09 19:02 UTC (permalink / raw)
To: linux-wireless
fatal: Unable to look up git.kernel.org (port 9418) (Name or service not known)
compat-wireless code metrics
494875 - Total upstream lines of code being pulled
1419 - backport code changes
1186 - backport code additions
233 - backport code deletions
5766 - backport from compat module
7185 - total backport code
1.4519 - % of code consists of backport work
1218 - Crap changes not yet posted
1179 - Crap additions not yet posted
39 - Crap deletions not yet posted
0.2461 - % of crap code
Base tree: linux-next.git
Base tree version: next-20100708
compat-wireless release: compat-wireless-2010-07-08-1-g469f74f
ssh: Could not resolve hostname wireless.kernel.org: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
^ permalink raw reply
* [PATCH 0/4] iwlwifi update for 2.6.36
From: Wey-Yi Guy @ 2010-07-09 19:24 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, ipw3945-devel, Wey-Yi Guy
We add support for 6050 series Gen2 devices
We also fix the bit mask of a FH register which will
cause timeout by polling unused bits
Newer version of uCode has advance error codes; we adding
support for these.
Emmanuel Grumbach (1):
iwlagn: fix the bit mask of a FH register in stop Tx DMA flow
Jay Sternberg (1):
iwlwifi: correct descriptions of advanced ucode errors
Shanyu Zhao (1):
iwlwifi: enable 6050 series Gen2 devices
Wey-Yi Guy (1):
iwlagn: more generic description for iwlagn devices
these patches are also available from wireless-next-2.6 branch on
git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-2.6.git
drivers/net/wireless/iwlwifi/Kconfig | 9 ++++-
drivers/net/wireless/iwlwifi/iwl-6000.c | 38 +++++++++++++++++++++++++
drivers/net/wireless/iwlwifi/iwl-agn-tx.c | 7 +++-
drivers/net/wireless/iwlwifi/iwl-agn.c | 44 +++++++++++++++++++++++++----
drivers/net/wireless/iwlwifi/iwl-agn.h | 1 +
drivers/net/wireless/iwlwifi/iwl-csr.h | 1 +
drivers/net/wireless/iwlwifi/iwl-eeprom.h | 4 ++
drivers/net/wireless/iwlwifi/iwl-fh.h | 7 +----
8 files changed, 95 insertions(+), 16 deletions(-)
^ permalink raw reply
* [PATCH 3/4] iwlagn: more generic description for iwlagn devices
From: Wey-Yi Guy @ 2010-07-09 19:24 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, ipw3945-devel, Wey-Yi Guy
In-Reply-To: <1278703480-13363-1-git-send-email-wey-yi.w.guy@intel.com>
Intel Wireless WiFi Next Gen AGN support two major categories:
1. Intel Wireless WiFi 4965 AGN device
2. Intel Wireless-N/Advanced-N/Ultimate-N family
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
---
drivers/net/wireless/iwlwifi/Kconfig | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/Kconfig b/drivers/net/wireless/iwlwifi/Kconfig
index 6491e27..a51e4da 100644
--- a/drivers/net/wireless/iwlwifi/Kconfig
+++ b/drivers/net/wireless/iwlwifi/Kconfig
@@ -87,10 +87,15 @@ config IWL4965
This option enables support for Intel Wireless WiFi Link 4965AGN
config IWL5000
- bool "Intel Wireless WiFi 5000AGN; Intel WiFi Link 1000, 6000, and 6050 Series"
+ bool "Intel Wireless-N/Advanced-N/Ultimate-N WiFi Link"
depends on IWLAGN
---help---
- This option enables support for Intel Wireless WiFi Link 5000AGN Family
+ This option enables support for use with the following hardware:
+ Intel Wireless WiFi Link 6250AGN Adapter
+ Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
+ Intel WiFi Link 1000BGN
+ Intel Wireless WiFi 5150AGN
+ Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
config IWL3945
tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
--
1.7.0.4
^ permalink raw reply related
* [PATCH 4/4] iwlagn: fix the bit mask of a FH register in stop Tx DMA flow
From: Wey-Yi Guy @ 2010-07-09 19:24 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, ipw3945-devel, Emmanuel Grumbach, Wey-Yi Guy
In-Reply-To: <1278703480-13363-1-git-send-email-wey-yi.w.guy@intel.com>
From: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
When we stop the Tx DMA channels, we poll bits 16:31 in
FH_TSSR_RX_STATUS_REG. From 4965 and up, only the bits 16:26 are legal.
Bits 27:31 are not used and are always unset.
Polling them will lead to fail on timeout but since the timeout is quite
small, the stall was not felt.
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
---
drivers/net/wireless/iwlwifi/iwl-agn-tx.c | 7 +++++--
drivers/net/wireless/iwlwifi/iwl-fh.h | 7 +------
2 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-agn-tx.c b/drivers/net/wireless/iwlwifi/iwl-agn-tx.c
index 2573234..55a1b31 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn-tx.c
+++ b/drivers/net/wireless/iwlwifi/iwl-agn-tx.c
@@ -950,9 +950,12 @@ void iwlagn_txq_ctx_stop(struct iwl_priv *priv)
/* Stop each Tx DMA channel, and wait for it to be idle */
for (ch = 0; ch < priv->hw_params.dma_chnl_num; ch++) {
iwl_write_direct32(priv, FH_TCSR_CHNL_TX_CONFIG_REG(ch), 0x0);
- iwl_poll_direct_bit(priv, FH_TSSR_TX_STATUS_REG,
+ if (iwl_poll_direct_bit(priv, FH_TSSR_TX_STATUS_REG,
FH_TSSR_TX_STATUS_REG_MSK_CHNL_IDLE(ch),
- 1000);
+ 1000))
+ IWL_ERR(priv, "Failing on timeout while stopping"
+ " DMA channel %d [0x%08x]", ch,
+ iwl_read_direct32(priv, FH_TSSR_TX_STATUS_REG));
}
spin_unlock_irqrestore(&priv->lock, flags);
}
diff --git a/drivers/net/wireless/iwlwifi/iwl-fh.h b/drivers/net/wireless/iwlwifi/iwl-fh.h
index 113c366..dd896f2 100644
--- a/drivers/net/wireless/iwlwifi/iwl-fh.h
+++ b/drivers/net/wireless/iwlwifi/iwl-fh.h
@@ -398,12 +398,7 @@
*/
#define FH_TSSR_TX_ERROR_REG (FH_TSSR_LOWER_BOUND + 0x018)
-#define FH_TSSR_TX_STATUS_REG_BIT_BUFS_EMPTY(_chnl) ((1 << (_chnl)) << 24)
-#define FH_TSSR_TX_STATUS_REG_BIT_NO_PEND_REQ(_chnl) ((1 << (_chnl)) << 16)
-
-#define FH_TSSR_TX_STATUS_REG_MSK_CHNL_IDLE(_chnl) \
- (FH_TSSR_TX_STATUS_REG_BIT_BUFS_EMPTY(_chnl) | \
- FH_TSSR_TX_STATUS_REG_BIT_NO_PEND_REQ(_chnl))
+#define FH_TSSR_TX_STATUS_REG_MSK_CHNL_IDLE(_chnl) ((1 << (_chnl)) << 16)
/* Tx service channels */
#define FH_SRVC_CHNL (9)
--
1.7.0.4
^ permalink raw reply related
* [PATCH 1/4] iwlwifi: enable 6050 series Gen2 devices
From: Wey-Yi Guy @ 2010-07-09 19:24 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, ipw3945-devel, Shanyu Zhao, Wey-Yi Guy
In-Reply-To: <1278703480-13363-1-git-send-email-wey-yi.w.guy@intel.com>
From: Shanyu Zhao <shanyu.zhao@intel.com>
To enable 6050 series Gen 2 devices:
1) new PCI_IDs are added;
2) new EEPROM version and calibration version numbers defined;
3) new hardware REV number defined;
Signed-off-by: Shanyu Zhao <shanyu.zhao@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
---
drivers/net/wireless/iwlwifi/iwl-6000.c | 38 +++++++++++++++++++++++++++++
drivers/net/wireless/iwlwifi/iwl-agn.c | 8 ++++++
drivers/net/wireless/iwlwifi/iwl-agn.h | 1 +
drivers/net/wireless/iwlwifi/iwl-csr.h | 1 +
drivers/net/wireless/iwlwifi/iwl-eeprom.h | 4 +++
5 files changed, 52 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-6000.c b/drivers/net/wireless/iwlwifi/iwl-6000.c
index 59681c5..0955219 100644
--- a/drivers/net/wireless/iwlwifi/iwl-6000.c
+++ b/drivers/net/wireless/iwlwifi/iwl-6000.c
@@ -829,6 +829,44 @@ struct iwl_cfg iwl6050_2agn_cfg = {
.need_dc_calib = true,
};
+struct iwl_cfg iwl6050g2_bgn_cfg = {
+ .name = "6050 Series 1x2 BGN Gen2",
+ .fw_name_pre = IWL6050_FW_PRE,
+ .ucode_api_max = IWL6050_UCODE_API_MAX,
+ .ucode_api_min = IWL6050_UCODE_API_MIN,
+ .sku = IWL_SKU_G|IWL_SKU_N,
+ .ops = &iwl6000_ops,
+ .eeprom_size = OTP_LOW_IMAGE_SIZE,
+ .eeprom_ver = EEPROM_6050G2_EEPROM_VERSION,
+ .eeprom_calib_ver = EEPROM_6050G2_TX_POWER_VERSION,
+ .num_of_queues = IWLAGN_NUM_QUEUES,
+ .num_of_ampdu_queues = IWLAGN_NUM_AMPDU_QUEUES,
+ .mod_params = &iwlagn_mod_params,
+ .valid_tx_ant = ANT_A,
+ .valid_rx_ant = ANT_AB,
+ .pll_cfg_val = 0,
+ .set_l0s = true,
+ .use_bsm = false,
+ .pa_type = IWL_PA_SYSTEM,
+ .max_ll_items = OTP_MAX_LL_ITEMS_6x50,
+ .shadow_ram_support = true,
+ .ht_greenfield_support = true,
+ .led_compensation = 51,
+ .use_rts_for_ht = true, /* use rts/cts protection */
+ .chain_noise_num_beacons = IWL_CAL_NUM_BEACONS,
+ .supports_idle = true,
+ .adv_thermal_throttle = true,
+ .support_ct_kill_exit = true,
+ .plcp_delta_threshold = IWL_MAX_PLCP_ERR_THRESHOLD_DEF,
+ .chain_noise_scale = 1500,
+ .monitor_recover_period = IWL_MONITORING_PERIOD,
+ .max_event_log_size = 1024,
+ .ucode_tracing = true,
+ .sensitivity_calib_by_driver = true,
+ .chain_noise_calib_by_driver = true,
+ .need_dc_calib = true,
+};
+
struct iwl_cfg iwl6050_2abg_cfg = {
.name = "Intel(R) Centrino(R) Advanced-N + WiMAX 6250 ABG",
.fw_name_pre = IWL6050_FW_PRE,
diff --git a/drivers/net/wireless/iwlwifi/iwl-agn.c b/drivers/net/wireless/iwlwifi/iwl-agn.c
index 66c83b2..b5d1939 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn.c
+++ b/drivers/net/wireless/iwlwifi/iwl-agn.c
@@ -4323,6 +4323,14 @@ static DEFINE_PCI_DEVICE_TABLE(iwl_hw_card_ids) = {
{IWL_PCI_DEVICE(0x0089, 0x1311, iwl6050_2agn_cfg)},
{IWL_PCI_DEVICE(0x0089, 0x1316, iwl6050_2abg_cfg)},
+/* 6x50 WiFi/WiMax Series Gen2 */
+ {IWL_PCI_DEVICE(0x0885, 0x1305, iwl6050g2_bgn_cfg)},
+ {IWL_PCI_DEVICE(0x0885, 0x1306, iwl6050g2_bgn_cfg)},
+ {IWL_PCI_DEVICE(0x0885, 0x1325, iwl6050g2_bgn_cfg)},
+ {IWL_PCI_DEVICE(0x0885, 0x1326, iwl6050g2_bgn_cfg)},
+ {IWL_PCI_DEVICE(0x0886, 0x1315, iwl6050g2_bgn_cfg)},
+ {IWL_PCI_DEVICE(0x0886, 0x1316, iwl6050g2_bgn_cfg)},
+
/* 1000 Series WiFi */
{IWL_PCI_DEVICE(0x0083, 0x1205, iwl1000_bgn_cfg)},
{IWL_PCI_DEVICE(0x0083, 0x1305, iwl1000_bgn_cfg)},
diff --git a/drivers/net/wireless/iwlwifi/iwl-agn.h b/drivers/net/wireless/iwlwifi/iwl-agn.h
index 5c46b2c..cc6464d 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn.h
+++ b/drivers/net/wireless/iwlwifi/iwl-agn.h
@@ -89,6 +89,7 @@ extern struct iwl_cfg iwl6000i_2bg_cfg;
extern struct iwl_cfg iwl6000_3agn_cfg;
extern struct iwl_cfg iwl6050_2agn_cfg;
extern struct iwl_cfg iwl6050_2abg_cfg;
+extern struct iwl_cfg iwl6050g2_bgn_cfg;
extern struct iwl_cfg iwl1000_bgn_cfg;
extern struct iwl_cfg iwl1000_bg_cfg;
diff --git a/drivers/net/wireless/iwlwifi/iwl-csr.h b/drivers/net/wireless/iwlwifi/iwl-csr.h
index 254c35a..ecf98e7 100644
--- a/drivers/net/wireless/iwlwifi/iwl-csr.h
+++ b/drivers/net/wireless/iwlwifi/iwl-csr.h
@@ -298,6 +298,7 @@
#define CSR_HW_REV_TYPE_1000 (0x0000060)
#define CSR_HW_REV_TYPE_6x00 (0x0000070)
#define CSR_HW_REV_TYPE_6x50 (0x0000080)
+#define CSR_HW_REV_TYPE_6x50g2 (0x0000084)
#define CSR_HW_REV_TYPE_6x00g2 (0x00000B0)
#define CSR_HW_REV_TYPE_NONE (0x00000F0)
diff --git a/drivers/net/wireless/iwlwifi/iwl-eeprom.h b/drivers/net/wireless/iwlwifi/iwl-eeprom.h
index 95aa202..f8b707d 100644
--- a/drivers/net/wireless/iwlwifi/iwl-eeprom.h
+++ b/drivers/net/wireless/iwlwifi/iwl-eeprom.h
@@ -276,6 +276,10 @@ struct iwl_eeprom_enhanced_txpwr {
#define EEPROM_6050_TX_POWER_VERSION (4)
#define EEPROM_6050_EEPROM_VERSION (0x532)
+/* 6x50g2 Specific */
+#define EEPROM_6050G2_TX_POWER_VERSION (6)
+#define EEPROM_6050G2_EEPROM_VERSION (0x553)
+
/* 6x00g2 Specific */
#define EEPROM_6000G2_TX_POWER_VERSION (6)
#define EEPROM_6000G2_EEPROM_VERSION (0x709)
--
1.7.0.4
^ permalink raw reply related
* [PATCH 2/4] iwlwifi: correct descriptions of advanced ucode errors
From: Wey-Yi Guy @ 2010-07-09 19:24 UTC (permalink / raw)
To: linville; +Cc: linux-wireless, ipw3945-devel, Jay Sternberg, Wey-Yi Guy
In-Reply-To: <1278703480-13363-1-git-send-email-wey-yi.w.guy@intel.com>
From: Jay Sternberg <jay.e.sternberg@intel.com>
ucode errors were redefined in new ucode images and all new errors
were showing as advanced sysasserts which was misleading. new errors
are not sequential so additional lookup table added. errors do not
overlap so both are used to support older and newer ucode images.
Signed-off-by: Jay Sternberg <jay.e.sternberg@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
---
drivers/net/wireless/iwlwifi/iwl-agn.c | 36 ++++++++++++++++++++++++++-----
1 files changed, 30 insertions(+), 6 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-agn.c b/drivers/net/wireless/iwlwifi/iwl-agn.c
index b5d1939..7391c63 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn.c
+++ b/drivers/net/wireless/iwlwifi/iwl-agn.c
@@ -2296,17 +2296,41 @@ static const char *desc_lookup_text[] = {
"DEBUG_1",
"DEBUG_2",
"DEBUG_3",
- "ADVANCED SYSASSERT"
};
-static const char *desc_lookup(int i)
+static struct { char *name; u8 num; } advanced_lookup[] = {
+ { "NMI_INTERRUPT_WDG", 0x34 },
+ { "SYSASSERT", 0x35 },
+ { "UCODE_VERSION_MISMATCH", 0x37 },
+ { "BAD_COMMAND", 0x38 },
+ { "NMI_INTERRUPT_DATA_ACTION_PT", 0x3C },
+ { "FATAL_ERROR", 0x3D },
+ { "NMI_TRM_HW_ERR", 0x46 },
+ { "NMI_INTERRUPT_TRM", 0x4C },
+ { "NMI_INTERRUPT_BREAK_POINT", 0x54 },
+ { "NMI_INTERRUPT_WDG_RXF_FULL", 0x5C },
+ { "NMI_INTERRUPT_WDG_NO_RBD_RXF_FULL", 0x64 },
+ { "NMI_INTERRUPT_HOST", 0x66 },
+ { "NMI_INTERRUPT_ACTION_PT", 0x7C },
+ { "NMI_INTERRUPT_UNKNOWN", 0x84 },
+ { "NMI_INTERRUPT_INST_ACTION_PT", 0x86 },
+ { "ADVANCED_SYSASSERT", 0 },
+};
+
+static const char *desc_lookup(u32 num)
{
- int max = ARRAY_SIZE(desc_lookup_text) - 1;
+ int i;
+ int max = ARRAY_SIZE(desc_lookup_text);
- if (i < 0 || i > max)
- i = max;
+ if (num < max)
+ return desc_lookup_text[num];
- return desc_lookup_text[i];
+ max = ARRAY_SIZE(advanced_lookup) - 1;
+ for (i = 0; i < max; i++) {
+ if (advanced_lookup[i].num == num)
+ break;;
+ }
+ return advanced_lookup[i].name;
}
#define ERROR_START_OFFSET (1 * sizeof(u32))
--
1.7.0.4
^ permalink raw reply related
* Re: 2.6.35-rc4-git3: Reported regressions from 2.6.34
From: Rafael J. Wysocki @ 2010-07-09 21:33 UTC (permalink / raw)
To: Linus Torvalds
Cc: Linux Kernel Mailing List, Maciej Rutecki, Andrew Morton,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI,
Frederic Weisbecker, Al Viro, Shawn Starr, Jesse Barnes,
Dave Airlie, David S. Miller, Patrick McHardy, Jens Axboe
In-Reply-To: <AANLkTiknnzWyVpqnPCpyiEVHLgkewd0zaGzLInABRe2G@mail.gmail.com>
On Friday, July 09, 2010, Linus Torvalds wrote:
> On Thu, Jul 8, 2010 at 4:33 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >
> > Unresolved regressions
> > ----------------------
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16353
> > Subject : 2.6.35 regression
> > Submitter : Zeev Tarantov <zeev.tarantov@gmail.com>
> > Date : 2010-07-05 13:04 (4 days old)
> > Message-ID : <loom.20100705T144459-919@post.gmane.org>
> > References : http://marc.info/?l=linux-kernel&m=127836002702522&w=2
>
> This is a gcc-4.5 issue. Whether it's also something that we should
> change in the kernel is unclear, but at least as of now, the rule is
> that you cannot compile the kernel with gcc-4.5. No idea whether the
> compiler is just entirely broken, or whether it's just that it
> triggers something iffy by being overly clever.
This claims to fix it, though: https://patchwork.kernel.org/patch/110988/
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16346
> > Subject : 2.6.35-rc3-git8 - include/linux/fdtable.h:88 invoked rcu_dereference_check() without protection!
> > Submitter : Miles Lane <miles.lane@gmail.com>
> > Date : 2010-07-04 22:04 (5 days old)
> > Message-ID : <AANLkTinof0k28rk4rMr66aubxcRL2rFa5ZEArj1lqD3o@mail.gmail.com>
> > References : http://marc.info/?l=linux-kernel&m=127828107815930&w=2
>
> I'm not entirely sure if these RCU proving things should count as regressions.
>
> Sure, the option to enable RCU proving is new, but the things it
> reports about generally are not new - and they are usually not even
> bugs in the sense that they necessarily cause any real problems.
>
> That particular one is in the single-thread optimizated case for fget_light, ie
>
> if (likely((atomic_read(&files->count) == 1))) {
> file = fcheck_files(files, fd);
>
> where I think it should be entirely safe in all ways without any
> locking. So I think it's a false positive too.
OK, so I'm going to close these bugs.
...
>
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16333
> > Subject : iwl3945: HARDWARE GONE??
> > Submitter : Priit Laes <plaes@plaes.org>
> > Date : 2010-07-02 16:02 (7 days old)
> > Message-ID : <1278086575.2889.8.camel@chi>
> > References : http://marc.info/?l=linux-kernel&m=127808659705983&w=2
>
> This either got fixed, or will be practically impossible to debug. The
> reporter ends up being unable to reproduce the issue.
Closed as unreproducible.
...
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16330
> > Subject : Dynamic Debug broken on 2.6.35-rc3?
> > Submitter : Thomas Renninger <trenn@suse.de>
> > Date : 2010-07-01 15:44 (8 days old)
> > Message-ID : <201007011744.19564.trenn@suse.de>
> > References : http://marc.info/?l=linux-kernel&m=127799907218877&w=2
>
> There's a suggested patch in
>
> http://marc.info/?l=linux-kernel&m=127862524404291&w=2
>
> but no reply to it yet.
Patch information added to the bug entry (it's been confirmed to work).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16329
> > Subject : 2.6.35-rc3: Load average climbing to 3+ with no apparent reason: CPU 98% idle, with hardly no I/O
> > Submitter : Török Edwin <edwintorok@gmail.com>
> > Date : 2010-07-01 7:40 (8 days old)
> > Message-ID : <20100701104022.404410d6@debian>
> > References : http://marc.info/?l=linux-kernel&m=127797005030536&w=2
>
> This seems to be partly a confusion about what "load average" is. It's
> not a CPU load, it's a system load average, and disk-wait processes
> count towards it. He has some problem with his CD-ROM, and it sounds
> like it might be hardware on the verge of going bad.
Closed.
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16324
> > Subject : Oops while running fs_racer test on a POWER6 box against latest git
> > Submitter : divya <dipraksh@linux.vnet.ibm.com>
> > Date : 2010-06-30 11:34 (9 days old)
> > Message-ID : <4C2B28F3.7000006@linux.vnet.ibm.com>
> > References : http://marc.info/?l=linux-kernel&m=127789697303061&w=2
>
> I wonder if this is the writeback problem. That POWER crash dump is
> unreadable, so it's hard to tell, but the load in question makes that
> at least likely.
>
> If so, it should hopefully be fixed in today's git (commit
> 83ba7b071f30f7c01f72518ad72d5cd203c27502 and friends).
OK, closed.
> > Bug-entry : http://bugzilla.kernel.org/show_bug.cgi?id=16323
> > Subject : 2.6.35-rc3-git4 - kernel/sched.c:616 invoked rcu_dereference_check() without protection!
> > Submitter : Miles Lane <miles.lane@gmail.com>
> > Date : 2010-07-01 12:21 (8 days old)
> > Message-ID : <AANLkTini6hz2LFeZi8CMUmY3xw1MU7NxmyesuxZ4oCdo@mail.gmail.com>
> > References : http://marc.info/?l=linux-kernel&m=127798693125541&w=2
>
> See earlier about these being marked as regressions, but it should be
> fixed by commit dc61b1d6 ("sched: Fix PROVE_RCU vs cpu_cgroup").
Closed.
...
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16309
> > Subject : 2.6.35-rc3 oops trying to suspend.
> > Submitter : Andrew Hendry <andrew.hendry@gmail.com>
> > Date : 2010-06-27 12:40 (12 days old)
> > Message-ID : <AANLkTinUH2p33-AWxOVDrLsNkn9rgEVrlwn5mfK7P8NH@mail.gmail.com>
> > References : http://marc.info/?l=linux-kernel&m=127764249926781&w=2
>
> I'm pretty sure this was fixed by Nick in commit 57439f878afa ("fs:
> fix superblock iteration race").
Closed.
...
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16304
> > Subject : i915 - high number of wakeups
> > Submitter : Enrico Bandiello <enban@postal.uv.es>
> > Date : 2010-06-27 09:52 (12 days old)
>
> Duplicate of that 16307 one.
Closed.
...
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16230
> > Subject : inconsistent IN-HARDIRQ-W -> HARDIRQ-ON-W usage: fasync, 2.6.35-rc3
> > Submitter : Dominik Brodowski <linux@dominikbrodowski.net>
> > Date : 2010-06-13 9:53 (26 days old)
> > Message-ID : <20100613095305.GA13231@comet.dominikbrodowski.net>
> > References : http://marc.info/?l=linux-kernel&m=127642282208277&w=2
>
> Fixed by commit f4985dc714d7.
Closed.
...
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16205
> > Subject : acpi: freeing invalid memtype bf799000-bf79a000
> > Submitter : Marcin Slusarz <marcin.slusarz@gmail.com>
> > Date : 2010-06-09 20:09 (30 days old)
> > Message-ID : <20100609200910.GA2876@joi.lan>
> > References : http://marc.info/?l=linux-kernel&m=127611427029914&w=2
> > http://marc.info/?l=linux-kernel&m=127688398513862&w=2
>
> This should be fixed by commit b945d6b2554d ("rbtree: Undo augmented
> trees performance damage and regression").
Yup, closed.
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16199
> > Subject : 2.6.35-rc2-git1 - include/linux/cgroup.h:534 invoked rcu_dereference_check() without protection!
> > Submitter : Miles Lane <miles.lane@gmail.com>
> > Date : 2010-06-07 18:14 (32 days old)
> > Message-ID : <AANLkTin2pPqOUx--9fIX3BH3e-cU6oCRufijcx_4ozx5@mail.gmail.com>
> > References : http://marc.info/?l=linux-kernel&m=127593447812015&w=2
>
> Another RCU proving thing. And this one looks the same as the 16323
> one above, and fixed by the same commit as that one.
Closed.
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16197
> > Subject : [BUG on 2.6.35-rc2] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/slot'
> > Submitter : Ryan Wang <openspace.wang@gmail.com>
> > Date : 2010-06-07 0:23 (32 days old)
> > Message-ID : <AANLkTincwMZPnYW3S4uz4k2GOn52RpgBIBRfzyD010Yo@mail.gmail.com>
> > References : http://marc.info/?l=linux-kernel&m=127587022219378&w=2
>
> These should all be gone. See commit 3be434f0244ee by Jesse ('Revert
> "PCI: create function symlinks in /sys/bus/pci/slots/N/"').
Yes, I've already closed it.
...
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16175
> > Subject : 2.6.35-rc1 system oom, many processes killed but memory not free
> > Submitter : andrew hendry <andrew.hendry@gmail.com>
> > Date : 2010-06-05 0:46 (34 days old)
> > Message-ID : <AANLkTim7CiW-yfugZUAHZCqLvXKgt9CwolCvbLGdCLAk@mail.gmail.com>
> > References : http://marc.info/?l=linux-kernel&m=127569877714937&w=2
>
> Not a regression or a kernel bug at all. See the thread. Big ramdisk
> filled up all of memory when it was filled by the builds.
Closed.
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16145
> > Subject : Unable to boot unless "notsc" or "clocksource=hpet", or acpi_pad disabling the TSC
> > Submitter : Tom Gundersen <teg@jklm.no>
> > Date : 2010-06-07 13:11 (32 days old)
> > Handled-By : Venkatesh Pallipadi <venki@google.com>
> > Len Brown <lenb@kernel.org>
>
> This is not a regression. See the full bugzilla details. The same
> problem persists at least back to 2.6.30 with his config. So it's
> somehow specific to his particular config use that requires "notsc" to
> boot.
Dropped from the list.
Thanks,
Rafael
^ permalink raw reply
* Re: 2.6.35-rc4-git3: Reported regressions from 2.6.34
From: Rafael J. Wysocki @ 2010-07-09 21:35 UTC (permalink / raw)
To: Frederic Weisbecker
Cc: Linus Torvalds, Linux Kernel Mailing List, Maciej Rutecki,
Andrew Morton, Kernel Testers List, Network Development,
Linux ACPI, Linux PM List, Linux SCSI List, Linux Wireless List,
DRI, Al Viro, Shawn Starr, Jesse Barnes, Dave Airlie,
David S. Miller, Patrick McHardy, Jens Axboe
In-Reply-To: <20100709020440.GJ6405@nowhere>
On Friday, July 09, 2010, Frederic Weisbecker wrote:
> On Thu, Jul 08, 2010 at 06:34:25PM -0700, Linus Torvalds wrote:
> > On Thu, Jul 8, 2010 at 4:33 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16284
> > > Subject : Hitting WARN_ON in hw_breakpoint code
> > > Submitter : Paul Mackerras <paulus@samba.org>
> > > Date : 2010-06-23 12:57 (16 days old)
> > > Message-ID : <20100623125740.GA3368@brick.ozlabs.ibm.com>
> > > References : http://marc.info/?l=linux-kernel&m=127729789113432&w=2
> >
> > This has "I have a fix, will post it very soon." in the thread from
> > Frederic, but I'm not seeing anything else. Frederic?
>
>
>
> Right. In fact it wasn't a regression. The per task breakpoint reservation
> design was broken from the beginning and this warning has revealed the
> problem. This only touched perf, and it did since perf support breakpoints.
> Fortunately ptrace wasn't concerned by this problem, even not by side effects
> of this.
>
> The fix is invasive as it's a rewrite of a (little) part of the breakpoint
> reservation. And since the symptom is only a warning and also breakpoints
> never released from the constraint table (just a counter, no memory leak),
> the fix is headed for 2.6.36.
>
> It is ready in tip:/perf/core:
>
> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commitdiff;h=45a73372efe4a63f44aa2e1125d4a777c2fdc8d8
>
> I think this ticket can be safely closed.
OK, closing.
Rafael
^ permalink raw reply
* Re: Compat-wireless release for 2010-07-09 is baked
From: Pavel Roskin @ 2010-07-09 21:56 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless
In-Reply-To: <20100709190222.115F242E2D@repository3.orbit-lab.org>
On Fri, 2010-07-09 at 15:02 -0400, Compat-wireless cronjob account
wrote:
> Base tree: linux-next.git
> Base tree version: next-20100708
> compat-wireless release: compat-wireless-2010-07-08-1-g469f74f
> ssh: Could not resolve hostname wireless.kernel.org: Name or service not known
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
Still not good. The 2010-07-09 release is not on the download site. I
assume the upload failed.
Perhaps only successful reports should go to the list, and unsuccessful
reports should go to those who can fix the problem?
--
Regards,
Pavel Roskin
^ permalink raw reply
* Re: Compat-wireless release for 2010-07-09 is baked
From: Luis R. Rodriguez @ 2010-07-09 22:29 UTC (permalink / raw)
To: Pavel Roskin; +Cc: linux-wireless
In-Reply-To: <1278712573.9411.4.camel@mj>
On Fri, Jul 9, 2010 at 2:56 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Fri, 2010-07-09 at 15:02 -0400, Compat-wireless cronjob account
> wrote:
>> Base tree: linux-next.git
>> Base tree version: next-20100708
>> compat-wireless release: compat-wireless-2010-07-08-1-g469f74f
>> ssh: Could not resolve hostname wireless.kernel.org: Name or service not known
>> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>> rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]
>
> Still not good. The 2010-07-09 release is not on the download site. I
> assume the upload failed.
I'll take a look.
> Perhaps only successful reports should go to the list, and unsuccessful
> reports should go to those who can fix the problem?
Sure, I'll try to address this, but also feel free to send patches against:
http://git.kernel.org/?p=linux/kernel/git/mcgrof/compat-user.git;a=summary
Luis
^ permalink raw reply
* [PATCH] mac80211: update mesh information element values
From: Steve deRosier @ 2010-07-09 23:48 UTC (permalink / raw)
To: linux-wireless; +Cc: javier, Steve deRosier
The old values conflicted with ANA approved values. The new values
were chosen to be consistent with those for the ANA request plan
for 802.11s.
The Peer Link IE no longer exists in draft standards, replaced by
the Peer Management IE. Leaving the old definition in was prudent
until mesh code can be changed to match.
Signed-off-by: Steve deRosier <steve@cozybit.com>
---
include/linux/ieee80211.h | 23 +++++++++++++----------
1 files changed, 13 insertions(+), 10 deletions(-)
diff --git a/include/linux/ieee80211.h b/include/linux/ieee80211.h
index 97b2eae..1ed60b5 100644
--- a/include/linux/ieee80211.h
+++ b/include/linux/ieee80211.h
@@ -1142,17 +1142,20 @@ enum ieee80211_eid {
/* 802.11s
*
* All mesh EID numbers are pending IEEE 802.11 ANA approval.
- * The numbers have been incremented from those suggested in
- * 802.11s/D2.0 so that MESH_CONFIG does not conflict with
- * EXT_SUPP_RATES.
+ * The numbers have been taken from ANA request plan for 802.11s
+ *
+ * Note that the Peer Link IE has been replaced with the similar
+ * Peer Management IE. We will keep the former definition until mesh
+ * code is changed to comply with latest 802.11s drafts.
*/
- WLAN_EID_MESH_CONFIG = 51,
- WLAN_EID_MESH_ID = 52,
- WLAN_EID_PEER_LINK = 55,
- WLAN_EID_PREQ = 68,
- WLAN_EID_PREP = 69,
- WLAN_EID_PERR = 70,
- WLAN_EID_RANN = 49, /* compatible with FreeBSD */
+ WLAN_EID_MESH_CONFIG = 113,
+ WLAN_EID_MESH_ID = 114,
+ WLAN_EID_PEER_MGMT = 115,
+ WLAN_EID_PEER_LINK = 55, /* no longer in 802.11s drafts */
+ WLAN_EID_PREQ = 130,
+ WLAN_EID_PREP = 131,
+ WLAN_EID_PERR = 132,
+ WLAN_EID_RANN = 126,
WLAN_EID_PWR_CONSTRAINT = 32,
WLAN_EID_PWR_CAPABILITY = 33,
--
1.7.0
^ permalink raw reply related
* RE: wl1271 firmware
From: Logan Gunthorpe @ 2010-07-10 0:19 UTC (permalink / raw)
To: Luciano Coelho; +Cc: linux-wireless
Hi Everyone,
Luciano Coelho Wrote:
> You need to get the firmware (wl1271-fw.bin) directly from TI or from
> your device manufacturer. I don't have the permission to redistribute
> it. The latest version that we are using is Rev. 6.1.0.0.310 (you can
> check this by running strings on and grepping the binary file).
>
> The NVS file is another story. It contains device-specific calibration
> values and you should probably get those from the device manufacturer.
> There is a common part (which is the INI file in tiwlan's terms), which
> you need to use to create the binary (check wl1271_ini.h for the binary
> file structure). The more problematic part is the device-specific self
> generated calibration. You need to run a specific sequence of commands
> in order to get these values and then apply these values to the correct
> place in the binary file.
>
> Shahar, maybe you could contribute a tool to generate the NVS file in
> the correct format for wl1271? That would be very cool and would help
> lots of people. Please let me know if you have interest and we can
> discuss this in more details.
I too am working with a WL1271 module and have just today got it
connected to an Atmel ARM9 development kit (AT91SAM9G45-EKES). So far it
appears to work but I have been gated by the firmware and NVS file issues.
I have a firmware binary, but it seems to be a newer version
(6.1.3.01.5) than what you are using. Does anyone have any idea if this
version will work? It seems to be the only one available on TI's
website. Additionally, our device manufacturer has been hesitant to
provide any support because we are on an unsupported platform and opted
to use the open source driver. Are there any other ways to obtain an
older version of the firmware?
The NVS file is another problem. TI's website has instructions to use a
cryptic tool that appears to come with their driver package. There is no
source for this tool and for obvious reasons would not work for us.
Anyway, I'd like to help in anyway I can. I've taken a look at the
twilan.ini file and I see the commonality with wl1271_ini.h. It would be
relatively easy to write a tool that parses the INI file and generates
the common part of the NVS file. However, I'd have no idea how to
generate the device specific calibration or the few fields missing from
the INI file.
Thanks,
Logan
P.S. I was not subscribed to this list when the message I'm replying to
was sent. I apologize if I broke the thread. I am subscribed now.
^ permalink raw reply
* 2.6.35-rc4-git4: Reported regressions 2.6.33 -> 2.6.34
From: Rafael J. Wysocki @ 2010-07-10 0:24 UTC (permalink / raw)
To: Linux Kernel Mailing List
Cc: Maciej Rutecki, Andrew Morton, Linus Torvalds,
Kernel Testers List, Network Development, Linux ACPI,
Linux PM List, Linux SCSI List, Linux Wireless List, DRI
[NOTES:
* This list seems to be shrinking at last.
* The bug entries with the NEEDINFO status will be closed next round if the
reporters don't follow up.]
This message contains a list of some post-2.6.33 regressions introduced before
2.6.34, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unresolved post-2.6.33 regressions, please let us know
either and we'll add them to the list. Also, please let us know if any
of the entries below are invalid.
Each entry from the list will be sent additionally in an automatic reply to
this message with CCs to the people involved in reporting and handling the
issue.
Listed regressions statistics:
Date Total Pending Unresolved
----------------------------------------
2010-07-10 122 25 24
2010-06-21 114 36 28
2010-06-13 111 40 34
2010-05-09 80 27 24
2010-05-04 76 26 22
2010-04-20 64 35 34
2010-04-07 48 35 33
2010-03-21 15 13 10
Unresolved regressions
----------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16357
Subject : acpi-cpufreq fails to load (No such device)
Submitter : Ambroz Bizjak <ambrop7@gmail.com>
Date : 2010-07-09 09:40 (1 days old)
Handled-By : Thomas Renninger <trenn@suse.de>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16348
Subject : kswapd continuously active when doing IO
Submitter : Marius Tolzmann <tolzmann@molgen.mpg.de>
Date : 2010-07-07 10:58 (3 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16320
Subject : iwl3945 crashes, seems to be disconnecting from the PCI bus
Submitter : Satish <eerpini@gmail.com>
Date : 2010-07-01 08:24 (9 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16318
Subject : macbook pro 5,1 does not boot with acpi
Submitter : <syamajala@gmail.com>
Date : 2010-06-30 13:38 (10 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16300
Subject : [2.6.34 regression] mplayer gets out of sync due to problems with ALSA
Submitter : Artem S. Tashkinov <t.artem@mailcity.com>
Date : 2010-06-26 20:39 (14 days old)
Handled-By : Takashi Iwai <tiwai@suse.de>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16270
Subject : Image is a hit-or-a-miss. Often displayed green+purple
Submitter : Vish <drkvi-a@yahoo.com>
Date : 2010-06-22 10:47 (18 days old)
First-Bad-Commit: http://git.kernel.org/linus/acef4a407ed6e0a9ed87a2747be592fe49e64bdd
Handled-By : Jean-Francois Moine <moinejf@free.fr>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16233
Subject : Fwd: [2.6.34] INFO: task rsync:20019 blocked for more than 120 seconds.
Submitter : Jan De Luyck <mailinglists+linuxkernel_20080830@kcore.org>
Date : 2010-06-14 19:49 (26 days old)
Message-ID : <AANLkTimutyh3WIALv3NIxA8Xt5JtU6tp4EWOnuSqhdyD@mail.gmail.com>
References : http://marc.info/?l=linux-kernel&m=127654498016377&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16207
Subject : Suspend and VT switch hangs since 2.6.34
Submitter : Tino Keitel <tino.keitel+xorg@tikei.de>
Date : 2010-06-09 17:53 (31 days old)
Message-ID : <20100609175356.GA17332@x61.home>
References : http://marc.info/?l=linux-kernel&m=127610606214060&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16206
Subject : PROBLEM: PPP and other serial port related application hangs in kernel space
Submitter : Ales Teska <ales.teska@gmail.com>
Date : 2010-06-09 20:46 (31 days old)
Message-ID : <900E3B14-5B92-4A37-9581-049DB40F4D1C@gmail.com>
References : http://marc.info/?l=linux-kernel&m=127611640301071&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16170
Subject : Leadtek Winfast DTV Dongle (STK7700P based) is not working in 2.6.34
Submitter : <macjariel@gmail.com>
Date : 2010-06-09 11:11 (31 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16158
Subject : winxp guest hangs after idle for ~30 minutes
Submitter : <brimhall@pobox.com>
Date : 2010-06-08 17:52 (32 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16139
Subject : wait_even_interruptible_timeout(), signal, spin_lock() = system hang
Submitter : Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Date : 2010-05-28 16:44 (43 days old)
Message-ID : <AANLkTiliRFydAhxH2-Dp1RKuz6sq7vgWIcMvLMi68ftg@mail.gmail.com>
References : http://marc.info/?l=linux-kernel&m=127506510328758&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16137
Subject : Ooops in BTRFS in 2.6.34 / x86_64 when mounting subvolume by name
Submitter : armin walland <a.walland@focusmr.com>
Date : 2010-05-27 12:27 (44 days old)
Message-ID : <201005271428.01239.a.walland@focusmr.com>
References : http://marc.info/?l=linux-kernel&m=127496434110736&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16097
Subject : 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated"
Submitter : Harald Dunkel <harald.dunkel@aixigo.de>
Date : 2010-05-25 9:12 (46 days old)
Message-ID : <4BFB947E.9080509@aixigo.de>
References : http://marc.info/?l=linux-kernel&m=127477877432254&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16082
Subject : host panic on kernel 2.6.34
Submitter : Hao, Xudong <xudong.hao@intel.com>
Date : 2010-05-24 8:23 (47 days old)
Message-ID : <BC00F5384FCFC9499AF06F92E8B78A9E04DCCCE242@shsmsx502.ccr.corp.intel.com>
References : http://marc.info/?l=linux-kernel&m=127468951208864&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16050
Subject : The ibmcam driver is not working
Submitter : Bill Davidsen <davidsen@tmr.com>
Date : 2010-05-25 23:02 (46 days old)
Handled-By : Hans de Goede <hdegoede@redhat.com>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16035
Subject : Incorrect initial resolution of (external) vga monitor with KMS
Submitter : <andreas.eckstein@gmx.net>
Date : 2010-05-23 12:28 (48 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15977
Subject : WARNING: at lib/dma-debug.c:866 check_for_stack
Submitter : Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date : 2010-05-14 8:56 (57 days old)
Message-ID : <AANLkTikyx2eaxaiUCFDSfpmn1UG0t2GOxArz6F4wp1LJ@mail.gmail.com>
References : http://marc.info/?l=linux-kernel&m=127382742729825&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15912
Subject : Audio/video sync and crackling issues with snd-hda-intel (AD1981 codec)
Submitter : Øyvind Stegard <oyvinst@ifi.uio.no>
Date : 2010-05-05 16:20 (66 days old)
Handled-By : Jaroslav Kysela <perex@perex.cz>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15862
Subject : 2.6.34-rc4/5: iwlagn unusable until reload
Submitter : Nico Schottelius <nico-linux-20100427@schottelius.org>
Date : 2010-04-27 7:49 (74 days old)
Message-ID : <20100427074934.GB3261@ikn.schottelius.org>
References : http://marc.info/?l=linux-kernel&m=127235784004839&w=2
Handled-By : Johannes Berg <johannes@sipsolutions.net>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15805
Subject : reiserfs locking
Submitter : Alexander Beregalov <a.beregalov@gmail.com>
Date : 2010-04-15 21:02 (86 days old)
Message-ID : <t2ka4423d671004151402n7b2dc425mdc9c6bb9640d63fb@mail.gmail.com>
References : http://marc.info/?l=linux-kernel&m=127136535323933&w=2
Handled-By : Frederic Weisbecker <fweisbec@gmail.com>
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15704
Subject : [r8169] WARNING: at net/sched/sch_generic.c
Submitter : Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Date : 2010-03-31 10:21 (101 days old)
Message-ID : <20100331102142.GA3294@swordfish.minsk.epam.com>
References : http://marc.info/?l=linux-kernel&m=127003090406108&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15673
Subject : 2.6.34-rc2: "ima_dec_counts: open/free imbalance"?
Submitter : Thomas Meyer <thomas@m3y3r.de>
Date : 2010-03-28 11:31 (104 days old)
Message-ID : <1269775909.5301.4.camel@localhost.localdomain>
References : http://marc.info/?l=linux-kernel&m=126977593326800&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15664
Subject : Graphics hang and kernel backtrace when starting Azureus with Compiz enabled
Submitter : Alex Villacis Lasso <avillaci@ceibo.fiec.espol.edu.ec>
Date : 2010-04-01 01:09 (100 days old)
Regressions with patches
------------------------
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16007
Subject : x86/pci Oops with CONFIG_SND_HDA_INTEL
Submitter : Graham Ramsey <ramsey.graham@ntlworld.com>
Date : 2010-05-19 17:09 (52 days old)
Handled-By : Yinghai Lu <yinghai@kernel.org>
Bjorn Helgaas <bjorn.helgaas@hp.com>
Patch : https://patchwork.kernel.org/patch/105662/
For details, please visit the bug entries and follow the links given in
references.
As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions introduced
between 2.6.33 and 2.6.34, unresolved as well as resolved, at:
http://bugzilla.kernel.org/show_bug.cgi?id=15310
Please let the tracking teak know if there are any Bugzilla entries that
should be added to the list in there.
Thanks!
^ permalink raw reply
* Re: Compat-wireless release for 2010-07-09 is baked
From: Pavel Roskin @ 2010-07-10 0:52 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless
In-Reply-To: <AANLkTingMmay_a0ZpwxRi2AQ6tVMJLiBSz_bm9HZVFUn@mail.gmail.com>
On Fri, 2010-07-09 at 15:29 -0700, Luis R. Rodriguez wrote:
> >> ssh: Could not resolve hostname wireless.kernel.org: Name or service not known
...
> > Perhaps only successful reports should go to the list, and unsuccessful
> > reports should go to those who can fix the problem?
>
> Sure, I'll try to address this, but also feel free to send patches against:
>
> http://git.kernel.org/?p=linux/kernel/git/mcgrof/compat-user.git;a=summary
Thanks for the tip!
I don't think I can fix DNS resolution of wireless.kernel.org from the
scripts.
cron-compat could be rewritten to call "mail" explicitly, so that
different addresses are used for different outcomes. crontab will need
to be changed accordingly.
--
Regards,
Pavel Roskin
^ permalink raw reply
* Re: 2.6.35-rc4-git4: Reported regressions 2.6.33 -> 2.6.34
From: Luis R. Rodriguez @ 2010-07-10 3:06 UTC (permalink / raw)
To: linux-wireless; +Cc: Rafael J. Wysocki, reinette chatre, Johannes Berg
In-Reply-To: <xkNyyYrLiTN.A.s_G.7p7NMB@chimera>
Below are the 802.11 ones only. One for iwl3945, the other for iwlagn:
On Fri, Jul 9, 2010 at 5:24 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> Unresolved regressions
> ----------------------
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16320
> Subject : iwl3945 crashes, seems to be disconnecting from the PCI bus
> Submitter : Satish <eerpini@gmail.com>
> Date : 2010-07-01 08:24 (9 days old)
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15862
> Subject : 2.6.34-rc4/5: iwlagn unusable until reload
> Submitter : Nico Schottelius <nico-linux-20100427@schottelius.org>
> Date : 2010-04-27 7:49 (74 days old)
> Message-ID : <20100427074934.GB3261@ikn.schottelius.org>
> References : http://marc.info/?l=linux-kernel&m=127235784004839&w=2
> Handled-By : Johannes Berg <johannes@sipsolutions.net>
Luis
^ permalink raw reply
* Re: [PATCH] mac80211: update mesh information element values
From: Steve deRosier @ 2010-07-10 5:05 UTC (permalink / raw)
To: linux-wireless; +Cc: javier, Steve deRosier
In-Reply-To: <1278719330-56441-1-git-send-email-steve@cozybit.com>
Hi,
I'd like to retract this patch. Considering that it will break
backwards compatibility with older kernels (which I neglected to
mention that in the commit message) and it's not really critical at
this time, I think it's a bit premature. Let's call it more a RFC
than a patch.
That said, about a month ago someone on this list complained about the
fact that WLAN_EID_MESH_CONFIG and WLAN_EID_MESH_ID numbers overlapped
with WLAN_EID_AP_CHAN_REPORT and WLAN_EID_NEIGHBOR_REPORT numbers.
That's what prompted this patch. I don't think that this patch fixes
the actual problem he had with mesh not working, but he might want to
try this just to eliminate that variable.
I apologize for the inconvenience. I'll resubmit this patch at a more
appropriate time in the future.
Thanks,
- Steve
On Fri, Jul 9, 2010 at 4:48 PM, Steve deRosier <steve@cozybit.com> wrote:
> The old values conflicted with ANA approved values. The new values
> were chosen to be consistent with those for the ANA request plan
> for 802.11s.
>
> The Peer Link IE no longer exists in draft standards, replaced by
> the Peer Management IE. Leaving the old definition in was prudent
> until mesh code can be changed to match.
>
> Signed-off-by: Steve deRosier <steve@cozybit.com>
> ---
> include/linux/ieee80211.h | 23 +++++++++++++----------
> 1 files changed, 13 insertions(+), 10 deletions(-)
>
> diff --git a/include/linux/ieee80211.h b/include/linux/ieee80211.h
> index 97b2eae..1ed60b5 100644
> --- a/include/linux/ieee80211.h
> +++ b/include/linux/ieee80211.h
> @@ -1142,17 +1142,20 @@ enum ieee80211_eid {
> /* 802.11s
> *
> * All mesh EID numbers are pending IEEE 802.11 ANA approval.
> - * The numbers have been incremented from those suggested in
> - * 802.11s/D2.0 so that MESH_CONFIG does not conflict with
> - * EXT_SUPP_RATES.
> + * The numbers have been taken from ANA request plan for 802.11s
> + *
> + * Note that the Peer Link IE has been replaced with the similar
> + * Peer Management IE. We will keep the former definition until mesh
> + * code is changed to comply with latest 802.11s drafts.
> */
> - WLAN_EID_MESH_CONFIG = 51,
> - WLAN_EID_MESH_ID = 52,
> - WLAN_EID_PEER_LINK = 55,
> - WLAN_EID_PREQ = 68,
> - WLAN_EID_PREP = 69,
> - WLAN_EID_PERR = 70,
> - WLAN_EID_RANN = 49, /* compatible with FreeBSD */
> + WLAN_EID_MESH_CONFIG = 113,
> + WLAN_EID_MESH_ID = 114,
> + WLAN_EID_PEER_MGMT = 115,
> + WLAN_EID_PEER_LINK = 55, /* no longer in 802.11s drafts */
> + WLAN_EID_PREQ = 130,
> + WLAN_EID_PREP = 131,
> + WLAN_EID_PERR = 132,
> + WLAN_EID_RANN = 126,
>
> WLAN_EID_PWR_CONSTRAINT = 32,
> WLAN_EID_PWR_CAPABILITY = 33,
> --
> 1.7.0
>
>
^ permalink raw reply
* Re: BCM4311 in Ad-hoc Mode - Connection Unsuccessful
From: Nicholas Betcher @ 2010-07-10 5:46 UTC (permalink / raw)
To: Linux-Wireless Mailing List
In-Reply-To: <AANLkTilE2uM6UoHe0UZo20CYfc8DCxpHLlSdQyzyJw2J@mail.gmail.com>
Some updates:
- I am using kernel version 2.6.34 from openSUSE 11.3 RC2.
- Per the advice of a user on IRC I tried compat-wireless (from
07/08/2010) and the problem still persists.
- My firmware is 478.104 (as recommended on the Wiki)
- This problem persists with or without WEP enabled on the phone.
- Scanning networks before connecting DOES reveal other networks.
- iw event -t shows:
1278739983.002762: wlan0 (phy #0): scan started
1278739984.284008: wlan0 (phy #0): scan finished: 2412 2417 2422 2427
2432 2437 2442 2447 2452 2457 2462 2467 2472 2484, ""
- I have no access to another Ad-hoc device/software.
Any help on this is greatly appreciated!
Thanks.
On Sun, Jul 4, 2010 at 5:37 AM, Nicholas Betcher <nbetcher@gmail.com> wrote:
> Hello,
> I have recently been using (lightly) tethering on my Android phone and
> it uses Ad-hoc to provide wireless tethering. Unfortunately openSUSE
> 11.3 RC1 seems to be unable to connect to it. I haven't quite pinned
> down at what point it is failing, but it isn't failing at obtaining a
> DHCP lease, it's something more problematic. I have verified my
> settings are all correct on both sides (computer and phone). Also - to
> rule out hardware issues - I have used Windows 7 on the same system to
> successfully connect to the phone.
> Here are various logs/etc:
>
> lspci -v -nn:
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4311
> 802.11b/g WLAN [14e4:4311] (rev 02)
> Subsystem: Hewlett-Packard Company BCM4311 802.11b/g Wireless
> LAN Controller [103c:1374]
> Flags: bus master, fast devsel, latency 0, IRQ 18
> Memory at b8000000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information: Len=78 <?>
> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [d0] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [13c] Virtual Channel
> Capabilities: [160] Device Serial Number [REMOVED INTENTIONALLY]
> Capabilities: [16c] Power Budgeting <?>
> Kernel driver in use: b43-pci-bridge
>
> dmesg:
> [ 328.352293] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> [ 328.384141] b43-pci-bridge 0000:03:00.0: PCI: Disallowing DAC for device
> [ 328.384147] b43-phy0: DMA mask fallback from 64-bit to 32-bit
> [ 328.398967] wlan0: Trigger new scan to find an IBSS to join
> [ 331.704086] wlan0: Trigger new scan to find an IBSS to join
> [ 335.704063] wlan0: Trigger new scan to find an IBSS to join
> [ 336.996057] wlan0: Creating new IBSS network, BSSID [REMOVED INTENTIONALLY]
> [ 367.704079] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
> [ 399.704089] wlan0: No active IBSS STAs - trying to scan for other
> IBSS networks with same SSID (merge)
>
>
> /var/log/messages:
> Jul 3 01:57:53 NickB-Laptop ifup: wlan0 name: BCM4311 802.11b/g WLAN
> Jul 3 01:57:53 NickB-Laptop ifup-wireless: wlan0 warning:
> using NO encryption
> Jul 3 01:57:53 NickB-Laptop kernel: [ 684.963046] b43-phy0: Loading
> firmware version 478.104 (2008-07-01 00:50:23)
> Jul 3 01:57:53 NickB-Laptop kernel: [ 684.995149] b43-pci-bridge
> 0000:03:00.0: PCI: Disallowing DAC for device
> Jul 3 01:57:53 NickB-Laptop kernel: [ 684.995153] b43-phy0: DMA mask
> fallback from 64-bit to 32-bit
> Jul 3 01:57:53 NickB-Laptop kernel: [ 685.008172] wlan0: Selected
> IBSS BSSID [REMOVED INTENTIONALLY] based on configured SSID
> Jul 3 01:57:54 NickB-Laptop ifup-dhcp: wlan0 Starting DHCP4 client
> Jul 3 01:57:54 NickB-Laptop dhcpcd[5932]: wlan0: dhcpcd 3.2.3 starting
> Jul 3 01:57:54 NickB-Laptop dhcpcd[5932]: wlan0: hardware address =
> [REMOVED INTENTIONALLY]
> Jul 3 01:57:54 NickB-Laptop dhcpcd[5932]: wlan0: broadcasting for a lease
> Jul 3 01:58:14 NickB-Laptop dhcpcd[5932]: wlan0: timed out
> Jul 3 01:58:15 NickB-Laptop ifup-dhcp: wlan0 DHCP4 continues
> in background
> Jul 3 01:58:24 NickB-Laptop kernel: [ 715.701300] wlan0: No active
> IBSS STAs - trying to scan for other IBSS networks with same SSID
> (merge)
> Jul 3 01:58:31 NickB-Laptop dhcpcd[4983]: eth0: timed out
> Jul 3 01:58:31 NickB-Laptop dhcpcd[4983]: eth0: lease expired 1799145
> seconds ago
> Jul 3 01:58:31 NickB-Laptop dhcpcd[4983]: eth0: broadcasting for a lease
> Jul 3 01:58:34 NickB-Laptop dhcpcd[5932]: wlan0: timed out
> Jul 3 01:58:34 NickB-Laptop dhcpcd[5932]: wlan0: broadcasting for a lease
> Jul 3 01:58:54 NickB-Laptop dhcpcd[5932]: wlan0: timed out
> Jul 3 01:58:54 NickB-Laptop dhcpcd[5932]: wlan0: broadcasting for a lease
> Jul 3 01:58:56 NickB-Laptop kernel: [ 747.704067] wlan0: No active
> IBSS STAs - trying to scan for other IBSS networks with same SSID
> (merge)
>
> More is probably needed to truly debug this problem, so please CC me
> and let me know what more is needed.
> Thanks a million for the great driver, (seriously) :)
> Nick Betcher, CPhT
> Certified Pharmacy Technician
>
^ permalink raw reply
* [patch] prism54: call BUG_ON() earlier
From: Dan Carpenter @ 2010-07-10 8:53 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: John W. Linville, André Goddard Rosa, Jiri Kosina,
linux-wireless, kernel-janitors
This test is off by one because strlen() doesn't include the NULL
terminator.
Signed-off-by: Dan Carpenter <error27@gmail.com>
diff --git a/drivers/net/wireless/prism54/isl_ioctl.c b/drivers/net/wireless/prism54/isl_ioctl.c
index 8d1190c..1051268 100644
--- a/drivers/net/wireless/prism54/isl_ioctl.c
+++ b/drivers/net/wireless/prism54/isl_ioctl.c
@@ -2067,7 +2067,7 @@ send_simple_event(islpci_private *priv, const char *str)
memptr = kmalloc(IW_CUSTOM_MAX, GFP_KERNEL);
if (!memptr)
return;
- BUG_ON(n > IW_CUSTOM_MAX);
+ BUG_ON(n >= IW_CUSTOM_MAX);
wrqu.data.pointer = memptr;
wrqu.data.length = n;
strcpy(memptr, str);
^ permalink raw reply related
* [PATCH] adm8211: fix memory leak
From: Kulikov Vasiliy @ 2010-07-10 12:28 UTC (permalink / raw)
To: kernel-janitors
Cc: Michael Wu, John W. Linville, David S. Miller, Johannes Berg,
Kalle Valo, Luis R. Rodriguez, linux-wireless, netdev
We must free priv->eeprom allocated in adm8211_read_eeprom().
Signed-off-by: Kulikov Vasiliy <segooon@gmail.com>
---
drivers/net/wireless/adm8211.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/adm8211.c b/drivers/net/wireless/adm8211.c
index 880ad9d..bde2fa8 100644
--- a/drivers/net/wireless/adm8211.c
+++ b/drivers/net/wireless/adm8211.c
@@ -1903,7 +1903,7 @@ static int __devinit adm8211_probe(struct pci_dev *pdev,
if (err) {
printk(KERN_ERR "%s (adm8211): Cannot register device\n",
pci_name(pdev));
- goto err_free_desc;
+ goto err_free_eeprom;
}
printk(KERN_INFO "%s: hwaddr %pM, Rev 0x%02x\n",
@@ -1912,6 +1912,9 @@ static int __devinit adm8211_probe(struct pci_dev *pdev,
return 0;
+ err_free_eeprom:
+ kfree(priv->eeprom);
+
err_free_desc:
pci_free_consistent(pdev,
sizeof(struct adm8211_desc) * priv->rx_ring_size +
--
1.7.0.4
^ permalink raw reply related
* [PATCH] atmel: unregister_netdev() on error
From: Kulikov Vasiliy @ 2010-07-10 13:11 UTC (permalink / raw)
To: kernel-janitors
Cc: Simon Kelley, John W. Linville, David S. Miller,
Stephen Hemminger, Eric Dumazet, Ben Hutchings, linux-wireless,
netdev
We must unregister registered device if probe_atmel_card() fails.
Signed-off-by: Kulikov Vasiliy <segooon@gmail.com>
---
drivers/net/wireless/atmel.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/atmel.c b/drivers/net/wireless/atmel.c
index c8f7090..b9334a3 100644
--- a/drivers/net/wireless/atmel.c
+++ b/drivers/net/wireless/atmel.c
@@ -1626,7 +1626,7 @@ struct net_device *init_atmel_card(unsigned short irq, unsigned long port,
if (!probe_atmel_card(dev)) {
unregister_netdev(dev);
- goto err_out_res;
+ goto err_out_unreg;
}
netif_carrier_off(dev);
@@ -1640,6 +1640,9 @@ struct net_device *init_atmel_card(unsigned short irq, unsigned long port,
return dev;
+err_out_unreg:
+ unregister_netdev(dev);
+
err_out_res:
release_region(dev->base_addr, 32);
err_out_irq:
--
1.7.0.4
^ permalink raw reply related
* Re: [PATCH] atmel: unregister_netdev() on error
From: Dan Carpenter @ 2010-07-10 14:12 UTC (permalink / raw)
To: Kulikov Vasiliy
Cc: kernel-janitors, Simon Kelley, John W. Linville, David S. Miller,
Stephen Hemminger, Eric Dumazet, Ben Hutchings, linux-wireless,
netdev
In-Reply-To: <1278767508-10164-1-git-send-email-segooon@gmail.com>
On Sat, Jul 10, 2010 at 05:11:47PM +0400, Kulikov Vasiliy wrote:
> We must unregister registered device if probe_atmel_card() fails.
I think you hit send accidentally on this one?
> if (!probe_atmel_card(dev)) {
> unregister_netdev(dev);
^^^^^^^^^^^^^^^^^^^^^^^
> - goto err_out_res;
> + goto err_out_unreg;
> }
>
> netif_carrier_off(dev);
> @@ -1640,6 +1640,9 @@ struct net_device *init_atmel_card(unsigned short irq, unsigned long port,
>
> return dev;
>
> +err_out_unreg:
> + unregister_netdev(dev);
^^^^^^^^^^^^^^^^^^^^^^
> +
What the pants? :P
regards,
dan carpenter
^ permalink raw reply
* Re: [PATCH] atmel: unregister_netdev() on error
From: Kulikov Vasiliy @ 2010-07-10 16:38 UTC (permalink / raw)
To: Dan Carpenter
Cc: kernel-janitors, Simon Kelley, John W. Linville, David S. Miller,
Stephen Hemminger, Eric Dumazet, Ben Hutchings, linux-wireless,
netdev
In-Reply-To: <20100710141204.GY19184@bicker>
On Sat, Jul 10, 2010 at 16:12 +0200, Dan Carpenter wrote:
> > +err_out_unreg:
> > + unregister_netdev(dev);
> ^^^^^^^^^^^^^^^^^^^^^^
> > +
>
> What the pants? :P
Hmm, I've slightly misunderstood the code, sorry.
Thanks, Dan.
^ permalink raw reply
* Issues with ath9k dropping connectivity - now no connectivity
From: Norman Henderson @ 2010-07-10 18:32 UTC (permalink / raw)
To: linux-wireless
Hi,
I'm a bit new to all of this - here's the short story. I would
appreciate any help available!
I was building a WAP using a PC Engines ALIX board (AMD Geode LX800),
DNMA92 wireless card (Atheros 92xx) and Voyage Linux (based on Debian
Lenny, 2.6.30 kernel with hostapd 0.6.9 and libnl1.1). It was all
working but, the wireless card would drop connectivity for no apparent
reason after an undetermined time (minutes to hours). Stations (Win or
cellphone) would no longer see it at all, as if it was no longer
transmitting.
The Voyage maintainer advised that ath9k isn't that stable at 2.6.30.
So, I upgraded the kernel to 2.6.32 using the Debian Lenny backport. I
then installed the "stable" compat-wireless, 2.6.32.16.
Hostapd appears to start OK. However, the wireless SSID is only
visible to the Windows clients for a short time - seconds/minutes -
and they aren't able to connect. There were no errors in the hostapd
startup and it does its key rotations periodically. All that's logged
from hostapd -dd during the actual time that the Win clients can see
it and are trying to connect is:
1278785975.350851: STA 00:13:02:be:7b:f9 sent probe request for broadcast SSID
1278785975.353034: MGMT (TX callback) ACK
1278785975.353073: mgmt::proberesp cb
(repeated a few times)
The Win7 station used to connect automatically but now doesn't and
when I click "connect" it fails and shortly thereafter the SSID
disappears from the list.
Nothing in /var/log. iw phy phy0 info and iw dev wlan0 info appear to
report sensible info as does iwconfig.
During boot I do get messages about "VIA Padlock Hash Engine not detected" and
modprobe: FATAL: Error inserting padlock_sha
(/lib/modules/2.6.32-bpo.5-686/kern...): No such device
>From googling it's not clear to me at least whether this is relevant.
Suggestions? What further diagnostics could I do?
Thanks,
Norm Henderson
^ permalink raw reply
* Re: Issues with ath9k dropping connectivity - now no connectivity
From: Felix Fietkau @ 2010-07-10 18:38 UTC (permalink / raw)
To: Norman Henderson; +Cc: linux-wireless
In-Reply-To: <AANLkTilq_VFbOPHmMuf1EFmewc_WBBpgvW0t7ogZdbdl@mail.gmail.com>
On 2010-07-10 8:32 PM, Norman Henderson wrote:
> Hi,
>
> I'm a bit new to all of this - here's the short story. I would
> appreciate any help available!
>
> I was building a WAP using a PC Engines ALIX board (AMD Geode LX800),
> DNMA92 wireless card (Atheros 92xx) and Voyage Linux (based on Debian
> Lenny, 2.6.30 kernel with hostapd 0.6.9 and libnl1.1). It was all
> working but, the wireless card would drop connectivity for no apparent
> reason after an undetermined time (minutes to hours). Stations (Win or
> cellphone) would no longer see it at all, as if it was no longer
> transmitting.
>
> The Voyage maintainer advised that ath9k isn't that stable at 2.6.30.
> So, I upgraded the kernel to 2.6.32 using the Debian Lenny backport. I
> then installed the "stable" compat-wireless, 2.6.32.16.
>
> Hostapd appears to start OK. However, the wireless SSID is only
> visible to the Windows clients for a short time - seconds/minutes -
> and they aren't able to connect. There were no errors in the hostapd
> startup and it does its key rotations periodically. All that's logged
> from hostapd -dd during the actual time that the Win clients can see
> it and are trying to connect is:
> 1278785975.350851: STA 00:13:02:be:7b:f9 sent probe request for broadcast SSID
> 1278785975.353034: MGMT (TX callback) ACK
> 1278785975.353073: mgmt::proberesp cb
> (repeated a few times)
>
> The Win7 station used to connect automatically but now doesn't and
> when I click "connect" it fails and shortly thereafter the SSID
> disappears from the list.
>
> Nothing in /var/log. iw phy phy0 info and iw dev wlan0 info appear to
> report sensible info as does iwconfig.
>
> During boot I do get messages about "VIA Padlock Hash Engine not detected" and
> modprobe: FATAL: Error inserting padlock_sha
> (/lib/modules/2.6.32-bpo.5-686/kern...): No such device
> From googling it's not clear to me at least whether this is relevant.
>
> Suggestions? What further diagnostics could I do?
I'd suggest using a 'bleeding edge' compat-wireless along with hostapd
version 0.7.2.
In OpenWrt we're using a compat-wireless based on wireless-testing
2010-07-06, along with two ath9k patches that were merged in a later
version.
According to my own testing and various user feedback, this is the most
stable version that we had so far.
I think 2.6.36 is probably going to be the first Linux Kernel version
with ath9k working in AP mode *reliably*.
- Felix
^ permalink raw reply
* Compat-wireless release for 2010-07-10 is baked
From: Compat-wireless cronjob account @ 2010-07-10 19:03 UTC (permalink / raw)
To: linux-wireless
>From git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/compat-wireless-2.6
55cfa0f..948cf60 linux-2.6.32.y -> origin/linux-2.6.32.y
4db5fad..91d8dae linux-2.6.33.y -> origin/linux-2.6.33.y
5789d0f..9923049 linux-2.6.34.y -> origin/linux-2.6.34.y
5ba7a3f..8302dc6 linux-2.6.35.y -> origin/linux-2.6.35.y
469f74f..bea1297 master -> origin/master
* [new tag] compat-wireless-2.6.33.6 -> compat-wireless-2.6.33.6
* [new tag] compat-wireless-v2.6.32.16 -> compat-wireless-v2.6.32.16
* [new tag] compat-wireless-v2.6.35-rc4 -> compat-wireless-v2.6.35-rc4
>From git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/compat-wireless-2.6
* [new tag] compat-wireless-v2.6.34.1 -> compat-wireless-v2.6.34.1
>From git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
59d8d6f..cb6fa5f history -> origin/history
+ 95a7e04...0811daa master -> origin/master (forced update)
78178c7..e467e10 stable -> origin/stable
* [new tag] next-20100709 -> next-20100709
compat-wireless code metrics
495293 - Total upstream lines of code being pulled
1419 - backport code changes
1186 - backport code additions
233 - backport code deletions
5766 - backport from compat module
7185 - total backport code
1.4507 - % of code consists of backport work
1218 - Crap changes not yet posted
1179 - Crap additions not yet posted
39 - Crap deletions not yet posted
0.2459 - % of crap code
Base tree: linux-next.git
Base tree version: next-20100709
compat-wireless release: compat-wireless-2010-07-08-2-gbea1297
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox