Thanks, nm-connection-editor is just what I was looking for. It seems like bugzilla.kernel.org is down, so I haven't been able to submit a bug report for the kernel. However, I did patch the specified code to confirm indeed the iwl-core.c file is at fault. In fact, I'm using the patched driver to connect to the network right now. So this definitely is not a network manager problem.
Bill ----- Original Message ----- From: "Dan Williams" <d...@redhat.com> To: "Bill C Riemers" <briem...@redhat.com> Cc: NetworkManager-list@gnome.org Sent: Wednesday, October 26, 2011 8:03:03 PM Subject: Re: Trying to understand a kernel error On Mon, 2011-10-24 at 15:02 -0400, Bill C Riemers wrote: > OK. In the mean time, is there a way to keep the network manager from trying > to connect to this network, other than using my airport mode switch? You can always remove the network using nm-connection-editor or the KDE tools (depending on your desktop) or change the network to disable autoconnect. Dan > Bill > > > On 10/24/2011 01:42 PM, Dan Williams wrote: > > On Mon, 2011-10-24 at 10:39 -0400, Bill C Riemers wrote: > >> Last night, I tried using wifi from the comfortinn I am staying at for the > >> week, and I repeatedly received a kernel error: > >> > >> :WARNING: at drivers/net/wireless/iwlwifi/iwl-core.c:482 > >> iwl_check_rxon_cmd+0x21 > >> 1/0x21f [iwlagn]() > >> > >> Actually, looking at the respective line of code, it seems the module is > >> complaining that channel number 6 is not a valid channel number... > > Probably best to persue this via kernel development lists actually, it's > > probably more of a kernel driver bug than an NM bug. But some things > > that come to mind: perhaps the AP's 802.11d IE is telling your card that > > it cannot use some channels; often APs get this wrong. Second, if this > > happens generally, it could be rfkill related. But actually, your > > problem is apparently this block: > > > > if ((rxon->flags& (RXON_FLG_CCK_MSK | RXON_FLG_SHORT_SLOT_MSK)) > > == (RXON_FLG_CCK_MSK | RXON_FLG_SHORT_SLOT_MSK)) { > > IWL_WARN(priv, "CCK and short slot\n"); > > errors |= BIT(7); > > } > > > > which is much more a kernel driver issue than an NM issue... (0x40 = bit 7) > > > > Dan > > > >> Now here are the problems related to network manager: > >> 1. I have no way of aborting the connection attempt. In fact now when > >> I'm in the hotel I have to have the wifi switched off otherwise it > >> automatically tries to connect to comfortinn, and generates the error > >> repeatedly, blocking me from doing anything else. > >> 2. I'm not sure if the problem is a kernel bug, or network manager is > >> passing invalid parameters. There seems to be no way to open the > >> connection in with the gnome interface to network manager. I can only > >> open the connection options for connections I'm actively connected to. > >> Is there a file on disk somewhere I can access, or an alternate UI? > >> > >> BTW. This problem seems related to the settings used for comfort inn, as I > >> have never had problems connecting to any other wifi network. > >> > >> Regards, > >> > >> Bill > >> > >> _______________________________________________ > >> networkmanager-list mailing list > >> networkmanager-list@gnome.org > >> http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > _______________________________________________ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list