linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: sedat.dilek@gmail.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: 3.4-rc5: Oops in run_timer_softirq()
Date: Mon, 07 May 2012 22:52:00 +0200	[thread overview]
Message-ID: <4FA835F0.2050003@fold.natur.cuni.cz> (raw)
In-Reply-To: <CA+icZUWwy6A5y8EM0b=xEwzP2gqo4mY_bUdUAG8NOVajAHzYvg@mail.gmail.com>

Sedat Dilek wrote:
> On Mon, May 7, 2012 at 9:26 PM, Martin Mokrejs
> <mmokrejs@fold.natur.cuni.cz> wrote:
>> Hmm, linux-3.4-rc6 tells me some news about my v5 firmware. Will try to upgrade. The ACPI message
>> is not new.
>>
>> [   11.008565] ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120320/utaddress-251)
>> [   11.008571] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>> [   11.936175] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d
>> [   11.936177] Copyright(c) 2003-2012 Intel Corporation
>> [   11.936364] iwlwifi 0000:09:00.0: pci_resource_len = 0x00002000
>> [   11.936366] iwlwifi 0000:09:00.0: pci_resource_base = ffffc90006684000
>> [   11.936368] iwlwifi 0000:09:00.0: HW Revision ID = 0x34
>> [   11.936462] iwlwifi 0000:09:00.0: irq 53 for MSI/MSI-X
>> [   12.058300] iwlwifi 0000:09:00.0: request for firmware file 'iwlwifi-6000g2b-6.ucode' failed.
>> [   12.137737] usb 1-1.5: usb auto-suspend, wakeup 0
>> [   12.158653] iwlwifi 0000:09:00.0: Firmware has old API version, expected v6, got v5.
>> [   12.158655] iwlwifi 0000:09:00.0: New firmware can be obtained from http://www.intellinuxwireless.org/.
>> [   12.158657] iwlwifi 0000:09:00.0: loaded firmware version 17.168.5.2 build 35905
>> [   12.158759] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEBUG enabled
>> [   12.158761] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
>> [   12.158763] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
>> [   12.158764] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
>> [   12.158766] iwlwifi 0000:09:00.0: CONFIG_IWLWIFI_P2P disabled
>> [   12.158768] iwlwifi 0000:09:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0
>> [   12.158816] iwlwifi 0000:09:00.0: L1 Disabled; Enabling L0S
>> [   12.175752] iwlwifi 0000:09:00.0: device EEPROM VER=0x71a, CALIB=0x6
>> [   12.175754] iwlwifi 0000:09:00.0: Device SKU: 0x150
>> [   12.175756] iwlwifi 0000:09:00.0: Valid Tx ant: 0x1, Valid Rx ant: 0x3
>> [   12.175768] iwlwifi 0000:09:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
>>
>> Martin
>>
> 
> What about a new subject :-)?

Well, I just thought that maybe it is related to the v5 firmware, but no, it is not.
I did not want to report the v5 vs. v6 line. This is really about the Oops. ;)

> Known issue - Check for these patches (pending in
> (net.git|wireless.git)#master):
> 
>       iwlwifi: use correct released ucode version
>       iwlwifi: use 6000G2B for 6030 device series

So when I already updated the firmware manually I do not these two patches, right?

Martin

  reply	other threads:[~2012-05-07 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 14:46 3.4-rc5: Oops in run_timer_softirq() Martin Mokrejs
2012-05-07 19:26 ` Martin Mokrejs
2012-05-07 19:45   ` Martin Mokrejs
2012-05-07 19:53   ` Sedat Dilek
2012-05-07 20:52     ` Martin Mokrejs [this message]
2012-05-14 19:14       ` Martin Mokrejs
2012-05-14 20:09         ` Sedat Dilek
     [not found] <4FA7DEC8.5040506@fold.natur.cuni.cz>
2012-05-07 16:33 ` Bjorn Helgaas
2012-05-07 16:51   ` Martin Mokrejs

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=4FA835F0.2050003@fold.natur.cuni.cz \
    --to=mmokrejs@fold.natur.cuni.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    /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).