From: Mikael Pettersson <mikpe@it.uu.se>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [3.7.0 regression] rt2x00lib_probe_dev: Error - Failed to initialize hw
Date: Mon, 17 Dec 2012 11:51:14 +0100 [thread overview]
Message-ID: <20686.63778.840426.61474@pilspetsen.it.uu.se> (raw)
I just updated an old 1st gen AMD64 laptop from kernel 3.6.0 to 3.7.0,
Fedora 15 user-space, and was greeted by the following kernel warning:
WARNING: at net/wireless/core.c:389 wiphy_register+0x5c3/0x600 [cfg80211]()
Hardware name: SAM#451B
Modules linked in: rt2500pci(+) snd_mpu401_uart rt2x00pci snd_rawmidi rt2x00lib sg snd_seq_device mac80211 cfg80211 amd64_agp agpgart snd eeprom_93cx6 soundcore via_rhine mii evdev ipv6 ehci_hcd uhci_hcd sr_mod cdrom usbcore usb_common
Pid: 378, comm: modprobe Not tainted 3.7.0 #1
Call Trace:
[<ffffffff810260b9>] ? warn_slowpath_common+0x79/0xc0
[<ffffffffa0115773>] ? wiphy_register+0x5c3/0x600 [cfg80211]
[<ffffffff810c5b3f>] ? __kmalloc+0xef/0x170
[<ffffffffa013ac97>] ? ieee80211_register_hw+0x347/0x6d0 [mac80211]
[<ffffffffa00f92ed>] ? rt2x00lib_probe_dev+0x53d/0x720 [rt2x00lib]
[<ffffffffa0060888>] ? rt2x00pci_probe+0x168/0x2e4 [rt2x00pci]
[<ffffffff81194cd0>] ? pci_device_probe+0xd0/0x170
[<ffffffff811f2934>] ? driver_probe_device+0x64/0x210
[<ffffffff811f2b73>] ? __driver_attach+0x93/0xa0
[<ffffffff811f2ae0>] ? driver_probe_device+0x210/0x210
[<ffffffff811f0f95>] ? bus_for_each_dev+0x45/0x80
[<ffffffff811f20d8>] ? bus_add_driver+0x178/0x250
[<ffffffff811f314e>] ? driver_register+0x6e/0x170
[<ffffffff81048a14>] ? notifier_call_chain+0x44/0x60
[<ffffffffa0196000>] ? 0xffffffffa0195fff
[<ffffffff810002ca>] ? do_one_initcall+0x11a/0x160
[<ffffffff81069786>] ? sys_init_module+0x76/0x1c0
[<ffffffff812c15d0>] ? system_call_fastpath+0x16/0x1b
---[ end trace f8413f27de31929d ]---
phy0 -> rt2x00lib_probe_dev: Error - Failed to initialize hw.
rt2500pci: probe of 0000:00:0c.0 failed with error -22
Rebooting into 3.6.0 shows no such error, booting 3.7.0 again shows the error,
so it's completely reproducible.
lspci -v for the device in question:
00:0c.0 Network controller: Ralink corp. RT2500 802.11g (rev 01)
Subsystem: Micro-Star International Co., Ltd. Unknown 802.11g mini-PCI Adapter
Flags: bus master, slow devsel, latency 64, IRQ 18
Memory at d0000000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
Kernel driver in use: rt2500pci
Kernel modules: rt2500pci
I've never actually used or configured this device (the laptop is always
on wired ethernet), but thought you should know about this possible driver
regression.
/Mikael
next reply other threads:[~2012-12-17 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 10:51 Mikael Pettersson [this message]
2012-12-17 11:10 ` devendra.aaru
2012-12-17 11:11 ` devendra.aaru
2012-12-17 12:22 ` Mikael Pettersson
2012-12-17 12:59 ` devendra.aaru
2012-12-17 13:21 ` Gertjan van Wingerde
2012-12-17 13:57 ` Mikael Pettersson
2012-12-17 14:14 ` devendra.aaru
2012-12-17 13:48 ` Stanislaw Gruszka
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=20686.63778.840426.61474@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®