Created attachment 438795 [details] Message Log Description of problem: Fedora 13 randomly freezing on Dell Studio 1558, no matter with radeon or catalyst 10.7 from rpmfusion. Normally it happens in low system usage time within 30 minutes after starting. Version-Release number of selected component (if applicable): kernel-PAE-2.6.33.6-147.2.4.fc13.i686 kernel-PAE-2.6.34.3-37.fc13.i686 How reproducible: Randomly freezing, but it seems to be more likely to happen within 30 mins after starting. In most of the cases, the freezing happens when system is in a low usage status (browsing text only forum) or left idle. Never freeze when using multi application or in heavy usage status: 4 hour HD video playback, constant 3D video game playing, overnight P2P sharing, running multi VirtualBox instances. Steps to Reproduce: 1. Start the system. 2. Left it idle. 3. Freezing at random time within 30 min. Actual results: Completely freezing. No input were accepted from keyboard, mouse. Ad-hoc network was terminated, too. Expected results: No freezing if left idle. Additional info: Freezing happens on the following time in /var/log/message: Aug 11 15:53:50 (with radeon driver, the rest are with catalyst rpmfusion) Aug 11 23:32:40 Aug 12 21:58:31 Aug 14 07:15:28 Aug 14 07:24:34 Aug 14 09:51:18 Aug 14 13:46:18 Aug 14 13:50:51 Aug 14 13:53:2Aug 14 13:56:32 (happened during when logging) I know it's really weird but it's 100% reproducible on this Dell Studio 1558. Then only way I can do to prevent it from freezing is trying to do something in the first 30 min. Launching IM or transmission is enough. Google said it might happened on BIOS version before A04. But mine is A06. BIOS version : A06 BIOS release date: 05/27/2010 Ubuntu 10.04 with 2.6.32 kernel on the same machine doesn't seem to have this issue.
Just noticed the bug 607737: https://bugzilla.redhat.com/show_bug.cgi?id=607737 Similar but no graphic related report were noticed before crash.
Created attachment 442479 [details] sosreport fedora 13 x64 on dell studio 1558 I have de same problem "Randomly freezing on Dell Studio 1558" but my kernel is x64 uname -a Linux lacar 2.6.33.8-149.fc13.x86_64 #1 SMP Tue Aug 17 22:53:15 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux I am attaching a sosreport, just in case it helps!
Does it still happen with the released kernel-2.6.34.6-47?
Still freezing with 2.6.34.6-47 [marco@lacar ~]$ uname -a Linux lacar 2.6.34.6-47.fc13.x86_64 #1 SMP Fri Aug 27 08:56:01 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux Is there any way to force a kernel dump ones the system has freezed? so I can send you the dump...
Please configure kdump http://fedoraproject.org/wiki/Kernel/kdump . Kernel should dump memory when system hangs (if NMI watchdog works). Then get logs from memory dump using "crash" tool and attach them here (don't delete vmcore file, can be useful).
I configure kdump and I enabled nmi at boot time in grub, I can force a dump when the system is not hang, but when the system is freezed nothing happend..... I do not know what else can I do.... Any advice? ..
If you have second computer you can configure netconsole https://fedoraproject.org/wiki/Netconsole to dump kernel massages. Or configure serial console if you have cable and connectors.
When system freeze does diodes on the laptop blink? (In reply to comment #6) > I configure kdump and I enabled nmi at boot time in grub, Does /proc/interrupt shows the NMI works? > I can force a dump > when the system is not hang, but when the system is freezed nothing > happend..... Did you tried to use SysRq magic key?
Hi, Yes I have try the magic keys several times and in /proc/interrupts I can see that NMI row shows numbers.... I have noticed that if I do not use any usb device I just plug a network cable I takes longer to frezze but in this Notebook lots of internal devices are usb, webcam, bluetooth, Wireless, etc... How can I make NMI to work apropriately??? Thanks, regards.
Can you 'cat /proc/cmdline' for me so I can see how you enabled nmi. Also can you run the following commands to check the NMI grep NMI /proc/interrupts dd if=/dev/urandom bs=1k count=16000 2>/dev/null | bzip2 >/dev/null grep NMI /proc/interrupts the numbers should have changed but as far as i know, the nmi watchdog doesn't work to well on 2.6.34 or earlier kernels. oddly, I would have expected false positives which you are not getting, so now I am curious. Cheers, Don
These are the outputs: [marco@lacar ~]$ cat /proc/cmdline ro root=/dev/mapper/vg_lacar-lv_root rd_LVM_LV=vg_lacar/lv_root rd_LVM_LV=vg_lacar/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=la-latin1 rhgb quiet nmi_watchdog=1 crashkernel=128M [marco@lacar ~]$ grep NMI /proc/interrupts NMI: 242801 242606 242514 242422 Non-maskable interrupts [marco@lacar ~]$ dd if=/dev/urandom bs=1k count=16000 2> /dev/null | bzip2 > /dev/null [marco@lacar ~]$ grep NMI /proc/interrupts NMI: 307885 307690 307598 307506 Non-maskable interrupts [marco@lacar ~]$ Thanks, Regards, Marco.
Marco, Thanks for the info. I am not sure how well nmi_watchdog=1 works, but nmi_watchdog=2 should work if you switch the clock source to tsc. Can you modify/add the following to your boot args in grub nmi_watchdog=2 clocksource=tsc also I will need the output from 'dmesg', if that is possible. Thanks, Don
Hi Don, I have modified the config: [marco@lacar ~]$ cat /proc/cmdline ro root=/dev/mapper/vg_lacar-lv_root rd_LVM_LV=vg_lacar/lv_root rd_LVM_LV=vg_lacar/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=la-latin1 rhgb quiet nmi_watchdog=2 clocksource=tsc crashkernel=128M acpi=off but the dump with nmi is still not working...when frezzed and nothing is wrote to the /var/log/messages... Any other possibility? Thanks Regards. Marco.
Sounds like the kernel is fine but userspace is hung. Usually sysRq is the way to go by dumping the tasks. Are you sure it is enabled? "echo 1 > /proc/sys/kernel/sysrq" And you said you can't ping the box once it is hung right? Cheers, Don
Yes it is enabled # cat /proc/sys/kernel/sysrq 1 If I do # echo c > /proc/sysrq-trigger panic and dump the memory... I also test the magic keys and they work if it is not freeze. And the system does not respond to ping once freezed. Thanks, Regards, Marco
I assume your laptop doesn't have a serial port. It would be nice to see if the kernel is displaying anything interesting. One possibility is that X is hung, though that should still allow the magic keys to work.. Does the machine work if you only boot to runlevel 3? (just '3' on the kernel commandline or in grub.conf). Also could you set 'softlockup_panic=1' and 'nmi_watchdog=panic,2' on the kernel commandline too. I figure either nmi watchdog or softlockup watchdog would go off if the machine is hanging. Both those options above should cause the kernel to panic, which you will hopefully see because some lights will flash on the keyboard. Cheers, Don
Hi Don, Not only the magic keys does not work when it is freeze but also the system does not respond to ping.... About runlevel 3 it is difficult to tell because the freeze is not alway fast some times it takes longer to freeze... but I can try to see if it is related to X. I will try to add softlockup_panic=1 and nmi_watchdog=panic,2 rigth away! Should I leave the option clocksource=tsc ? Do you know where can I find information about these kinds of kernel options? Is there a good paper to read? Thanks! Regards. Marco
I've tried the system in runlevel 3 and It frezze again with "softlockup_panic=1 and nmi_watchdog=panic,2" either.... I do not know what else to do, I can not go on with the system hanging every time.... I will have to change fedora for other distro. Help... Thanks, Regards, Marco.
How long did you wait after the freeze for the machine to panic? You will probably have to wait at least 3 minutes just to be sure. Assuming you don't see the panic after 3 minutes, I am running out of ideas. So, the lockup detectors are not working to panic the box, the magic sysrq key sequences do not work to panic the box, you are not using X in initlevel 3, and you can't ping the box once it is frozen. :-( Ok, a colleague of mine is suggesting the GPU power management might be screwing things up. Can you try booting with 'nomodeset' to run the video drivers in legacy mode? Cheers, Don
Thanks Don, I add nomodeset to kernel parameters, then start x by hand (startx) and about an hour later the system frezzed.... So nomodeset did not help.... Do you know if there is a way to start the linux kernel with a debugger?? For example in Solaris you could start solaris with a debugger and when the kernel frezze you could tell the debugger to save the dump with a key sequence... So you do not depend on Hardware to panic the system. Thanks, Regards. Marco
Don Thanks for your help, I will wait until Fedora 14 is released and if Fedoara 14 does not fix the problem I will install other distro, but I can not continue with a system that hungs several times a day. Regards. Marco.
(In reply to comment #20) > Thanks Don, > > I add nomodeset to kernel parameters, then start x by hand (startx) and about > an hour later the system frezzed.... So nomodeset did not help.... does the problem still happen without starting X? > > Do you know if there is a way to start the linux kernel with a debugger?? For > example in Solaris you could start solaris with a debugger and when the kernel > frezze you could tell the debugger to save the dump with a key sequence... > So you do not depend on Hardware to panic the system. well linux can do that to with the alt-sysrq key sequence, but you said that was not working for you. Cheers, Don
I did not try without X and nomodeset but without nomodeset in runlevel 3 it has frezzed without X. I am waiting for Fedora 14, last chance before installing Ubuntu. Regards. Marco
Hi. I'd like to add my own comments. I bought the Studio 1558 in April 2010. I deleted the Windows 7 partition, and re-partitioned it so that I had Windows 7, a MBR grub boot partition, 4 linux "/boot and /" partitions, 4GB swap, a 10GB NTFS partition for backup stuff for windows to use, and the remainder as a linux partition (about 300GB). I reinstalled Windows 7 from the supplied DVD though had to download drivers from Dell. Windows 7 has NEVER froze or crashed on this laptop. The initial install of Fedora 12 64 bit froze during the GUI install, several times. I was finally able to install it in text mode after several attempts. Once installed, it would freeze from time to time, I had to hit the power button to kill it. There was no pattern to the freeze, sometime it was in "mid type" or "mouse move", other times it would freeze while just sitting there. Fedora 13 installed fine, so freezes during the process in GUI mode. But again, it would freeze at odd times. A pattern did develop, it seemed to freeze about 3 minutes after logging in following the first boot of the day. I would power off the back on again, and it would stay up the rest of the day. Often, it would stay running overnight without problem. I installed Fedora 14 last night. The installation and patching to current was perfect, no freezes. I suspected it might be the Broadcom wireless driver so I deliberately did not install it. I left it running overnight, this morning it had frozen. The hourly cronlog showed the last successful run at 2am. I installed the Broadcom driver this morning, the laptop has frozen 3 times this morning already. I am typing this message on it now, it's stayed up for 30 minutes so far. Due to the multi boot nature of the laptop, I have the old Fedora 12 and 13 still available. I have upgraded the BIOS as Dell puts out new ones, it obviously has not helped. If I can help to debug this, I'd be happy to. I've used every version of Fedora since Core 1 came out and usually install it the day it is released. I have Fedora running on 6 computers at home and work. I support 200 Red Hat servers at work. I got my first RHCE in 2001. I used to teach the RHCE classes. In other words, I'm not a novice.
Hi I am having the same issue, but I am using Ubuntu. The reason I am posting this comment is that I read one of the first comments, where it said it was not happening on 10.04, I have 10.10 Maverick and symptoms are similar. I hope this post heps. Computer freezes mostly when I am using firefox (even while I am typing) and using virtualbox. Although I was able to watch videos on firefox for hours. And it does not happen when I am watching videos using mplayer. This is actually the third time I try to send this message. uname -a Linux vbendiglaptop 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux The laptop is a dell 1558 purchased in September 2010. Let me know if you need more info on the system. I would be glad to help since there seems to be something that affects at least this two distros.
Hi, I just ran into another bug report https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/662998 Seems that the power management options in the "On Battery" section is causing this issue. I put all options to "never" and unchecked "spin down hard disks when possible" option. Problem seems to be solved , the computer just keeps running without problems. Regards, Victor
I checked my PowerSave settings, I already was set to "never". Plus, I never run on battery. The freezes have always happened on A/C power. I had been running fairly well, but for some reason the laptop froze 5 times this evening, all within 1 minute of logging in, all within a 10 minute timeframe. However, it has now been up for 5 minutes, allowing me to type this. Clearly there is a problem with Linux and the 1558. Apparently other distros are suffering too. Dell and Microsoft appear to have resolved it, as Windows 7 Home Premium 64 bit (the OS that came with the laptop) has never frozen. Not once. My research indicates that Windows used to freeze on this laptop with the earlier versions of the BIOS. I have the most current BIOS installed. I'm positive that it's a software issue, not a hardware failure.
2.6.35.9-61.rc1.fc14.i686 seems to be working fine here, I get it from http://kojipkgs.fedoraproject.org/packages/kernel/2.6.35.9/61.rc1.fc14/i686/ No hangs, no screen flickerings https://bugzilla.redhat.com/show_bug.cgi?id=585673 My smolt profile, http://www.smolts.org/client/show/pub_2f86caf1-da4a-45a1-b299-a583eb693301 Current uptime, 16:24:28 up 1:20, 5 users, load average: 0.65, 0.77, 0.73
Just an illusion... frozen two hours later...
Having dmesg with call trace would be really helpful to solve this problem ... Maybe problem happens because bug in some module, try to blacklist dell_wmi and wmi modules and see if that help. If not see lsmod output and try blacklist other non vital modules that possibly are dell specific.
Gash, I did not note this before but logs attached to this bugzilla have entries from proprietary broadcom wireless driver (ok it is now open source but still in staging, not shipped with official fedora). It is my first suspicious that cause troubles here. Please check if system still hangs without wireless driver.
It hangs a few times with F14 live (no prop. driver there)... so doesn't seems like a broadcom bug... but under heavy wifi load things get worst... for example download a torrent is almost a death certificate, just a few minutes and my system hangs... I'll try blacklisting wmi modules... BTW,I have a kernel than never hangs, http://kojipkgs.fedoraproject.org/packages/kernel/2.6.35.4/14.fc14/i686/ ...but surprise... I can't get the wl driver working in that kernel... akmod just give me some errors at compile time... anyway I insist, there are some broadcomless kernels than hangs...
uname -r 2.6.35.9-61.rc1.fc14.i686 uptime 03:04:43 up 10:52, 9 users, load average: 2.31, 1.77, 1.63 wmi modules blacklisted, broadcom drivers removed... heavy net and cpu usage... still running!
On Dell Inspiron 9100 with Mobility Radeon 9600 M10: Last working kernel 2.6.33.8-149. Anything newer freezes X when any significant screen activity (firefox or even evolution) is introduced. Definitely radeon is not working in 2.6.34 on this hardware. FWIW once I had the music on when tested new kernel out of latest (as of today) 2.6.34 series. "Broken record" playback continued for several cycles then stopped. Fan speed goes up shortly after the freeze. Haven't tried configuring kdump yet. It may indicate that something is still running. I have another radeon based dell inspiron 1501 which experienced same freezes (firefox or evolution) with different kernels. Right now running F14 with no problems. Will F14 kernel work in F13?
There are many reports of it working, but I don't want to say definitively that it will. :) Please test it and let us know. --Kyle
I have a new Dell Studio 1558 and I'm experience freezing too. Usually once or twice a day but occasionally it will freeze repeatedly within a few minutes of booting. After searching, I found a lengthy thread on the Dell support forum about this issue: http://en.community.dell.com/support-forums/laptop/f/3519/t/19335401.aspx The short version is that it seems to affect 64 bit Windows and Linux but not 32 bit. It's reported more frequently on the i7 boards than the i5 and i3 (I have an i3 though and have experience freezing). There was some indication this might be related to an overheating problem but nobody seemed to know for sure. There definitely are temp issues on this laptop with Fedora. The fan runs at high speed constantly instead of varying with the temperature like it does on Windows. Also, the GNOME sensors applet report two temps via ACPI: TZ01 CPU which is always 0C and TZ02 CPU which is always 27C. I'm guessing one is actually the CPU and the other is the ATI chip? But neither seems to be reporting a real temp. Anyway, if I can contribute any hardware info that might help solve this, I'm happy to do so.
After upgrading my F13 environment kernel to the latest from Fedora 14 my inspiron 9100 only experienced a lockup once during 5 weeks period. The radeon (or other unknown to me) driver responsible for lockups is definitely better in Fedora 14 kernel.
(In reply to comment #36) > I have a new Dell Studio 1558 and I'm experience freezing too. Usually once or > twice a day but occasionally it will freeze repeatedly within a few minutes of > booting. Blacklisting modules as notice in comments 31 - 33 does not help?
(In reply to comment #38) > (In reply to comment #36) > > I have a new Dell Studio 1558 and I'm experience freezing too. Usually once or > > twice a day but occasionally it will freeze repeatedly within a few minutes of > > booting. > > Blacklisting modules as notice in comments 31 - 33 does not help? My unit came with the Intel 6200 option rather than the broadcom wireless hardware. So I think those modules don't apply. Or maybe I'm wrong? Here's the output of lsmod: Module Size Used by fuse 61443 3 sunrpc 201180 1 cpufreq_ondemand 9278 4 acpi_cpufreq 7345 1 freq_table 3955 2 cpufreq_ondemand,acpi_cpufreq mperf 1481 1 acpi_cpufreq nf_conntrack_netbios_ns 1574 0 ip6t_REJECT 4279 2 nf_conntrack_ipv6 18078 8 ip6table_filter 1687 1 ip6_tables 17481 1 ip6table_filter ipv6 286354 42 ip6t_REJECT,nf_conntrack_ipv6 uinput 7368 0 snd_hda_codec_atihdmi 2727 1 snd_hda_codec_idt 55722 1 snd_hda_intel 24447 2 arc4 1449 2 ecb 2119 2 snd_hda_codec 86743 3 snd_hda_codec_atihdmi,snd_hda_codec_idt,snd_hda_intel snd_hwdep 6392 1 snd_hda_codec snd_seq 53791 0 snd_seq_device 6191 1 snd_seq snd_pcm 80190 2 snd_hda_intel,snd_hda_codec uvcvideo 55654 0 videodev 65053 1 uvcvideo iwlagn 208939 0 v4l1_compat 12986 2 uvcvideo,videodev iwlcore 195683 1 iwlagn i2c_i801 11088 0 snd_timer 19892 2 snd_seq,snd_pcm dell_wmi 3323 0 mac80211 229015 2 iwlagn,iwlcore v4l2_compat_ioctl32 9622 1 videodev cfg80211 134933 3 iwlagn,iwlcore,mac80211 wmi 8138 1 dell_wmi dell_laptop 6477 0 snd 63984 12 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer rfkill 17622 3 cfg80211,dell_laptop r8169 37411 0 iTCO_wdt 11256 0 iTCO_vendor_support 2610 1 iTCO_wdt mii 4310 1 r8169 soundcore 6576 1 snd snd_page_alloc 7559 2 snd_hda_intel,snd_pcm joydev 9785 0 dcdbas 8524 1 dell_laptop microcode 18548 0 sdhci_pci 7871 0 sdhci 18464 1 sdhci_pci firewire_ohci 21314 0 mmc_core 64193 1 sdhci firewire_core 45817 1 firewire_ohci crc_itu_t 1563 1 firewire_core video 21637 0 output 2253 1 video radeon 637441 3 ttm 55166 1 radeon drm_kms_helper 25961 1 radeon drm 178062 5 radeon,ttm,drm_kms_helper i2c_algo_bit 5205 1 radeon i2c_core 26900 6 videodev,i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit
(In reply to comment #39) > > Blacklisting modules as notice in comments 31 - 33 does not help? > > My unit came with the Intel 6200 option rather than the broadcom wireless > hardware. So I think those modules don't apply. Or maybe I'm wrong? bcm80211 module does not apply, Intel wireless device is handled by iwlagn and iwlcore modules, they should not hang the system Try to blacklist dell_wmi and wmi ?
Good news everyone. I was going back over the list of things I'd tried and noticed that the BIOS on my Dell 1558 was still showing the old version. My attempt to upgrade it apparently didn't work. I tried a second time and verified that the BIOS did actually get upgraded to the latest version and, since then, I've gone several days without any freezes at all. If I get another freeze I'll try blacklisting the dell_wmi module and report back.
I just updated to the last (A11) bios version, and still got random freezes...
tried also with removed dell_wmi module (with rmmod, not with blacklisting) and got a freeze few minutes later...
Perhaps need to remove wmi module as well. Do you have broadcom wifi ?
yes, i have a broadcom wifi. I'm trying with adding pcie_aspm=off in the /boot/grub/menu.lst file. seen at comment 76 : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/656745 I made a full hardware test with the dell support, and it doesn't detect any problem at all.
I add some informations : distro : Fedora 14 uname -a: Linux hostname 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux lspci : 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11) 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11) 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11) 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11) 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11) 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11) 00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11) 00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06) 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06) 02:00.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series] 02:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series] 04:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) 07:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) 07:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01) 07:00.2 System peripheral: Ricoh Co Ltd Device e852 (rev 01) 07:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04) ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04) ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04) ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04) ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04) ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04) ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04) ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04) ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04) ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04) ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04) ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04) Bios version : A11 dell_wmi loaded trying the kernel parameter : pcie_aspm=off waiting for freeze.
> 04:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) Try to blacklist also brcm80211 module, if you have it.
lsmod | grep brcm : nothing i use wl and lib80211 from the broadcom-wl package in rpmfusion (proprietary driver, right ?). Peoples have that bug with intel wifi, but i will try to blacklist it if i get a freeze with aspm off.
I thought the BIOS update had fixed the freeze problem for me but it started again like crazy last night. It was freezing within minutes of boot up almost every time. I had been trying to use bittorrent when the freezes started and when I shut down bittorrent Fedora seemed to become stable again, so that might lend credence to the idea that the freezes are related to a bug in the wifi driver. Or it could be coincidence, who knows... :( According to the specs, my 1558 has the "Intel Centrino Advanced-N 6200" wireless adapter. Lsmod shows iwlagn and iwlcore
One day without freeze. quote : "The Active State Power Management (ASPM) driver pcie_aspm in the default mode appears to be picking up the configuation from the BIOS default, which seems to be causing issues on this particular Vostro. I suggest as a workaround disabling PCIe ASPM with the kernel parameter: pcie_aspm=off " i use dell 1558 laptop A11 bios version with the following and i think this time the bug is gone : lsmod : Module Size Used by michael_mic 2122 4 arc4 1449 2 ecb 2119 2 fuse 61667 3 sunrpc 201276 1 cpufreq_ondemand 9278 8 acpi_cpufreq 7345 1 freq_table 3955 2 cpufreq_ondemand,acpi_cpufreq mperf 1481 1 acpi_cpufreq ip6t_REJECT 4279 2 nf_conntrack_ipv6 18078 9 ip6table_filter 1687 1 ip6_tables 17481 1 ip6table_filter ipv6 286354 70 ip6t_REJECT,nf_conntrack_ipv6 uinput 7368 0 snd_hda_codec_atihdmi 2727 1 snd_hda_codec_idt 55722 1 lib80211_crypt_tkip 7987 0 snd_hda_intel 24479 2 fglrx 2560199 87 snd_hda_codec 86743 3 snd_hda_codec_atihdmi,snd_hda_codec_idt,snd_hda_intel snd_hwdep 6392 1 snd_hda_codec wl 2555141 0 snd_seq 53791 0 snd_seq_device 6191 1 snd_seq uvcvideo 56073 0 snd_pcm 80190 2 snd_hda_intel,snd_hda_codec videodev 69118 1 uvcvideo r8169 37411 0 v4l2_compat_ioctl32 7665 1 videodev btusb 15514 0 iTCO_wdt 11256 0 bluetooth 89276 1 btusb snd_timer 19892 2 snd_seq,snd_pcm dell_laptop 6477 0 snd 63984 12 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer i7core_edac 16210 0 iTCO_vendor_support 2610 1 iTCO_wdt rfkill 17622 2 bluetooth,dell_laptop soundcore 6576 1 snd dell_wmi 3323 0 edac_core 41336 1 i7core_edac lib80211 5095 2 lib80211_crypt_tkip,wl mii 4310 1 r8169 joydev 9785 0 wmi 8138 1 dell_wmi snd_page_alloc 7559 2 snd_hda_intel,snd_pcm i2c_i801 11088 0 microcode 18500 0 dcdbas 8524 1 dell_laptop cryptd 7111 0 aes_x86_64 7758 2 aes_generic 26908 1 aes_x86_64 xts 2530 1 gf128mul 7668 1 xts dm_crypt 11755 1 sdhci_pci 7871 0 sdhci 18464 1 sdhci_pci firewire_ohci 21314 0 firewire_core 45817 1 firewire_ohci mmc_core 64193 1 sdhci crc_itu_t 1563 1 firewire_core video 21637 0 output 2253 1 video radeon 637424 0 ttm 55166 1 radeon drm_kms_helper 25961 1 radeon drm 178014 3 radeon,ttm,drm_kms_helper i2c_algo_bit 5205 1 radeon i2c_core 27089 6 videodev,i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit ------------------------------------------- cat blacklist.conf : # # Listing a module here prevents the hotplug scripts from loading it. # Usually that'd be so that some other driver will bind it instead, # no matter which driver happens to get probed first. Sometimes user # mode tools can also control driver binding. # # Syntax: see modprobe.conf(5). # # watchdog drivers blacklist i8xx_tco # framebuffer drivers blacklist aty128fb blacklist atyfb blacklist radeonfb blacklist i810fb blacklist cirrusfb blacklist intelfb blacklist kyrofb blacklist i2c-matroxfb blacklist hgafb blacklist nvidiafb blacklist rivafb blacklist savagefb blacklist sstfb blacklist neofb blacklist tridentfb blacklist tdfxfb blacklist virgefb blacklist vga16fb blacklist viafb # ISDN - see bugs 154799, 159068 blacklist hisax blacklist hisax_fcpcipnp # sound drivers blacklist snd-pcsp # I/O dynamic configuration support for s390x (bz #563228) blacklist chsc_sch -------------------------------- /boot/grub/menu.lst : # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/mapper/vg_rebel-lv_root # initrd /initrd-[generic-]version.img #boot=/dev/sda default=0 timeout=0 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu #waiting for freeze : title Fedora (2.6.35.11-83.fc14.x86_64) root (hd0,0) kernel /vmlinuz-2.6.35.11-83.fc14.x86_64 ro root=/dev/mapper/vg_rebel-lv_root rd_LUKS_UUID=luks-XXX-XXX rd_LVM_LV=vg_rebel/lv_root rd_LVM_LV=vg_rebel/lv_swap rd_NO_MD rd_NO_DM LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=fr-latin9 rhgb quiet radeon.modeset=0 pcie_aspm=off initrd /initramfs-2.6.35.11-83.fc14.x86_64.img #random freeze : title Fedora (2.6.35.10-74.fc14.x86_64) root (hd0,0) kernel /vmlinuz-2.6.35.10-74.fc14.x86_64 ro root=/dev/mapper/vg_rebel-lv_root rd_LUKS_UUID=luks-XXX-XXX rd_LVM_LV=vg_rebel/lv_root rd_LVM_LV=vg_rebel/lv_swap rd_NO_MD rd_NO_DM LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=fr-latin9 rhgb quiet radeon.modeset=0 initrd /initramfs-2.6.35.10-74.fc14.x86_64.img title Fedora (2.6.35.6-45.fc14.x86_64) root (hd0,0) kernel /vmlinuz-2.6.35.6-45.fc14.x86_64 ro root=/dev/mapper/vg_rebel-lv_root rd_LUKS_UUID=luks-XXX-XXX rd_LVM_LV=vg_rebel/lv_root rd_LVM_LV=vg_rebel/lv_swap rd_NO_MD rd_NO_DM LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=fr-latin9 rhgb quiet initrd /initramfs-2.6.35.6-45.fc14.x86_64.img
I tried the workaround suggested by Siegfried Chaisson - boot with kernel parameter "pcie_aspm=off". My 1558 (BIOS A11, Broadcom Wireless) has not crashed since I did it. It stayed up for 47 hours. I shut it down, let it sit for 4 hours, then rebooted. It has been up for 12 hours and counting following this second reboot. This is the most stable it has been since I bought it almost a year ago. I am very optimistic that this is the workaround we need until a fix is developed. Thanks Siegfried.
It would be great if you could test the Fedora 15 Alpha liveCD (or the forthcoming Beta, which should have yet another ASPM fix.)
I installed the Fedora 15 Alpha ISO last night, and patched to current levels. I have made no changes to kernel boot parameters, it is running as set by the installer. I encountered no freezes during the installation, no freezes during the patching, and no freezes since the reboot following patching. I will continue to monitor for a few more days. [root@localhost log]# date Sat Mar 12 17:27:55 EST 2011 [root@localhost log]# uname -a Linux localhost.localdomain 2.6.38-0.rc8.git0.1.fc15.x86_64 #1 SMP Tue Mar 8 08:22:15 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux [root@localhost log]# uptime 17:27:59 up 18:13, 4 users, load average: 1.02, 1.08, 1.07 [root@localhost log]#
The laptop has been running without problem with the F15 patched Alpha for almost 3 days. I am going to shut it down now to go back to my regular F14 system. [root@localhost log]# uname -a Linux localhost.localdomain 2.6.38-0.rc8.git0.1.fc15.x86_64 #1 SMP Tue Mar 8 08:22:15 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux [root@localhost log]# uptime 18:11:09 up 2 days, 17:56, 4 users, load average: 1.04, 1.03, 1.05 [root@localhost log]# I still have the F15 system on my laptop (multi boot environment), so can test further if needed.
After my last freeze, I decided to try the pcie_aspm=off fix and that appears to have finally done it. With that parameter in place I've had no freezes for over a week. If I remove, I can usually get a freeze within a few hours. So at this point I'm convinced that's where the bug lives. I'm wondering how to proceed at this point to help find a fix for the bug. Should a bug report be filed upstream somewhere against "pcie_aspm"? Is there any further hardware information I can provide that might help isolate the problem in pcie_aspm?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Not freezing on f15...
I concur with Juan. I have had no crashes under Fedora 15 either. I have NOT made the pcie_aspm=off change required for f14, it is running as generated by the installer.