Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): Kernel 2.6.40.6-0.fc15.i686 How reproducible: Always Steps to Reproduce: 1. Install kernel 2.6.40.6-0.fc15.i686 2. Install iwl6000gwb firmware (with all related wireless stuff). 3. Start up wireless lan Actual results: Everything stops, computer freezes. Expected results: wireless Lan will start working fine. Additional info: Kernel 2.6.38.6-26.rc1.fc15.i686 does not have this problem, everything works fine. Problem started when I upgraded the kernel. I have an Intel Centrino Advanced N 6230 wireless card.
I wonder, why is it not a bug? You were expecting that the Intel 6230 was going to crash the system? Why? And how do I avoid it? It worked fine with 2.6.38.6-26.rc1.fc15.i686 What changed? Will it work fine at a later release or should I just dump that card?
I'm not really sure where to go with this. Are you using NetworkManager? Can you setup netconsole over a wired connection to see if some output is produced that might be helpful?
Yes indeed, I am using NetworkManager. Let me get home and I'll input the version number. I changed the card for a Habey HB-NB037H and everything is working fine now (Atheros AR9285 chipset (MAC,Baseband,RF) with AR3011) I will switch the card back to the Centrino 6230 to run the tests. Q. I am not familiar with netconsole. Are these instructions current with Fedora 15? (http://fedoraproject.org/wiki/Netconsole) I am just not sure if systemd introduced any change that impacted these instructions. What logging level do you want from netconsole? JP
NetworkManager version 0.9.1.90-3.git20110927.fc15
There should be no systemd influence on that. You just have to modify /etc/modprobe.d/netconsole.conf and do "modprobe netconsole" and reproduce the problem. Remember to disable iptables and ip6tables on both machines. Level should be the highest one i.e. 9. Other than netconsole you may try to catch call-trace from virtual terminal (Atl+Ctrl+F2).
Created attachment 532267 [details] Log File before system crashes Log file from nc -l -u 6666
Log does not contain call-trace. I do not know why? I guess kernel hugs too quickly and we are not able send messages through network. I think there should be way to force we flush dmesg before we hung up, but I'm not sure how. Perhaps you could try to catch call-trace on virtual terminal and make a photo?
ran it again and the Log got just a little farther away... [ 25.339118] avahi-daemon[805]: Service "scorpblue" (/services/udisks.service) successfully established. [ 25.339127] avahi-daemon[805]: Service "scorpblue" (/services/ssh.service) successfully established. [ 25.339135] avahi-daemon[805]: Registering HINFO record with values 'I686'/'LINUX'. [ 25.573479] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 25.577677] Bluetooth: BNEP filters: protocol multicast [ 25.798666] Bluetooth: RFCOMM TTY layer initialized [ 25.802803] Bluetooth: RFCOMM socket layer initialized [ 25.806871] Bluetooth: RFCOMM ver 1.11 [ 26.115056] iwlagn 0000:02:00.0: Error sending REPLY_BT_COEX_PROT_ENV: time out after 500ms. [ 26.119463] iwlagn 0000:02:00.0: failed to send BT env command How do i catch call-trace on a virtual terminal?
> How do i catch call-trace on a virtual terminal? First blacklist iwlagn module: echo "blacklist iwlagn" > /etc/modprobe/iwlagn.conf Then reboot system and log into Xwindow session, such NetworkManager will start. Then switch to virtual console (Alt+Ctrl+F2) and login as root. Then do "modprobe iwlagn", since module will load NetworkManager will try to setup network connection and system should crash. Then take a photo.
Created attachment 532465 [details] Video of iwlagn crashing I could not take a photo at the end because the crash wipes the screen. I did a second best, taking a video. (I can open it with VLC). Likewise, I used netconsole and ssh to initiate the modprobe remotely and capture the output as text. This is the result: ========= [ 502.021907] cfg80211: Calling CRDA to update world regulatory domain [ 502.118290] cfg80211: World regulatory domain updated: [ 502.118482] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 502.118749] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 502.119003] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 502.119286] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 502.119531] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 502.119780] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 502.152168] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d [ 502.152426] iwlagn: Copyright(c) 2003-2011 Intel Corporation [ 502.152872] iwlagn 0000:02:00.0: enabling device (0000 -> 0002) [ 502.153131] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 502.153409] iwlagn 0000:02:00.0: setting latency timer to 64 [ 502.153690] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0 [ 502.169044] iwlagn 0000:02:00.0: device EEPROM VER=0x716, CALIB=0x6 [ 502.169237] iwlagn 0000:02:00.0: Device SKU: 0Xb [ 502.169389] iwlagn 0000:02:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3 [ 502.169694] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 502.210802] iwlagn 0000:02:00.0: loaded firmware version 17.168.5.1 build 33993 [ 502.213274] Registered led device: phy0-led [ 502.252806] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 502.337206] cfg80211: Calling CRDA for country: PA [ 502.347431] cfg80211: Regulatory domain changed to country: PA [ 502.348067] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 502.348829] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 502.349529] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 502.350247] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm) [ 502.350999] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 503.594482] hrtimer: interrupt took 600051426 ns ===============================
Besides the one I sent with the video, I was able to obtain another one where the computer took longer to crash, I was able to try to login to the wifi and while inputing the credentials, the crash came. ======================== [ 328.536519] cfg80211: Calling CRDA to update world regulatory domain [ 328.643954] cfg80211: World regulatory domain updated: [ 328.644211] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 328.644469] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 328.644730] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 328.644981] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 328.645271] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 328.645530] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 328.677886] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d [ 328.678197] iwlagn: Copyright(c) 2003-2011 Intel Corporation [ 328.678646] iwlagn 0000:02:00.0: enabling device (0000 -> 0002) [ 328.678874] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 328.679186] iwlagn 0000:02:00.0: setting latency timer to 64 [ 328.679473] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0 [ 328.694674] iwlagn 0000:02:00.0: device EEPROM VER=0x716, CALIB=0x6 [ 328.694866] iwlagn 0000:02:00.0: Device SKU: 0Xb [ 328.695055] iwlagn 0000:02:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3 [ 328.695733] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 328.758946] iwlagn 0000:02:00.0: loaded firmware version 17.168.5.1 build 33993 [ 328.761417] Registered led device: phy0-led [ 328.800804] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 328.896148] cfg80211: Calling CRDA for country: PA [ 328.910647] cfg80211: Regulatory domain changed to country: PA [ 328.910861] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 328.911204] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 328.911471] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 328.911727] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm) [ 328.911975] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 329.273516] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 334.136530] wlan0: authenticate with 00:0f:66:0a:2e:ba (try 1) [ 334.149668] wlan0: 00:0f:66:0a:2e:ba denied authentication (status 15) [ 537.524129] iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after 500ms. [ 537.524163] iwlagn 0000:02:00.0: set power fail, ret = -110 [ 544.560082] iwlagn 0000:02:00.0: Queue 9 stuck for 10000 ms. [ 544.560120] iwlagn 0000:02:00.0: On demand firmware reload [ 545.062107] ieee80211 phy0: Hardware restart was requested [ 546.665674] hrtimer: interrupt took 1100048021 ns ============================== I am not sure if it is significant that on all crashes the last sentence is the "hrtimer" interrupt sentence.
I'm not able to play the video, if there is a call trace, could you do a snapshot of it and attach image here? > [ 334.149668] wlan0: 00:0f:66:0a:2e:ba denied authentication (status 15) > [ 537.524129] iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after 500ms. > [ 537.524163] iwlagn 0000:02:00.0: set power fail, ret = -110 > [ 544.560082] iwlagn 0000:02:00.0: Queue 9 stuck for 10000 ms. > [ 544.560120] iwlagn 0000:02:00.0: On demand firmware reload That mean the iwlagn firmware hang, but this should not make kernel crash. > [ 546.665674] hrtimer: interrupt took 1100048021 ns That is indeed strange, I'm not sure what does it mean. Could you install kernel-debug and see if it print some other errors, call-traces, etc ...
There aren't call-traces on the video. Just the text that I attached on comment 10. In fact, the last line appears quite slowly (pixel line by pixel line) and then the screen blanks. Power is still on, but the screen is black. Tonight I'll install kernel-debug and see what happens. Do I need to set up any variable/command to make the additional error/call-traces appear with kernel-debug or it will just do it by default with "dmesg -n 8"? I've never used kernel-debug.
Call-traces are printed on the higher log level, so no special dmesg settings is needed, but "dmesg -n 8" is fine, it will unmask other prints, which could be informative.
Comment from the part of hrtimer_interrupt that emits the "hrtimer: interrupt took ... ns" message: * The next timer was already expired due to: * - tracing * - long lasting callbacks * - being scheduled away when running in a VM My guess is the "long lasting callback" option is the most likely. I just don't know which callback that might be... :-(
Just curious, could you try rebooting with "pci=nomsi" on the kernel command line? Does that happen to make any difference?
After that test, could you also try a reboot with "clocksource=tsc" on the kernel command line? Does that change anything?
success. I rebooted with pci=nomsi and the wireless lan started without crashing the system. I'll proceed to install kernel-debug and see what happens.
Ran the test without the pci=nomsi on the kernel-debug and the system crashed again. Here is the output: ====================== [ 116.555253] cfg80211: Calling CRDA to update world regulatory domain [ 116.679906] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d [ 116.679960] iwlagn: Copyright(c) 2003-2011 Intel Corporation [ 116.680902] iwlagn 0000:02:00.0: enabling device (0000 -> 0002) [ 116.681106] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 116.681426] iwlagn 0000:02:00.0: setting latency timer to 64 [ 116.681826] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0 [ 116.696329] cfg80211: World regulatory domain updated: [ 116.696383] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 116.696467] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 116.696504] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 116.696559] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 116.696608] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 116.696661] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 116.698817] iwlagn 0000:02:00.0: device EEPROM VER=0x716, CALIB=0x6 [ 116.698860] iwlagn 0000:02:00.0: Device SKU: 0Xb [ 116.698894] iwlagn 0000:02:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3 [ 116.699229] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 116.819601] iwlagn 0000:02:00.0: loaded firmware version 17.168.5.1 build 33993 [ 116.822616] Registered led device: phy0-led [ 116.879427] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 117.649033] hrtimer: interrupt took 699989972 ns =========================== I do not see any function call trace I am going to try using strace -vx modprobe iwlagn
Created attachment 532746 [details] trace file of iwlagn on kernel-debug The system crashed. Attached is the result of strace. This is the output of netconsole =============================== [ 700.575831] cfg80211: Calling CRDA to update world regulatory domain [ 700.754202] cfg80211: World regulatory domain updated: [ 700.754252] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 700.754305] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 700.754349] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 700.754392] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 700.754434] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 700.754477] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 700.809763] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d [ 700.809816] iwlagn: Copyright(c) 2003-2011 Intel Corporation [ 700.810948] iwlagn 0000:02:00.0: enabling device (0000 -> 0002) [ 700.811182] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 700.811507] iwlagn 0000:02:00.0: setting latency timer to 64 [ 700.811903] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0 [ 700.829945] iwlagn 0000:02:00.0: device EEPROM VER=0x716, CALIB=0x6 [ 700.829991] iwlagn 0000:02:00.0: Device SKU: 0Xb [ 700.830090] iwlagn 0000:02:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3 [ 700.830969] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 700.948709] iwlagn 0000:02:00.0: loaded firmware version 17.168.5.1 build 33993 [ 700.951871] Registered led device: phy0-led [ 701.012669] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 701.275215] cfg80211: Calling CRDA for country: PA [ 701.291832] cfg80211: Regulatory domain changed to country: PA [ 701.291851] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 701.291867] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 701.291884] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 701.291903] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm) [ 701.291921] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 704.022235] hrtimer: interrupt took 600006103 ns ===================================== Does it help? JP
tried on the regular kernel (not the debug version) with clocksource=tsc and it crashed again. Looks like the problem is solved with pci=nomsi This is the netconsole output: =============================== [ 236.844629] cfg80211: Calling CRDA to update world regulatory domain [ 236.929897] cfg80211: World regulatory domain updated: [ 236.930151] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 236.930424] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 236.930684] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 236.930938] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 236.931229] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 236.931488] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 236.963645] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d [ 236.963902] iwlagn: Copyright(c) 2003-2011 Intel Corporation [ 236.964375] iwlagn 0000:02:00.0: enabling device (0000 -> 0002) [ 236.964603] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 236.964887] iwlagn 0000:02:00.0: setting latency timer to 64 [ 236.965231] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0 [ 236.980465] iwlagn 0000:02:00.0: device EEPROM VER=0x716, CALIB=0x6 [ 236.980657] iwlagn 0000:02:00.0: Device SKU: 0Xb [ 236.980811] iwlagn 0000:02:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3 [ 236.981120] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [ 237.033789] iwlagn 0000:02:00.0: loaded firmware version 17.168.5.1 build 33993 [ 237.036304] Registered led device: phy0-led [ 237.075673] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 237.150250] cfg80211: Calling CRDA for country: PA [ 237.159655] cfg80211: Regulatory domain changed to country: PA [ 237.160285] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 237.161038] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 237.161779] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 237.162468] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm) [ 237.163227] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 237.537426] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 246.532085] iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after 500ms. [ 246.532363] iwlagn 0000:02:00.0: set power fail, ret = -110 [ 247.032092] iwlagn 0000:02:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms. [ 248.568094] iwlagn 0000:02:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms. [ 250.070094] iwlagn 0000:02:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms. [ 251.578087] iwlagn 0000:02:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms. [ 253.087089] iwlagn 0000:02:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms. [ 254.594091] iwlagn 0000:02:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms. [ 255.008081] iwlagn 0000:02:00.0: Queue 9 stuck for 10000 ms. [ 255.013696] iwlagn 0000:02:00.0: On demand firmware reload [ 255.529572] ieee80211 phy0: Hardware restart was requested
Interesting...it sounds like your box doesn't like MSI. Could you attach the output of running 'lspci -n'?
Started with pci=nomsi ... [root@scorpblue ~]# lspci -n 00:00.0 0600: 1002:5950 (rev 10) 00:01.0 0604: 1002:5a3f 00:04.0 0604: 1002:5a36 00:05.0 0604: 1002:5a37 00:06.0 0604: 1002:5a38 00:07.0 0604: 1002:5a39 00:12.0 0101: 1002:4379 (rev 80) 00:13.0 0c03: 1002:4374 (rev 80) 00:13.1 0c03: 1002:4375 (rev 80) 00:13.2 0c03: 1002:4373 (rev 80) 00:14.0 0c05: 1002:4372 (rev 83) 00:14.1 0101: 1002:4376 (rev 80) 00:14.2 0403: 1002:437b (rev 01) 00:14.3 0601: 1002:4377 (rev 80) 00:14.4 0604: 1002:4371 (rev 80) 00:18.0 0600: 1022:1100 00:18.1 0600: 1022:1101 00:18.2 0600: 1022:1102 00:18.3 0600: 1022:1103 01:05.0 0300: 1002:5975 02:00.0 0280: 8086:0091 (rev 34) 08:01.0 0607: 1524:1412 (rev 10) 08:01.1 0501: 1524:0530 (rev 01) 08:01.2 0805: 1524:0550 (rev 01) 08:01.3 0501: 1524:0520 (rev 01) 08:01.4 0501: 1524:0551 (rev 01) 08:02.0 0200: 10ec:8139 (rev 10)
I think it might be something with the intel 6230 card. The Habey HB-NB037H did not present any problem.
Are you still seeing this with 2.6.43/3.3?
I will have to check. I have been using the Habey HB-NB037H since then. Let me switch them back and try this weekend
Actually I upgraded the kernel I am still facing similar problems. I changed the cards and tried to boot and it froze. I could not even turn it on level 3 (adding a 3 at the end of the kernel invocation in grub2). I started the laptop with the live cd Fedora-16-i686-Live-XFCE.iso (downloaded Feb 2012 04:04:17 AM EST. ) and it came up but without the network. The reported kernel by the livecd is 3.1.0-7.fc16.i686 I cannot turn on the wifi. The kernel seems to see it but iwlagn shows a pci_enable_msi failed and ends with a probe failed with error -22. I am going to try and extract the /var/log/message from the hard disk and see if there is anything interesting and report later.
Created attachment 590854 [details] Var Log Message file rescued from the hard disk This the last /var/log/mesages It dies in the middle of Network Manager activating the wifi card. I remember seeing a black screeen with vertical, equally spaced white lines I was trying to go to level 3 instead of the graphic mode. Kernel command line: BOOT_IMAGE=/vmlinuz-3.3.7-1.fc16.i686 root=UUID=daa47c96-4e10-4413-9fe5-49b81097304b ro rd.md=0 rd.lvm=0 rd.dm=0 quiet SYSFONT=latarcyrheb-sun16 rd.luks=0 KEYTABLE=es LANG=en_US.UTF-8 selinux=0 3
Uploaded the /var/log/messages. The interesting and relevant parts are as follows (I think): Jun 10 20:33:47 scorpblue chronyd[991]: Linux kernel major=3 minor=3 patch=7 Jun 10 20:33:47 scorpblue kernel: [ 0.000000] Linux version 3.3.7-1.fc16.i686 (mockbuild.fedoraproject.org) (gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #1 SMP Tue May 22 14:14:30 UTC 2012 Jun 10 20:33:47 scorpblue kernel: [ 8.985452] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d Jun 10 20:33:47 scorpblue kernel: [ 8.985461] Copyright(c) 2003-2011 Intel Corporation Jun 10 20:33:47 scorpblue kernel: [ 8.985618] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002) Jun 10 20:33:47 scorpblue kernel: [ 8.985731] iwlwifi 0000:02:00.0: pci_resource_len = 0x00002000 Jun 10 20:33:47 scorpblue kernel: [ 8.985738] iwlwifi 0000:02:00.0: pci_resource_base = f7cdc000 Jun 10 20:33:47 scorpblue kernel: [ 8.985745] iwlwifi 0000:02:00.0: HW Revision ID = 0x34 Jun 10 20:33:47 scorpblue kernel: [ 8.985802] iwlwifi 0000:02:00.0: pci_enable_msi failed(0Xffffffea) Jun 10 20:33:47 scorpblue kernel: [ 8.986109] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG enabled Jun 10 20:33:47 scorpblue kernel: [ 8.990158] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS enabled Jun 10 20:33:47 scorpblue kernel: [ 8.990166] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled Jun 10 20:33:47 scorpblue kernel: [ 8.990172] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled Jun 10 20:33:47 scorpblue kernel: [ 8.990179] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_P2P disabled Jun 10 20:33:47 scorpblue kernel: [ 8.990214] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0 Jun 10 20:33:47 scorpblue kernel: [ 8.990336] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S Jun 10 20:33:47 scorpblue kernel: [ 9.005365] iwlwifi 0000:02:00.0: device EEPROM VER=0x716, CALIB=0x6 Jun 10 20:33:47 scorpblue kernel: [ 9.005372] iwlwifi 0000:02:00.0: Device SKU: 0x1F0 Jun 10 20:33:47 scorpblue kernel: [ 9.005379] iwlwifi 0000:02:00.0: Valid Tx ant: 0x3, Valid Rx ant: 0x3 Jun 10 20:33:47 scorpblue kernel: [ 9.005460] iwlwifi 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels Jun 10 20:33:47 scorpblue kernel: [ 9.119611] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-6000g2b-6.ucode' failed. Jun 10 20:33:47 scorpblue kernel: [ 9.371941] iwlwifi 0000:02:00.0: Firmware has old API version, expected v6, got v5. Jun 10 20:33:47 scorpblue kernel: [ 9.376388] iwlwifi 0000:02:00.0: New firmware can be obtained from http://www.intellinuxwireless.org/. Jun 10 20:33:47 scorpblue kernel: [ 9.380775] iwlwifi 0000:02:00.0: loaded firmware version 17.168.5.2 build 35905 Jun 10 20:33:47 scorpblue kernel: [ 9.619475] cfg80211: World regulatory domain updated: Jun 10 20:33:47 scorpblue kernel: [ 9.619486] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Jun 10 20:33:47 scorpblue kernel: [ 9.619496] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 10 20:33:47 scorpblue kernel: [ 9.619505] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Jun 10 20:33:47 scorpblue kernel: [ 9.619512] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Jun 10 20:33:47 scorpblue kernel: [ 9.619520] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 10 20:33:47 scorpblue kernel: [ 9.619528] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jun 10 20:33:47 scorpblue kernel: [ 10.320727] cfg80211: Calling CRDA for country: PA Jun 10 20:33:47 scorpblue kernel: [ 10.330505] cfg80211: Regulatory domain changed to country: PA Jun 10 20:33:47 scorpblue kernel: [ 10.330514] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Jun 10 20:33:47 scorpblue kernel: [ 10.330524] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) Jun 10 20:33:47 scorpblue kernel: [ 10.330533] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Jun 10 20:33:47 scorpblue kernel: [ 10.330541] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm) Jun 10 20:33:47 scorpblue kernel: [ 10.330548] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
What do you want me to do? I noticed the var log messages complaining about having old firmware on the card. Do you want me to upgrade it first and then we can run all the battery of tests (if needed) with the new firmware? Or should I try right now fiddling with the pci=nomsi, tsc, lspci stuff? Let me know JP
I went ahead and tried pci=nomsi and it is working fine. I haven't changed the firmware yet. I'll upload /var/log/messages, dmesg and boot.log lspci -n looks the same to me. /var/log/messages is a lot more detailed. It seems to have kept the debug levels we used last time.
Created attachment 590869 [details] detailed var log messages with debug info. system is working after applying pci=nomsi to the grub2 entry Not sure if anything is not working yet.
Created attachment 590870 [details] boot log. Did not see anything interesting here, just for completeness sake
Created attachment 590872 [details] dmesg file. not sure if it is helpful, but for completeness sake
system seems to be working now, not sure if you want to run any kind of additional test, or propose any change.. Please let me know JP
Fedora 15 has reached it's end of life as of June 26, 2012. As a result, we will not be fixing any remaining bugs found in Fedora 15. In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. Thank you for taking the time to file a report. We hope newer versions of Fedora suit your needs.