Arch Linux

SpiderX

Member

Registered: 2011-07-13

Posts: 3

Arch locked up

Hi,

Im faily new to arch.
Im running this on a Acer Revo 3700.

iv been having issues with arch locking up from a cold boot. it will boot up and i can log in, load up firefox, start browsing and then its locks up, and i have to restart by hold down the power button for 5 seconds then power it back on, after it the second boot, its works fine.

iv ran a full memtest and that was ok.

Here is my kernel.log that shows the crash

Jul 13 19:54:16 localhost kernel: [  103.655004] BUG: unable to handle kernel paging request at 7486ea98
Jul 13 19:54:16 localhost kernel: [  103.655017] IP: [<f9e90b9b>] _nv024187rm+0x612/0x754 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.655441] *pde = 00000000 
Jul 13 19:54:16 localhost kernel: [  103.655447] Oops: 0000 [#1] PREEMPT SMP 
Jul 13 19:54:16 localhost kernel: [  103.655454] last sysfs file: /sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0/enable
Jul 13 19:54:16 localhost kernel: [  103.655462] Modules linked in: ipv6 fuse ext2 nvidia(P) snd_hda_codec_hdmi rt2860sta(C) snd_hda_codec_realtek arc4 ecb snd_hda_intel rt2800pci rt2800lib snd_hda_codec crc_ccitt snd_hwdep joydev rt2x00pci r8169 intel_agp snd_pcm evdev sg mii snd_timer intel_gtt rt2x00lib i2c_i801 mac80211 iTCO_wdt snd cfg80211 rfkill soundcore i2c_core snd_page_alloc processor eeprom_93cx6 serio_raw iTCO_vendor_support pcspkr agpgart psmouse thermal wmi button ext4 mbcache jbd2 crc16 usbhid hid sd_mod pata_acpi uhci_hcd ata_piix ehci_hcd libata usbcore scsi_mod
Jul 13 19:54:16 localhost kernel: [  103.655548] 
Jul 13 19:54:16 localhost kernel: [  103.655555] Pid: 831, comm: X Tainted: P         C  2.6.39-ARCH #1 Acer Aspire R3700/TDPS05 R3700
Jul 13 19:54:16 localhost kernel: [  103.655565] EIP: 0060:[<f9e90b9b>] EFLAGS: 00013202 CPU: 3
Jul 13 19:54:16 localhost kernel: [  103.655985] EIP is at _nv024187rm+0x612/0x754 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.655992] EAX: f4b8dadc EBX: f4d7fc00 ECX: 00000840 EDX: f486e000
Jul 13 19:54:16 localhost kernel: [  103.655997] ESI: f486e000 EDI: f4fcc400 EBP: f4b8dac4 ESP: f44ed968
Jul 13 19:54:16 localhost kernel: [  103.656003]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jul 13 19:54:16 localhost kernel: [  103.656010] Process X (pid: 831, ti=f44ec000 task=f4d05780 task.ti=f44ec000)
Jul 13 19:54:16 localhost kernel: [  103.656014] Stack:
Jul 13 19:54:16 localhost kernel: [  103.656017]  f486e000 035e0840 00123017 f4b8dadc f486a000 f486b000 f4fcc400 f9e22067
Jul 13 19:54:16 localhost kernel: [  103.656033]  f486a000 f4d7fc00 00000006 f486b000 f486b000 00000000 f9e1fa9d f486a000
Jul 13 19:54:16 localhost kernel: [  103.656047]  f486b000 f486b000 00000010 00000000 f9e38e6e f486a000 f486b000 00000000
Jul 13 19:54:16 localhost kernel: [  103.656061] Call Trace:
Jul 13 19:54:16 localhost kernel: [  103.656492]  [<f9e22067>] ? _nv003399rm+0x48c/0x53d [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e1fa9d>] ? _nv020243rm+0x5a/0x103 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e38e6e>] ? _nv020367rm+0x1b1/0x2dd [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e1ff9f>] ? _nv020247rm+0x33a/0x498 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e38ead>] ? _nv020367rm+0x1f0/0x2dd [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e1d7ae>] ? _nv020421rm+0xee/0x1c2 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9eb3be4>] ? _nv024791rm+0xd4/0x207 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9eb6fd9>] ? _nv003636rm+0x119/0x127 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9eb834e>] ? _nv003653rm+0x136/0x17d [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9eb3024>] ? _nv024991rm+0x190/0x19e [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9eb7614>] ? _nv024987rm+0xf/0x13 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e27e2e>] ? _nv020428rm+0x448/0x841 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e1e34a>] ? _nv020118rm+0x124/0x1e6 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9e892bf>] ? _nv024290rm+0x1be/0x2e0 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9d78a29>] ? _nv015074rm+0x55/0x8e [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9d72077>] ? _nv015270rm+0x138/0x212 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9d1d3ba>] ? _nv013033rm+0x50f/0x852 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9d2aaf1>] ? _nv013030rm+0x45/0x155 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9d41e44>] ? _nv013028rm+0x197/0x4ef [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f8440>] ? _nv003778rm+0x86b/0x938 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f6702>] ? _nv003776rm+0xb9/0xe1 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f674c>] ? _nv025722rm+0xf/0x13 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f6baa>] ? _nv003788rm+0x129/0x674 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f6702>] ? _nv003776rm+0xb9/0xe1 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f674c>] ? _nv025722rm+0xf/0x13 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f6915>] ? _nv003782rm+0x15f/0x2cb [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f6702>] ? _nv003776rm+0xb9/0xe1 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f99f6739>] ? _nv025724rm+0xf/0x13 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9f78a8e>] ? _nv002396rm+0xb9/0xf1 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9f7b49b>] ? rm_free_unused_clients+0x7c/0x183 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c106951a>] ? up+0x2a/0x40
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9f9a1b6>] ? nv_kern_ctl_close+0x66/0x100 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<f9f9b0d1>] ? nv_kern_close+0x361/0x480 [nvidia]
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c110432a>] ? kfree+0x12a/0x150
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c125f43d>] ? vga_arb_release+0xbd/0xd0
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c111602a>] ? fput+0xaa/0x1e0
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c1112c74>] ? filp_close+0x54/0x80
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c104948b>] ? put_files_struct+0x7b/0xd0
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c1049585>] ? exit_files+0x45/0x60
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c10499d1>] ? do_exit+0x151/0x790
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c104a2a8>] ? do_group_exit+0x38/0xa0
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c10589ae>] ? get_signal_to_deliver+0x2be/0x480
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c10029fd>] ? do_signal+0x6d/0x840
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c13425f3>] ? __bad_area_nosemaphore+0x119/0x128
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c10289f0>] ? vmalloc_sync_all+0x120/0x120
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c1028d99>] ? do_page_fault+0x3a9/0x420
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c11149cf>] ? vfs_write+0x11f/0x160
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c1114120>] ? wait_on_retry_sync_kiocb+0x50/0x50
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c10289f0>] ? vmalloc_sync_all+0x120/0x120
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c10034c5>] ? do_notify_resume+0x65/0x80
Jul 13 19:54:16 localhost kernel: [  103.656675]  [<c134aa64>] ? work_notifysig+0x13/0x1b
Jul 13 19:54:16 localhost kernel: [  103.656675] Code: 48 17 11 fa e8 ec 13 0e 00 83 c4 04 e8 f8 13 0e 00 85 c0 74 05 e8 d6 fe 01 00 8d 45 18 50 ff b3 89 01 00 00 ff b3 84 01 00 00 56 <ff> 96 98 0a 00 80 83 c4 10 6a 00 68 e8 83 00 00 ff 75 1c ff 75 
Jul 13 19:54:16 localhost kernel: [  103.656675] EIP: [<f9e90b9b>] _nv024187rm+0x612/0x754 [nvidia] SS:ESP 0068:f44ed968
Jul 13 19:54:16 localhost kernel: [  103.656675] CR2: 000000007486ea98
Jul 13 19:54:16 localhost kernel: [  103.669504] ---[ end trace 1790123513af4ae9 ]---
Jul 13 19:54:16 localhost kernel: [  103.669514] Fixing recursive fault but reboot is needed!
Jul 13 19:54:26 localhost kernel: [  114.030773] hald[736]: segfault at 2000000e ip b76c2f57 sp bfc227e0 error 4 in libgobject-2.0.so.0.2800.8[b7691000+4c000]
Jul 13 19:54:26 localhost kernel: [  114.032297] polkitd[921]: segfault at 55471110 ip b7761b83 sp b69fef90 error 6 in libgio-2.0.so.0.2800.8[b7715000+128000]
Jul 13 19:54:26 localhost kernel: [  114.032545] upowerd[1013] general protection ip:b7685f62 sp:bfee094c error:7480 in libdbus-glib-1.so.2.2.0[b767e000+24000]
Jul 13 19:54:26 localhost kernel: [  114.032749] console-kit-dae[852]: segfault at 4489fffe ip b77d4caf sp bfa4a591 error 4 in libgthread-2.0.so.0.2800.8[b77d3000+4000]
Jul 13 19:54:26 localhost kernel: [  114.036978] dbus-daemon[712] general protection ip:805db88 sp:bf941590 error:1674 in dbus-daemon[8048000+65000]
Jul 13 19:54:26 localhost kernel: [  114.227700] xfce4-power-man[999]: segfault at 4067a628 ip b7112b8a sp bf85d0a0 error 6 in libgobject-2.0.so.0.2800.8[b70eb000+4c000]
Jul 13 19:54:26 localhost kernel: [  114.227772] dbus-daemon[953]: segfault at 84 ip 08078a62 sp bf9f8030 error 4 in dbus-daemon[8048000+65000]
Jul 13 19:54:26 localhost kernel: [  114.386658] fusermount[1169]: segfault at b8057668 ip b7841713 sp bfa03700 error 4 in ld-2.14.so[b7837000+1f000]
Jul 13 19:54:26 localhost kernel: [  114.387353] xfce4-notifyd[1002]: segfault at 8a ip b7084666 sp bfa6f6cc error 4 in libdbus-1.so.3.5.7[b7071000+47000]
Jul 13 19:54:26 localhost kernel: [  114.388485] sh[944] general protection ip:8091b90 sp:bfd1f5f0 error:8908 in bash[8048000+a8000]
Jul 13 19:55:26 localhost kernel: [  173.874403] show_signal_msg: 2 callbacks suppressed
Jul 13 19:55:26 localhost kernel: [  173.874415] hald-addon-acpi[780]: segfault at 80 ip b772d76f sp bfadcd98 error 4 in ld-2.14.so[b771e000+1f000]

Last edited by SpiderX (2011-07-14 11:06:03)

litemotiv

Forum Fellow

Registered: 2008-08-01

Posts: 5,026

Re: Arch locked up

SpiderX, please use code tags when pasting code and/or logs.

---

ᶘ ᵒᴥᵒᶅ

dodo3773

Member

Registered: 2011-03-17

Posts: 818

Re: Arch locked up

Please use code brackets when posting really long stuff like this. I am not that great at reading log files but what I do see is a bunch of seg faults like dbus and console-kit-daemon. Based on the log am I right by assuming that you are running xfce? If so how are you launching it? Are you using "ck-launch-session"? Are you sure that you are up to date all the way?

Last edited by dodo3773 (2011-07-13 22:13:59)

rowdog

Member

From: East Texas

Registered: 2009-08-19

Posts: 118

Re: Arch locked up

When you analyze logs and you find a crash, you really want to begin with the first crash since it can take down a lot of other stuff.

I believe that your NVIDIA binary blob driver crashed the X process which then took down all the other stuff. The crash you describe sounds like X dying. If you have a LAN you should be able to ssh in from another machine and issue a proper reboot command.

In any case, the most likely cause is your video driver. We had a recent kernel upgrade; did you rebuild the binary blob? If so, you might want to try an older or newer version of the driver.

SpiderX

Member

Registered: 2011-07-13

Posts: 3

Re: Arch locked up

litemotiv - sorry, now in code tags

dodo3773 - yes im using xfce, im using slim and using exec ck-launch-session startxfce4, also im up to date.

rowdog - how would i rebuild the binary blob?

rowdog

Member

From: East Texas

Registered: 2009-08-19

Posts: 118

Re: Arch locked up

rowdog - how would i rebuild the binary blob?

Sorry, I may have given you a bum steer there. ATI requires a recompile on kernel upgrade and I can't remember if that's true for NVIDIA; I dumped them  a couple years ago.

Leonid.I

Member

From: Aethyr

Registered: 2009-03-22

Posts: 999

Re: Arch locked up

iv been having issues with arch locking up from a cold boot. it will boot up and i can log in, load up firefox, start browsing and then its locks up, and i have to restart by hold down the power button for 5 seconds then power it back on, after it the second boot, its works fine.

So after the powercycle the system is stable? Then it's a hw issue with a high probability.

---

Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd

SpiderX

Member

Registered: 2011-07-13

Posts: 3

Re: Arch locked up

Well, iv been playing around with other kernels and drivers, im now using kernel26-ck-atom, and the last 2 boots have been fine, so we shall see...