Re: Computer instability under Debian Stable
Adrian Levi, 5.07.2011:
> On 3 July 2011 17:43, Adrian Levi <adrian.levi@gmail.com> wrote:
> > My home server has been experiencing instability issues running Debian stable.
>
> Ha, I turned off kdm and left the computer sitting in vt1. I got the following:
> (Hand typed excuse any typo's)
>
> gemini login: [24573.123365] general protection fault: 0000 [#1] smp
> [24573.124005] last sysfs file:
> /sys/devices/pci0000:00/0000:00:11.0/host2/target2:0:0/2:0:0:0/block/sdb/uevent
> [24573.124005] Modules linked in: powernow_k8 cpufreq_userspace
> cpufreq_conservative cpufreq_stats cpufreq_powersave parport_pc ppdev
> lp parport sco bridge stp bnep rfcomm l2cap bluetooth rfkill
> binfmt_misc fuse ext2 loop firewire_sbp2 firewire_core crc_itu_t
> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm
> radeon snd_seq snd_timer snd_sec_device ttm snd edac_core soundcore
> snd_page_alloc drm_kms_helper drm edac_mce_amd i2c_piix4 i2c_algo_bit
> i2c_core k10temp evdev shpchp joydev pci_hotplug asus_atk0110 button
> pcspkr processor ext4 mbcache jbd2 crc16 raid456 md_mod
> async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy
> async_tx hid_microsoft sg sr_mod cdrom sd_mod crc_t10dif usbhid hid
> usb_storage ohci_hcd ahci sata_sil e1000 libata xhci scsi_mod ehci_hcd
> thermal thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan]
> [24573.124005] Pid: 4922, comm: setiathome-5.28 Not tainted
> 2.6.32-5-amd64 #1 System Product Name
> [24573.124005] RIP: 0010:[<ffffffff811927c5>] [<ffffffff811927c5>]
> rb_next+0x1a/0x46
> [24573.124005] RSP: 0000:ffff88041bc95e38 EFLAGS: 00010006
> [24573.124005] RAX: 2024748b4c18246c RBX: ffff8803ead1cdf8 RCX: 00000000148ced55
> [24573.124005] RDX: 2024748b4c18246c RSI: ffff8803ead1cde8 RDI: 0000000000000000
> [24573.124005] RBP: ffff8803ead1cde8 R08: ffff88041bbf0048 R09: 0000000001000000
> [24573.124005] R10: 0000000000000000 R11: 0000000000000001 R12: ffff88000f8157e8
> [24573.124005] R13: ffff88000f815780 R14: 00007fbfd758d010 R15: 00007fbfd7d8e010
> [24573.124005] FS: 00000000422ff940(0063) GS: ffff88000f800000(0000)
> knlGS: 0000000000000000
> [24573.124005] CS: 0010 DS: 0000 ES: 0000 CRO: 0000000080050033
> [24573.124005] CR2: 00007fbfd6a4b000 CR3: 00000003ffd33000 CR4: 00000000000006f0
> [24573.124005] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [24573.124005] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [24573.124005] Process setiathome-5.28 (pid 4922, threadinfo
> ffff88041bc94000, task ffff8803ead1aa60)
> [24573.124005] Stack:
> [24573.124005] ffffffff81040440 ffff88000f8157e8 ffff8803ead1cde8
> ffff8803ead1cde8
> [24573.124005] <0> ffffffff81041ab7 ffff8803ead1aa98 ffff88000f815780
> ffff88000f815780
> [24573.124005] <0> 0000000000100000 0000000000006415 ffffffff8103a9b0
> 0000000000100000
> [24573.124005] Call Trace:
> [24573.124005] [<ffffffff81040440>] ? set_next_entity+0x22/0x56
> [24573.124005] [<ffffffff81041ab7>] ? pick_next_task_fair+0xa3/0xd6
> [24573.124005] [<ffffffff812faf25>] ? schedule+0x5d2/0x7b4
> [24573.124005] [<ffffffff81011576>] ? retint_careful+0x14/0x32
> [24573.124005] Code: 74 0e 48 8b 50 08 48 85 d2 74 05 48 89 d0 eb f2
> c3 48 8b 07 48 89 fa 31 ff 48 83 e0 fc 48 39 c2 74 31 48 8b 42 08 48
> 85 c0 74 16 <48> 8b 50 10 48 85 d2 74 05 48 89 d0 eb f2 48 89 c7 eb 15
> 48 89
> [24573.124005] RIP: [<ffffffff811927c5>] rb_next+0x1a/0x46
> [24573.124005] RSP: <ffff88041bc95e38>
> [24573.124005] ---[ end trace b22872e9ad7860a0 ]---
>
> I have seen one of these before many years ago :-) that one was due to
> a memory stick problem but I've tested the memory in this machine a
> dozen times for days at end, what to do next?
Just a thought: have you tried disabling setiathome? (And also, did
you have the same setiathome version running on the Ubuntu that didn't
freeze?)
Reply to: