/srv/irclogs.ubuntu.com/2010/12/08/#ubuntu-us-mn.txt

jeremyAis anyone still running Lucid?  or has everyone updated to Maverick?02:23
tonyyarussoNope, still Lucid on everything here.02:26
jeremyAI've got a 64-bit install.02:27
jeremyAAMD Athlon X2 5400+ w/8GB RAM, lots of disk02:27
jeremyAran for two years on 8.04.x stably02:27
jeremyAI upgraded to 10.04 so I could try out KVM02:27
jeremyAand now the thing is hard hanging a couple of times per day02:27
tonyyarussoWeird.02:27
jeremyAI've got it loaded with noacpi as a kernel argument now02:27
jeremyAbut that doesn't seem to help02:28
jeremyAnothing gets logged in dmesg or /var/log/messages02:28
jeremyAand there is no apparent slowdown before it halts02:28
tonyyarussoTry running a command-line-only system for a few hours and see if anything happens.  (To distinguish between a graphics driver problem and something else)02:28
jeremyAit _is_ command line only02:28
jeremyAheadless setup, usually02:29
tonyyarussooh02:29
jeremyAI've got a cheapo 15" lcd plugged into it now, to read the text consoles.02:29
tonyyarussoWell now that ain't good.02:29
jeremyAwhen it dies, it deactivates the VGA too02:29
jeremyAand takes my cheapo usb-based KVM switch with it, too02:29
tonyyarussoAnything in /var/crash/02:29
tonyyarusso?02:29
jeremyAooh, I'll check02:29
jeremyAnope, dead empty02:29
tonyyarussocrud02:29
jeremyA/var/log/kern* hasn't a thing either02:29
tonyyarusso/var/log/debug?02:30
tonyyarusso/var/log/faillog?02:30
jeremyAdebug drops off after xinetd started after the last crash and starts up again with a kernel entry...02:31
jeremyADec  7 16:38:11 localhost xinetd[2567]: removing time02:31
jeremyADec  7 19:48:13 localhost kernel: [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)02:31
jeremyADec  7 19:48:13 localhost kernel: [    0.000000] MTRR default type: uncachable02:31
jeremyAnope, only two failed logins listed in /var/log/faillog -- root on 06/20/10, and me on 06/25/0902:31
jeremyAthis thing is knocking the tar out of me02:32
tonyyarussoAny chance it's actually a hardware problem that coincidentally is happening after the OS upgrade?02:32
jeremyAconceivable.02:32
jeremyAcpuburn didn't turn up any heating problems02:32
jeremyAdang this is my external gateway.02:32
jeremyAwhen I go to bed tonight, I'll bring it down and fire up memtest86+02:33
jeremyAI'm worried that it could be a SATA controller going, or mobo failing.02:34
jeremyAafter burning 3 days on this, I'm thinking I'm getting to the point where I could throw a new machine at the problem.02:34
tonyyarussoDoes your hard drive support SMART?02:35
jeremyAyeah, they're all working AOK02:35
jeremyAthough I don't trust SMART too far.02:35
tonyyarusso'k02:35
jeremyAit's kind of dumb when it comes to predicting errors02:36
jeremyAall six satas say they're aok.02:36
jeremyAbut...it does make me wonder about power...02:37
jeremyAI wonder if my PS is acting up.02:37
tonyyarussoYou could always read through all of the posts on this thread:  http://ubuntuforums.org/showthread.php?t=147878702:37
tonyyarusso;)02:38
tonyyarusso(Although waiting for the next LTS might be faster.)02:38
jeremyAI went through the first 25 pages of that, then skipped ahead to the end02:39
jeremyAwhere people say "huh.  no solution found."02:39
jeremyAmainly because I think there are a lot of different root causes02:39
tonyyarussohttps://help.ubuntu.com/community/FaultyHardware might be useful, although it sounds like you already knew these.02:41
jeremyA500watt powersupply for six sata drives...I wonder if I'm pushing my luck here02:44
tonyyarussoCare to list off what else you have in there?  (PCI cards, fans, etc.)02:47
jeremyAIntel PCI-express NIC02:47
jeremyAthat's it02:47
tonyyarussoNot a single fan eh?  That could be your problem too :P02:47
jeremyAa dvd burner that's not even plugged in, because I'm out of sata cables02:47
jeremyAhahaha02:48
jeremyA=)02:48
jeremyAgot me.02:48
jeremyAokay, fan on the back02:48
jeremyAnice big quiet fan on the CPU02:48
jeremyAI'd have to look to see if there are others02:48
jeremyAI'm seeing posts on forums, telling me that other people consider 6 drives on a single 500w P/S to be pushing the envelope02:49
tonyyarussojeremyA: what socket is that Athlon?02:52
jeremyAAM2+ I think02:55
jeremyAam202:55
jeremyAsitting in a biostar a740G M2+ motherboard02:55
jeremyAwith 8gb of ddr2 ram02:55
jeremyA65watt Athlon 64X2 5400 brisbane dual-core02:56
tonyyarussowell this calculator doohickey just recommended 312W, so that doesn't seem bad yet.02:57
jeremyAwait'll we add in the drives...02:57
tonyyarussothat's with the drives, assuming 7200rpm02:57
jeremyAoh, okay.02:57
jeremyAhrm.02:57
jeremyAshould be fine then02:57
jeremyAunless the P/S is failing02:57
jeremyAbut it's usually not dying at periods of particularly heavy load02:57
jeremyAand I'm almost never over 4gb RAM usage02:58
jeremyAMem:       8128336    4232644    3895692          0      41628    213518402:58
jeremyAtwo of these drives are ancient 160gb 7200rpm barracudas...but I don't think they'd be taking 100w of power each or anything03:00
jeremyAwhere'd you find the calculator, anyway?  :)03:01
tonyyarussogoogle "PSU calculator", first result03:02
jeremyAthx03:03
jeremyAnewegg has one, too:  http://educations.newegg.com/tool/psucalc/index.html03:07
jeremyAthey're suggesting a 408w P/S for me.03:07
jeremyAtonyyarusso:  are all your machines Intel hardware?03:22
tonyyarussojeremyA: Nope.  I'm typing on an AMD Phenom II X4 905e machine currently.03:22
jeremyAokay, good to know03:23
jeremyAI've been reading through that thread, and noticed a guy saying "lucid only freezes on my AMD hardware"03:23
tonyyarussoThe rest are, unless you count the ARM gadget.03:23
jeremyAinterestingly, I noted that the BIOS had the ACPI set to to v1.  I set it to v2 when it was down last, and deactivated the onboard sound03:25
tonyyarussoI have a board here that's on v2 now, but has an option for v3.03:27
jeremyAyeah, I have to take the gateway down to refsck a disk once my wife is done checking email03:27
jeremyAbut since I'm booted with noacpi, I don't think the acpi version that BIOS is using should matter03:27
jeremyAbbiab03:28
jeremyAso...how the heck do I enabled the --mark-- in rsyslog?03:54
jeremyAI put these lines in /etc/rsyslog.conf03:55
jeremyA$ModLoad immark  # provides --MARK-- message capability03:55
jeremyA$MarkMessagePeriod 6003:55
jeremyAbut nowhere in any logfile do I find my MARKs03:55
jeremyAwhoops, my bad03:55
jeremyAthere they are in kern.log03:55
jeremyAnot in messages where I expected them03:55
* jeremyA <-- dummie03:55
jeremyAhey, tonyyarusso, you around?18:57
tonyyarussojeremyA: kinda - at work, but yes.19:18
jeremyAdo any of your amd machines use tsc as a clocksource?19:21
jeremyAafter upgrading to the 2.6.34 kernel, I got a note about my tsc clocksource being unstable.19:21
jeremyAso I've set it to use clocksource=hpet on the next book19:21
tonyyarussoum, I have no idea.  I've never touched anything like that.19:24
* tonyyarusso uses default kernels and such19:24

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!