linux-kernel - stable-3.1: iwlwifi broken with nomsi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111128195939.GA15362@localhost>
Date:	Mon, 28 Nov 2011 20:59:39 +0100
From:	Johan Hovold <jhovold@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	Wey-Yi Guy <wey-yi.w.guy@...el.com>,
	"John W. Linville" <linville@...driver.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: stable-3.1: iwlwifi broken with nomsi

Hi Greg, 

I believe commit 63665158282dd3b5d70 (iwlwifi: allow pci_enable_msi fail)
needs to be added to the 3.1 stable tree as the driver fails to probe
with MSI disabled since commit 084dd79172cb3 (iwlagn: move PCI related
operations from probe and remove to PCI layer) without it:

[    2.564901] iwlagn 0000:0e:00.0: PCI INT A -> GSI 18 (level, low) ->
IRQ 18
[    2.564962] iwlagn 0000:0e:00.0: setting latency timer to 64
[    2.564977] iwlagn 0000:0e:00.0: pci_resource_len = 0x00002000
[    2.567136] iwlagn 0000:0e:00.0: pci_resource_base = f8038000
[    2.569274] iwlagn 0000:0e:00.0: HW Revision ID = 0x0
[    2.571375] iwlagn 0000:0e:00.0: pci_enable_msi failed
[    2.571431] iwlagn 0000:0e:00.0: PCI INT A disabled
[    2.575598] iwlagn: probe of 0000:0e:00.0 failed with error -1

The problem was initially reported here:

	https://lkml.org/lkml/2011/10/26/314

but the fix was never marked for stable.

Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/