FS#22714 - [kernel: 2.6.37-5] Freeze/Crash with Kernel 2.6.37
Attached to Project:
Arch Linux
Opened by Ben Mehne (ben0mega) - Wednesday, 02 February 2011, 04:15 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 15 February 2012, 08:07 GMT
Opened by Ben Mehne (ben0mega) - Wednesday, 02 February 2011, 04:15 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 15 February 2012, 08:07 GMT
|
Details
Description: Crash (no response via any key-combo nor via
cap lock).
I believe it was caused by the following bug (warning) in the kernel (could be unrelated, but it seems most likely) The attached log is the last of many such traces. Additional info: * latest Steps to reproduce: Run computer for a period of time - crash (no known immediate precipitating agent) Unloading btusb, bluetooth increases the time before a crash but does not stop it. xorg becomes the top process before a crash/freeze (any logs available on request) (22701 is a duplicate of this under the wrong severity level) |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 15 February 2012, 08:07 GMT
Reason for closing: Upstream
Wednesday, 15 February 2012, 08:07 GMT
Reason for closing: Upstream
The freezes began with the update to the 2.6.37-5 kernel and occur at unpredictable intervals, but as often as 5 times a day.
Downgrading to binutils 2.20 for the kernel build fixed this for me.
If this isn't an option, you might try and temporarily adjust arch/x86/boot/relocs.c to include "jiffies" in rel_sym_regex, i.e. make it "(^_end$|^jiffies$)".
Hope this helps.
'Tainted: P WC'
First, 'W' means that you had a warning before, you should try to find the first one that occurs (without 'Tainted: W') in order to allow finding the problem.
Second, P means 'proprietary'. You have a non-GPL kernel module (nvidia in both cases) loaded. While this hasn't been causing problems as long as I can remember, nobody in the kernel developer land will help you unless you can reproduce the problem without a 'P' taint.
Third, C means 'crap' - a staging driver is loaded, in both cases brcm80211. Staging drivers are not well-tested and likely unstable, so they are the first suspects when considering potential bugs. Your warnings occured in mac80211 somewhere, so they are with high probability connected to brcm80211. If your crashes are also related to that is unknown to me, but it is the best suspect.
config:# CONFIG_RELOCATABLE is not set
config.x86_64:# CONFIG_RELOCATABLE is not set
But if wanted I could update the binutils package to include the fix for that issue just to be double sure...
kernel_log (241.5 KiB)
I've attached my everything.log excerpt for the cpudynd segfault
pc: amd athlon 64 x2 dual core 4400+, amd 5770 graphics card running with the latest catalyst
I'm attaching my kernel.log file in case it provides any relevant information.
PS: Toward the end there is an issue with iwlagn. This is an open issue I have with compat-wireless that doesn't load the module properly. This has been reported and does not cause any kernel panic.
/etc/init.d/networkmanager stop
rmmod brcm80211
rmmod mac80211
rmmod cfg80211
rmmod rfkill
sleep 2
modprobe rfkill
modprobe cfg80211
modprobe mac80211
modprobe brcm80211
sleep 2
/etc/init.d/networkmanager start
though not always and often the problem comes back soon after. Still getting the same logged errors though. I would switch to nouveau to help but it plays merry havoc with my screen resolution and, as this is my work machine, I'm a little hesitant about losing the graphical desktop for a few days.
Don't know if this will help anyone or narrow down the issue, but there it is :)
------------[ cut here ]------------
Feb 19 18:27:29 SilverLeaf kernel: WARNING: at net/mac80211/rx.c:2860 ieee80211_rx+0x32e/0x8b0 [mac80211]()
Feb 19 18:27:29 SilverLeaf kernel: Hardware name: MacBookPro6,2
Feb 19 18:27:29 SilverLeaf kernel: Modules linked in: arc4 ecb brcm80211(C) mac80211 cfg80211 hidp ipv6 rfcomm sco bnep l2cap snd_hda_codec_hdmi btusb bluetooth rfkill hid_apple uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 uas usbhid bcm5974 hid usb_storage snd_seq_dummy snd_hda_codec_cirrus snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device joydev nouveau ttm drm_kms_helper snd_hda_intel snd_pcm_oss drm firewire_ohci tg3 snd_hda_codec snd_hwdep applesmc snd_pcm firewire_core i2c_i801 i2c_algo_bit snd_mixer_oss video uhci_hcd libphy ehci_hcd crc_itu_t usbcore input_polldev snd_timer i2c_core shpchp pci_hotplug output evdev sg snd ac battery button soundcore snd_page_alloc processor pcspkr intel_agp intel_gtt iTCO_wdt iTCO_vendor_support intel_ips tpm_tis tpm tpm_bios fuse ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ata_piix pata_acpi libata scsi_mod
Feb 19 18:27:29 SilverLeaf kernel: Pid: 0, comm: kworker/0:0 Tainted: G WC 2.6.37-ARCH #1
Feb 19 18:27:29 SilverLeaf kernel: Call Trace:
Feb 19 18:27:29 SilverLeaf kernel: <IRQ> [<ffffffff8105683a>] warn_slowpath_common+0x7a/0xb0
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff81056885>] warn_slowpath_null+0x15/0x20
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffffa04b855e>] ieee80211_rx+0x32e/0x8b0 [mac80211]
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffffa0532518>] ? wlc_dpc+0x178/0x7e0 [brcm80211]
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffffa04a0b51>] ieee80211_tasklet_handler+0xc1/0xd0 [mac80211]
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8105d2f2>] tasklet_action+0xa2/0x180
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8105dbf9>] __do_softirq+0xc9/0x250
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8102bfdc>] ? ack_apic_level+0x6c/0x1f0
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8100cddc>] call_softirq+0x1c/0x30
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8100f0b5>] do_softirq+0x65/0xa0
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8105de7d>] irq_exit+0x8d/0x90
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8100ecbc>] do_IRQ+0x6c/0xe0
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff813a7353>] ret_from_intr+0x0/0x11
Feb 19 18:27:29 SilverLeaf kernel: <EOI> [<ffffffff812426db>] ? intel_idle+0xdb/0x1b0
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff812426ba>] ? intel_idle+0xba/0x1b0
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff812d781c>] cpuidle_idle_call+0x8c/0x170
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8100a23a>] cpu_idle+0xaa/0x160
Feb 19 18:27:29 SilverLeaf kernel: [<ffffffff8139dad1>] start_secondary+0x20d/0x214
Feb 19 18:27:29 SilverLeaf kernel: ---[ end trace 9bb3b3e194073094 ]---
https://patchwork.kernel.org/patch/504981/
Looks like it was backported and landed in 2.6.37.1. Ben, could you try the kernel in testing and see if this fixes the problem?
I would like to find out what firmware other people are using along with 2.6.38 and if I am using the best version located here git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
Thanks!