Return-path: Received: from smtp1.uu.se ([130.238.7.54]:44025 "EHLO smtp1.uu.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751958Ab2LQMYI (ORCPT ); Mon, 17 Dec 2012 07:24:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <20687.3736.365327.811519@pilspetsen.it.uu.se> (sfid-20121217_132415_304444_4ABC28AF) Date: Mon, 17 Dec 2012 13:22:48 +0100 From: Mikael Pettersson To: "devendra.aaru" Cc: Mikael Pettersson , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [3.7.0 regression] rt2x00lib_probe_dev: Error - Failed to initialize hw In-Reply-To: References: <20686.63778.840426.61474@pilspetsen.it.uu.se> Sender: linux-wireless-owner@vger.kernel.org List-ID: devendra.aaru writes: > On Mon, Dec 17, 2012 at 5:51 AM, Mikael Pettersson wrote: > > 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]() > > I am seeing this line actually when i do vim +389 net/wireless/core.c. > > u16 all_iftypes = 0; > > its good if you tell us the top sha1 of yours? It's the plain linux-3.7.tar.xz from kernel.org, no git involved. Lines 389-390 of net/wireless/core.c are: if (WARN_ON(c->max_interfaces < 2)) return -EINVAL; /Mikael > > > > 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: > > [] ? warn_slowpath_common+0x79/0xc0 > > [] ? wiphy_register+0x5c3/0x600 [cfg80211] > > [] ? __kmalloc+0xef/0x170 > > [] ? ieee80211_register_hw+0x347/0x6d0 [mac80211] > > [] ? rt2x00lib_probe_dev+0x53d/0x720 [rt2x00lib] > > [] ? rt2x00pci_probe+0x168/0x2e4 [rt2x00pci] > > [] ? pci_device_probe+0xd0/0x170 > > [] ? driver_probe_device+0x64/0x210 > > [] ? __driver_attach+0x93/0xa0 > > [] ? driver_probe_device+0x210/0x210 > > [] ? bus_for_each_dev+0x45/0x80 > > [] ? bus_add_driver+0x178/0x250 > > [] ? driver_register+0x6e/0x170 > > [] ? notifier_call_chain+0x44/0x60 > > [] ? 0xffffffffa0195fff > > [] ? do_one_initcall+0x11a/0x160 > > [] ? sys_init_module+0x76/0x1c0 > > [] ? 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. > > > > there are lots of WARN_ON's btw, :) may be one of them triggered, but > please tell us the top sha1 of yours, so that the wireless dev's can > easily see whats' happening with the rt2x00 to trigger this :) > > > > 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 > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ >