From: wwguy <wey-yi.w.guy@intel.com>
To: werner <w.landgraf@ru.ru>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"dave.taht@gmail.com" <dave.taht@gmail.com>,
"rientjes@google.com" <rientjes@google.com>,
"arend@broadcom.com" <arend@broadcom.com>,
"toralf.foerster@gmx.de" <toralf.foerster@gmx.de>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"larry.finger@gmail.com" <larry.finger@gmail.com>
Subject: Re: 3.1-rc9 and 3.1 wifi problem , problem continues with 3.1
Date: Wed, 26 Oct 2011 15:21:22 -0700 [thread overview]
Message-ID: <1319667682.14693.29.camel@wwguy-ubuntu> (raw)
In-Reply-To: <web-633781994@zbackend1.aha.ru>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Wed, 2011-10-26 at 14:47 -0700, werner wrote:
> As reported, with 3.1-rc9 the wifi of a friend's laptop
> didnt work at all. With 3.0.4 it's working normally.
>
> The problem continues with 3.1
>
> Now I take some files for identify the problem. Below see
> lsmod and dmesg , and enclosed is hwinfo and syslog of
> that laptop as it was running with 3.1 just as wifi didn't
> work. For comparison, on syslog you can see the
> previous boots (I separated them by blank lines), all with
> 3.0.4 , when wifi was working.
>
> I hope that's now enough information to fix that problem.
>
>
> Werner Landgraf
could you try this test patch
Thanks
Wey
[-- Attachment #2: 0001-iwlwifi-allow-pci_enable_msi-fail.patch --]
[-- Type: text/x-patch, Size: 1126 bytes --]
>From 64a1b22cc9d179d69c66b23619691ba2a13ee646 Mon Sep 17 00:00:00 2001
From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Date: Wed, 26 Oct 2011 15:15:38 -0700
Subject: [PATCH 1/1] iwlwifi: allow pci_enable_msi fail
Continue the init process even fail to enable msi
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
---
drivers/net/wireless/iwlwifi/iwl-pci.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-pci.c b/drivers/net/wireless/iwlwifi/iwl-pci.c
index 35d4551..911186f 100644
--- a/drivers/net/wireless/iwlwifi/iwl-pci.c
+++ b/drivers/net/wireless/iwlwifi/iwl-pci.c
@@ -429,10 +429,9 @@ static int iwl_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
pci_write_config_byte(pdev, PCI_CFG_RETRY_TIMEOUT, 0x00);
err = pci_enable_msi(pdev);
- if (err) {
- dev_printk(KERN_ERR, &pdev->dev, "pci_enable_msi failed");
- goto out_iounmap;
- }
+ if (err)
+ dev_printk(KERN_ERR, &pdev->dev,
+ "pci_enable_msi failed(0X%x)", err);
/* TODO: Move this away, not needed if not MSI */
/* enable rfkill interrupt: hw bug w/a */
--
1.7.0.4
next prev parent reply other threads:[~2011-10-26 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 21:47 3.1-rc9 and 3.1 wifi problem , problem continues with 3.1 werner
2011-10-26 21:11 ` Guy, Wey-Yi
2011-10-26 22:21 ` wwguy [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-27 12:53 werner
2011-10-27 12:57 ` wwguy
2011-10-27 20:12 ` David Rientjes
2011-10-27 19:30 ` Guy, Wey-Yi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1319667682.14693.29.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=arend@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=ilw@linux.intel.com \
--cc=larry.finger@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rientjes@google.com \
--cc=toralf.foerster@gmx.de \
--cc=w.landgraf@ru.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).