Random Lock-ups...

rewind · 2011-02-26 00:07:08

After new installation with net-install got some random lock-ups with no other choice than reset. The first one was when I tried to issue and "sudo powerpill -Syu", the second and the third was in GUI, the last one smashed the fs of /home. They are completely random, two times after restart locks up before even get to GUI, with this:
http://i55.tinypic.com/25us31u.jpg
Tried to search some of these but with no result.
Now I'm running S.M.A.R.T. self-test in extended mode in Disk Utility, just to be sure there's no problem with it. I've already checked the RAM and I guess there is no problem with / because on the same HDD is an Ubuntu installation which have no such problems.
This is my third install of Arch from scratch and I followed closely the "Beginners guide". I'll appreciate any help on the subject, because I'm considering to start all over again with core installation /this is the first net-install I'm doing and I guess it might be that/.

-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

jasonwryan · 2011-02-26 00:14:11

Welcome to the boards.

Some information about your system would help others assist you: your graphics card, any errors in your logs, that sort of thing...

https://wiki.archlinux.org/index.php/Fo … ow_to_Post

rewind · 2011-02-26 16:24:30

Hello and thanks for the correction. Sorry that I didn't informed myself before posting here.
The machine is with the following hardware:
AMD Phenom II x2-550 CPU
DFI Lanparty DK 790GX-m2rs Motherboard
2x2GB DDR2-1066 Mhz
HD4870 512MB
and with 2.6.37-ARCH Kernel on Arch x86_64. Video driver is Catalyst 11.2 via catalyst-daemon.
There's two 1TB drives with various partitions, one of which is "/" and one 2TB drive as "/home".
It makes impression that the only partition that have errors after lockup is the /home partition, I tested it with no problems found so far.
In one of the forum treads that have similar log outputs found a suggestion that I would check /var/log/everything.log and there is something that makes sense. I guess for every "syslog-ng starting up; version..." there should be an "syslog-ng shutdown; version...", so I searched for line with the first one without the second one above it and this is what i found so far:

