My home server has been experiencing instability issues running Debian stable.
My issue is I have no sound output and overnight the computer will
hard lock-up so that the num-lock light won't even toggle.
I updated to 2.6.38 thinking it might be a kernel compatibility issue
but the problem remains.
I downloaded and booted from an Ubuntu 11.04 CD and the system has
been running stable over the last 5 something days.
Ram has passed countless passes on Memtest86+, The CPU i'd have
figured would have failed running any OS.
Likewise the system is stable running Win 7 64bit.
I have attached an lspci -vv and lsmod.
I have a feeling that my issue might be Debians firmware stripped
kernel but don't know where else to look for problems, dmesg dosen't
seem to provide any hints.
Basic rundown of the system is:
AMD 235 40w CPU
Asus M4A88TD-V EVO/USB3 Motherboard.
16G DDR3 1333 Ram (Kingston)
6 HDD comprising:
750G for OS,
5x 2TB in software raid 6,
Satasil card in JBOD mode for extra SATA ports.
I have attached files from Ubuntu 11.04 Live CD where everything works.
I would appreciate pointers as to where to continue my search for the problem.
Adrian
--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
Subsystem: ASUSTeK Computer Inc. Device 843e
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [c4] HyperTransport: Slave or Primary Interface
Command: BaseUnitID=0 UnitCnt=12 MastHost- DefDir- DUL-
Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 1: MLWI=8bit DwFcIn- MLWO=8bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
Revision ID: 3.00
Link Frequency 0: [b]
Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability 0: 200MHz+ 300MHz- 400MHz+ 500MHz- 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
Feature Capability: IsocFC- LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
Link Frequency 1: 200MHz
Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
Link Frequency Capability 1: 200MHz- 300MHz- 400MHz- 500MHz- 600MHz- 800MHz- 1.0GHz- 1.2GHz- 1.4GHz- 1.6GHz- Vend-
Error Handling: PFlE- OFlE- PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE+ PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
Prefetchable memory behind bridge Upper: 00-00
Bus Number: 00
Capabilities: [54] HyperTransport: UnitID Clumping
Capabilities: [40] HyperTransport: Retry Mode
Capabilities: [9c] HyperTransport: #1a
Capabilities: [f8] HyperTransport: #1c
My home server has been experiencing instability issues running Debian stable.
My issue is I have no sound output and overnight the computer will
hard lock-up so that the num-lock light won't even toggle.
I updated to 2.6.38 thinking it might be a kernel compatibility issue
but the problem remains.
I downloaded and booted from an Ubuntu 11.04 CD and the system has
been running stable over the last 5 something days.
Ram has passed countless passes on Memtest86+, The CPU i'd have
figured would have failed running any OS.
Likewise the system is stable running Win 7 64bit.
I have attached an lspci -vv and lsmod.
I have a feeling that my issue might be Debians firmware stripped
kernel but don't know where else to look for problems, dmesg dosen't
seem to provide any hints.
So, before upgrading the kernel to 2.6.38, where you using the standard stable Debian
kernel (2.6.32)? If not (but seems yes), maybe downgrading the kernel back to the stable
one is a good thing to test.
Maybe this is still a hardware issue (typically bad electrical contacts) you have
temporarly disabled because of physical manipulations on the machine. So, I encourage you
to retry Debian and see how long the uptime can be. Of course this test may require
several days...
Another thing, have you see any kernel oops (Call Trace, etc.) in the logs?
Did you try to unload kernel modules you might have installed recently?
Nicolas
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> My home server has been experiencing instability issues running Debian stable.
>
> My issue is I have no sound output and overnight the computer will
> hard lock-up so that the num-lock light won't even toggle. I updated
> to 2.6.38 thinking it might be a kernel compatibility issue but the
> problem remains. I downloaded and booted from an Ubuntu 11.04 CD and
> the system has been running stable over the last 5 something days.
You need to figure out what happens to trigger the freezing. Are there
any entries in syslog that might indicate something? There's cron
scripts running over night ... Perhaps the easiest way to approach this
is setting the system clock 12 hours or so ahead and see if the freeze
occurs at a different time. If it does, you can try to track down what
scripts are running over night and find out which one causes the
freeze.
Or you could try to stop the cron daemon and see if it still freezes.
Take a look at /Documentation/sysrq.txt in the kernel source
tree. Perhaps you can get at least some info when the computer is frozen
with that.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87boxbli3m.fsf@yun.yagibdah.de">http://lists.debian.org/87boxbli3m.fsf@yun.yagibdah.de
07-03-2011, 01:10 PM
Adrian Levi
Computer instability under Debian Stable
On 3 July 2011 18:56, Nicolas Bercher <nbercher@yahoo.fr> wrote:
Hi Nicolas,
> So, before upgrading the kernel to 2.6.38, where you using the standard
> stable Debian kernel (2.6.32)? *If not (but seems yes), maybe downgrading
> the kernel back to the stable one is a good thing to test.
The problem was also in 2.6.32 ans was the reason I tried 2.6.38.
> Maybe this is still a hardware issue (typically bad electrical contacts) you
> have temporarly disabled because of physical manipulations on the machine.
> *So, I encourage you to retry Debian and see how long the uptime can be. *Of
> course this test may require several days...
The chassis is fine, Running an Ubuntu Live CD and Win7Pro 64bit works
flawlessly.
If I reboot out of Ubuntu it will fail overnight, sometimes less than 2 hours.
> Another thing, have you see any kernel oops (Call Trace, etc.) in the logs?
> Did you try to unload kernel modules you might have installed recently?
I don't see anything on the screen, Can't wake up the screen (it goes
blank) no oops, no nothing. Dosen't even respond to a num-lock,
caps-lock button press.
Adrian
--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CABAdhH4-AaWUk_NUXbCnO7v-f5WwtvwCHabiDDGm2SLNAM3RwA@mail.gmail.com">http://lists.debian.org/CABAdhH4-AaWUk_NUXbCnO7v-f5WwtvwCHabiDDGm2SLNAM3RwA@mail.gmail.com
07-03-2011, 01:12 PM
Adrian Levi
Computer instability under Debian Stable
On 3 July 2011 21:27, lee <lee@yun.yagibdah.de> wrote:
> You need to figure out what happens to trigger the freezing. *Are there
> any entries in syslog that might indicate something? *There's cron
> scripts running over night ... Perhaps the easiest way to approach this
> is setting the system clock 12 hours or so ahead and see if the freeze
> occurs at a different time. *If it does, you can try to track down what
> scripts are running over night and find out which one causes the
> freeze.
>
> Or you could try to stop the cron daemon and see if it still freezes.
>
> Take a look at /Documentation/sysrq.txt in the kernel source
> tree. Perhaps you can get at least some info when the computer is frozen
> with that.
I'll have to try sysrq key combinations.
Adrian
--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CABAdhH4F7aknpS5h9EH+o9hf9EoufpQ9-E7mDmiMBrd=X2RfxA@mail.gmail.com">http://lists.debian.org/CABAdhH4F7aknpS5h9EH+o9hf9EoufpQ9-E7mDmiMBrd=X2RfxA@mail.gmail.com
07-03-2011, 02:04 PM
green
Computer instability under Debian Stable
Adrian Levi wrote at 2011-07-03 01:43 -0600:
> My issue is I have no sound output and overnight the computer will
> hard lock-up so that the num-lock light won't even toggle.
If you are not getting any sound anyway, have you tried removing all the snd
modules?
07-03-2011, 02:12 PM
Nicolas Bercher
Computer instability under Debian Stable
On 03/07/2011 15:10, Adrian Levi wrote:
I don't see anything on the screen, Can't wake up the screen (it goes
blank) no oops, no nothing. Dosen't even respond to a num-lock,
caps-lock button press.
Adrian
OK, so you may want to use a live cd to inspect the Debian logs...?
Nicolas
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
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?
Regards,
Adrian
--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CABAdhH6NUYT3h4JtGOGViBoTsnQC_DawkXoG7jN-0yiSiu25og@mail.gmail.com">http://lists.debian.org/CABAdhH6NUYT3h4JtGOGViBoTsnQC_DawkXoG7jN-0yiSiu25og@mail.gmail.com
07-05-2011, 11:08 AM
"Selim T. Erdogan"
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?)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110705110835.GA3957@cs.utexas.edu">http://lists.debian.org/20110705110835.GA3957@cs.utexas.edu
07-05-2011, 12:11 PM
Adrian Levi
Computer instability under Debian Stable
On 5 July 2011 21:08, Selim T. Erdogan <selim@alumni.cs.utexas.edu> wrote:
> 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?)
Seti is a recent addition to that machine. It was locking up before I
installed it.
Adrian
--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CABAdhH5YjThepUqzD7UCtFOtNgXTuQCNLFkV6qQ82V8mh1V=s A@mail.gmail.com">http://lists.debian.org/CABAdhH5YjThepUqzD7UCtFOtNgXTuQCNLFkV6qQ82V8mh1V=s A@mail.gmail.com