...
Feb 25 02:04:54 localhost kernel: usb 3-1.2: new low speed USB device using ohci_hcd and address 4
Feb 25 02:04:54 localhost kernel: input: Dell Dell USB Keyboard Hub as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1.1/3-1.1:1.1/input/input4
Feb 25 02:04:54 localhost kernel: generic-usb 0003:413C:2002.0002: input,hidraw1: USB HID v1.10 Device [Dell Dell USB Keyboard Hub] on usb-0000:00:12.0-1.1/input1
Feb 25 02:04:54 localhost kernel: usbcore: registered new interface driver usbhid
Feb 25 02:04:54 localhost kernel: usbhid: USB HID core driver
Feb 25 02:04:54 localhost kernel: input: Logitech Optical USB Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1.2/3-1.2:1.0/input/input5
Feb 25 02:04:54 localhost kernel: generic-usb 0003:046D:C016.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:12.0-1.2/input0
Feb 25 02:04:54 localhost kernel: scsi 6:0:0:0: Direct-Access     HTC      Android Phone    0100 PQ: 0 ANSI: 2
Feb 25 02:04:54 localhost kernel: sd 6:0:0:0: Attached scsi generic sg4 type 0
Feb 25 02:04:54 localhost kernel: sd 6:0:0:0: [sdd] Attached SCSI removable disk
Feb 25 02:04:54 localhost kernel: sky2 0000:02:00.0: eth0: enabling interface
Feb 25 02:04:56 localhost dhcpcd[3176]: eth0: carrier acquired
Feb 25 02:04:56 localhost kernel: sky2 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both
Feb 25 02:04:56 localhost dhcpcd[3176]: eth0: broadcasting for a lease
Feb 25 02:05:00 localhost dhcpcd[3176]: eth0: offered 192.168.1.100 from 192.168.1.1
Feb 25 02:05:00 localhost dhcpcd[3176]: eth0: acknowledged 192.168.1.100 from 192.168.1.1
Feb 25 02:05:00 localhost dhcpcd[3176]: eth0: checking for 192.168.1.100
Feb 25 02:05:04 localhost dhcpcd[3176]: eth0: leased 192.168.1.100 for 86880 seconds
Feb 25 02:05:04 localhost dhcpcd[3176]: forked to background, child pid 3211
Feb 25 02:05:04 localhost crond[3228]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel info
Feb 25 02:05:04 localhost crond[3228]: no timestamp found (user root job sys-hourly)
Feb 25 02:05:04 localhost crond[3228]: no timestamp found (user root job sys-daily)
Feb 25 02:05:04 localhost crond[3228]: no timestamp found (user root job sys-weekly)
Feb 25 02:05:04 localhost crond[3228]: no timestamp found (user root job sys-monthly)
Feb 25 02:08:01 localhost crond[3228]: FILE /var/spool/cron/root USER root PID 3240 job sys-hourly
Feb 25 02:23:12 localhost syslog-ng[3177]: syslog-ng starting up; version='3.2.2'
Feb 25 02:23:12 localhost kernel: Initializing cgroup subsys cpuset
Feb 25 02:23:12 localhost kernel: Initializing cgroup subsys cpu
Feb 25 02:23:12 localhost kernel: Linux version 2.6.37-ARCH (tobias@T-POWA-LX) (gcc version 4.5.2 20110127 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Feb 18 18:32:16 CET 2011
Feb 25 02:23:12 localhost kernel: Command line: BOOT_IMAGE=/boot/vmlinuz26 root=/dev/disk/by-uuid/fcc20a79-1b71-452a-b1c7-301cfda1b513 ro
Feb 25 02:23:12 localhost kernel: BIOS-provided physical RAM map:
Feb 25 02:23:12 localhost kernel: BIOS-e820: 0000000000000000 - 0000000000097800 (usable)
Feb 25 02:23:12 localhost kernel: BIOS-e820: 0000000000097800 - 00000000000a0000 (reserved)
...

The next one looks exactly the same, as the one above, but then there is another one:

...
usb-0000:00:12.0-1.1/input1
Feb 25 09:57:11 localhost kernel: usbcore: registered new interface driver usbhid
Feb 25 09:57:11 localhost kernel: usbhid: USB HID core driver
Feb 25 09:57:11 localhost kernel: scsi 6:0:0:0: Direct-Access     HTC      Android Phone    0100 PQ: 0 ANSI: 2
Feb 25 09:57:11 localhost kernel: sd 6:0:0:0: Attached scsi generic sg4 type 0
Feb 25 09:57:11 localhost kernel: sd 6:0:0:0: [sdd] Attached SCSI removable disk
Feb 25 09:57:11 localhost kernel: input: Logitech Optical USB Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1.2/3-1.2:1.0/input/input5
Feb 25 09:57:11 localhost kernel: generic-usb 0003:046D:C016.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:12.0-1.2/input0
Feb 25 09:57:11 localhost kernel: scsi 7:0:0:0: Direct-Access     RIM      Blackberry SD    0001 PQ: 0 ANSI: 4 CCS
Feb 25 09:57:11 localhost kernel: sd 7:0:0:0: Attached scsi generic sg5 type 0
Feb 25 09:57:11 localhost kernel: sd 7:0:0:0: [sde] Attached SCSI removable disk
Feb 25 09:57:11 localhost kernel: sky2 0000:02:00.0: eth0: enabling interface
Feb 25 09:57:11 localhost dhcpcd[3245]: version 5.2.10 starting
Feb 25 09:57:11 localhost dhcpcd[3245]: eth0: waiting for carrier
Feb 25 09:57:14 localhost dhcpcd[3245]: eth0: carrier acquired
Feb 25 09:57:14 localhost kernel: sky2 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both
Feb 25 09:57:14 localhost dhcpcd[3245]: eth0: rebinding lease of 192.168.1.100
Feb 25 09:57:14 localhost dhcpcd[3245]: eth0: acknowledged 192.168.1.100 from 192.168.1.1
Feb 25 09:57:14 localhost dhcpcd[3245]: eth0: checking for 192.168.1.100
Feb 25 09:57:19 localhost dhcpcd[3245]: eth0: leased 192.168.1.100 for 86880 seconds
Feb 25 09:57:19 localhost dhcpcd[3245]: forked to background, child pid 3273
Feb 25 09:57:19 localhost crond[3290]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel info
Feb 25 09:57:22 localhost polkitd[3390]: started daemon version 0.99 using authority implementation `local' version `0.99'
Feb 25 09:58:01 localhost crond[3290]: FILE /var/spool/cron/root USER root PID 3571 job sys-hourly
Feb 25 09:58:01 localhost crond[3290]: FILE /var/spool/cron/root USER root PID 3572 job sys-daily
Feb 25 10:02:58 localhost syslog-ng[3270]: syslog-ng starting up; version='3.2.2'
Feb 25 10:02:58 localhost kernel: Initializing cgroup subsys cpuset
Feb 25 10:02:58 localhost kernel: Initializing cgroup subsys cpu
Feb 25 10:02:58 localhost kernel: Linux version 2.6.37-ARCH (tobias@T-POWA-LX) (gcc version 4.5.2 20110127 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Feb 18 18:32:16 CET 2011
Feb 25 10:02:58 localhost kernel: Command line: BOOT_IMAGE=/boot/vmlinuz26 root=/dev/disk/by-uuid/fcc20a79-1b71-452a-b1c7-301cfda1b513 ro
Feb 25 10:02:58 localhost kernel: BIOS-provided physical RAM map:
Feb 25 10:02:58 localhost kernel: BIOS-e820: 0000000000000000 - 0000000000097800 (usable)
Feb 25 10:02:58 localhost kernel: BIOS-e820: 0000000000097800 - 00000000000a0000 (reserved)
...

I was charging a Blackberry and an Android phones on the USB and since I've disconnected them there wasn't any lockups so far. Is there something wrong in the logs above and what else I should check for in that case ?
Without that problem I'm very happy with my new installation, with the speedy interface and the perfectly complete documentation, the customization levels that can be accomplished and with what can be learned that way.
P.S. You will have to excuse me for my English, I'm not native speaker /typer actually /

jasonwryan · 2011-02-26 19:11:17

You could try plugging one of your phones back in and if it locks up check dmesg...

rewind · 2011-03-06 21:44:56

It's a bit odd. The machine was up more than 72 hours with overclocked processor and with BOINC running in the background with no issues. That was without the phones connected. Then I tried with the Blackberry plugged and there was no problem again. Tried with both phones too at the same USB ports, but nothing similar happened yet.

davidm · 2011-03-06 21:58:19

rewind wrote:

I was charging a Blackberry and an Android phones on the USB and since I've disconnected them there wasn't any lockups so far. I

Hmmm. There is the possibility that the current draw is related. I believe I have read that many implementations and official standards for USB aren't really intended to charge devices in this manner and can often cause strange problems.

It's a bit odd. The machine was up more than 72 hours with overclocked processor and with BOINC running in the background with no issues. That was without the phones connected. Then I tried with the Blackberry plugged and there was no problem again. Tried with both phones too at the same USB ports, but nothing similar happened yet.

Hmm. If you have yet to do so try the same test with both devices badly needing a charge (whether they are charging or not is perhaps significant as it relates to current draw). Then attempt to generate a moderately heavy load on the computer. If it occurs again suddenly perhaps look at the power supply first to see if it may be failing or inadequate. Or it could be something more esoteric having to do with the design of the USB system.

Last edited by davidm (2011-03-06 21:59:57)

Arch Linux

#1 2011-02-26 00:07:08

Random Lock-ups...

#2 2011-02-26 00:14:11

Re: Random Lock-ups...

#3 2011-02-26 16:24:30

Re: Random Lock-ups...

#4 2011-02-26 19:11:17

Re: Random Lock-ups...

#5 2011-03-06 21:44:56

Re: Random Lock-ups...

#6 2011-03-06 21:58:19

Re: Random Lock-ups...

Board footer